Eresus Guard
A cloud workbench for authorized application security: run DAST against approved web apps, review source-analysis results, and keep HTTP evidence and OAST callbacks beside each finding.
Start from a project, confirm the target is in scope, configure authentication and modules, then review the result in the same workspace. Guard is a product at guard.eresussec.com; this page describes its documented workflows.
What the workbench covers
Authorized web and API testing
Define the project and target explicitly, configure an assessment profile and authentication, and keep the approved scope attached to the run.
Source analysis across repository languages
Agentic SAST examines a pinned repository clone using language-aware source and sink context. Candidates must cite a real file, line, and snippet, then pass validation and trace before they become findings.
Evidence attached to the finding
Review the relevant HTTP request and response, OAST callbacks, or source location alongside the finding instead of deciding from a severity label alone.
How teams use Guard
Scope before scanning
Authorize the target first. Guard does not let a discovered link silently expand the job beyond the project’s approved scope.
Evidence-led triage
Inspect the proof, decide whether it affects the application, assign an owner, and give engineering a reproducible path to investigate.
Retest after remediation
Return to the same authorized target and verify whether the original behavior changed; retain the result with the assessment record.
Explore Guard workflows
Authorized target setup, authentication, HTTP records, and OAST evidence.
See the source families, file classification, and candidate validation workflow.
Learn what stays attached to a finding and how teams review it.
Eresus Guard FAQs
What is Eresus Guard?
Eresus Guard is a cloud workbench for authorized application-security assessments. Teams start a project, approve the target, configure the scan, and review findings with their supporting evidence in Workbench.
Does Guard keep HTTP proof with DAST findings?
Yes. The documented DAST workflow keeps HTTP records and OAST callbacks with the assessment so a reviewer can inspect the request, response, or callback behind a result.
How does Guard’s source analysis reduce unsupported findings?
Source-analysis candidates must reference a real file, line, and code snippet. They then pass validation and trace before they are stored as findings.
Can I scan a target without authorization?
No. Guard is for authorized assessment. Teams confirm that the target belongs to the approved project and scope before running a scan.