Checklist

CMMC 2.0 readiness checklist

Nineteen steps from “does this apply to us?” to a defensible affirmation, each tied to the regulation or standard it comes from. Tick items as you go; progress is saved in this browser only.

1 · Applicability and level

  1. Federal Contract Information (FCI) points to Level 1; Controlled Unclassified Information (CUI) points to Level 2 or higher. Check contract documents and markings, and the CUI Registry for categories.23

  2. Look for DFARS 252.204-7021 in solicitations and contracts and note the CMMC status it requires: Level 1 (Self), Level 2 (Self), Level 2 (C3PAO) or Level 3 (DIBCAC).45

  3. Phase 1 began November 10, 2025. Phase 2 (planned for November 10, 2026) is suspended pending a DoW review, so check the DoW CIO page before planning around C3PAO dates.12

  4. Primes must flow the CMMC requirement to subcontractors that will process, store or transmit FCI or CUI, at the level appropriate to the information flowed down.4

2 · Scope

  1. Classify assets as CUI assets, Security Protection Assets, Contractor Risk Managed Assets, Specialized Assets or Out-of-Scope assets. Specialized Assets explicitly include OT, IoT/IIoT, government property, restricted information systems and test equipment.6

  2. Document where CUI flows and consider isolating it into an enclave to shrink the assessment scope. Keep a current network diagram.67

  3. Identify every ESP and CSP that touches CUI or security functions. Cloud services that store, process or transmit CUI must meet the FedRAMP Moderate baseline or equivalent.829

3 · Implement and document

  1. Implement the requirements in FAR 52.204-21 for systems that hold FCI. POA&Ms are not permitted at Level 1.1011

  2. CMMC Level 2 is aligned to NIST SP 800-171 Rev 2. Rev 3 (97 requirements) is published, but DoD Class Deviation 2024-O0013 keeps DFARS 252.204-7012 contractors on Rev 2 for now.121314

  3. The SSP describes the boundary, environment and how each requirement is met. It is one of the requirements that can never be placed on a POA&M.1211

  4. Use NIST SP 800-171A objectives and the DoW CMMC assessment guide to test each requirement the way an assessor would, and keep the evidence.157

  5. Level 3 adds 24 enhanced requirements from NIST SP 800-172 and requires a Final Level 2 (C3PAO) status first.162

4 · Score, affirm and report

  1. Requirements are weighted 1, 3 or 5 points; a perfect Level 2 score is 110.17

  2. A Conditional Level 2 status needs a score of at least 80% (88 of 110), only 1-point items on the POA&M (with a narrow FIPS-encryption exception), none of the excluded requirements, and closeout within 180 days.11

  3. Post assessment results in the Supplier Performance Risk System. DFARS 252.204-7019/7020 separately require a current NIST SP 800-171 DoD Assessment score in SPRS.1819

  4. A senior Affirming Official must affirm compliance after each assessment and annually; status lapses if annual affirmation is missed.201

5 · Operate

  1. DFARS 252.204-7012 requires reporting cyber incidents to DoD via DIBNet within 72 hours of discovery (a DoD-approved medium assurance certificate is needed) and preserving images and relevant data for at least 90 days.821

  2. Level 2 self-assessments are repeated every three years; Level 1 annually. Changes to the boundary or environment should trigger an SSP update.12

  3. If production lines, test benches or building systems touch CUI, they are Specialized Assets: document them in the inventory, SSP and diagrams, and protect them with OT-appropriate controls (see NIST SP 800-82r3).622

Sources

  1. DoW CIO, About CMMC (Phase 2 suspension notice, Jul 13, 2026)
  2. 32 CFR Part 170, Cybersecurity Maturity Model Certification (CMMC) Program (eCFR)
  3. DoD CUI Registry
  4. DFARS 252.204-7021, Contractor Compliance with the CMMC Level Requirements
  5. DFARS CMMC final rule (DFARS Case 2019-D041), Federal Register, Sep 10, 2025
  6. 32 CFR 170.19, CMMC scoping (eCFR)
  7. DoW CIO, CMMC Resources & Documentation (assessment and scoping guides)
  8. DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting
  9. FedRAMP Marketplace
  10. FAR 52.204-21, Basic Safeguarding of Covered Contractor Information Systems
  11. 32 CFR 170.21, Plan of Action and Milestones requirements (eCFR)
  12. NIST SP 800-171 Rev. 2, Protecting CUI in Nonfederal Systems
  13. NIST SP 800-171 Rev. 3 (May 2024)
  14. DFARS Class Deviation 2024-O0013, Revision 1 (NIST SP 800-171 Rev 2 for DFARS 252.204-7012)
  15. NIST SP 800-171A, Assessing Security Requirements for CUI
  16. NIST SP 800-172, Enhanced Security Requirements for Protecting CUI
  17. 32 CFR 170.24, CMMC scoring methodology (eCFR)
  18. Supplier Performance Risk System (SPRS)
  19. DFARS 252.204-7019, Notice of NIST SP 800-171 DoD Assessment Requirements
  20. 32 CFR 170.22, Affirmation (eCFR)
  21. DIBNet, DoD cyber incident reporting portal
  22. NIST SP 800-82 Rev. 3, Guide to Operational Technology (OT) Security (Sep 2023)

Educational summary, not legal advice. Always confirm requirements against the current regulation and your contract.