How to use Eresus Guard
On this page
Use Workbench at the route provisioned for your organization. The normal path is to select the project, confirm the authorized target or repository, set up the right assessment, and review its saved results.
#Daily workflow
- Open Workbench and sign in with your organization's configured method.
- In Project spaces, select or create the project that owns the target or source repository.
- Open Target authorization and confirm that the target is covered by the project's current authorization and included scope. A host discovered during an assessment does not automatically become authorized.
- Open Assessment setup and choose the network or repository-only workflow. Set the scope, exclusions, optional test-user references, allowed domains, and safety bounds that apply to the work.
- Review the summary and save the setup. Saving records the definition; it does not start a run.
- Use Start authorized scan for a network assessment or Start source analysis for a repository-only review. Workbench checks current authorization, scope, entitlement, and run readiness. Resolve any displayed blocker before starting.
- Follow network scans in Scan journal. Source analysis activity is listed under Agent assessments.
- In Findings register, open each result you plan to act on. Review its linked HTTP Records or OAST Interactions when present before assigning, exporting, or retesting it.
#Add existing traffic
If you already have captured HTTP traffic or an API specification, open Import traffic (Ingest) and add it to the project. Imported records are inputs for review; they do not expand the project's authorization or scope.
#Keep evidence in context
An HTTP record shows captured request and response evidence. An OAST callback is an observation to review alongside the finding and assessment that produced it. Neither a callback nor a source candidate replaces operator review.
#Related guides
- First authorized assessment
- Workbench guide
- SAST languages and source files
- Scope and safety
- Findings, HTTP Records, and OAST
Need a workflow that is not documented here? Email contact@eresussec.com.