Skip to main content
Download PDF and Open HTML give the fixed-layout house document for sending or printing: a branded cover, confidentiality notice, the found-vulnerabilities list, and a full write-up per finding.
The PDF report cover page

The PDF report cover page

​
The finding anatomy

Every finding follows the same anatomy, so a client reads each issue the same way:
Total risk, probability, criticality, the weakness class (CWE), the affected network or site, the CVSS score and vector, and the affected assets.
What the issue is, in plain language.
What an attacker can do, the business impact, and the likelihood of exploitation.
Root cause, how the weakness manifests, an evidence walkthrough, the affected components and assets, and the conditions and prerequisites.
A prerequisites line, then numbered steps a reviewer can follow to see the issue.
Immediate actions, the configuration or code fix, hardening and defence in depth, compensating controls, references, and how to verify the fix.
The captured request and response, in monospace, that proves the finding.
The report also carries a coverage page (the weakness classes checked) and a glossary (severity, probability, criticality, CVSS, CWE, KEV, EPSS, retest, out of scope), so a non-specialist reader can follow it.
The AI can draft these sections from the evidence and your house style, grounded in the project’s real data, for you to review and accept. It never invents hosts, versions or payloads.