Test the authenticated paths your users actually reach.
Configure authorized authentication in Eresus Workbench before an assessment runs. Cookie, Basic, Bearer, and custom-header options let teams assess approved in-session and API workflows without treating credentials as an afterthought.
Set authentication as part of the assessment, not a post-scan workaround.
Choose the project and target, then configure the authentication option that the authorized application requires. The assessment setup keeps the relevant scope, modules, and authentication decisions together before a scan starts.
Give reviewers the context needed to reproduce a real authenticated finding.
Authenticated routes need more than a scanner verdict. Workbench stores findings beside the HTTP records and out-of-band callbacks that support review, so the team can see what was assessed and why the result needs remediation.
Three steps from approved scope to a reviewable result.
- 1
Confirm authorization for the project and target.
- 2
Configure cookie, Basic, Bearer, or custom-header authentication.
- 3
Inspect evidence, remediate the route, and retest the stored record.