Cross-Framework Mapping

Minnesota Consumer Data Privacy ActvsISO 28001:2007 Supply Chain Security Management

See exactly how Minnesota Consumer Data Privacy Act controls map to ISO 28001:2007 Supply Chain Security Management. Pre-computed mappings, identified gaps, and coverage analysis.

2
Controls Mapped
6
Gaps Found
12%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

Minnesota Consumer Data Privacy Act maps to ISO 28001:2007 Supply Chain Security Management with 12% coverage across 1 directly mapped controls. Analysis of 8 Minnesota Consumer Data Privacy Act controls identifies 7 compliance gaps — primarily concentrated in Enforcement Sanctions and Data Broker Registration - Minnesota CDPA.

Source: TheArtOfService Knowledge Graph | 8 controls analysed | 706 frameworks | 324K+ cross-framework mappings

Control Mappings

Showing 2 of 2 mapped controls across 1 domains. Sign up to explore all 324K+ mappings across 706 frameworks.

Chief Privacy Officer Governance - Minnesota CDPA(2 mappings)

MN-CDPA-Chief-Privacy-Officer-Section-325O-06-MN-UNIQUE-Designation-Privacy-Programme-TrainingMinnesota CDPA Chief Privacy Officer + Section 325O.06 + MINNESOTA-UNIQUE Designation + Privacy Programme + Training2 targets
ISO28001-PC-04Supply Chain Continuity Planning
ISO28001-PS-01Facility Security

Related Comparisons

Other Minnesota Consumer Data Privacy Act comparisons

Other ISO 28001:2007 Supply Chain Security Management comparisons

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 706 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 706 framework browser
  • Cross-framework mappings (324K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between Minnesota Consumer Data Privacy Act and ISO 28001:2007 Supply Chain Security Management?

Minnesota Consumer Data Privacy Act has 8 controls across its framework, while ISO 28001:2007 Supply Chain Security Management covers 36 controls. Direct mapping analysis identifies 1 overlapping controls (12% coverage). The frameworks diverge most significantly in Enforcement Sanctions and Data Broker Registration - Minnesota CDPA, where 1 Minnesota Consumer Data Privacy Act controls have no direct ISO 28001:2007 Supply Chain Security Management equivalent.

How many controls map between Minnesota Consumer Data Privacy Act and ISO 28001:2007 Supply Chain Security Management?

Of 8 total Minnesota Consumer Data Privacy Act controls, 1 map directly to ISO 28001:2007 Supply Chain Security Management controls — representing 12% coverage. The remaining 7 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping Minnesota Consumer Data Privacy Act to ISO 28001:2007 Supply Chain Security Management?

7 Minnesota Consumer Data Privacy Act controls have no direct equivalent in ISO 28001:2007 Supply Chain Security Management. The highest concentration of gaps is in Enforcement Sanctions and Data Broker Registration - Minnesota CDPA with 1 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between Minnesota Consumer Data Privacy Act and ISO 28001:2007 Supply Chain Security Management?

The domain with the highest gap count is Enforcement Sanctions and Data Broker Registration - Minnesota CDPA (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.