Discovery-first workflow

Why discovery comes first

A new scope rarely has enough context for deep targeted testing. Discovery gives the platform a map of reachable hosts, services, endpoints, technologies, and authentication surfaces.

The operating loop

1. 1Run discovery.
2. 2Review assets and services.
3. 3Promote important assets to managed.
4. 4Fill business criticality, data sensitivity, owner, and authentication context.
5. 5Add credentials or repositories where needed.
6. 6Run a targeted follow-up assessment.
7. 7Triage findings and retest fixes.
8. 8Automate repeated coverage.

What to look for

• Admin, auth, billing, checkout, API, gateway, file, VPN, and identity surfaces.
• Internal systems found through a private runner.
• Assets that handle customer or regulated data.
• Hosts with many services or recent findings.
• Surfaces that are blocked only because context or credentials are missing.