CI and automation

Treat Workbench as the place to start authorized assessments and review findings. Do not use a CLI scan command as the customer onboarding or pipeline path. The public documentation site does not publish a Guard API origin for CI jobs.

#Use reviewed results in a pipeline

1. Run and triage the assessment in Workbench.
2. Open Evidence exports and export reviewed findings as SARIF or CSV.
3. Pass that export to the downstream ticketing or CI workflow that consumes it.
4. Return to Workbench to inspect the finding and its HTTP Record or OAST callback before making a remediation decision.

Keep credentials out of job logs and exports. Use staging unless production testing is explicitly authorized, and keep a human reviewer involved in triage.

#Request programmatic automation

Direct programmatic access is provisioned privately only when included in the customer agreement. Email contact@eresussec.com to request access and ask whether your workspace includes it. Eresus will provide the private connection details after access is granted; do not guess an API host from this public site.

See Reports and exports, API targets, and Programmatic access.