
CMMC Level 2 requires a defense contractor that handles controlled unclassified information (CUI) to meet all 110 security requirements in NIST SP 800-171 Revision 2. Since the Department of War suspended Phase II on July 13, 2026, Level 2 is met by a self-assessment every three years, scored in SPRS and affirmed every year by a senior official.
We checked the Department of War CIO's CMMC pages on October 10, 2026: Phase II remains suspended. Our CMMC compliance services scope where CUI lives, build the controls and write the System Security Plan; we are not a C3PAO and certify no one. This is general information, not legal advice.
Who needs CMMC Level 2?
Any company that will process, store or transmit CUI on its own systems while performing a defense contract or subcontract. The CMMC program rule, 32 CFR Part 170, applies to primes and subcontractors at every tier: a subcontractor that handles only federal contract information (FCI) needs Level 1, and one that handles CUI needs at least Level 2 (Self). Our CMMC glossary entry explains the program as a whole.
CUI is government information that a law, regulation or government-wide policy requires or permits to be handled with safeguarding or dissemination controls, such as drawings or specifications marked CUI. If a prime sends you files like that, ask in writing which CMMC level the subcontract carries. If you only handle non-public contract information, read our CMMC Level 1 checklist instead.
What are the 110 CMMC Level 2 requirements?
Level 2 uses the 110 requirements of NIST SP 800-171 Revision 2, grouped into 14 families that CMMC calls domains. NIST withdrew Revision 2 on May 14, 2024, when it published Revision 3, but the Department still applies Revision 2 for both CMMC and DFARS 252.204-7012. Our NIST SP 800-171 glossary entry explains the standard itself, and our CMMC vs NIST 800-171 comparison explains how the program and the standard relate.
| Family | Requirements | What it covers |
|---|---|---|
| Access Control (AC) | 22 | Authorized users and devices, least privilege, separate admin accounts, remote and wireless access, encrypting CUI on mobile devices |
| Awareness and Training (AT) | 3 | Security awareness, role-based training, insider threat awareness |
| Audit and Accountability (AU) | 9 | Audit logs that trace actions to users, log review, alerts when logging fails, protected logs |
| Configuration Management (CM) | 9 | Baseline configurations, approved changes, least functionality, application allow or deny lists, control of user-installed software |
| Identification and Authentication (IA) | 11 | Unique identifiers, multifactor authentication, replay-resistant authentication, password rules, no reuse of identifiers |
| Incident Response (IR) | 3 | An incident handling capability, tracking and reporting incidents, testing the response |
| Maintenance (MA) | 6 | Controlled maintenance and tools, sanitizing equipment removed for repair, MFA for remote maintenance, supervising maintenance staff |
| Media Protection (MP) | 9 | Protecting, marking and sanitizing media with CUI, encrypting portable storage, controlling removable media, protecting backups |
| Personnel Security (PS) | 2 | Screening people before access, protecting CUI when staff leave or transfer |
| Physical Protection (PE) | 6 | Limiting and monitoring physical access, escorting visitors, access logs, safeguards at alternate work sites |
| Risk Assessment (RA) | 3 | Periodic risk assessments, vulnerability scans, remediation |
| Security Assessment (CA) | 4 | Assessing controls, plans of action, ongoing monitoring, the System Security Plan |
| System and Communications Protection (SC) | 16 | Boundary protection, deny by default, no split tunneling, separate subnetworks for public systems, FIPS-validated encryption for CUI in transit and at rest |
| System and Information Integrity (SI) | 7 | Flaw remediation, malware protection and scans, security alerts, monitoring for attacks and unauthorized use |
A self-assessment checks every assessment objective in NIST SP 800-171A; miss one, and the whole requirement is scored as not met. For a requirement-by-requirement working list, use our NIST 800-171 checklist.
How is CMMC Level 2 assessed during the Phase II suspension?
On July 13, 2026 the Department of War suspended Phase II, which was due to start on November 10, 2026. The Department of War CIO's CMMC page says that all Phase I self-assessment requirements remain in place. The implementing memo says that during the suspension, program offices may only require CMMC Level 1 (Self) or Level 2 (Self), may not designate Level 2 (C3PAO) or Level 3 (DIBCAC) assessments, and will grant no waivers. Contracts that already carry a C3PAO or DIBCAC requirement are to have it removed at the next option period or administrative modification, so check yours.
The memo also says the Department will enforce NIST SP 800-171 Revision 2 through self-assessments and select government-led assessments, and that DFARS 252.204-7012 remains in effect, including its 72-hour cyber incident reporting. Third-party assessment by a C3PAO still exists in the rule, every three years, but no new contract can require it during the suspension. The memo promised further guidance at the end of the CIO's 60-day review; as of October 10, 2026, the CIO's CMMC pages had posted none. Our post on the CMMC Phase II suspension tracks what changes next.
How is a Level 2 self-assessment scored in SPRS?
The CMMC scoring method in 32 CFR 170.24 starts at the maximum, 110, and subtracts the value of each requirement that is not met: 5, 3 or 1 points, depending on how much risk the gap creates. The score can go negative, and partial credit exists only in limited cases, such as multifactor authentication. A requirement that does not apply counts as met, and evidence must be in final form: drafts and unapproved policies do not count.
Enter the results in the Supplier Performance Risk System (SPRS): the level, date, scope, CAGE codes and overall score, such as 105 out of 110. A senior person, the Affirming Official, then affirms compliance in SPRS, again after any POA&M closeout and every year after that. Keep the evidence for six years from the status date.
What are the POA&M limits for Level 2?
A plan of action and milestones (POA&M) lets you hold a Conditional Level 2 (Self) status while you close a few gaps, but only within limits set by 32 CFR 170.21:
- Your score must be at least 80% of the maximum, which is 88 of 110.
- No requirement on the POA&M may be worth more than 1 point, except CUI encryption (SC.L2-3.13.11) when you encrypt with cryptography that is not FIPS-validated.
- Six requirements can never go on a POA&M: external connections (AC.L2-3.1.20), control of public information (AC.L2-3.1.22), the System Security Plan (CA.L2-3.12.4), and escorting visitors, physical access logs and managing physical access (PE.L2-3.10.3 to 3.10.5).
- You must close every item and complete a closeout self-assessment of those items within 180 days, or the conditional status expires.
What goes in the System Security Plan?
Requirement CA.L2-3.12.4 asks for a System Security Plan (SSP) that describes the system boundary, the environments it runs in, how each requirement is implemented and its connections to other systems. NIST prescribes no format and offers a CUI SSP template with Revision 2. Write it from the configuration you deployed: for each requirement, name the setting, the procedure and the evidence, and keep the asset inventory and network diagram the scoping rule expects beside it. The SSP can never sit on a POA&M, and an enduring exception it documents, with its mitigations, is assessed as met.
How does an enclave shrink the scope?
Every asset that processes, stores or transmits CUI is assessed against all 110 requirements, so the cheapest Level 2 is usually the smallest one. 32 CFR 170.19 sorts assets into five categories:
| Asset category | What it is | How it is assessed |
|---|---|---|
| CUI assets | Systems that process, store or transmit CUI | Against all Level 2 requirements |
| Security protection assets | Tools that protect the scope, such as the firewall, identity provider or monitoring | Against the requirements relevant to what they do |
| Contractor risk managed assets | Systems that could handle CUI but are kept from it by policy and practice | Documented in the SSP; an assessor may run a limited check |
| Specialized assets | IoT, operational technology, test equipment and government-furnished equipment | Documented and managed under your risk-based policies |
| Out-of-scope assets | Systems that cannot handle CUI and are physically or logically separated | Not assessed; be ready to justify why they cannot handle CUI |
An enclave puts CUI, and the people who need it, into a separate environment, such as a dedicated cloud tenant or a segmented network, so most of the company falls out of scope. A cloud service that holds CUI must be FedRAMP Moderate authorized or meet equivalent requirements, and which Microsoft 365 environment fits (commercial, GCC or GCC High) depends on the data you hold. Our CMMC certification cost guide shows how scope drives the budget.
CMMC Level 2 checklist: what should be ready before you self-assess?
Before you score yourself, check that each of these exists in final form, because drafts do not count as evidence:
- A written assessment scope: where CUI arrives and goes, an asset inventory sorted into the five categories above, and a current network diagram.
- A System Security Plan that says how each of the 110 requirements is implemented, with the boundary and connections described.
- Policies and procedures for all 14 families, approved and dated.
- Configuration evidence exported from your identity, device management, firewall, logging and backup systems, with dates visible.
- FIPS-validated encryption for CUI in transit and at rest. Encryption that is not FIPS-validated can sit on a POA&M, the one exception to the 1-point limit.
- Operating records: training completions, incident response test results, vulnerability scans and the tickets that fixed what they found.
- A scored self-assessment against every NIST SP 800-171A objective, with a POA&M only where 32 CFR 170.21 allows one.
- An Affirming Official who has reviewed the evidence before affirming in SPRS.
Which official CMMC Level 2 documents should you use?
Work from the primary documents rather than a vendor's summary of them:
| Document | Published by | What it gives you |
|---|---|---|
| CMMC Assessment Guide, Level 2 (version 2.13, September 2024, PDF) | Department of War CIO | The assessment objectives for each requirement and the examine, interview and test methods. Self-assessments are expected to use the same criteria as third-party assessments. |
| CMMC Scoping Guidance, Level 2 (PDF) | Department of War CIO | How to sort assets into the five categories and draw the boundary |
| NIST SP 800-171A (June 2018) | NIST | The assessment procedures behind every objective. NIST withdrew it in 2024 along with Revision 2, but 32 CFR Part 170 still cites the June 2018 version. |
| NIST SP 800-171 Rev. 2 supplemental material | NIST | The security requirements as a spreadsheet and a CSV file, plus Word templates for the System Security Plan and the plan of action |
| Configure Microsoft Entra ID for CMMC compliance | Microsoft Learn | Identity settings for the Level 2 access control, identification and authentication, and other identity-related requirements. Microsoft notes that companies still have to complete the other configurations and processes CMMC requires. |
What is a realistic sequence for reaching Level 2?
- Confirm the data. Read each contract and flow-down, and ask the prime in writing whether you will receive CUI.
- Map where CUI goes and draw the boundary.
- Assess the gaps against the NIST SP 800-171A objectives.
- Fix the 5-point requirements first. They move the score most and can never go on a POA&M.
- Write the SSP from the deployed configuration.
- Self-assess with the 32 CFR 170.24 method, using a POA&M only where the rule allows.
- Enter and affirm in SPRS.
- Operate it: monitor and patch all year, affirm annually and reassess within three years.
Our pages for government contractors and manufacturers cover the rest of their IT.
Frequently asked questions
What is CMMC Level 2?
CMMC Level 2 is the middle level of the Department of War's Cybersecurity Maturity Model Certification program, for contractors that process, store or transmit CUI. It requires all 110 requirements of NIST SP 800-171 Revision 2, which 32 CFR 170.14 makes identical to the Level 2 requirements, and today it is met by a self-assessment every three years with an affirmation every year.
What is CMMC Level 2 certification?
It is the third-party version of Level 2. Under 32 CFR 170.17, an authorized or accredited C3PAO assesses the company against the same 110 requirements and enters the results through the CMMC instance of eMASS, which passes them to SPRS, giving a Final or Conditional Level 2 (C3PAO) status that must be renewed every three years. The rule still contains it, but during the Phase II suspension no new contract may require it, so contracts call for Level 2 (Self) instead.
Is CMMC Level 2 certification required right now?
Not by any new contract. During the Phase II suspension, contracts may require only Level 1 (Self) or Level 2 (Self), and C3PAO requirements are to come out of existing contracts. The 110 requirements still apply. We checked this on October 10, 2026.
How often is a CMMC Level 2 self-assessment required?
Every three years, with an affirmation by your Affirming Official at each assessment and every year in between. The Department of War CIO's CMMC page says an assessment lapses if the annual affirmation is missed.
What SPRS score do you need for CMMC Level 2?
A final Level 2 (Self) status needs every requirement met, a score of 110, with requirements that do not apply counted as met. A score of at least 88 can earn a conditional status if the open items meet the POA&M rules, but they must be closed and reassessed within 180 days.
What happens in a CMMC Level 2 assessment?
Whoever assesses, the method is the same. The Level 2 assessment guide has the assessor examine documents and configurations, interview the people who run the controls and test that the controls work, against every NIST SP 800-171A objective. A requirement counts as met only when all of its objectives are met. In a self-assessment your own team does this and enters the score in SPRS; in a C3PAO assessment the assessor records a result for each objective.
What is the difference between CMMC Level 2 and Level 3?
Level 3 adds 24 selected requirements from NIST SP 800-172 on top of Level 2, and 32 CFR Part 170 says the Department will generally reserve it for contracts supporting its most critical programs and technologies. The government assesses it, through DCMA's DIBCAC, and a Final Level 2 (C3PAO) status for the same scope is a prerequisite. During the Phase II suspension no contract may designate a Level 3 assessment.
Sources and further reading
- Department of War CIO: Cybersecurity Maturity Model Certification: the Phase II suspension notice, checked October 10, 2026.
- Department of War CIO: About CMMC: Level 2 self-assessment, POA&M and affirmation, checked October 10, 2026.
- Implementing Suspension of CMMC Phase II, July 13, 2026 memo (PDF), checked October 10, 2026.
- 32 CFR Part 170, CMMC Program, eCFR: unchanged since December 16, 2024, including the Level 2 certification and Level 3 sections, checked October 10, 2026.
- CMMC Assessment Guide, Level 2, version 2.13 (PDF) and CMMC Scoping Guidance, Level 2 (PDF): assessment methods and scoping, checked October 10, 2026.
- CMMC Model Overview, version 2.13 (PDF): the 14 domains and 110 requirements, checked October 7, 2026.
- NIST SP 800-171 Rev. 2: withdrawn May 14, 2024, still the CMMC baseline, with the requirements spreadsheet and the SSP and plan of action templates, checked October 10, 2026.
- NIST SP 800-171A (June 2018): assessment procedures for the requirements, withdrawn May 14, 2024 and still cited by 32 CFR Part 170, checked October 10, 2026.
- Microsoft Learn: Configure Microsoft Entra ID for CMMC compliance, checked October 10, 2026.
- DFARS 252.204-7012: incident reporting and cloud requirements, checked October 7, 2026.
Related reading
Also on this topic: CMMC Level 1 Checklist: The 15 Requirements Explained · POA&M Template and System Security Plan Template, With Examples
Discuss cmmc 2.0 compliance services for your business.
Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.

