After an engagement finishes, SpartanX gives you a complete analysis view that combines summary metrics, detailed findings, auditability, and follow-up actions. This is where teams move from observation into prioritization and remediation planning.
Start with the engagement overview
The overview page helps you understand the engagement at a glance.
Item | What it tells you |
Status | Whether the engagement completed successfully |
Type | Whether it was a new scan, validation scan, or retest |
Start and end dates | The time window of the engagement |
Risk score | SpartanX priority score for the engagement outcome |
Vulnerability count | Total number of findings across all severities |
The risk score shown here is SpartanX's own scoring model, which includes exploitability, difficulty, and business criticality. This helps prioritize real-world risk more effectively than severity alone.
Schedule future runs or rerun immediately
From the completed engagement view, you can either rerun the engagement immediately or schedule it on a recurring basis. This is useful when you want to support continuous testing for a high-priority environment.
Apply compliance filters
If you need to align findings to a specific compliance framework, you can filter the completed engagement accordingly. This makes it easier to isolate the findings that are relevant to standards such as SOX, HIPAA, or PCI DSS.
Understand exploitability status
One of the most important parts of the completed engagement view is the distinction between different exploitability outcomes.
Status | Meaning |
Exploited | The issue was confirmed and includes proof of exploitation |
Partially exploited | The issue was validated to some extent but not fully chained to full exploitation |
Non-exploitable | The condition exists but could not be exploited in practice |
Unverified | The issue could not yet be conclusively confirmed |
This helps teams focus on what is actionable now instead of treating every theoretical issue as equally urgent.
Review the reasoning log and agent workflow
The full reasoning log remains available after completion. You can review how reconnaissance was performed, which testing paths were selected, and how the platform expanded into relevant domains such as web applications, APIs, cloud environments, or other target types.
SpartanX dynamically activates the right testing capabilities based on what it finds. That means a web application finding can lead into API testing, and infrastructure discoveries can inform additional cloud or network analysis.
Explore the assets, vulnerabilities, knowledge, and secrets tabs
The completed engagement view also gives you access to several important supporting areas.
Tab | What it contains |
Assets | Every target that was in scope for the engagement |
Vulnerabilities | Full finding list with filtering and drill-down detail |
Knowledge | Shared discoveries captured across the testing workflow |
Secrets | Credentials, tokens, or keys discovered during testing |
The Knowledge area is especially important because it shows how discoveries are shared across the platform during the engagement. The Secrets area is useful when tokens, passwords, or API keys are discovered and later reused across other testing paths.
Next step after analysis
Once you have reviewed the completed engagement, the natural next step is reporting. SpartanX lets you move directly from the engagement view into the reporting workflow, where you can generate technical, executive, and compliance-focused outputs from the same results.