Core concepts
These are the words you will see across the product and the rest of this documentation.
| Concept | What it is |
|---|---|
| Project | The workspace for an engagement. It holds your targets, runs, and results, and it is the boundary for access and organization. |
| Target | What an assessment runs against: a domain, a web application, or (self-hosted) an IP address or range. |
| Template | A ready-made assessment type you choose when launching. It decides which parts of the assessment run, from a quick surface check to a deep review. |
| Run | One execution of a template against a target. You can follow it live or come back to the results. |
| Finding | Something the assessment discovered or confirmed, ranked by risk, with evidence and remediation. |
| Evidence | The raw proof behind a finding: the commands that ran and their output, stored as artifacts you can open. |
How they fit together
Section titled “How they fit together”A project contains one or more targets. You launch a run by choosing a template and a target. The run produces findings, and every finding links to the evidence that supports it.
Finding status
Section titled “Finding status”Findings move through a small set of states so you can triage them:
- Candidate: discovered but not yet proven. This is the normal output of the discovery phase.
- Confirmed: proven exploitable with proof-of-concept evidence during the confirmation phase (self-hosted).
- Triaged states such as accepted risk or false positive, which you set as you review.
- How an assessment runs: the two phases and the live view.
- Projects and targets: create a project and add targets.