Framework overlap

Does GDPR cover Notifiable Data Breaches Scheme (Australia)?

You hold GDPR and have been told to do Notifiable Data Breaches Scheme (Australia). Here is how much overlaps, control by control.

38% of Notifiable Data Breaches Scheme (Australia) you already have

GDPR already covers about 38% of Notifiable Data Breaches Scheme (Australia), leaving 5 of 8 controls as genuinely new work.

Already covered 1 Likely covered 2 New work 5

What is genuinely new work

Nothing in GDPR reaches these. This is the list to scope.

AUNDB-A1
Applicability, Scope, and Data Breach Response Plan
AUNDB-A2
Containment and 30-Day Assessment of Suspected Eligible Data Breaches
AUNDB-A6
Exceptions: Remedial Action, Enforcement, Multiple Entities, Inconsistency with Other Law
AUNDB-A7
Recordkeeping, Communications Strategy, Post-Incident Review, Board Reporting
AUNDB-A8
Specific Information Categories, Third-Party and Cloud Coordination, OAIC Guidance Updates
Show the 3 you already have
AUNDB-A3
Eligible Data Breach Determination and Serious Harm Threshold
AUNDB-A4
Notification to the Commissioner: Statement Content and Timing
AUNDB-A5
Notification to Affected Individuals: Methods and Content

How this is calculated

Already covered means a mapping runs from a control in GDPR to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition