DPO Radio

Every coverage exercise waits on one setup task: mapping a new framework into your control library. By hand, a framework with 200 requirements takes days. A general-purpose AI drifts from your actual control library, because it does not know your local controls.
The workflow compares a framework in your workspace with your existing rules and gives a verdict on each requirement: add a new rule, refresh an existing one, or change nothing. Each suggestion carries:
Your compliance specialist accepts the right ones, one by one or all at once, and rejects the rest.
Start the workflow from any framework added to your workspace.
For each requirement in the framework, the workflow proposes a mapping to one or more entries in your control library.
Every suggestion is one of three kinds: a new rule, a refresh of an existing rule, or no change required. The third is as useful as the first two, because it tells you a requirement is already handled rather than uncovered.
Each mapping cites both the regulatory requirement and the proposed control library entry.
Your compliance specialist reviews each mapping. Accepted mappings are saved; rejected ones stay on record in the audit trail.
Accepted mappings become the starting point for control coverage exercises, such as ISO 27001 Annex A coverage and the SOC 2 Trust Services Criteria evidence map.
The audit trail records the standard three workflow events: the run starting, the draft being produced, and the accept or reject decision.



Each mapping cites both the regulatory text and the control library entry. A mapping Forseti cannot ground carries a "no grounding" marker.

Your compliance specialist accepts each mapping; the workflow saves nothing on its own.

The audit trail follows each mapping from proposal, through your specialist's decision, to the coverage exercise that uses it.
| Framework | How Compliance Rule Auto-Mapping Supports It |
|---|---|
| Vietnam Personal Data Protection Law | Maps PDPL requirements into the organisation's control library. |
| EU GDPR | Maps GDPR requirements into the organisation's control library. |
| ISO 27001 | Maps ISO 27001 Annex A controls into the organisation's control library. |
| SOC 2 | Maps SOC 2 Trust Services Criteria into the organisation's control library. |

Use rule mapping to propose operational links. Applicability workflows prepare separate decisions about whether controls apply. See Statement of Applicability Workflows.
See a framework compared with your existing rules, with every suggestion quoting its source article. Request a personalised demo.


Run rule auto-mapping when you roll out a new framework, and use the accepted mappings to start your coverage exercises.

Talk to our team about how the workflow fits your regulatory programme rollout.
No. Your compliance specialist accepts suggestions individually or in bulk and rejects the rest, and the run reports how many rules were actually created. Nothing reaches the rule library without that step.
Every suggestion quotes its source article beside the proposed rule body. Where it refreshes an existing rule, it also shows the rule it would replace. The reviewer compares the proposal with the text it came from, not with a score.
The requirement is shown with a "no mapping" marker. Your compliance specialist then creates a new control library entry, maps it to an existing entry, or accepts the gap.
Yes. Re-running against the updated framework shows new or changed requirements, and flags existing mappings where the underlying regulatory text has changed.
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.