Cloud Workbench for AppSec you can review
Scanning and triage live in Workbench. Findings keep HTTP records and OAST callbacks.
You start a scan in the browser.
Open Workbench. Pick the project. Approve the target. The assessment runs in the cloud. The team reviews it in the same screen.
The finding keeps the request that proved it.
Open the finding. Read the HTTP record. Check the OAST callback if one fired. Replay with cURL when you need to show engineering.
Nothing runs until the domain is yours.
Authorization first. Metadata IPs stay out. If the evidence changes later, retest against the stored record.
The screens your team actually uses.
Dashboard
Open work, waiting findings, and the next decision.
Scan history
Every run, target, and result in one list.
OAST callbacks
Hits that arrived after the page responded.
Modules
Coverage you turn on inside the project.
Projects
Scope, history, and who owns the work.
Admin
People, SSO, and SLA in one place.
Three steps. Then the workspace.
- 1
Request a workspace
Send the organization and the apps. We open Workbench for that team.
- 2
Sign in
Password login on every plan. SSO (OIDC/SAML) is Enterprise.
- 3
Scan, then read the proof
Authorize the target. Review the finding with the HTTP still attached.
Current source catalog. Counts change as modules are added, replaced, or retired.
Request a workspace. Login if you already have one.
Professional, Business, Enterprise, or MSSP. Scanning and review happen in Workbench.