Most Level 2 contractors know the 110 requirements but underestimate the assessment mechanics: scoring, POA&M eligibility, evidence hashing, affirmations and what a C3PAO actually records. This guide covers how a CMMC Level 2 assessment works under 32 CFR Part 170 and DFARS 252.204-7021, from scoping and readiness through the Findings Report, Conditional and Final status, POA&M closeout and annual affirmation. It also covers the current programme status, because the DoD paused CMMC in Phase 1 in July 2026, which changes what contractors face today but not how the rule defines a certification assessment. It is written for compliance leads, IT and security managers at defence industrial base suppliers, and the consultants who prepare them. For the requirement families, Rev. 2 versus Rev. 3 and SPRS basics, start with the NIST SP 800-171 and CMMC 2.0 Guide; this page goes deeper on the assessment itself.
Key takeaways
- Check the status before planning spend. On 13 July 2026 the DoD suspended Phase II (due 10 November 2026) and set up a reform task force; the DoD CIO says implementation is paused in Phase 1, so solicitations currently require Level 2 self-assessments, while the rule text for C3PAO assessments remains in 32 CFR 170.17.
- Every requirement must end MET. A Conditional status needs a score of at least 80 per cent of the maximum and only POA&M-eligible gaps, and every POA&M item must be closed by a closeout assessment within 180 days or the status expires.
- The SSP is a gate, not a document. Without a current System Security Plan (CA.L2-3.12.4) the assessment cannot be completed, and the SSP name, date and version are recorded in CMMC eMASS.
- Evidence is hashed and kept for six years. The C3PAO records artefact names, hash values and the hashing algorithm; the contractor must retain the hashed artefacts for six years from the CMMC Status Date.
- Affirmations carry the long-term risk. A senior Affirming Official must affirm continuing compliance in SPRS after each assessment and closeout and annually, for each CMMC UID, and that includes the service accounts, keys and cloud identities inside the boundary.
What it is and who it applies to
CMMC Level 2 verifies that a contractor has implemented the 110 security requirements of NIST SP 800-171 Rev. 2 on the information systems that process, store or transmit Controlled Unclassified Information (CUI). The programme rule is 32 CFR Part 170; the contract clause is DFARS 252.204-7021 (NOV 2025 version, published at 90 FR 43575 on 10 September 2025). The clause requires the contractor to have and maintain a current CMMC status at the level the contracting officer specifies for every system used in performance that handles FCI or CUI, and to process that information only on systems holding that status.
There are two ways to reach Level 2:
- Level 2 (Self): the organisation assesses itself, posts the result in SPRS, repeats every three years and affirms annually.
- Level 2 (C3PAO): an authorised or accredited CMMC Third-Party Assessment Organisation assesses the organisation seeking certification (OSC) and submits results to the CMMC instantiation of eMASS, which passes them to SPRS. A Final Level 2 status is current for up to three years, with affirmations no older than one year.
| Item | Position checked 27 October 2026 | Source |
|---|---|---|
| Phase I (self-assessments in solicitations) | Began 10 November 2025; still in effect | DoD CIO About CMMC page |
| Phase II (Level 2 C3PAO requirements) | Scheduled for 10 November 2026; suspended 13 July 2026 | DoD CIO About CMMC page |
| Reform task force | Established 13 July 2026 to review the programme | DoD CIO About CMMC page |
| Enforcement during the pause | SP 800-171 Rev. 2 through self-assessments and select government-led assessments; DFARS 252.204-7012 still applies | DoD CIO About CMMC page |
| C3PAO assessment rules | Still in 32 CFR 170.17, 170.21 and 170.22 | eCFR |
The pause may end, or the rule may change after the task force review. Organisations that will need a C3PAO assessment, or that choose one voluntarily to strengthen their position with primes, should prepare to the rule as written and watch the DoD CIO page. Primes still flow the clause down: subcontractors handling FCI or CUI (other than COTS suppliers) must hold the required status and complete affirmations before award and annually.
Structure and key requirements
Assessment basis and scoring
The C3PAO assesses against NIST SP 800-171A (June 2018), using examine, interview and test methods against each assessment objective, within the scope defined in 32 CFR 170.19. Each requirement is MET, NOT MET or NOT APPLICABLE; an objective assessed as N/A counts as MET. Scoring under 170.24 starts at the maximum (one point per requirement, 110) and subtracts the point value of each NOT MET requirement, so a score can go negative.
| Rule | What it means in the assessment |
|---|---|
| 5, 3 and 1 point values | 5 for requirements whose failure could lead to significant exploitation or CUI exfiltration, 3 for confined effects, 1 for limited or indirect effects |
| IA.L2-3.5.3 multi-factor authentication | 3 points lost if MFA covers only remote and privileged users; 5 points if no MFA at all |
| SC.L2-3.13.11 FIPS-validated cryptography | 3 points lost if encryption is used but not FIPS-validated; 5 if no encryption |
| CA.L2-3.12.4 System Security Plan | Must exist and be current, or the assessment cannot be completed |
| Temporary deficiency | Assessed MET if covered by an operational plan of action with reviews and progress |
| Enduring exception | Assessed MET if described in the SSP with its mitigations |
Conditional and Final status
A Final Level 2 (C3PAO) status requires every requirement MET, either at the initial assessment or after a POA&M closeout assessment. A Conditional status is possible when the gaps meet the POA&M rules in 170.21:
- Minimum score: the assessment score divided by the total number of Level 2 requirements must be at least 0.8 (88 of 110).
- Never on a POA&M: AC.L2-3.1.20 (external connections), AC.L2-3.1.22 (publicly accessible content), CA.L2-3.12.4 (SSP), PE.L2-3.10.3, PE.L2-3.10.4 and PE.L2-3.10.5 (escorting, physical access logs and physical access devices).
- 1-point items only: no requirement on the POA&M may carry a point value above 1, with one exception: SC.L2-3.13.11 may be included where encryption is used but is not FIPS-validated (a 3-point deduction).
- Closeout: a C3PAO must perform a POA&M closeout assessment and post results within 180 days of the Conditional CMMC Status Date. If it does not happen, the Conditional status expires, normal contractual remedies apply and the OSC cannot receive new awards needing Level 2 (C3PAO) for that scope.
Cloud and external service providers
CUI in a cloud offering requires the offering to be FedRAMP Moderate (or higher) authorised or to meet equivalent requirements under DoD policy, and the customer responsibility matrix (CRM) items must be documented or referenced in the SSP. A non-cloud External Service Provider (for example, a managed security provider) must be documented in the SSP with its service description and responsibility matrix, and the ESP services used to meet requirements are assessed within the OSC's scope. In both cases the OSC's on-premises connection to the provider is in scope. See the FedRAMP Guide.
Identity and NHI requirements
Identity requirements carry many of the 5-point values and are where assessors most often find incomplete coverage, because SP 800-171 applies to "users, processes acting on behalf of users, and devices", not only to people. In practice, non-human identities fail objectives that human accounts pass.
| Requirement (Rev. 2) | Human-account evidence usually ready | NHI evidence assessors ask for |
|---|---|---|
| 3.1.1 Limit access to authorised users, processes and devices | Joiner, mover and leaver records, directory groups | Inventory of service accounts, API keys, app registrations and workload identities in scope, each with an owner and purpose |
| 3.1.5 Least privilege | Role definitions, admin group membership | Permission review of service principals and automation accounts; no standing domain or tenant admin for scripts |
| 3.5.1 and 3.5.2 Identify and authenticate users, processes, devices | SSO and MFA configuration | How each process authenticates (certificate, managed identity, key), and where the secret lives |
| 3.5.3 MFA | Conditional access or IdP policy | Justification for non-interactive accounts excluded from MFA, and compensating controls (network restriction, workload identity) |
| 3.5.10 Cryptographically protected passwords | Directory hashing settings | No plaintext credentials in scripts, scheduled tasks or configuration files; vault use |
| 3.3.1 and 3.3.2 Audit logging and traceability | Sign-in logs | Logs that attribute automated actions to a named identity, not a shared account |
- Security Protection Assets: identity providers, privileged access tools, vaults and the SIEM provide security functions to the boundary, so they are in scope as Security Protection Assets and are assessed against the requirements relevant to what they do. A cloud vault or IdP outside the FedRAMP-authorised estate is a common late surprise.
- Shared and generic accounts: a shared "svc_backup" used by three administrators fails individual accountability. Split interactive use from automation and record which tool owns each credential. See the Service Account Inventory Template.
- AI tools in the enclave: an AI assistant or agent with access to CUI repositories is a process acting on behalf of users. It needs an identity, least-privilege scopes and logging like any other process, and the SSP must describe it. See Audit Readiness for AI Agents and NHIs.
Valid account abuse (MITRE ATT&CK T1078 Valid Accounts) is the attacker path these requirements exist to block, which is why assessors test that dormant and orphaned non-human accounts are actually disabled rather than only listed.
Implementation steps
- Confirm the requirement. Read the solicitation and contract for the CMMC level and assessment type, and check the DoD CIO page for the current phase. Decide whether a C3PAO assessment is required now, expected later, or voluntary.
- Fix the scope. Classify every asset using the 170.19 categories (below), draw the network diagram and decide whether to use an enclave. See the CMMC Scoping Guide.
- Bring the SSP current. Describe how each requirement is implemented, every enduring exception and its mitigation, each ESP and CSP with its responsibility matrix, and the asset inventory. See the System Security Plan Template and Guide.
- Run an internal assessment to 800-171A objectives. Score honestly with 170.24 point values. Anything below 88, or any gap in the never-on-POA&M list, must be fixed before booking.
- Assemble and freeze evidence. Build an evidence index by objective (policy, configuration export, screenshot, log sample, interview owner). Use a NIST-approved hash such as SHA-256 and record the algorithm.
- Book a C3PAO and hold a pre-assessment. Agree scope, CAGE codes, the SSP version, logistics, interviewees and the on-site or remote test plan. Do not change the SSP version during the assessment without telling the lead assessor.
- Support the assessment. Provide named owners for each family and live demonstrations for test objectives. If a requirement is found NOT MET, new evidence may be considered during the assessment and for 10 business days after the active period, provided the Findings Report has not been delivered.
- Close POA&M items and affirm. Remediate within the 180-day window, schedule the closeout assessment early, then have the Affirming Official affirm in SPRS. Set the annual affirmation date in the compliance calendar.
Rollback and contingency: if remediation for a POA&M item will not complete in time, plan for expiry rather than hoping for an extension. Keep a narrower enclave option ready, so that a smaller CUI scope can be reassessed quickly if the broad scope cannot be closed out.
Evidence and assessment
Scoping categories and how each is assessed
| Category (170.19) | Examples | Assessment treatment |
|---|---|---|
| CUI Assets | File servers, M365 GCC High tenant, engineering workstations | Assessed against all Level 2 requirements |
| Security Protection Assets | IdP, EDR console, SIEM, vault, PAM tool, MSSP SOC | Assessed against the requirements relevant to the capability provided |
| Contractor Risk Managed Assets | Assets that could hold CUI but are prevented by policy and practice | SSP review; limited spot check only if the assessor has questions |
| Specialized Assets | OT, IIoT, test equipment, government-furnished equipment | Inventory, SSP treatment and network diagram; SSP review only |
| Out-of-Scope Assets | Systems physically or logically separated from CUI; KVM-only VDI endpoints | Not assessed, but the OSC must justify why they cannot handle CUI |
What the C3PAO records
The eMASS submission includes the assessment date, level and unique identifier, the C3PAO and each assessor, the CAGE codes in scope, the SSP name, date and version, the CMMC Status Date, the result for each requirement objective, POA&M usage, and the artefact names with hash values and algorithm. The contractor keeps the hashed artefacts for six years. Practically, this means:
- Evidence must be reproducible: store the exact files that were hashed, in a write-once or access-controlled repository, so that a later DIBCAC review can match hashes.
- Interview evidence needs owners: objectives such as account review or incident handling are confirmed by interview; nominate staff who actually do the work.
- Test evidence needs a live system: MFA prompts, account lockout, session termination and log generation are often demonstrated, not screenshotted.
After the assessment: detection and measurement
A status is only as good as the next affirmation, and a DCMA DIBCAC assessment can override it. Track these measures monthly:
- Self-score drift: the internal 170.24 score re-run quarterly; any drop below the last assessed score is an issue for the Affirming Official.
- Open POA&M days remaining: days to the 180-day closeout deadline per item.
- Scope changes: new systems, SaaS tools or ESPs added since the SSP version assessed.
- NHI hygiene: percentage of in-scope non-human identities with a named owner, and number of credentials older than the rotation standard.
- Affirmation timeliness: days until each CMMC UID's annual affirmation falls due.
- Subcontractor coverage: percentage of CUI-handling subcontractors with a current status and affirmation in SPRS.
Mapping to other frameworks
| CMMC Level 2 assessment element | NIST SP 800-53 Rev. 5 | NIST CSF 2.0 | ISO/IEC 27001:2022 |
|---|---|---|---|
| System Security Plan | PL-2 System Security and Privacy Plans | GV.OC-03 | Clause 6.1.3 (Statement of Applicability) |
| Assessment and scoring | CA-2 Control Assessments | ID.IM-02 | Clause 9.2 internal audit |
| POA&M | CA-5 Plan of Action and Milestones | ID.IM-02 | Clause 10.2 nonconformity and corrective action |
| Annual affirmation and ongoing compliance | CA-7 Continuous Monitoring | GV.OC-03 | Clause 9.1 monitoring and measurement |
| Identity and account requirements | AC-2, AC-6, IA-2, IA-5 | PR.AA-01, PR.AA-05 | Annex A 5.15, 5.16, 5.18, 8.5 |
| Asset inventory for scoping | CM-8 System Component Inventory | ID.AM-01 | Annex A 5.9 |
| Logging | AU-2 Event Logging | PR.PS-04 | Annex A 8.15 |
| Subcontractor flow-down | SR-3 Supply Chain Controls and Processes | GV.SC-07 | Annex A 5.19, 5.20 |
SP 800-171 Rev. 3 maps directly to SP 800-53 controls, but CMMC Level 2 still assesses Rev. 2 numbering (for example IA.L2-3.5.3, where Rev. 3 uses 03.05.03). Keep the SSP in Rev. 2 numbering for the assessment and keep a Rev. 3 crosswalk for future change. See the NIST SP 800-171A Rev 3 Assessment Guide and the DFARS 252.204-7012 Guide.
Common pitfalls
- Booking the C3PAO before the self-score is real: organisations that score themselves at 110 on paper then find six or seven NOT MET items, drop below 88 and leave with no status at all. Run a mock assessment by someone independent first.
- A stale or generic SSP: template language that describes intended controls, not the deployed configuration, fails CA.L2-3.12.4, which cannot be put on a POA&M and stops the assessment.
- Forgetting Security Protection Assets: the MSSP, cloud IdP or vault that protects the enclave is in scope. If its provider cannot supply a responsibility matrix and evidence, the objectives it covers fail.
- Treating service accounts as out of scope: shared admin accounts, embedded passwords in scripts and non-expiring API keys fail identification, authentication and least-privilege objectives. Third-party identity compromise is a recurring path into suppliers, as the Schneider Electric Jira breach illustrates: an infostealer-infected machine held credentials for Jira migration accounts.
- Missing the 180-day window: remediation is often finished but the closeout assessment is not scheduled in time. The Conditional status then expires regardless of the actual state.
- Affirming without checking: the annual affirmation is a statement by a senior official that all requirements are implemented and maintained across the scope. Signing it from memory, after scope has grown, creates False Claims Act exposure.
Practitioner checklist
- Check the DoD CIO CMMC page and the contract clause for the current phase and assessment type before committing budget.
- Classify every asset in the 170.19 categories and record CUI flows on a current network diagram.
- Bring the SSP to the deployed state, including enduring exceptions, ESP and CSP responsibility matrices and the SSP version to be assessed.
- Score internally with 170.24 point values and close every gap that would leave the score below 88 or touch the never-on-POA&M list.
- Inventory all in-scope non-human identities with owner, purpose, authentication method and secret location.
- Build a hashed evidence index by assessment objective and store artefacts for six years.
- Name an Affirming Official, set annual affirmation dates per CMMC UID and require a sign-off pack before each affirmation.
- Schedule any POA&M closeout assessment well inside 180 days and keep an enclave fallback.
- Confirm each CUI-handling subcontractor's status and affirmation in SPRS before award and annually.
Standards and references
- eCFR: 32 CFR 170.17 Level 2 certification assessment and affirmation requirements
- eCFR: 32 CFR 170.21 Plan of Action and Milestones requirements
- eCFR: 32 CFR 170.24 CMMC Scoring Methodology
- eCFR: 32 CFR 170.19 CMMC scoping
- eCFR: 32 CFR 170.22 Affirmation
- eCFR: DFARS 252.204-7021 Contractor Compliance with the CMMC Level Requirements
- DoD CIO: About CMMC
- NIST: SP 800-53 Rev. 5
Related NHI Mgmt Group resources: NIST SP 800-171 and CMMC 2.0 Guide · CMMC Scoping Guide · CUI Guide · Service Account Inventory Template. This guide summarises the CMMC Level 2 assessment rules in 32 CFR Part 170 and DFARS 252.204-7021 and is not legal advice.