Export reports

Open Reports to export the supported findings register. Analyst, Admin or Owner is required; Viewer can inspect findings in the app but cannot export the report.

Create an export

1. Choose the current organization and open Reports.
2. Select the findings report.
3. Choose the available severity and status filters.
4. Review the preview, counts and provenance.
5. Download CSV for a spreadsheet or JSON for structured processing.

Exports are generated from current data and filters. They include provenance such as organization, generated time, the requesting user, rule-set version and source scan references. Synthetic data is labeled in the export, not just in the UI.

Make a report useful

Include the review period, coverage limitations and decisions alongside the exported rows. An export of open findings alone cannot prove that unsupported capabilities or unconnected sources are safe. Use a consistent filter when comparing review periods.

Treat downloaded reports as organization data. They can contain asset names, destinations, evidence metadata and user information even when credential values are redacted. Follow your handling policy when storing or sharing them.

SecureObs preview

The SecureObs integration is currently a read-only preview of the payload that would be shared. It does not establish a live connection or transmit the report to SecureObs. Review the on-screen explanation before treating the preview as a completed integration.

Scheduled reports, arbitrary inventory exports and build-to-build reporting are not implemented. Use the supported findings export and your own scheduling or review process where appropriate.