Framework overlap

Does PCI SSF cover Maryland Online Data Privacy Act of 2024?

You hold PCI SSF and have been told to do Maryland Online Data Privacy Act of 2024. Here is how much overlaps, control by control.

50% of Maryland Online Data Privacy Act of 2024 you already have

PCI SSF already covers about 50% of Maryland Online Data Privacy Act of 2024, leaving 4 of 8 controls as genuinely new work.

Already covered 0 Likely covered 4 New work 4

No control in PCI SSF maps directly to one in Maryland Online Data Privacy Act of 2024. 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 SSF reaches these. This is the list to scope.

MD-MODPA-Enforcement-Maryland-AG-Brown-CPD-Section-14-4613-10K-Per-Violation-Consumer-Protection-Act
Maryland MODPA Enforcement + Maryland AG + CPD + Section 14-4613 + USD 10K Per Violation + Consumer Protection Act
MD-MODPA-Notice-Section-14-4605-Categories-Purposes-Rights-Sale-Disclosure-Biometric-Health
Maryland MODPA Privacy Notice + Section 14-4605 + Categories + Purposes + Rights + Sale Disclosure + Biometric Health
MD-MODPA-Scope-SB541-Title-14-Subtitle-46-Sections-14-4601-14-4614-Effective-1-October-2025-AG-Brown
Maryland MODPA Scope + SB541 + Title 14 Subtitle 46 + Sections 14-4601 to 14-4614 + Effective 1 October 2025 + AG Brown
MD-MODPA-Universal-Opt-Out-Section-14-4604-GPC-Global-Privacy-Control-Recognition-Mandatory
Maryland MODPA Universal Opt-Out + Section 14-4604 + Global Privacy Control + Mandatory Recognition
Show the 4 you already have
MD-MODPA-Consumer-Rights-Section-14-4603-Access-Correction-Deletion-Portability-Opt-Out-Appeal
Maryland MODPA Consumer Rights + Section 14-4603 + Access + Correction + Deletion + Portability + Opt-Out + Appeal
MD-MODPA-Controller-Duties-Security-DPA-Section-14-4608-14-4609-Processor-Contract-Assessment
Maryland MODPA Controller Duties + Section 14-4608 + Section 14-4609 + Processor Contract + DPA
MD-MODPA-Pseudonymisation-De-Identification-Section-14-4610-4611-Internal-Research-Aggregated
Maryland MODPA Pseudonymisation + De-Identification + Section 14-4610 + 14-4611 + Internal Research + Aggregated
MD-MODPA-Sensitive-Data-Health-Biometric-Section-14-4607-Reasonably-Necessary-Proportionate-Data-Minimization
Maryland MODPA Data Minimization + Sensitive + Health + Biometric + Section 14-4607 + Reasonably Necessary + Proportionate

How this is calculated

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