The U.S. and EU are converging on a similar conclusion: Cybersecurity can no longer be self-declared. Each has selected their own unique path. The U.S. has introduced the Cybersecurity Maturity Model Certification (CMMC) and the EU is using the NIS2 Directive. Both raise the bar for organizations handling sensitive data or critical infrastructure, yet they differ sharply in structure, enforcement and compliance methodologies.
Framework vs. regulation
CMMC is a defense-specific certification program built on a fixed technical foundation: NIST SP 800-171's 110 security requirements for Level 2, verified through self-assessment or certified third-party assessment organization (C3PAO) audit. NIS2 is different; it’s a directive that EU Member States transpose into national law, without a fixed control checklist. Article 21 sets out measures that are technology-neutral and outcomes-based. In fact, the directive specifies what to achieve, scaled to an organization's size and risk exposure, leaving each member state and entity to determine how.
Legal analysts summarize the difference plainly: NIS2 is a regulation, but concrete control mechanisms are largely lacking. CMMC ties directly to a specific, prescriptive framework, which gives CMMC a clearer technical bar to hit. NIS2 gives entities more flexibility, and more ambiguity about what "compliant" looks like.
What Article 21 of the NIS2 directive actually asks for
Article 21(2) prescribes 10 minimum risk-management measures, covering access control, multi-factor authentication, network segmentation, encryption, incident handling, business continuity and supply-chain security, including a direct obligation under Article 21(2)(d) to assess suppliers' cybersecurity posture and development practices. Both frameworks require flow-down of security expectations to vendors and subcontractors, and both mandate security-awareness training for personnel.
Where these measures diverge sharply is enforcement. NIS2 backs its requirements with financial penalties, including up to €10 million or 2% of global turnover for essential entities, plus explicit personal accountability for management bodies that can't be delegated away. CMMC's enforcement mechanism is different: Non-compliance doesn't trigger a fine, it triggers exclusion from contract award entirely.
How organizations are actually closing the gap
In practice, few organizations build two parallel compliance programs. Side-by-side analysis shows CMMC Level 2 and NIS2 Article 21 controls may overlap by roughly 60–80%, with most control domains fully aligned. Organizations which have already achieved ISO/IEC 27001 certification or built toward NIS2 compliance find they've addressed a significant share of CMMC's requirements, existing policies, technical controls and governance structures can often be adapted rather than rebuilt.
Legal advisors caution NIS2 readiness is not a substitute for CMMC certification. EU-based defense contractors selling into the U.S. supply chain still need control-level evidence, documented system boundaries and formal assessment readiness specific to CMMC. NIS2 accelerates that work without completing it.
For public-sector-adjacent vendors and private contractors alike, the practical response has been to build a single underlying security architecture, often centered on zero-trust-aligned access control and continuous monitoring, which maps to both frameworks' control domains, then layer the framework-specific documentation and assessment work on top. It's a more efficient path than treating CMMC and NIS2 as separate obligations, and it reflects where transatlantic cybersecurity regulation appears to be heading: Broadly aligned expectations, enforced through very different levers.
The bigger picture
Neither framework is static. CMMC's Phase 2 third-party assessment requirement was suspended by the Department of War in July 2026 pending a program review, even as the underlying NIST SP 800-171 obligations remain in force for contractors. NIS2, meanwhile, is still being transposed unevenly across Member States, meaning the exact shape of "compliant" continues to shift by jurisdiction. For companies operating on both sides of the Atlantic, this instability is itself a reason to invest in the shared 60–80% of controls now rather than waiting for either framework to fully settle or evolve.
CMMC started as a defense-contracting mandate, but the pressures behind it (breach costs, insurance economics, legal liability and growing government scrutiny) reach well beyond the defense industrial base. With cyberattacks on the rise, a strong posture isn’t just about keeping attackers out. It’s about preparing for the breach which eventually gets through, and knowing exactly what’s exposed when it does.
This is where data governance supports a prudent response. You can’t safeguard data you haven’t mapped. Collibra helps organizations govern their data and AI, so they know what they hold, where it lives and who can reach it. For government and regulated organizations, Collibra Platform for Government is FedRAMP Rev. 5 (NIST SP 800-53) compliant and built around security, which gives teams tighter control of their data boundary. Today, it’s unclear how the U.S. or the EU will resolve CMMC and NIS2, but knowing your data is the work that won’t change.
If you want to learn more about security frameworks and zero trust from a US Federal perspective, check out “How Zero Trust Can Ready Your Data for AI.”
- Bernard DepuydtBernard DepuydtSenior Account ExecutiveCollibra
Bernard Depuydt
Bernard Depuydt
Senior Account Executive
Collibra












