Framework overlap

Does AICPA Privacy Management Framework (PMF) cover Data Protection Act 2017?

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

32% of Data Protection Act 2017 you already have

AICPA Privacy Management Framework (PMF) already covers about 32% of Data Protection Act 2017, leaving 15 of 22 controls as genuinely new work.

Already covered 0 Likely covered 7 New work 15

No control in AICPA Privacy Management Framework (PMF) maps directly to one in Data Protection Act 2017. 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-DPA17-s14-20
Registration of controllers and processors
MU-DPA17-s22-23
Duties of controller and collection of personal data
MU-DPA17-s25-26
Notification and communication of a personal data breach
MU-DPA17-s27
Duty to destroy personal data
MU-DPA17-s33
Record of processing operations
MU-DPA17-s34-35
Data protection impact assessment and prior consultation
MU-DPA17-s37
Right of access
MU-DPA17-s38
Automated individual decision making
MU-DPA17-s39
Rectification, erasure or restriction of processing
MU-DPA17-s4-5
Data Protection Office and functions of the Commissioner
MU-DPA17-s40-41
Right to object and exercise of rights
MU-DPA17-s42-43
Offences and penalties (unlawful disclosure)
MU-DPA17-s44
Exceptions and restrictions
MU-DPA17-s45-48
Annual report, compliance audit, codes and certification
MU-DPA17-s6-13
Investigation, enforcement notices and powers of the Commissioner
Show the 7 you already have
MU-DPA17-s21
Principles relating to processing of personal data
MU-DPA17-s24
Conditions for consent
MU-DPA17-s28
Lawful processing
MU-DPA17-s29
Special categories of personal data
MU-DPA17-s30
Personal data of a child
MU-DPA17-s31
Security of processing
MU-DPA17-s36
Transfer of personal data outside Mauritius

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