Frameworks · Levels

CMMC Level 1 vs. Level 2: FCI vs. CUI

Fifteen basic safeguards or 110 requirements. Which one applies is decided by the data in your contracts, and most machine shops hold more CUI than they think.

FAR 52.204-21 NIST SP 800-171 Rev 2 32 CFR 170.15–170.16

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 1CMMC Level 2
ProtectsFCICUI (including CTI and export-controlled data)
Source requirementsFAR 52.204-21NIST SP 800-171 Rev 2
Requirements15 (17 in the CMMC practice numbering)110 / 320 objectives
Assessment todayAnnual self-assessmentSelf-assessment (Phase 1) or C3PAO, every 3 years
ScoreMet / not met, all requiredSPRS score, −203 to 110
POA&M allowedNoYes, limited: score ≥ 88, eligible controls only, 180 days
AffirmationAnnual, senior officialAnnual, 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 dataUsuallyWhy
Purchase order, delivery schedule, invoiceFCIContract information not intended for public release, not CUI-designated.
Statement of work without technical dataFCIUnless marked or containing controlled technical information.
Technical drawings with distribution statements B–FCUIControlled Technical Information (CTI) category.
CAD models, STEP / IGES files, CAM programs derived from themCUIDerivatives of CTI inherit its controls.
ITAR / EAR export-controlled technical dataCUIExport Controlled category; also ITAR access limits to U.S. persons.
DD Form 254 and classified-program correspondenceCUIOften marked; treat as CUI unless the contracting officer says otherwise.
Inspection reports and first-article data for a controlled partCUIContain dimensions and tolerances from CTI.

Decision rules when you are not sure

  1. 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.
  2. Look at the markings. CUI banners, distribution statements B through F, and export-control legends are strong signals.
  3. 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.
  4. 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.

Scoping review

Scope your CUI boundary before you sign the next affirmation.

A scoping review maps where CUI actually lives, scores your environment against all 110 requirements, and prices the enclave path that fits your headcount.

  • 01Boundary and asset inventory against 32 CFR § 170.19
  • 02SPRS score check and POA&M eligibility
  • 03Enclave fit: GCC High, PreVeil or Cuick Trac
  • 04Introductions to vetted RPOs and C3PAOs