DPO Radio

Privacy-Scanner Anomaly Explanation

Overview Image

Why Anomaly Explanation Matters

A privacy scanner that surfaces a thousand findings without categorisation is worse than no scanner at all — the privacy team cannot triage the queue and the findings sit unaddressed. The fix is structured categorisation with deterministic severity so the team knows which findings are critical and which are routine.

The privacy-scanner anomaly explanation workflow takes a completed scan and sorts its findings into four buckets: third-party trackers, undocumented endpoints, secure-connection problems, and cookies. Severity is computed from the findings themselves — how many distinct trackers, how many distinct cookie names — rather than being asked of the model, and the scan's overall severity is simply the highest severity of any non-empty bucket. The explanation and the remediation steps are what the assistant writes; the categorisation and the score are not.

How It Works

Trigger From a Scanner Finding

The workflow runs against a privacy-scanner finding. The scan source, the offending entity (cookie, tracker, banner config), and the affected operating jurisdiction feed the workflow context.

Four-Bucket Categorisation

Third-party trackers, undocumented endpoints, secure connection, and cookies. Each bucket carries its own item list and its own remediation path.

Deterministic Severity

Severity is computed deterministically from data category, consent state, exposure scope, and jurisdiction. The same input always produces the same severity output; the AI does not vary severity assignment by run.

Structured Explanation With Citation

The explanation cites the relevant ePrivacy national overlay and the underlying organisation policy. The DPO sees both the regulatory anchor and the policy reference.

Suggested Remediation Per Bucket

Each finding ships with a suggested remediation routed to the appropriate downstream workflow — banner update, tracker removal, consent flow revision, propagation audit log fix.

Three Audit Events Per Run

The audit trail walks each finding from scanner identification through anomaly explanation and operator remediation routing.

The Difference

Graphic Image

Without Anomaly Explanation

Graphic Image

With Forseti Anomaly Explanation

IconPrivacy-scanner findings accumulate without categorisation.
IconFindings are categorised into four buckets with deterministic severity.
IconSeverity is assigned ad hoc with risk of inconsistent triage.
IconPer-bucket remediation routes through downstream workflows.
IconRemediation routing is bespoke per finding with no shared structure.
IconThe audit trail walks each finding end to end.

Built for Auditable AI

Build For Image

Severity is deterministic; the same input produces the same severity output. The audit trail records the input, the bucket, and the severity for every finding.

Build For Image

The workflow does not remediate autonomously. The DPO accepts the routing; downstream remediation runs through standard workflows with operator confirmation.

Build For Image

Explanations cite the regulatory anchor and the organisation policy reference. Ungrounded explanations ship with the "no grounding" marker.

Regulatory Framework Support

FrameworkHow Anomaly Explanation Supports It
EU ePrivacy national overlaysCategorises anomalies against the operating jurisdiction's ePrivacy implementation.
EU GDPRCites GDPR consent and lawful-basis requirements where the anomaly affects consent state.
Overview Image

Related Forseti Work

Use scanner findings as input to triage where they relate to an incident. The incident review starts from the relevant recorded facts. See Incident and Continuity Workflows.

Background Image

See Anomaly Explanation in Action

Ready to see a queue of 200 privacy-scanner findings categorised in five minutes with deterministic severity? Request a personalised demo.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

Next Steps

Icon Image

Start a Compliance Pilot

Run anomaly explanation against your privacy-scanner backlog and measure triage throughput.

Icon Image

Discuss Your Compliance Needs

Talk to our team about how anomaly explanation fits your scanner cadence.

Frequently Asked Questions About Anomaly Explanation

Third-party trackers, undocumented endpoints, secure connection, and cookies. A scan result is sorted into all four; each bucket reports the number of affected items, its own severity, the affected items themselves, and a remediation path. The scan's headline severity is the highest of any bucket that has items in it.

Yes. Severity is computed from data category, consent state, exposure scope, and jurisdiction. The same input produces the same severity output regardless of run.

No. Findings are categorised and routed; remediation runs through downstream workflows with operator confirmation.

The operating jurisdictions the organisation has configured. The ePrivacy national overlay applied per finding matches the affected jurisdiction.

Yes. Each run sends requests to the AI provider your organisation has configured, and your provider bills your organisation for them directly. A run is never refused because a Forseti allowance ran out, and the Usage page reports what each feature consumed.