The level is set by the data you handle, not the size of your company. If a contract involves only Federal Contract Information (FCI), you need CMMC Level 1: 15 basic safeguards, self-assessed every year, no POA&M allowed. If it involves Controlled Unclassified Information (CUI), you need Level 2: all 110 requirements of NIST SP 800-171 Rev 2, assessed either by you or by a C3PAO — the solicitation says which.
How the DoD decides which level a contract gets
Under the CMMC rule (32 CFR Part 170, effective December 16, 2024) and its contracting companion (48 CFR, effective November 10, 2025), the program office — the DoD, now also styled the Department of War — picks the level based on the type of information the contractor will process, store, or transmit. The contracting officer writes that level into the solicitation, and the DFARS 252.204-7021 clause carries it into the contract.
- FCI is information provided by or generated for the Government under contract that isn’t intended for public release — invoices, schedules, routine correspondence. Almost every DoD contractor handles FCI.
- CUI is information the Government requires to be safeguarded under law, regulation, or policy — drawings marked CUI, export-controlled technical data, controlled technical information (CTI). If the contract carries DFARS 252.204-7012, you are almost certainly handling CUI.
Put simply: FCI only → Level 1. Any CUI → Level 2 (or Level 3 for a small set of high-priority programs).
CMMC Level 1 at a glance
| Requirements | 15 safeguards, identical to FAR 52.204-21 |
|---|---|
| Assessed by | You (self-assessment) |
| How often | Annually, with a senior-official affirmation in SPRS |
| POA&M allowed? | No. All 15 must be MET to claim Level 1 |
| Typical cost driver | Documenting what you already do; MFA and patching discipline |
Level 1 is “basic cyber hygiene”: limit system access to authorized users, sanitize media, escort visitors, patch, run antivirus, and so on. Most small businesses already do most of it; the work is proving it consistently and signing the affirmation knowing a false claim is a False Claims Act exposure.
CMMC Level 2 at a glance
| Requirements | 110 security requirements from NIST SP 800-171 Revision 2 |
|---|---|
| Assessed by | Self-assessment or a Certified Third-Party Assessment Organization (C3PAO) — the solicitation specifies which |
| How often | Every 3 years, plus an annual affirmation in SPRS |
| POA&M allowed? | Yes, within strict limits — minimum score 88/110, only 1-point items, closed within 180 days. See What can go on a CMMC POA&M |
| Typical cost driver | FIPS-validated encryption, MFA everywhere CUI lives, logging and review, a real System Security Plan, incident response, and the evidence to prove each one |
Level 2 is where the effort lives. The 110 requirements span 14 families — access control, audit and accountability, configuration management, identification and authentication, incident response, media protection, physical protection, risk assessment, security assessment, system and communications protection, system and information integrity, awareness and training, maintenance, and personnel security — and each requirement has assessment objectives that must all be met for the requirement to count.
Level 2 self-assessment vs. Level 2 C3PAO: who decides?
The DoD does, contract by contract. The rule describes a four-phase rollout:
| Phase | Starts | What can be required |
|---|---|---|
| 1 | Nov 10, 2025 | Level 1 (self) or Level 2 (self) in new solicitations; DoD may require Level 2 (C3PAO) at its discretion |
| 2 | Nov 10, 2026 | Level 2 (C3PAO) in applicable new solicitations |
| 3 | Nov 10, 2027 | Level 2 (C3PAO) also as a condition for exercising option periods; Level 3 requirements begin |
| 4 | Nov 10, 2028 | Full implementation in all applicable solicitations and contracts |
Status as of October 2026: on July 13, 2026 the Department CIO issued a memorandum suspending the Phase 2 transition and launching a 60-day CMMC Reform Task Force; Class Deviation 2026-O0025 Revision 3 (September 3, 2026) carried that into contracting. Practically: contracting officers may still require Level 1 (Self) or Level 2 (Self) in solicitations, but the November 10, 2026 C3PAO-certification trigger is paused until the Department says otherwise. The rule itself, 32 CFR Part 170, is unchanged, and its November 10, 2028 full-implementation date is still on the books. The Task Force delivered its recommendations internally in mid-September; public release is pending.
What that means for a CUI handler: the level you need hasn’t changed — CUI is still Level 2 — and the 110 requirements are still a contract obligation today under DFARS 252.204-7012. What’s paused is who signs off. Build to Level 2 now; treat the assessor question as a scheduling decision, not a reason to wait.
Where Level 3 fits
Level 3 adds 24 enhanced requirements selected from NIST SP 800-172 on top of a completed Level 2 (C3PAO) certification, and is assessed by the Government (DCMA’s DIBCAC), not a C3PAO. It’s reserved for programs the DoD considers highest-priority. If you don’t already know your program is a Level 3 candidate, it almost certainly isn’t.
Three questions that tell you which level you need
- Does your contract include DFARS 252.204-7012? If yes, the Government expects you to protect CUI → Level 2.
- Do you receive, create, or store anything marked CUI, ITAR/EAR technical data, or controlled technical information? Include drawings, specs, test data, and anything your prime forwards from the program. Any yes → Level 2.
- What does the solicitation say? From November 2025 onward, the CMMC level is stated in the solicitation. When in doubt, ask the contracting officer in writing — the answer is contractual, not a judgement call.
Mistakes we see most often
- “We’re small, so we’re Level 1.” Size is irrelevant. A five-person machine shop that receives a CUI-marked drawing is a Level 2 organization.
- “Level 1 is trivial.” It’s small, not trivial. Every one of the 15 requirements must be fully met — there is no POA&M — and the affirmation is a legal statement.
- “We’ll scope the CUI out later.” Scoping is the single biggest cost lever, but it has to be done honestly and before the assessment. A CUI enclave that your engineers quietly work around is worse than no enclave.
- “Our prime will handle it.” Primes flow the requirement down. They don’t absorb it.
Side-by-side comparison
| Level 1 | Level 2 | Level 3 | |
|---|---|---|---|
| Information | FCI | CUI | CUI on high-priority programs |
| Requirements | 15 (FAR 52.204-21) | 110 (NIST SP 800-171 Rev 2) | 110 + 24 (NIST SP 800-172 subset) |
| Assessor | Self | Self or C3PAO | DIBCAC (Government) |
| Cadence | Annual | Triennial + annual affirmation | Triennial + annual affirmation |
| POA&M | Not permitted | Limited (≥88/110, 1-point items, 180 days) | Limited |
