NIST SP 800-171 Revision 3 organizes 97 security requirements (130 numbered identifiers, 33 of them marked withdrawn) across 17 control families for protecting Controlled Unclassified Information (CUI) on nonfederal systems, while CMMC (Cybersecurity Maturity Model Certification) 2.0 — the Department of Defense's contractual program for verifying that defense contractors actually meet it — still certifies against the older 110-requirement, 14-family Revision 2 baseline via DFARS clause 252.204-7012. They are frequently discussed together because CMMC does not define its own technical control set — its final rule text builds directly on SP 800-171 (plus a slice of SP 800-172 at the top tier) and adds an assessment-and-certification layer on top.
Key takeaways
- NIST's Revision 3, published May 2024, formally supersedes Revision 2 (February 2020, updated 28 January 2021).
- CMMC is the mechanism DoD uses to confirm that a defense contractor or subcontractor has actually implemented the required security measures for FCI and CUI, rather than relying on self-attestation alone.
- Revision 2. CMMC's final rule ties its Level 2 and Level 3 requirements to NIST SP 800-171 Revision 2 by name, and its scoring method (32 CFR 170.24) is written around Rev.
- 32 CFR 170.3(e) starts Phase 1 on the effective date of the companion DFARS rule, and each later phase one calendar year after the previous one.
What does SP 800-171 Rev. 3 actually require?
NIST's Revision 3, published May 2024, formally supersedes Revision 2 (February 2020, updated 28 January 2021). Its publication page states it "provides federal agencies with recommended security requirements for protecting the confidentiality of CUI when the information is resident in nonfederal systems and organizations," for use "in contractual vehicles or other agreements." The requirements are tailored down from the NIST SP 800-53B moderate control baseline.
Each requirement has an identifier such as 03.01.01 (family 01 = Access Control, requirement 01) through 03.17.03. The full text contains 130 such identifiers, but 33 read "Withdrawn" with a pointer — for example, 03.01.13 is "Addressed by 03.13.08" — so 97 requirements are active. Counting them per family:
| Family | Active | Family | Active |
|---|---|---|---|
| 01 Access Control | 16 | 10 Physical Protection | 5 |
| 02 Awareness and Training | 2 | 11 Risk Assessment | 3 |
| 03 Audit and Accountability | 8 | 12 Security Assessment and Monitoring | 4 |
| 04 Configuration Management | 10 | 13 System and Communications Protection | 10 |
| 05 Identification and Authentication | 8 | 14 System and Information Integrity | 5 |
| 06 Incident Response | 5 | 15 Planning (new) | 3 |
| 07 Maintenance | 3 | 16 System and Services Acquisition (new) | 3 |
| 08 Media Protection | 7 | 17 Supply Chain Risk Management (new) | 3 |
| 09 Personnel Security | 2 | Total | 97 |
NIST's Appendix E change log lists what changed from the 2020/2021 edition, including that it:
- "Eliminated the distinction between basic and derived security requirements" that structured Rev. 2;
- "Introduced organization-defined parameters (ODPs)" — values such as a time period or frequency that the agency or the implementing organization fills in, documented in Appendix D;
- "Added new tailoring categories: Other Related Controls (ORC) and Not Applicable (N/A)";
- Added, removed, retitled and regrouped individual requirements to reduce redundancy with SP 800-53.
A companion assessment document, SP 800-171A Rev. 3, was published alongside it; see our SP 800-171A guide.
What are the CMMC 2.0 levels, and how is each assessed?
CMMC is the mechanism DoD uses to confirm that a defense contractor or subcontractor has actually implemented the required security measures for FCI and CUI, rather than relying on self-attestation alone. It was established as a final rule at 32 CFR Part 170, published in the Federal Register on 15 October 2024 (89 FR 83092) and effective 16 December 2024. Its stated purpose is "to verify contractors have implemented required security measures necessary to safeguard Federal Contract Information (FCI) and Controlled Unclassified Information (CUI)."
The rule defines four CMMC statuses, summarized from its Table 1:
| CMMC status | Source of requirements | Assessment |
|---|---|---|
| Level 1 (Self) | 15 requirements required by FAR clause 52.204-21 | Self-assessment annually; no POA&Ms permitted |
| Level 2 (Self) | 110 NIST SP 800-171 R2 requirements required by DFARS clause 252.204-7012 | Self-assessment every 3 years; POA&Ms permitted, must close within 180 days |
| Level 2 (C3PAO) | Same 110 NIST SP 800-171 R2 requirements | Independent assessment by an accredited CMMC Third-Party Assessment Organization (C3PAO) every 3 years |
| Level 3 (DIBCAC) | The Level 2 requirements plus 24 selected requirements from NIST SP 800-172 (Feb. 2021) | Government assessment by DoD's Defense Industrial Base Cybersecurity Assessment Center (DIBCAC); requires a prior Final Level 2 (C3PAO) status |
Level 1 applies to contractors handling only FCI; Levels 2 and 3 apply once a contractor processes, stores or transmits CUI. In its cost analysis DoD estimated that 8,350 medium and large entities would need a Level 2 C3PAO assessment, ramping from 135 assessments in year one to 4,452 in year four. Level 3's extra requirements are covered in our SP 800-172 guide.
Under 32 CFR 170.21, an organization can reach a Conditional Level 2 status if its score is at least 0.8 of the maximum (88 of 110), only 1-point requirements sit on the Plan of Action and Milestones (POA&M) — with a narrow exception for non-FIPS-validated encryption — and six named requirements, including the System Security Plan, are met. The POA&M must close within 180 days or the status expires.
Which revision does CMMC assess, Rev. 2 or Rev. 3?
Revision 2. CMMC's final rule ties its Level 2 and Level 3 requirements to NIST SP 800-171 Revision 2 by name, and its scoring method (32 CFR 170.24) is written around Rev. 2's basic and derived requirements with 5-, 3- and 1-point values. A contractor building a compliance program around the newest NIST text risks building against a baseline DoD contracts do not reference. Until DoD formally updates its DFARS clauses and CMMC's incorporated requirement set, the 110-requirement, 14-family Rev. 2 structure is the one that counts for a CMMC assessment, even though Rev. 3 is NIST's current publication for every other purpose. Rev. 3 is still worth reading for its new Supply Chain Risk Management family, which has no Rev. 2 equivalent.
When do the CMMC phases start, and what is suspended in 2026?
32 CFR 170.3(e) starts Phase 1 on the effective date of the companion DFARS rule, and each later phase one calendar year after the previous one. That DFARS rule (90 FR 43560, published 10 September 2025) took effect on 10 November 2025, which fixes the dates below:
| Phase | Start | What DoD said it would add |
|---|---|---|
| 1 | 10 November 2025 | Level 1 (Self) or Level 2 (Self) as a condition of award; Level 2 (C3PAO) at DoD discretion |
| 2 | 10 November 2026 | Level 2 (C3PAO) for applicable contracts; Level 3 (DIBCAC) at discretion |
| 3 | 10 November 2027 | Level 2 (C3PAO) for all applicable contracts, including option periods; Level 3 for applicable contracts |
| 4 | 10 November 2028 | Full implementation, including option periods on older contracts |
Phase 2 did not start as written. A Department of War Chief Information Officer request for information posted on SAM.gov on 13 July 2026 states that "the DoW Chief Information Officer (CIO) has suspended CMMC Phase II requirements and directed a CMMC Reform Task Force to comprehensively review the program and deliver actionable recommendations for reform." The same notice asks companies about the challenges of "maintaining, verifying, and reporting" their Phase I self-assessments, and about cost drivers in complying with "the CMMC framework and NIST SP 800-171 Rev 2". The suspension changed no regulation text: the eCFR version history for 32 CFR part 170 still shows only the 16 December 2024 text, with the original four-phase schedule in 170.3. Check each solicitation for the clauses it actually contains.
Does CMMC apply to a device or firmware supplier?
Often less than suppliers fear. Work through the rule's own scope tests:
Do you sell only COTS items?32 CFR 170.3(c) applies CMMC to contracts "except those exclusively for COTS items", and DoD's response to public comments says "CMMC requirements do not apply to contracts and subcontracts that are exclusively for the delivery of COTS products to a DoD buyer." A catalogue sensor or gateway sold unchanged is usually out of scope. Will FCI or CUI touch your systems?CMMC assesses "contractor owned information systems", not your product. Custom hardware built to a DoD drawing, or firmware changed to a program's specification, usually brings FCI or CUI (drawings, test data) onto your engineering systems. What does the prime flow down?Under 32 CFR 170.23, an FCI-only subcontract needs Level 1 (Self); a CUI subcontract needs at least Level 2 (Self), and Level 2 (C3PAO) if the prime has a Level 2 (C3PAO) or Level 3 requirement. Which systems are in scope?Only the systems that process, store or transmit the FCI or CUI. Many suppliers keep CUI in a separate enclave rather than bring the whole company into scope. What must be reported?DFARS 252.204-7021 requires the CMMC status in SPRS, an annual "affirmation of continuous compliance" by an affirming official, and the same from subcontractors before award.
The COTS exemption covers the product you deliver, not the tools you use: DoD notes that "[t]he exemption does not apply to a contractor's use of COTS products within its information systems that process, store, or transmit CUI."
Which 800-171 requirements touch firmware and components?
When a hardware supplier is in scope, a handful of requirements map directly onto engineering work. Rev. 3 numbering is shown with the Rev. 2 counterpart CMMC assesses today.
| Rev. 3 requirement | Rev. 2 counterpart | What it asks, in short |
|---|---|---|
| 03.04.10 System Component Inventory | 3.4.1 | Inventory of hardware, software and firmware components, updated with installs and updates |
| 03.11.02 Vulnerability Monitoring and Scanning | 3.11.2, 3.11.3 | Scan at a defined frequency and when new vulnerabilities are identified; remediate within defined times |
| 03.14.01 Flaw Remediation | 3.14.1 | Install security-relevant software and firmware updates within a defined period |
| 03.14.03 Security Alerts, Advisories, and Directives | 3.14.3 | Receive and act on advisories |
| 03.16.02 Unsupported System Components | new in Rev. 3 | Replace components when the vendor no longer supports them, or document mitigation |
| 03.17.03 Supply Chain Requirements and Processes | new in Rev. 3 | Identify and address weaknesses in supply chain elements and processes |
Rev. 3's discussion text for 03.11.02 notes that analysis of custom software "may require additional approaches, such as static analysis, dynamic analysis, or binary analysis." For the supply-chain side, see our NIST SP 800-161 C-SCRM guide; the wider control source is NIST SP 800-53.
What does CMMC scoping look like for one supplier?
Worked example — synthetic, labelled for illustration. The company, contract and findings are made up.
A 60-person maker of rugged Ethernet switches gets two requests from a prime contractor.
Contract Abuys the standard catalogue switch, unchanged. The team confirms it is a COTS item; no CMMC flowdown applies. Contract Basks for a variant with a custom firmware build and receives the prime's interface specification marked CUI. The flowdown requires Level 2 (Self). ScopeThe team creates an enclave: one engineering VLAN, a separate file share and two build machines. Only those systems, and the people using them, enter scope. Self-assess against Rev. 2The first pass scores 82 of 110. Two misses are 5-point requirements, which cannot go on a POA&M, so they are fixed before submission. The score rises to 92, at least 0.8 of 110, and the remaining 1-point items go on a POA&M for a Conditional Level 2 (Self) status with 180 days to close. Engineering evidenceFor 3.4.1 and 3.11.2, the build machines' software inventory and a vulnerability scan record are kept with dates. ReportThe affirming official posts the score in SPRS and diaries the annual affirmation.
What are the common CMMC mistakes for hardware suppliers?
- Quoting 130 requirements for Rev. 3. 33 of the 130 identifiers are withdrawn; the active count is 97, and CMMC assesses Rev. 2's 110.
- Implementing Rev. 3 instead of Rev. 2 for a CMMC assessment.
- Treating the product as the assessment target. CMMC assesses the contractor's information systems, not the device you ship.
- Assuming the Phase 2 suspension removed everything. DoD's notice suspends Phase II; the Phase I self-assessment, the DFARS 252.204-7012 clause and the 32 CFR part 170 text are unchanged.
- Scoping the whole company when a CUI enclave would do.
- Missing the COTS line. Customization can turn a catalogue product into a CUI job.
Where does SoftWSP fit?
SoftWSP does not assess CMMC, write a System Security Plan or post SPRS scores. What it can supply is component and vulnerability evidence for firmware the customer uploads: it extracts an SBOM as CycloneDX 1.6 JSON, matches components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report for engineer review — inputs for inventory and vulnerability-monitoring requirements such as 03.04.10 and 03.11.02. See device firmware security, the SBOM viewer, and our firmware SBOM guide. For the regulated-device view in this cluster, start with FDA premarket cybersecurity.
This guide summarises public NIST and DoD/Department of War publications on a fast-moving 2026 policy change; it does not constitute legal or compliance advice.
Put this guide to work
Frequently asked questions
What is NIST SP 800-171?
"Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations" — a NIST publication that gives federal agencies a baseline of security requirements for Controlled Unclassified Information (CUI) when it is processed, stored or transmitted by nonfederal systems and organizations, intended for use in the contracts and agreements those agencies sign with contractors. Revision 3, published May 2024 and formally superseding Revision 2 (February 2020, updated January 2021), organizes its requirements into 17 families derived from the NIST SP 800-53B moderate control baseline.
How many requirements does SP 800-171 Rev. 3 contain?
NIST's published text assigns each requirement an identifier from 03.01.01 (the first Access Control requirement) through 03.17.03 (the last Supply Chain Risk Management requirement). Counting those identifiers directly in the final PDF gives 130, but 33 of them are marked "Withdrawn" (incorporated into or addressed by other requirements), leaving 97 security requirements spread across the 17 families, versus 110 requirements across 14 families in Revision 2 — a reorganization, not a lighter standard, since Rev. 3 adds three new families (Planning; System and Services Acquisition; Supply Chain Risk Management) and, per NIST's own change log, "eliminated the distinction between basic and derived security requirements" that Rev. 2 used.
What is CMMC 2.0 and how does it relate to SP 800-171?
CMMC (Cybersecurity Maturity Model Certification) is the Department of Defense program, established as a final rule at 32 CFR Part 170 (89 FR 83092, published 15 October 2024), that verifies defense contractors and subcontractors have implemented the security measures needed to safeguard Federal Contract Information (FCI) and CUI. The rule's own text states CMMC Level 2 — the tier that applies to any contractor processing, storing or transmitting CUI — requires implementing "the 110 NIST SP 800-171 R2 required by DFARS clause 252.204-7012"; Level 3 adds 24 selected requirements from NIST SP 800-172 (February 2021). CMMC is, in effect, DoD's contractual mechanism for proving SP 800-171 compliance rather than a separate technical standard.
Does CMMC require the newer Rev. 3, or still Rev. 2?
Still Revision 2. The 32 CFR Part 170 final rule text ties every CMMC Level 2 and Level 3 requirement explicitly to "NIST SP 800-171 R2" via DFARS clause 252.204-7012 — it does not reference Revision 3. As of November 2026, the Department had not amended that DFARS clause to point to Rev. 3, so contractors pursuing a CMMC assessment should keep implementing against Rev. 2's 110 requirements even though NIST itself has moved to the newer 97-requirement Rev. 3 baseline for its own publications.
Sources
- NIST: SP 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations (May 2024) — publication page
- NIST SP 800-171r3 (Ross, Pillitteri), full text PDF
- DoD: Cybersecurity Maturity Model Certification (CMMC) Program, final rule, 32 CFR Part 170 (Docket DoD-2023-OS-0063, RIN 0790-AL49), pre-publication text scheduled for the Federal Register 15 October 2024
- Federal Register: Cybersecurity Maturity Model Certification (CMMC) Program — document 2024-22905 (listing)
- Holland & Knight: DoW Suspends CMMC Phase II Requirements (July 2026)
- SAM.gov: DoW CIO request for information, Reforming CMMC and Reducing Compliance Burden for the Defense Industrial Base (DoDCIOReformingCMMCforDIB001), posted 13 July 2026
- NIST: SP 800-171A Rev. 3, Assessing Security Requirements for Controlled Unclassified Information (May 2024) — publication page
- eCFR: 32 CFR Part 170, Cybersecurity Maturity Model Certification (CMMC) Program — current text (§170.3 phases, §170.21 POA&M, §170.23 subcontractors, §170.24 scoring)
- Federal Register: DFARS: Assessing Contractor Implementation of Cybersecurity Requirements (DFARS Case 2019-D041), final rule, 90 FR 43560, 10 September 2025, effective 10 November 2025 — clause 252.204-7021
About this guide
SoftWSP Regulation Desk
Covers the Medical & regulated devices cluster: 30 guides.

In this cluster
Questions about this page?
