Glossary
Project (Site)
Section titled “Project (Site)”A workspace tied to one target URL. Owns the assigned plan slot, working-hours window, scan history, and findings. The dashboard refers to projects as Sites in some places (e.g., My Sites); the API uses project. See Create a project.
The saved URL attached to a project. One URL per project. Credentials and scope rules live on the asset, not the project.
Plan slot
Section titled “Plan slot”One unit of paid scan capacity. Each Starter / Growth / Teams plan you buy becomes one slot. A slot moves through four states:
- available — purchased, not yet attached to a project.
- assigned — attached to a project, ready to scan.
- in use — currently scanning.
- consumed — spent. Cannot scan that project again until a new slot is assigned.
Scan agents
Section titled “Scan agents”Five specialised testing agents that run inside a full scan. Plan tier decides which are included:
- Map the site structure — discovery / crawling.
- Check the browser experience — front-end and UI testing.
- Check the server and APIs — backend probing for injection and similar.
- Check login, roles, and permissions — authentication and authorization testing.
- Check known software flaws — SCA (software composition analysis).
A separate Business Logic agent is gated to higher tiers. See Scan types and Plans.
Safe mode / Boss mode
Section titled “Safe mode / Boss mode”The two dangerous-action modes for a scan:
- Safe mode — every dangerous action pauses for human approval. After 5 minutes without a decision, the action is skipped.
- Boss mode — agents proceed with in-scope dangerous actions automatically. Scope and safety checks still apply.
Configured in the scan wizard’s Configuration step. See Approvals.
Working hours
Section titled “Working hours”The time window during which scan traffic is permitted against a target. Format: anytime or DAYS HH:MM-HH:MM TIMEZONE. Overnight windows are not supported. See Scheduling.
Scan state
Section titled “Scan state”The phase a scan run is in. Common states:
- Estimating / Queued / Starting — preparing.
- Running / Uploading — active.
- Scheduled — waiting for the working-hours window.
- Approval pending — Safe-mode action waiting on a decision.
- Awaiting credit confirmation — scan paused on credit balance.
- Complete — finished. Findings ready.
- Error / Stopped — interrupted.
Finding
Section titled “Finding”A single issue PhantomOps reports — vulnerability, misconfiguration, or risky exposure. Each finding has a short ID (e.g., WTE-007), severity, status, and a write-up with the structure What it is / Why it matters / How to fix / Proof of concept / References.
Severity
Section titled “Severity”Five levels: Critical, High, Medium, Low, Informational. Drives sort order in the Issues list and prioritization on the Findings page.
Triage
Section titled “Triage”Moving a finding from Open into Triaged, Resolved, or Not Applicable. Mark as not applicable removes it from the open list and reports but keeps the record. Remove the finding deletes it permanently. See Triage.
Credits
Section titled “Credits”The unit PhantomOps spends to run scan compute. Each plan slot includes a starting credit balance; you can top up with purchased credits. See Credits.
Report variants
Section titled “Report variants”Four PDF export shapes — Full Report, Findings Only, Remediation Plan, Coverage Report — each carrying a specific subset of report sections. See Export and reports.
Organization
Section titled “Organization”The top-level container that owns projects, plan inventory, and users. A user belongs to exactly one organization (super-admins can move between).
Common roles: Pentester, Project Admin, Organization Admin, Super Admin. Role decides what you can do — invite users, assign plans, delete projects, change organization settings. See Settings → Users.