DPO Radio

Multi-framework compliance programmes carry conflicts. GDPR data minimisation versus Cybersecurity Law log retention. PDPL cross-border restriction versus DORA cross-EU reporting. SOC 2 evidence retention versus the right to erasure. Each conflict can be resolved with a documented position, but only if the team finds the conflict first. A team that does not have a catalog of known conflicts discovers them during inspection.
The cross-framework conflict catalog ships 22 known conflicts across 12 framework pairs out of the box. Each conflict carries the requirement IDs from both sides, a description of the tension, suggested resolutions, and a flag indicating whether legal-counsel review is required before resolution.
Twenty-two known conflicts across twelve framework pairs ship out of the box. The catalog expands when new regulatory packs ship or when existing packs are updated.
Filter chips combine for deep drill-down. Pair selectors isolate GDPR × Cybersecurity Law, PDPL × DORA, ISO 27001 × SOC 2, and the other pairs. Topic filters (retention, cross-border, consent, evidence, log, incident notification) tighten the view.
Click a conflict row for the side-by-side view. Each side shows the requirement text, the citation, and the operational implication.
Each conflict carries suggested resolutions. The resolutions are starting points, not committed positions; the country compliance manager adopts, adapts, or rejects.
The triage flow for each conflict runs through three states — acknowledge, assign to an owner, resolve. Legal-counsel review is required for flagged conflicts before resolution.
When regulatory packs update, new or shifted conflicts surface in a "new since last review" view. The country compliance manager triages explicitly rather than missing the update.



Every state change — acknowledge, assign, resolve — is recorded in the audit trail with operator and time.

Resolutions are operator decisions. The catalog does not auto-resolve a conflict; the suggested resolutions are starting points the operator adopts or rejects.

The catalog is scoped to the customer organisation. Resolution positions for one organisation are not visible to another.

A catalogue entry can inform a review. Use the Statement of Applicability workflows to inspect supporting evidence and proposed decisions, then have an authorised person apply the selected rows to a draft.
Ready to see a multi-framework programme triaged against the 22-conflict catalog with side-by-side positions? Request a personalised demo.


Triage the catalog against your installed pack roster and route the relevant conflicts to your team for one quarter.

Talk to our team about which framework pairs matter most for your programme.
22 known conflicts across 12 framework pairs out of the box. The catalog expands when new regulatory packs ship or when existing packs are updated.
No. Suggested resolutions are starting points; the country compliance manager adopts, adapts, or rejects. Resolution commitment is an operator action.
Each conflict carries a flag indicating whether legal-counsel review is required before resolution. Flagged conflicts route to the legal counsel; resolution by another role is blocked until counsel signs off.
New or shifted conflicts surface in the "new since last review" view so they are not missed in routine triage.
Yes. All tiers — Light, Standard, Enterprise — have the cross-framework conflict catalog.