Loading…...
Choose an authorized target, configure a short run, and use the evidence to understand the first finding.
A first run is deliberately narrow: one verified target, the quick scan profile, and low attack depth. The goal is not to break anything — it is to watch a controlled attack run execute end-to-end and read its verdict with your own eyes.
The four steps below take you from picking a target to reading a scored verdict, and each step names what you should have in hand before moving on. Followed in order, the whole path stays inside a single sitting.
By the end you will know where findings live, how a verdict maps back to the scenario that produced it, and what re-running the same scenario changes. That baseline is what every later workflow — CI gating, schedules, run comparisons — builds on.
Add a host or URL to the allowed target scope. Prefer staging for the first attempt.
Start with `quick` and low depth to validate the configuration. Expand only if the question requires more scenarios.
Follow the status on the run page and confirm whether it completed or failed before interpreting any score.
Open the finding, inspect its evidence and affected target, and then route it to the responsible team. Severity orders the queue; it does not prove impact by itself.