Framework overlap

Does AICPA Privacy Management Framework (PMF) cover Mauritius DPA?

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

88% of Mauritius DPA you already have

AICPA Privacy Management Framework (PMF) already covers about 88% of Mauritius DPA, leaving 1 of 8 controls as genuinely new work.

Already covered 0 Likely covered 7 New work 1

No control in AICPA Privacy Management Framework (PMF) maps directly to one in Mauritius DPA. 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.

MU-DPA-Scope-Act-20-2017-Assent-18-December-2017-Effective-15-January-2018-DPO-Mauritius-Convention-108
Mauritius DPA Scope + Act 20 of 2017 + Assent 18 December 2017 + Effective 15 January 2018 + DPO Mauritius + Convention 108+
Show the 7 you already have
MU-DPA-Cross-Border-Transfer-Section-36-Adequacy-SCC-BCR-Mauritius-Global-Business-IBC-Financial-Services
Mauritius DPA Cross-Border + Section 36 + Adequacy + SCC + BCR + Mauritius Global Business + Financial Services
MU-DPA-Data-Subject-Rights-Sections-26-33-Access-Rectification-Erasure-Restriction-Portability-Objection
Mauritius DPA Subject Rights + Sections 26 to 33 + Access + Rectification + Erasure + Restriction + Portability + Objection
MU-DPA-Enforcement-Commissioner-Section-41-43-MUR-200K-5-Year-Prison-ICT-Appeal-Tribunal-Supreme-Court
Mauritius DPA Enforcement + Commissioner + Section 41 + Section 43 + MUR 200K + 5 Year Prison + ICT Appeal Tribunal + Supreme Court
MU-DPA-Governance-DPO-Designation-Section-25-DPO-ROPA-DPIA-Codes-Section-38-Commissioner-Registration
Mauritius DPA Governance + DPO + ROPA + DPIA + Codes Section 38 + Commissioner Registration
MU-DPA-Security-Breach-Notification-Section-25-BREACH-72-Hour-Commissioner-Cyber-Security-Strategy
Mauritius DPA Security + Breach Notification + Section 25-BREACH + 72 Hour + Commissioner + Cyber Security Strategy
MU-DPA-Sensitive-Personal-Data-Section-24-Health-Biometric-Genetic-Sexual-Section-25-Children-16
Mauritius DPA Sensitive Data + Section 24 + Health + Biometric + Genetic + Sexual + Section 25 + Children 16
MU-DPA-Seven-Principles-Section-21-Lawfulness-Purpose-Minimisation-Accuracy-Storage-Integrity-Accountability
Mauritius DPA Seven Principles + Section 21 + Lawfulness + Purpose + Minimisation + Accuracy + Storage + Integrity + Accountability

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