Every assessment produces the same paperwork problem. Engineers want raw output and CVE references. Executives want one page that says how bad it is and what to do. Auditors want findings tied to controls. Writing those three documents by hand from one pile of evidence is where a clean week of testing turns into a slow weekend of formatting. The Reports page exists to make that the fast part.
Three templates for three readers
- Technical — raw scan output, CVE references, and per-finding evidence. The version your engineers will actually act on.
- Executive — a stakeholder-facing summary with business impact and recommended actions, minus the packet dumps.
- Compliance — findings mapped to control frameworks (SOC 2, ISO, NIST and the rest), carrying the work from the Compliance Dashboard straight into the document.
Four export formats
Pick the template, set an Assessment ID, choose a format, and generate. Reports export to PDF for the polished deliverable, HTML for something you can host or email, Markdown for a repo or wiki, and JSON for feeding another system. Everything you generate lands in Report History, with open-folder integration so you are never hunting for the file you made yesterday.
The CLI mirrors this: zypheron report --last --format pdf generates the same kinds of deliverable from a finished scan without opening a window. Same evidence, two front doors.
The Auto-Doc panel does the gathering
The slowest part of report writing is not the writing — it is reassembling what happened. The Auto-Doc panel collates evidence from your workspace context as you work: command logs, screenshots, findings, credentials, exploits, IOCs, lateral movement, recon, and notes. By the time you sit down to generate, the material is already organized instead of scattered across terminal scrollback and a notes file.
AI Report Assist, with you in the loop
AI Report Assist drafts narrative sections from your collated evidence so you start from a draft instead of a blank page. It is built around operator review on purpose: the assistant proposes, you edit and approve, and the export reflects what you signed off on. It is a force multiplier for the writing, not an unattended author. For client-facing work, that human checkpoint is the feature, not a limitation.
Run your scans, let Auto-Doc gather, pick the template for your reader, and export. The document that used to eat the back half of an engagement becomes a few minutes at the end of it.