Framework overlap

Does AICPA Privacy Management Framework (PMF) cover ESRB Privacy Certified?

You hold AICPA Privacy Management Framework (PMF) and have been told to do ESRB Privacy Certified. Here is how much overlaps, control by control.

15% of ESRB Privacy Certified you already have

AICPA Privacy Management Framework (PMF) already covers about 15% of ESRB Privacy Certified, leaving 17 of 20 controls as genuinely new work.

Already covered 0 Likely covered 3 New work 17

No control in AICPA Privacy Management Framework (PMF) maps directly to one in ESRB Privacy Certified. 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 AICPA Privacy Management Framework (PMF) reaches these. This is the list to scope.

ESRB-PC-01
COPPA Safe Harbor program eligibility and Seal selection
ESRB-PC-02
Initial certification assessment and ESRB review
ESRB-PC-03
Ongoing compliance reports, spot audits and annual recertification
ESRB-PC-04
Use of the certification Seal
ESRB-PC-05
Complaint handling and dispute resolution mechanism
ESRB-PC-06
Online Privacy Notice (privacy policy)
ESRB-PC-07
Direct Notice to parents
ESRB-PC-09
Material change notification
ESRB-PC-11
Internal Operations Exception scope
ESRB-PC-12
Parental access, review and deletion rights
ESRB-PC-13
Data retention and secure deletion
ESRB-PC-14
Third-party and SDK due diligence
ESRB-PC-16
Incident handling and ESRB notification
ESRB-PC-17
Behavioural advertising and targeted-advertising controls
ESRB-PC-18
Age screening and mixed-audience determination
ESRB-PC-19
Geolocation and persistent identifiers
ESRB-PC-20
User-generated content, photos, video, audio and moderation
Show the 3 you already have
ESRB-PC-08
Verifiable Parental Consent (VPC)
ESRB-PC-10
Data minimisation for child personal information
ESRB-PC-15
Confidentiality, security and integrity of child PI

How this is calculated

Already covered means a mapping runs from a control in AICPA Privacy Management Framework (PMF) 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