SpartanX provides a rich, multi-layered view of engagement results — from high-level risk scores and vulnerability distributions to detailed agent reasoning trails, exploitation evidence, and remediation workflows. This section walks through how to extract maximum insight from a completed engagement.
The Engagements Dashboard
The Engagements dashboard gives you a at-a-glance overview of all tests — planned, in-progress, and completed. Key data points visible at a glance:
Engagement status: pending, in progress, completed, completed with errors, or paused
Risk score per engagement
Start and end dates, and total duration
Vulnerability counts, color-coded by severity (purple = critical, red = high, orange = medium, blue = low)
Engagements can complete with errors when external factors interrupt the test — for example, if a firewall or router at the target becomes temporarily unreachable. The engagement still produces results, but some coverage may be incomplete.
The Corporate Risk Score
Opening an engagement reveals the Corporate Risk Score — a proprietary metric scored from 0 (lowest risk) to 100 (highest risk). The score factors in:
CVSS severity of discovered vulnerabilities
Actual exploitability — whether the vulnerability was confirmed, partially exploited, or unverifiable
Exploitation complexity — from trivial to multi-step attack chains
Business value of affected assets
The dashboard also shows a vulnerability distribution breakdown: confirmed, suspected, likely false positive, and false positive.
Exploitability Summary
For each engagement, SpartanX reports how many vulnerabilities were:
Fully exploited — confirmed with a working proof of concept
Partially exploited — vulnerability confirmed but full exploitation stopped by guardrails
Verified non-exploitable — present but not exploitable under tested conditions
Unverified — insufficient data to confirm or deny exploitability
Agent Reasoning and Audit Trail
SpartanX provides a detailed view of what the AI agents did during the engagement. The Plan screen shows:
Reconnaissance phase — active and passive discovery steps
Agent swarm invocations — which specialized modules were activated and why (e.g., if an API is detected, the API analysis swarm is launched; if AWS infrastructure is found, the AWS cloud module activates)
Task lists and executed commands with timestamps
Decision reasoning — the agent's rationale for each action taken
This audit trail is searchable and browsable, allowing security teams to understand exactly what happened at every step of the engagement.
Reviewing Individual Vulnerabilities
The vulnerability list within an engagement supports powerful filtering — by severity, exploitability, status, or any combination. For each finding, you can view:
Summary and CVSS vector
Proof of concept availability and exploitation evidence
OWASP and MITRE ATT&CK mappings
CWE classification
Step-by-step reproduction instructions
Source code analysis (if repositories are linked)
Updating Vulnerability Status
Vulnerability status can be updated to reflect the current remediation state. Any status change requires a written reason, creating an audit trail. Access controls can be configured to restrict who is allowed to change vulnerability status — preventing front-line engineers from inaccurately altering findings. SpartanX serves as the source of truth.
Knowledge, Secrets, and Collaboration
Within the engagement view:
The Knowledge tab shows restrictions and observations added by both users and agents during the engagement.
The Secrets tab shows credentials discovered or provided — revealing a credential requires justification and is access-controlled.
Comments can be left on individual vulnerabilities, enabling team collaboration and clear ownership tracking.
What's Next
The next section covers the Vulnerabilities section — your centralized workspace for managing findings across all engagements, including pull request generation, Jira integration, playbook automation, and more.