/compliance/data-posture) answers one question: if an
auditor walked in today, what state is our data in? It reads the same
scan findings Data Security produces and
rolls them up per workspace rather than per dataset.
What the page shows
Severity rollup
Datasets carry the same four-level scale used everywhere else in the platform.
See the severity scale for the thresholds
behind each label.
The activity timeline
The timeline is the narrative an auditor asks for: not “what is the state now” but “what happened, and when did you react”. Each day is bucketed with its highest severity, its critical and high counts, and how many datasets were affected. Click a bucket to open the detail view, which groups that day’s events by dataset so you can see the sequence: upload, scan, findings, heal, re-scan. Events carry one of five severities:critical, high, medium,
low, none.
Scoping
Both the summary and the timeline accept an optional list of dataset ids, so you can scope the page to one project’s datasets rather than the whole workspace. This is the same scoping a report uses, which means what you see here is what a report over that scope will contain.API
All of them accept
dataset_ids to narrow the scope, and all read
requests need compliance.access.
Dataset lineage
Auditors reliably ask “where did this training corpus come from?”. Lineage is the single answer, and it is included for every dataset in scope of a compliance report. You can also read it per dataset from the dataset detail page.See also
Reports
Turn this posture into a document for an auditor.
Running scans
Where the findings behind these figures come from.