All articles · Compliance

CMMC 2.0: the DoD cyber framework explained for teams used to ANSSI

The three CMMC levels, what they share with the ANSSI IT hygiene guide, the gaps to address at scoping, and ten tips to prepare for the assessment.

If you are a subcontractor, even at tier 2 or 3, on a US Department of Defense (DoD) program, CMMC 2.0 already applies to you. Since November 10, 2025, CMMC clauses have been entering DoD contracts, and prime contractors flow them down their entire supply chain, Europe included.

The good news for teams already working with the French ANSSI frameworks: much of the way is already covered. This article introduces CMMC, shows what it shares with the ANSSI IT hygiene guide, and ends with ten practical tips to prepare for an assessment.

CMMC 2.0 in brief

CMMC (Cybersecurity Maturity Model Certification) is how the DoD verifies that its suppliers protect the information it entrusts to them. It is codified in federal regulation 32 CFR Part 170 and creates no new requirements: it enforces existing controls and organizes how they are verified.

Two types of information determine the required level:

  • FCI (Federal Contract Information): any non-public information related to a contract;
  • CUI (Controlled Unclassified Information): sensitive unclassified information, a rough equivalent of the French Diffusion Restreinte marking.
LevelInformationFrameworkRequirementsAssessment
1 – FoundationalFCIFAR 52.204-2115 requirements (17 practices)Annual self-assessment
2 – AdvancedCUINIST SP 800-171 Rev. 2110 requirements, 14 domainsSelf-assessment or third party (C3PAO)
3 – ExpertCUI on critical programsSelection of NIST SP 800-17224 requirements on top of Level 2DoD assessment (DIBCAC)

The core of the program is Level 2. Its 110 requirements are verified through 320 assessment objectives (NIST SP 800-171A). About two thirds are technical: access control, MFA, logging, hardening, encryption, filtering. The rest is organizational: training, risk assessment, incident handling, system security plan (SSP).

Where things stand in November 2026

  • Phase 1 has been in force since November 10, 2025: Level 1 and Level 2 self-assessments, reported in the DoD SPRS system.
  • The move to Phase 2, which was to make third-party certification widespread from November 10, 2026, was suspended on July 13, 2026 while a reform task force carries out its work.
  • NIST has published revision 3 of SP 800-171 (97 requirements), but CMMC remains anchored on revision 2 until the transition rule is published.

A close cousin of the ANSSI frameworks

An organization that seriously applies the 42 measures of the ANSSI IT hygiene guide already covers about 80% of the 110 CMMC Level 2 practices. This is the result of our measure-by-measure mapping matrix:

Coverage by the hygiene guideCMMC Level 2 practicesOf which Level 1 practices
Full226
Partial689
Not covered202
Total11017

Both frameworks share the same logic: a closed list of measures, applicable to everyone, without the risk-based weighting of ISO 27001. Network segmentation, dedicated administration accounts, removable media, patching, logging: the same fundamentals appear on both sides.

The difference lies mainly in the level of requirement and evidence. Most mappings are “partial”: the ANSSI measure points in the right direction, but CMMC asks for a defined parameter, a written procedure and evidence the assessor can verify.

For French defense industrial base (BITD) companies, the IGI 1300 and II 901 instructions bring a very useful culture of information protection and security accreditation: the notion of a CUI scope is close to that of a Diffusion Restreinte information system.

Gaps to address at scoping

A few gaps are structural and deserve attention from the scoping stage:

  • Cryptography: CMMC requires FIPS 140 validated modules (NIST CMVP program). An ANSSI qualification does not substitute for it; there is no mutual recognition.
  • Multi-factor authentication: mandatory for all network access and privileged access, whereas the hygiene guide recommends it “where possible”.
  • Incident reporting: report to the DoD within 72 hours (DFARS clause 252.204-7012), with system images preserved.
  • Cloud: a service hosting CUI must be FedRAMP Moderate or equivalent. SecNumCloud alone is not enough.
  • Domains the guide barely covers: maintenance, media protection and marking, personnel screening, alerts on the logging chain.

10 tips to prepare for CMMC from an ANSSI baseline

  1. Identify your CUI flows first. Ask your prime contractor which CMMC level is targeted and which information is actually shared. Everything else follows from that.
  2. Reduce the scope. An enclave dedicated to CUI costs far less to bring into compliance than the whole information system. Your experience with accredited systems applies directly.
  3. Map against what you already have. Start from your ANSSI, ISO 27001 or accreditation measures: you will quickly identify the missing 20% instead of rebuilding everything.
  4. Write the SSP early. The system security plan is mandatory and serves as the assessor's guiding thread. Your accreditation file is an excellent starting point.
  5. Address FIPS cryptography from the start. Check the CMVP certificates of your VPNs, disk encryption and protocols. It is the most frequent gap among European manufacturers.
  6. Enforce MFA everywhere. All remote access, all privileged accounts and user network access: no “legacy” exceptions.
  7. Set every parameter in writing. Lockout duration, patching deadlines, logged events: many of the 320 objectives start with “the parameter is defined”.
  8. Vet your providers and cloud services. Managed service provider, SOC, email, storage: each one falls within the assessment scope, and a cloud hosting CUI must be FedRAMP Moderate or equivalent.
  9. Prepare the 72-hour incident report. Obtain a certificate to access the DoD DIBNet portal, build the report into your incident procedure and test it in an exercise.
  10. Run an independent pre-assessment. A mock assessment against the 320 objectives gives a realistic SPRS score and a prioritized plan of action (POA&M), before the official self-assessment or a C3PAO visit.

In summary

CMMC is not a leap into the unknown for a French organization used to ANSSI requirements: the technical baseline is largely shared. The effort lies in formalization, evidence and a few specifically American requirements such as FIPS 140, FedRAMP and reporting to the DoD.

Sources

← All articles