CLI operations
On this page
The customer-facing CLI workflows documented here support client login, diagnostics, version reporting, and an Eresus-approved server process. Customer assessments start in Workbench. This is not a CLI scan guide.
If your organization does not have a provisioned workspace, request access by emailing contact@eresussec.com. There is no public self-signup.
#Supported customer workflows
| Command | Use | Limit |
|---|---|---|
eresus-guard login | Run it, then enter the provisioned username/email and access code when prompted to authenticate the local client. | Does not create a workspace or replace Workbench SSO. |
eresus-guard doctor | Print readiness diagnostics for the installed client environment when support asks for them. | A diagnostic report is not proof that an assessment ran or that a target is authorized. |
eresus-guard version | Print version and available build details for support. | Share the output only through the support channel Eresus provides. |
eresus-guard server | Start a server process for an Eresus-approved operator or MSSP deployment. | Use only with deployment instructions supplied for that environment; it is not a local scan launcher. |
#Start and review assessments
Use Workbench to select the project, confirm the target and authorization, set up the assessment, start it, and review the saved findings and evidence. Saving setup does not start a run. Do not use a CLI scan command as the customer onboarding path.
For account access, see Login, SSO, and reconnect. For scan setup, see Projects and scans. For support diagnostics, see Configuration and support.
Need a workflow that is not documented here? Email contact@eresussec.com.