CMMC vs NIST SP 800-171: how they differ, and what CUI is
NIST SP 800-171 (often shortened to "NIST 800-171") is a set of security requirements for protecting Controlled Unclassified Information, or CUI, on a company's own systems.
CMMC is the Department of Defense program that checks whether a contractor has met the security requirements its contracts call for.
Is NIST 800-171 the same as CMMC?
Not quite. At Level 2 they share one set of requirements, and they do different jobs.
At Level 2, those are the 800-171 requirements: the CMMC rule calls them "identical to the requirements in NIST SP 800-171 R2." So 800-171 says what to do, DFARS clause 252.204-7012 puts it in your contract, and CMMC verifies it.
12NIST wrote 800-171 as recommended requirements for federal agencies to put into contracts. CMMC is the checking program. It sets who assesses, how the score is counted, how long a result lasts and who must affirm it.
| Point of comparison | NIST SP 800-171 | CMMC |
|---|---|---|
| What it is | NIST's security requirements for protecting CUI in nonfederal systems. | DoD's program for verifying that contractors meet required security. |
| Made binding by | DFARS 252.204-7012 in DoD contracts. | 32 CFR Part 170, put into contracts by DFARS 252.204-7021. |
| Information covered | CUI. | FCI at Level 1; CUI at Levels 2 and 3. |
| Requirements | Revision 2: 110, in 14 families. Revision 3: 17 families. | Level 1: 15, from FAR 52.204-21. Level 2: the 110 of 800-171 Revision 2. Level 3: 24, from NIST SP 800-172. |
| Revision DoD applies today | Revision 2. | Revision 2. |
| How it is checked | NIST sets the requirements and, in SP 800-171A, how to assess them. DoD does the checking: during the CMMC suspension, through self-assessments and select government-led assessments. | Self-assessment (Levels 1 and 2), a C3PAO (Level 2) or DCMA DIBCAC (Level 3), recorded in SPRS, the Supplier Performance Risk System. |
| Status, November 2026 | In force through DFARS 252.204-7012. | Phase 1 (self-assessment) in force; Phase 2 suspended since July 13, 2026. |
What NIST SP 800-171 is
NIST SP 800-171, from the National Institute of Standards and Technology, gives "recommended security requirements for protecting the confidentiality of CUI" in nonfederal systems, such as a contractor's own network. Revision 2 (February 2020, updated January 2021) sorts its 110 requirements into 14 families. Revision 3 (May 2024) uses 17 families, adds and removes requirements, and introduces organization-defined parameters. NIST withdrew Revision 2 on May 14, 2024, yet DoD still applies it.
123For defense contractors, the duty to follow 800-171 comes from DFARS clause 252.204-7012, which set an implementation deadline of December 31, 2017. The same clause requires you to report cyber incidents to DoD within 72 hours of discovery. A cloud provider that stores, processes or transmits covered defense information must meet security requirements equivalent to the FedRAMP Moderate baseline. The clause flows down to subcontracts that involve that information or operationally critical support.
2What CMMC is
CMMC, the Cybersecurity Maturity Model Certification program, is set out in 32 CFR Part 170. It verifies that defense contractors and subcontractors have put the required protections in place for Federal Contract Information (FCI) and CUI. The program rule took effect on December 16, 2024. A second rule put CMMC into contracts through DFARS clause 252.204-7021, and Phase 1 began when it took effect on November 10, 2025. Since September 2025 the Department of Defense may also call itself the Department of War, though statutes keep the Defense name.
14256The three levels
- Level 2
Covers CUI: the 110 requirements of NIST SP 800-171 Revision 2, assessed every three years. Either the company assesses itself, called Level 2 (Self), or an authorized or accredited third-party assessment organization does, called Level 2 (C3PAO). Only the C3PAO route comes with a certificate.
1
Contracting officers must check SPRS before award, and must not award a contract, task order, or delivery order to an offeror whose CMMC status is not posted there at the level the solicitation requires.
2Source: DFARS 240.371-4(b), Class Deviation 2026-O0025 (effective February 1, 2026; current revision Revision 3, September 3, 2026).
How the two fit together
Because Level 2 is identical to NIST SP 800-171 Revision 2, CMMC adds no Level 2 security requirements of its own. It adds rules for checking them, and it leaves DFARS 252.204-7012 in force.
1- Scoring.
Assessments follow NIST SP 800-171A (June 2018). Each unmet requirement takes its value of 1, 3 or 5 points off a maximum of 110, so a score can go negative. Two requirements lose 3 points instead of 5 when they are partly in place: multi-factor authentication used only for remote and privileged users, and encryption that is not FIPS-validated. Without an up-to-date system security plan, the assessment cannot be completed.
1 - Open gaps.
Not every gap can be deferred. A plan of action is not permitted at all at Level 1. At Level 2, a plan of action earns a conditional status only if your score is at least 88 of 110, every item on it is a 1-point requirement or CUI encryption that is in place but not FIPS-validated, and it does not carry the system security plan requirement or five other named requirements.
1Source: 32 CFR 170.21(a).
-
A conditional status runs on a clock: the plan of action must be closed out by a follow-up assessment within 180 days of the conditional status date, and if it is not, the conditional status expires.
12Source: 32 CFR 170.21(b).
-
An award can be made while a Level 2 status is still conditional. Level 1 requires a final status before award.
2Source: DFARS 240.371-3(b)(2), Class Deviation 2026-O0025 (effective February 1, 2026; current revision Revision 3, September 3, 2026).
- A named signer.
The affirmation is a person, not a company: a named senior official must affirm continuing compliance in SPRS after every assessment and annually after that.
1Source: 32 CFR 170.22(a).
Why CMMC uses Revision 2, not Revision 3
A federal rule that incorporates a standard by reference must name the exact edition it uses. DoD named Revision 2, citing the time industry and assessors need to prepare for a later one. It said Revision 3 "is not currently applicable to this rule" and committed to future amendments that adopt the current version. DoD's current version of DFARS 252.204-7012, issued under a 2026 class deviation, also names Revision 2.
427DoD has signalled a move. In April 2025 it published Revision 3 parameter values "in preparation to implement" it. The 2026 federal regulatory agenda lists a DoD amendment to 32 CFR Part 170 that would set a deadline and transition period for the move. As of this page's review date that amendment has not been published, so Revision 2 is what applies.
187Where CMMC stands in November 2026
On July 13, 2026 the Department of War suspended the November 2026 transition to CMMC Phase 2 and opened a 60-day review of the program. That review window has closed; the suspension remains in effect, and as of this page's review date the Department's CMMC library lists no further guidance. What that does NOT change: NIST SP 800-171 Rev 2 and DFARS 252.204-7012 still apply today, and CMMC Level 1 / Level 2 self-assessments still carry their contract designations. While the suspension lasts, program offices may not designate Level 2 (C3PAO) or Level 3 (DIBCAC) assessments. The Department still enforces NIST SP 800-171 Rev 2 through self-assessments and select government-led assessments. The underlying rules were not rescinded — the timeline was suspended.
125Source: Department of War Chief Information Officer memorandum, "Removing Barriers to Defense Industrial Base Expansion: Immediate Suspension and Strategic Review …," July 13, 2026, cleared for open publication (26-P-1023); implemented by the Under Secretary of War (Acquisition and Sustainment) memorandum of the same date.
Where an active solicitation names Level 2 (C3PAO) or Level 3 (DIBCAC), the Department has directed that the solicitation be amended to remove or revise it. In an existing contract, the requirement is to be removed by modification before the next option period is exercised or at the next scheduled administrative modification.
What is CUI?
CMMC uses the definition in 32 CFR 2002.4(h). CUI is information the Government creates or possesses, or that a company creates or possesses for the Government. What makes it CUI is that a law, regulation or Government-wide policy requires or permits safeguarding or dissemination controls on it. Classified information is never CUI. Nor is information a company holds in its own systems that did not come from, and was not created for, an executive branch agency or an entity acting for one.
19The CUI Registry, kept by the National Archives (NARA) and open to the public, is the authoritative list of categories and their markings. DoD also keeps its own CUI Registry, set up by DoD Instruction 5200.48.
9CUI Basic and CUI Specified
If the law, regulation or Government-wide policy behind a category requires protection but sets no specific controls, the information is CUI Basic and gets the uniform controls of 32 CFR Part 2002. If it spells out its own controls, the information is CUI Specified. Those controls may be stricter, or simply different. Specified information must name its category in the marking, as in CUI//SP-CTI.
9Examples of CUI
From the Registry:
- Controlled Technical Information (CTI):
Technical information with military or space application that is subject to controls on its use and release. Under DFARS 252.204-7012 it is CUI Specified, marked CUI//SP-CTI.
9 - Export Controlled:
Information on items, technology or software whose export could reasonably be expected to adversely affect US national security and nonproliferation objectives, including ITAR items. It is Basic or Specified, depending on the authority.
9 - General Proprietary Business Information:
Information about a company's products, business or activities, such as financial information, trade secrets, research and development, and product designs. It is CUI when it is held by or for the Government and a law, regulation or Government-wide policy calls for protecting it. It is Basic or Specified, depending on the authority. Your own business records are not CUI just because they are confidential.
9
CUI and FCI are not the same
FCI is non-public information provided by or generated for the Government under a contract to develop or deliver a product or service. It excludes information the Government makes public and simple transactional information, such as what is needed to process payments. FCI alone leads to Level 1, and CUI leads to Level 2 or higher.
12105How you know you hold CUI
DoD Instruction 5200.48 requires DoD to identify CUI in the contract and to mark it. Under DFARS 252.204-7012, covered defense information also includes CUI you develop, receive, use or store in support of the contract. Technical data your own engineers produce for a DoD job can qualify. Controlled technical information is to be marked with one of the distribution statements B through F under DoD Instruction 5230.24. A drawing or data package marked that way is a cue to check whether you hold CTI.
29What this means for your company
Look for these clauses in your contracts:
- DFARS 252.204-7012:
NIST SP 800-171 Revision 2, 72-hour incident reporting and the cloud rule. These stay in force during the CMMC suspension.
2 - DFARS 252.240-7997:
The NIST SP 800-171 DoD Assessment clause. It requires you to give the Government access to your facilities, systems and people if it needs to run a Medium or High assessment. Under the same class deviation, it replaced 252.204-7020.
2 - DFARS 252.204-7021:
The CMMC level you must hold. During the suspension, program offices may only name Level 1 (Self) or Level 2 (Self).
2
Next, find where your FCI and CUI live.
The required level covers every system that processes, stores or transmits them in performance of the contract. Outside providers count too. A provider that handles only your security data, such as logs or configuration, still counts as an External Service Provider. Its services are assessed as part of your assessment.
12Hyper Vigilance provides managed CMMC compliance. The work happens inside your own cloud tenant. You keep the tenant, its configuration, and the documentation and evidence produced for you; our tools stay ours. We keep it current between assessments.
Your tenant and your data are yours from day one, and everything we build runs on Microsoft 365's own tools inside it. The design keeps your CUI in your own tenant, not on our systems. What our systems handle, by design, is security data about your environment, such as logs and configuration, and that security data is what places our services inside your assessment scope. Under the CMMC rule, a provider whose systems hold your CUI either meets FedRAMP requirements as a cloud provider or has its services examined as part of your assessment. Certifying the provider itself is voluntary (32 CFR 170.19(c)(2)). Our services and people sit inside your assessment scope — your SSP, your Shared Responsibility Matrix, and your assessor interviews.
Where to start
Your contracts already decide which of today's rules reach you — the timeline everyone was planning around moved, and they did not. A scoping conversation tells you which ones.
Sources
- 32 CFR Part 170, Cybersecurity Maturity Model Certification (CMMC) Program (eCFR; unamended since December 16, 2024).
- DFARS 252.204-7012 and 252.204-7021 (eCFR); DFARS Class Deviation 2026-O0025, Revision 3 (September 3, 2026), including DFARS 252.240-7997 and FAR 52.240-93.
- NIST SP 800-171, Revision 2 (February 2020, updated January 2021), and its Revision 3 (May 2024); NIST SP 800-171A (June 2018); NIST SP 800-172 (February 2021) and its Revision 3 (May 2026).
- 89 FR 83092 (October 15, 2024), the CMMC Program final rule; 90 FR 43560 (September 10, 2025), the DFARS CMMC acquisition final rule.
- Department of War CMMC program pages (dowcio.war.gov/CMMC).
- Executive Order 14347, Restoring the United States Department of War (September 5, 2025).
- Unified Agenda of Federal Regulatory and Deregulatory Actions, 2026 (91 FR 52792), Department of War entry RIN 0790-AM01; 1 CFR 51.9.
- DoD memorandum on Revision 3 organization-defined parameters for NIST SP 800-171 (April 10, 2025).
- 32 CFR Part 2002, Controlled Unclassified Information; the CUI Registry (National Archives); DoD Instruction 5200.48; DoD Instruction 5230.24.
- FAR 52.204-21, Basic Safeguarding of Covered Contractor Information Systems (eCFR).