Framework overlap

Does PCI PIN Security cover Privacy Act 2020?

You hold PCI PIN Security and have been told to do Privacy Act 2020. Here is how much overlaps, control by control.

75% of Privacy Act 2020 you already have

PCI PIN Security already covers about 75% of Privacy Act 2020, leaving 2 of 8 controls as genuinely new work.

Already covered 0 Likely covered 6 New work 2

No control in PCI PIN Security maps directly to one in Privacy Act 2020. 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 PCI PIN Security reaches these. This is the list to scope.

NZPRV-1
IPP 1-4 Purpose, Source, Collection from Subject, Manner of Collection
NZPRV-4
IPP 9-10 Retention, Limits on Use
Show the 6 you already have
NZPRV-2
IPP 5 Storage and Security of Personal Information
NZPRV-3
IPP 6-8 Access, Correction, Accuracy
NZPRV-5
IPP 11-12 Disclosure, Cross-Border Disclosure (Schedule 8)
NZPRV-6
IPP 13 Unique Identifiers, Privacy Impact Assessment, Privacy by Design
NZPRV-7
Notifiable Privacy Breach Scheme
NZPRV-8
Privacy Officer, OPC Cooperation, Compliance Notices, Complaints, Training

How this is calculated

Already covered means a mapping runs from a control in PCI PIN Security 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