Checklist: CMMC Level 2 readiness and SPRS affirmations for defense contractors
Fourteen steps for a defense contractor’s contracts, security and executive leads, from finding the CMMC level each contract names to the scope, score, plan of action, Supplier Performance Risk System entries and annual affirmations that keep a company eligible, each tied to 32 CFR part 170 or DFARS 252.204-7021.
Who this is for
Companies, prime contractors and subcontractors alike, that will process, store or transmit Federal Contract Information or Controlled Unclassified Information on their own systems under a Department of Defense contract or subcontract [1]. The DFARS rule that put the CMMC clause into contracts took effect on November 10, 2025 [3], which is when Phase 1 of the phased rollout in 32 CFR 170.3(e) began. Phase 2 starts one calendar year after Phase 1; in it, DoD intends to add Level 2 (C3PAO) certification as a condition of award for applicable contracts, although it may delay that requirement to an option period [1]. As checked on November 14, 2026, DFARS Class Deviation 2026-O0025, Revision 3, signed September 3, 2026 (digital signature), carries forward a Department of War CIO memorandum of July 13, 2026 that suspends the November 2026 Phase 2 transition, permits Level 1 (Self) or Level 2 (Self) assessments in all procurement requests, and tells contracting officers to remove or revise CMMC requirements in new and existing solicitations and contracts [5]. The levels and the phase-in are set out in our explainer.
Scope of the steps
The steps cover Level 2, in both its self-assessment and third-party (C3PAO) forms. Each names the section of 32 CFR part 170 [1] or the paragraph of the clause at DFARS 252.204-7021 [2] it rests on, as published in the eCFR on November 12, 2026. Where a step is our suggestion, it says so. The owner shown is the role that usually holds the work; apart from the Affirming Official, the rule does not assign roles. Which level applies to a given contract is set by the contract, and questions on a specific contract belong with the Contracting Officer and counsel.
The checklist
Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.
Contracts manager
Paragraph (d)(1)(i) of the clause requires a current CMMC status at the level the Contracting Officer inserts, from Level 1 (Self) to Level 3 (DIBCAC), for every system that handles FCI or CUI in performance of the contract [2]. Section 170.3(d) leaves the choice of level to the program manager or requiring activity [1].
CISO or IT lead
Section 170.19(c) requires the scope to be specified before a Level 2 assessment; its Table 3 sorts assets into CUI assets, security protection assets, contractor risk managed assets, specialized assets and out-of-scope assets, and requires each in-scope category to appear in the asset inventory, the System Security Plan and the network diagram [1].
CISO with procurement
Sections 170.16(c)(2) and 170.17(c)(5) allow a cloud provider for CUI only if it is FedRAMP Authorized at Moderate or higher, or meets equivalent requirements under DoD policy; sections 170.16(c)(3) and 170.17(c)(6) require other external service providers to be documented and assessed within the scope [1].
CISO
Section 170.24 says the absence of an up-to-date plan at assessment means the assessment cannot be completed, and section 170.21(a)(2)(iii) bars the plan requirement (CA.L2-3.12.4) from any plan of action [1].
Security team
Sections 170.16(c)(1) and 170.17(c)(1) require assessment against NIST SP 800-171A and scoring under section 170.24, which subtracts 5, 3 or 1 points for each requirement NOT MET, credits partial implementation only for multi-factor authentication and FIPS-validated encryption, and accepts only evidence in final form [1]. Scoring yourself first is our suggestion.
CISO
Section 170.21(a)(2): a Conditional status needs a score of at least 80 percent of the Level 2 requirements, no plan item worth more than 1 point (except non-FIPS-validated encryption under SC.L2-3.13.11), and none of six named requirements, including the System Security Plan and three physical-access requirements [1].
CISO with the Affirming Official
Section 170.17(c)(4) requires artifacts to be hashed with a NIST-approved algorithm, the list and hash values given to the C3PAO for upload to the CMMC instance of eMASS, and the artifacts kept for six years; section 170.17(c)(2) allows NOT MET requirements to be re-evaluated for 10 business days after the active assessment if the findings report has not been delivered [1].
Chief executive
Sections 170.4 and 170.22(a)(1) define the Affirming Official as the senior representative responsible for CMMC compliance with authority to affirm it; section 170.22(a)(2) requires each affirmation to give that person’s name, title and contact details and a statement that all applicable requirements are implemented and will be maintained [1]. Recording the appointment in writing is our suggestion.
Compliance lead
Section 170.16(a)(1)(i) lists the SPRS inputs: level, status date, assessment scope, all CAGE codes in scope, overall score and plan of action status [1]. Clause paragraph (e)(2) requires current self-assessment results for each CMMC unique identifier not covered by a C3PAO or DIBCAC assessment [2]. DFARS 252.204-7019 requires a summary score not more than three years old, unless the solicitation sets a shorter period [4].
Contracts manager
Clause paragraph (e)(1) requires the identifiers SPRS issues, and any changes to them throughout the life of the contract, task order or delivery order [2].
Subcontracts and supply chain manager
Section 170.23: FCI only requires Level 1 (Self); CUI requires at least Level 2 (Self), or Level 2 (C3PAO) where the prime contract requires C3PAO or Level 3 [1]. Clause paragraphs (d)(4) and (f) require the clause to be flowed down and the subcontractor’s status and affirmation to be in place before award [2].
Compliance lead
The clause defines a Final Level 2 status as current for up to three years, with an affirmation no older than one year, and paragraph (d)(2) limits FCI and CUI to systems with the required status [2]. Section 170.16(c)(4) requires self-assessment artifacts to be kept for six years from the status date [1]. The calendar is our suggestion.
Spotted an error? Tell us and we will check it and correct the checklist where needed.