The one-sentence difference
Level 1 protects Federal Contract Information (FCI), information provided by or generated for the government under a contract that is not intended for public release. Level 2 protects Controlled Unclassified Information (CUI), information the government has designated in the CUI Registry as requiring safeguarding or dissemination controls. The level is set by the most sensitive data you receive, not by your company size.
| CMMC Level 1 | CMMC Level 2 | |
|---|---|---|
| Protects | FCI | CUI (including CTI and export-controlled data) |
| Source requirements | FAR 52.204-21 | NIST SP 800-171 Rev 2 |
| Requirements | 15 (17 in the CMMC practice numbering) | 110 / 320 objectives |
| Assessment today | Annual self-assessment | Self-assessment (Phase 1) or C3PAO, every 3 years |
| Score | Met / not met, all required | SPRS score, −203 to 110 |
| POA&M allowed | No | Yes, limited: score ≥ 88, eligible controls only, 180 days |
| Affirmation | Annual, senior official | Annual, senior official |
| Typical 3-year cost (small firm) | $5k–$30k | $75k–$150k+ |
Level 1: the FAR 52.204-21 basic safeguards
FAR 52.204-21 lists 15 basic safeguarding requirements, which CMMC splits into 17 practices. They cover authorized users, transaction limits, external connections, public posting, identification and authentication, media sanitization, physical access and visitor control, boundary protection, public-facing subnetworks, flaw remediation, malicious-code protection and updates, and scanning. Every one of them maps to a NIST SP 800-171 requirement, and most carry 5 points in the SPRS methodology. A Level 1 contractor that later receives CUI is starting from a real foundation, not from zero.
Level 1 does not allow a POA&M. You either implement all practices or you cannot affirm.
Level 2: the full NIST SP 800-171 Rev 2 baseline
Level 2 requires all 110 requirements across 14 families, assessed through the 320 objectives of NIST SP 800-171A. The score is calculated with the DoD Assessment Methodology, posted to SPRS, and must be at least 88 for Conditional status, with the remaining items closed within 180 days. Six requirements can never be deferred: 3.1.20 3.1.22 3.12.4 3.10.3 3.10.4 3.10.5. See the POA&M rules and run the SPRS calculator.
32 CFR Part 170 still references NIST SP 800-171 Revision 2, even though NIST published Revision 3 in May 2024. Assess against Rev 2 until the rule or a class deviation says otherwise.
FCI or CUI? Real examples from the shop floor
| Document or data | Usually | Why |
|---|---|---|
| Purchase order, delivery schedule, invoice | FCI | Contract information not intended for public release, not CUI-designated. |
| Statement of work without technical data | FCI | Unless marked or containing controlled technical information. |
| Technical drawings with distribution statements B–F | CUI | Controlled Technical Information (CTI) category. |
| CAD models, STEP / IGES files, CAM programs derived from them | CUI | Derivatives of CTI inherit its controls. |
| ITAR / EAR export-controlled technical data | CUI | Export Controlled category; also ITAR access limits to U.S. persons. |
| DD Form 254 and classified-program correspondence | CUI | Often marked; treat as CUI unless the contracting officer says otherwise. |
| Inspection reports and first-article data for a controlled part | CUI | Contain dimensions and tolerances from CTI. |
Decision rules when you are not sure
- Read the contract. DFARS 252.204-7012 in the contract means the government expects covered defense information; 252.204-7021 states the CMMC level directly.
- Look at the markings. CUI banners, distribution statements B through F, and export-control legends are strong signals.
- Ask the prime or contracting officer in writing. Primes are required to tell you what CUI they flow down. Keep the answer in your SSP evidence.
- When in doubt, scope it in. Under-scoping is how contractors end up affirming controls that do not cover the data. Then shrink scope deliberately with an enclave; see the scoping guide.