88% of Privacy Act 1988 (Australia) you already have
GDPR already covers about 88% of Privacy Act 1988 (Australia), leaving
1 of 8 controls as genuinely new work.
Already covered 0
Likely covered 7
New work 1
No control in GDPR
maps directly to one in Privacy Act 1988 (Australia). Everything counted as covered is covered because both
map to the same third standard, which is what a crosswalk is, but it is an inference rather
than a lookup.
What is genuinely new work
Nothing in GDPR reaches these. This is the list to scope.
AUPRV-2APP 2-5 Anonymity, Solicited/Unsolicited Collection, Notification
Show the 7 you already have
AUPRV-1APP 1 Open and Transparent Management + Privacy Management Framework
AUPRV-3APP 6-9 Use/Disclosure, Direct Marketing, Cross-Border, Government Identifiers
AUPRV-4APP 10-11 Quality, Security of Personal Information
AUPRV-5APP 12-13 Access and Correction of Personal Information
AUPRV-6Sensitive Information, PIA, Privacy by Design, Children
AUPRV-7Notifiable Data Breaches (NDB) Scheme, Incident Response
AUPRV-8OAIC Cooperation, Vendor Management, Training, Complaints, Enforcement
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