Reports and audit evidence
Export a defined scope and explain exactly what the records demonstrate.
Generate an evidence report
Open Reports, select the report period, and request PDF or CSV. The UI offers 7, 30, 90 and 365-day periods. The report covers available agent inventory, configured policies, recorded violations, scan findings and selected administrative audit records.
If generation fails, preserve the selected period and retry the download. The Recent download requests list describes requests in that page session, not a durable proof that a recipient received or reviewed a file. Times are displayed in UTC.
Review before sharing
Check the organization, selected period, tested target, detector readiness, policy versions and any incomplete or excluded checks. Inspect the actual file for sensitive content and capture-policy behavior. A report documents available recorded scope; it does not establish a certification, independent assurance or exhaustive coverage of your application.
Scan-specific evidence is also available from the assessment workflow. Connected-agent testing explains the difference between a queue receipt, completed scan and finding.
Use the audit log
Open Audit Log to inspect recorded organization actions, resource types, resource IDs and timestamps. The CSV action exports the rows currently loaded in the page; paginate when reviewing additional records. Do not describe the page’s current-row download as a complete organization archive.
Audit records are administrative evidence. Their presence does not establish immutability, tamper resistance or a complete history of every external tool operation. Define any additional audit retention/export controls in your deployment.
Keep a useful review package
Keep the report, its period and generation time, the relevant trace/scan/regression IDs, policy versions and a short statement of tested boundaries. Retention and capture settings can limit what historical content remains. See compliance evidence, policy templates and data handling.