Monitor regulatory compliance

Select Security & Compliance → Compliance.

The page opens on Impact Summary over the last 30 days.

Choose 7d, 30d, 90d or All time.

Every tab, chart and export on the page reads this window. The Findings tab is the one exception: a worklist framed by 30 days would hide a July finding still due in September, so it ignores the period deliberately.

Open the Channel selector and pick one of Managed chat, Browser extension, Inline proxy (SWG), Document analysis, Claude Code or API / image, or leave it on All channels.

A channel with no records in the window is still listed with a zero, so a surface that is switched off is distinguishable from one that is clean.

Open Tenant and pick an account, or leave All tenants.

Detections that carry no tenant, or a tenant id no account matches, cannot be reached by this filter. The scope bar says how many there are so the per-tenant views are not mistaken for a partition of the whole.

Select the currency chip and pick the currency the cross-regulation totals are expressed in.

Only the totals convert. Each regulation keeps the currency its authority actually fines in, and the chip shows the rate date and whether the rates are the shipped reference set or manually adjusted. Changing a rate is admin_user only; an auditor reads the rates and cannot edit them.

On Impact Summary, select a row in Exposure by regulation or a segment in Where these detections came from.

The page scopes to that regulation or channel and the chip appears in the scope bar. Selecting it again clears it.

Select the Detections tab.

The table lists date, entity types, action, regulations, articles, risk, direction and review state for the active scope. Filters for Entity Type, Risk Level, Action and a date range are applied by the gateway before paging, so the total under the table counts the filtered set.

Select a row.

The dialog names the action taken, the risk level, the articles the detection would have violated, the potential fine and the session it came from. For an auditor the matched values are replaced by the entity-type placeholder and the dialog says Matched values are hidden for your role — the entity type is shown instead.

Select Download PDF or Export HTML in the table toolbar.

Both export the full filtered set, not the visible page, capped at 500 rows. The PDF cover prints the subject, the active filters, the period and the number of rows actually laid out.

In the Detections table row actions — or in a detection's audit drawer on All detections — select Open as finding.

The control checks first and renders the answer: if a finding is already live for that detection it shows the status chip and links to it instead of creating a second one.

Go to the Findings tab, select the row, and fill in Owner and Due.

Owner is an email address — the responsible person is often not a gateway user. Leave Due empty for no deadline. An overdue open finding is marked Past due and still open.

Write the plan in Next step and set Status to Open, In progress or Closed.

Closing stamps the closure date; reopening clears it, because a reopened finding that still carried a closure timestamp would read on every report as closed on that day.

If the finding became a ticket in your own system, paste its identifier in Ticket reference and its link in Ticket link.

Ticket link must be an absolute http or https URL or the save is refused. The reported ticket status is displayed but is never mapped onto Status — this finding's status is what CID recorded a person deciding, and a remote workflow must not be able to rewrite a compliance record.

Set the period, and the channel, tenant and regulation filters if the record should be narrower than the whole appliance.

The capture takes the scope bar as it stands, so what you see is what is frozen.

Go to Evidence, type an optional note in What is this capture for? and select Capture this period.

A Period captured. toast confirms it. Re-freezing the same window is allowed — refusing would make a first mistaken capture permanent — and the toast then reads Captured. These are the same figures as an earlier record for this window.

Select Check on a row.

The gateway re-hashes the stored bytes and the chip reads Unchanged or Altered. This is a checksum, not a signature: it shows whether a record changed after capture, carries no trusted timestamp, and does not stop anyone with database access.

Select the download action for the raw record, or Evidence pack for the archive.

The raw download is the exact bytes that were hashed, so sha256sum on the file reproduces the value shown in the row. The pack adds the rendered report, per-regulation dossiers, a checksum manifest, a MANIFEST.json and a VERIFY.txt with the commands to check it offline.

Select What's inside before downloading.

The popover lists every file, the mapping version the figures were computed under, and a What it cannot show list of gaps. It also carries the reconciliation chip: Report matches the record, Report and record disagree, or Not checked — and the pack download refuses on either of the last two rather than shipping a document that looks complete.

Select Dossier, choose GDPR, KVKK or EU AI Act, then Download JSON or Download PDF.

Sections marked From record are filled from the frozen figures; sections marked Deployer are evidence no gateway can hold — a DPIA, a record of processing activities, a human-oversight procedure. Neither an unfilled automatic section nor a deployer section is dropped: both render and both appear in the closing evidence-gap list.

Select the Decision Simulator tab.

The three cards Without CID-Core, With CID-Core and Reduction load over the page's period, channel and tenant scope.

The cards and the coverage rows recompute on every change; nothing is saved.

Scroll to Methodology.

The notes state the arithmetic for the run you are looking at. The exposure ceiling is the statutory maximum applied per detection; an actual fine depends on incident scope and the authority's discretion.

Select Download PDF.

The gateway re-runs the simulation server-side and renders it with the subject, channel and period printed on the cover, so a run scoped to one team is not filed as if it described the organisation. The PDF exists for the two slider modes only.