Docs/Reporting & Exports

Evidence

Reporting & Exports

CSV and JSON export workflows for audit, operational reporting and evidence sharing.

Audit logs export

State-changing operations with actor, correlation ID, timestamp and result metadata.

Findings export

Open and historical findings by domain, severity, provider and remediation status.

Resources export

Normalized multi-cloud inventory with provider metadata and scope identifiers.

Evidence artifact export

Evidence references linked to action executions and compliance workflows.

Export workflow

01

Choose scope

Pick organization-wide data or narrow the export by provider, domain, status, scope or reporting window.

02

Generate file

Small exports return directly; larger bundles run as background jobs and appear in export history.

03

Validate contents

Check row counts, timestamps, filters and checksum metadata before sending outside the team.

04

Hand off evidence

Share the export with auditors or stakeholders together with the request context and reporting period.

Typical export fields

ExportImportant fields
Audit logsactor, action, target, result, correlationId, createdAt
Findingsdomain, severity, status, provider, resourceId, estimatedImpact
Resourcesprovider, region, type, scopeId, tags, metadata, lastSeenAt
EvidenceartifactType, source, checksum, generatedBy, generatedAt

Operational notes

Exports are always tenant-scoped by organization context.

Asynchronous export jobs are metered and can be plan-gated.

Large evidence bundles should be validated before auditor sharing.

Use consistent reporting windows for trend comparisons.

Next: check export entitlements in Plans & Features or create an audit bundle.

TurboFinOps

Start with one cloud scope. Prove savings fast.

Connect AWS, Azure, or GCP and get actionable findings, score trends, and auditable remediation paths in minutes.

Built for FinOps, governance and audit workflows