SpartanX includes a flexible reporting workflow that supports multiple audiences, from technical teams to executive stakeholders and compliance owners. Reports are generated from completed engagement data and can be adapted to match the purpose of the final deliverable.
Access the reporting area
After reviewing a completed engagement, open the Reports tab inside that engagement and select Generate Reports. This opens the report repository and allows you to configure a new output.
Choose the right report type
Report type | Best for |
Technical Report | Security teams and developers who need full technical detail, evidence, and code context |
Executive Report | Leadership audiences who need a concise risk summary |
Technical Risk Summary | Teams that want a focused overview of technical risk without a full technical report |
Statistical Executive Risk Summary | Management audiences who want a data-oriented summary |
Compliance Reports | Audiences who need findings mapped to frameworks such as ISO 27001, SOX, DORA, HIPAA, PCI DSS, GDPR, OWASP, or NIST |
One engagement can generate multiple report types at the same time, which makes it easy to serve different internal stakeholders without repeating the analysis process.
Generate a report step by step
The report creation workflow is straightforward and can be completed in a few guided steps.
Step | What to do |
1 | Select the collection and choose which assets to include |
2 | Choose the report language |
3 | Review the optional advanced prompt |
4 | Run the task and track progress in the Reports panel |
The asset selection step is especially useful if you tested more than you want to include in the final document. For example, you may want to exclude staging systems from a report intended for a production-facing audience.
SpartanX currently supports report generation in English, Spanish, and Portuguese.
Review the completed report
Once a report is ready, you can open it and move through the content section by section. The interface allows you to jump directly to individual findings, review evidence, and understand how the report was produced.
Reports can include technical evidence such as code snippets, screenshots, and detailed descriptions of the vulnerability and attack path. This makes them useful not only for executive communication, but also for remediation planning.
Export options
Export format | Availability |
Markdown | Available |
Available | |
CSV snippets | Available |
Google Docs / Google Drive | Coming soon |
Refine the report with the chatbot
If the first version of the report is not quite right, you can refine it directly in the platform. For example, you can request a more developer-focused tone, remove tables, or align the structure to a previous report style.
This refinement workflow is valuable because it reduces the need for manual editing outside the platform. Once the final version is saved, it remains available in the Reports area for later review or download.