How to use Eresus Guard

You operate Eresus Guard in Workbench. Sign in at https://workbench.eresussec.com.

This site is documentation and access requests. It does not start scans. Professional, Business, and Enterprise do not onboarding-scan from the CLI.

Workbench dashboard for the current project

Daily path

Open Workbench and sign in. Password login is on every plan. SSO is Enterprise, under Admin → Authentication.
Select the Project that owns the target. Create one if the workspace is empty. Everything you run today should land in that project.
Confirm authorization: hosts, identities, and exclusions belong to the project. A host that appears during a scan does not join scope until you add it.
Start the right Assess flow:
- New Scan for an authorized web or API target
- SAST Scan for a repository or source archive
- Ingest when you already have URLs, cURL, OpenAPI, Postman, or captured HTTP
Stay on Dashboard or Active Scan while the run is live. Pause or stop from Workbench if the target becomes unstable. Reconnect restores the same screen.
Open Findings. For each row you intend to act on, open the finding, then the linked HTTP Record or OAST callback. Then export, assign, or retest.

Findings triage with attached HTTP and OAST evidence

What belongs in the same project

Authorized DAST, API assessments, authenticated testing with dedicated test identities, SAST, SCA, IaC, secrets, and bounded agent follow-up. Agent work uses the same authorization gate and writes into the same evidence trail. It does not replace native modules.

What does not belong in an assessment

Production user sessions. Hosts outside the project authorization gate. Treating an OAST callback or a SAST candidate as a confirmed exploit before review.

If you need the first-run checklist, continue with First authorized assessment. For the map of every area, see Workbench.

Need a workflow that is not documented here? Email contact@eresussec.com.