Summary statistics
Overlaps: 1 · Conflicts: 0 · Gaps: 0
1 article-level crossrefs catalogued between Data Governance Act and DORA from the Fontvera EU regulatory corpus. Article numbers are verbatim from the underlying obligation_crossrefs table; descriptions are extracted, not paraphrased.
All crossrefs between these regulations
| Article (A) | Article (B) | Type | Severity | Description |
|---|---|---|---|---|
| DORA Art 13 | Data Governance Act Art 13 | overlap | low | [entity affected: authorities in charge of cybersecurity] Both regulations require authorities in charge of cybersecurity to cooperate with other relevant sectoral authorities and exchange information |
Overlaps explained
No conflict-type crossrefs were catalogued for this pair, but the 1 overlaps below mean a single control can be designed to satisfy both regulations at once. Plan the controls jointly to avoid duplicate effort:
- DORA Art 13 vs Data Governance Act Art 13 (low severity) — [entity affected: authorities in charge of cybersecurity] Both regulations require authorities in charge of cybersecurity to cooperate with other relevant sectoral authorities and exchange information to ensure consistency in regulatory decisions.
Which regulation takes precedence
EU law does not lay down a universal precedence rule between Data Governance Act and DORA. In practice three resolution approaches apply: lex specialis (the more specific provision wins when both purport to govern the same conduct); regulator guidance (EDPB, EBA, ESMA and the AI Office have all issued joint readings on overlapping articles — check the most recent applicable opinion); and document the choice (when the regulations leave the call to the controller, the audit defence is your written reasoning, not the regulator's silence). Where the corpus surfaces a conflict rather than an overlap, treat that as an escalation path to legal — not a control-design question.
What this means for your compliance team
Treat the 1 overlaps as design opportunities — one control, two regulatory anchors. Treat the 0 conflicts as escalation paths to legal: the regulations themselves don't resolve them, you do, and you document the reasoning. The 0 gaps point at scenarios where one regulation is silent while the other speaks — assume the regulator who has the explicit rule will win.
Related Fontvera pages
- data governance act article 5 member state
- data governance act vs dma comparison
- data governance act vs dsa comparison
- data governance act vs eprivacy comparison
Check your full compliance exposure with the 5-minute Fontvera diagnostic →