Skip to main content

Report Catalog

Before building a report, check whether it already exists. This page is the complete list, grouped by who usually asks for it.

Scanning

Consolidated Security Report dialog on Scan Results: 4 scans, 3 targets, 4 tools; title, HTML / PDF / DOCX format and optional evidence screenshots

ReportContentFormatsWhere
Per-scan reportOne web / API / network / TLS scan with findings, evidence and remediationHTML · PDF · DOCXScanning → CompletedView / HTML / PDF per row · GET /api/native-scans/results/{scan_id}/download?format=
Consolidated security reportSelected scans (or all completed scans of a target) merged into one executive document: risk matrix, findings by tool, optional evidence screenshots of affected URLs, remediation roadmapHTML · PDF · DOCXScanning → Consolidated Report (tick scans first, or it takes all completed) · POST /api/reports/consolidated · POST /api/reports/target → job, then GET /api/reports/{job_id}/download; history at GET /api/reports/history
App Scan reportThe all-tools application assessment with standards mappingHTML · PDFApp Scan → run → Report · GET /api/app-scan/{app_scan_id}/report
Code reportPer-repository / per-scan SAST, secrets, SCA, IaC findings with tool breakdownPDF (+ raw artifacts per tool)Code Command Center → Reports → Export · GET /api/code/reports/{scan_id}/export?format=pdf · …/artifact/{kind}
SBOMComponents, licences, vulnerabilities for a code scan or imageCycloneDX / SPDX JSON · CSV · vulnerabilities CSV · licence noticesCode → SBOM & Licences → Download / Export · GET /api/code/sbom/{scan_id}/download · …/export?format=csv|csv-vulns|json · …/report
Container scan exportImage vulnerabilities from a full analysisJSON · CSV · CycloneDXContainer Security → scan → Export · GET /api/container/scans/{scan_id}/export?format=json|csv|cyclonedx
Container compliance reportImage / registry / account against CIS Docker, NIST, PCI DSS or SOC 2JSON · HTML · PDFContainer Security → Compliance → Generate · POST /api/container-security/compliance-report
Kubernetes compliance reportCluster against CIS, NIST, PCI DSS, SOC 2 or HIPAAJSON · HTML · PDFKubernetes Security → Compliance → Generate report · POST /api/k8s/compliance/report

Cloud, vulnerabilities and risk

ReportContentFormatsWhere
Cloud findings exportFiltered CSPM findingsCSV · XLSXCloud Security → Findings → Export · GET /api/cspm/findings/export?format=csv|xlsx (session only)
Vulnerability occurrences / findingsThe unified lake, filterableJSON over the APIGET /api/vulnerabilities/occurrences · GET /api/vulnerabilities/findings
Risk register exportRisks with treatment plans and controlsCSV (selection) · JSON / CSV (full)Risk Management → Export CSV on a selection · Reports → Full Risk Export · GET /api/risk-management/reports/export?format=json|csv
Risk executive summaryRegister posture for a board packJSON (+ PDF data)GET /api/risk-management/reports/executive-summary · …/executive-pdf-data
Heat map export5 × 5 matrix dataJSONRisk Management → Heat Map → Heat Map Export
SLA breachesCurrent breach listJSONGET /api/sla/breaches

Compliance and audit

ReportContentFormatsWhere
Audit reportsControls (with overrides and evidence counts), findings, drift history, remediation audit trail, compliance-score historyCSV per sectionAudit Reports · POST /api/compliance-engine/reports/generate…/download/{section} — see Audit Reports
Auditor packagePer framework, per control, evidence in four layersZIPEvidence Hub → Download audit package · GET /api/evidence-completion/auditor-package/{framework}
Statement of ApplicabilityRequirement → controls → statusJSONGET /api/common-controls/soa/{framework}
Assessment PDFA completed questionnaire with answers, evidence and scorePDFGET /api/assessments/{assessment_id}/export-pdf
DPDP audit packEvent log slice + module state, SHA-256 sealedJSON · PDFDPDP Compliance → Audit & Export · POST /api/dpdp/audit/pack…/pack/{pack_id}/pdf
DPDP breach reportsRule 7(2) Board report and CERT-In report textText (for filing)Breach → Report text · GET /api/dpdp/breach/{incident_id}/dpb-report-text · …/cert-in-report-text
Compliance posture PDFCover, implementation summary, status distribution, per-framework scoresPDFExecutive Dashboard → Export PDF · GET /api/executive-dashboard/export-pdf

Executive

ReportContentFormatsWhere
Board report · Trend analysis · Certification planSee Executive DashboardOn screen · PDFExecutive Dashboard → Executive Reports
Gap analysis · Remediation roadmapGenerated documents from the current gapsOn screen · PDF · emailExecutive Dashboard → Gap Analysis / Remediation Roadmap
Scheduled reportsAny of the above on a cadencePDF by email, historyScheduled Reports

Branded report family (API)

A set of branded, team-scoped documents that share one design system (cover page, document control table, charts, header/footer) and are rendered server-side. They are available over the API today and are what integrations and scripts should call for a finished document:

RouteFormatsContent
GET /api/export/executive-dashboardPDFExecutive dashboard summary
GET /api/export/compliance-posturePDFCompliance posture (same as the dashboard's Export PDF)
GET /api/export/cloud-posture · .html · .docxPDF · HTML · DOCXCloud posture across connected accounts
GET /api/export/web-app · .html · .docxPDF · HTML · DOCXWeb-application security findings
GET /api/export/network · .html · .docxPDF · HTML · DOCXNetwork security findings
GET /api/export/app-sec · .html · .docxPDF · HTML · DOCXApplication security (code + dependencies)
GET /api/export/consolidated-exec · .html · .docxPDF · HTML · DOCXConsolidated executive report across modules
GET /api/export/scan-results?scan_type=PDFScan results by type
GET /api/export/ai-decisionsPDFAI SOC agent decisions audit

All of them stream the file with a Content-Disposition attachment header; authenticate with X-API-Key.

Retention and scope

  • Generated reports (consolidated, executive, scheduled, audit) are kept 180 days by default (REPORT_RETENTION_DAYS); per-scan reports follow the scan retention policy in Scan Management.
  • Every report contains only the active team's data; API keys are scoped to their team.
  • Branding (logo, colours, confidentiality banner) comes from the team's brand configuration and applies to every server-rendered document.