4 min read

NIST SP 800-171 Rev 2 vs Rev 3 for CMMC: The Numbers, Counted

Revision 3 has 97 requirements against 110, and 422 determination statements against 320, plus 88 parameters. Counted from NIST datasets, with what a Mac fleet should read now and why CMMC still assesses Revision 2.
NIST SP 800-171 Rev 2 vs Rev 3 for CMMC: The Numbers, Counted
Photo by Quilia / Unsplash
Quick answer. CMMC Level 2 is assessed against NIST SP 800-171 Revision 2. Revision 3 has fewer numbered requirements, 97 against 110, and more to assess: 422 determination statements against 320, plus 88 organization-defined parameters that Revision 2 does not have. Build to Revision 2, and read Revision 3 so the eventual change does not surprise you.

Which revision governs today

Revision 2. 32 CFR 170.2 incorporates it by reference, and the text of DFARS 252.204-7012 attached to Class Deviation 2026-O0025, Revision 3 names "Revision 2" in the clause itself. No rule we could find adopts Revision 3 into CMMC. The longer argument, including the oddity that NIST has withdrawn the revision the rule requires, is in CMMC mandates a NIST standard NIST has withdrawn.

The counts, taken from NIST's own dataset

The figures below were counted on 10 November 2026 from the machine-readable exports NIST publishes for both revisions through its Cybersecurity and Privacy Reference Tool, not copied from a summary.

MeasureRevision 2Revision 3
Requirement families1417
Security requirements11097 active (33 further entries are marked withdrawn)
Determination statements in the assessment guide320 (SP 800-171A)422 (SP 800-171A Rev 3)
Organization-defined parametersNone88

The 320 figure for Revision 2 is the count CMMC uses for Level 2 assessment objectives; it comes from SP 800-171A and is not in the Revision 2 export.

Family by family

FamilyRev 2Rev 3 active
Access Control2216
Awareness and Training32
Audit and Accountability98
Configuration Management910
Identification and Authentication118
Incident Response35
Maintenance63
Media Protection97
Personnel Security22
Physical Protection65
Risk Assessment33
Security Assessment (Rev 3: Security Assessment and Monitoring)44
System and Communications Protection1610
System and Information Integrity75
Planning (new)03
System and Services Acquisition (new)03
Supply Chain Risk Management (new)03
Total11097

A lower number in a family does not mean the obligation went away. NIST's withdrawal notes say where each one went. Most read "Incorporated into" or "Addressed by" another requirement. A few were dropped for other stated reasons, such as "Technology-specific" for 03.13.14 and "Recategorized as NCO" for 03.13.02.

Fewer requirements, more to assess

Consolidation is why the requirement count fell while the assessment guide grew by 102 determination statements. Add the 88 parameters and an assessor has more discrete things to check under Revision 3 than under Revision 2. Anyone describing Revision 3 as lighter is counting headings.

Organization-defined parameters: who defines them

Revision 3 leaves blanks in some requirements for a value to be assigned, such as a time period or a list. The label says "organization-defined", and for a contractor the organization doing the defining is the federal agency, not you. DoD issued a memorandum in April 2025 assigning its values for Revision 3. That memorandum does not make Revision 3 operative for CMMC.

Three changes a Mac fleet should read now

  • Cryptography, 03.13.11. Revision 2 names FIPS-validated cryptography in the requirement. Revision 3 reads: "Implement the following types of cryptography to protect the confidentiality of CUI: [Assignment: organization-defined types of cryptography]." The FIPS question moves from the requirement text to whatever value the agency assigns. It does not disappear, and under the revision CMMC uses today it has not moved at all. See macOS 27 on a CUI fleet.
  • Multi-factor authentication, 03.05.03. Revision 3 reads: "Implement multi-factor authentication for access to privileged and non-privileged accounts." Revision 2's 3.5.3 distinguishes local and network access. If your current design relies on that distinction for non-privileged local logins on Macs, Revision 3 as written does not carry it forward.
  • Unsupported System Components, 03.16.02. One of three requirements in the new System and Services Acquisition family. A Mac that can no longer run a supported macOS is the obvious case to plan for.

The other new requirements by title: Planning has Policy and Procedures, System Security Plan, and Rules of Behavior. System and Services Acquisition adds Security Engineering Principles and External System Services. Supply Chain Risk Management has a plan requirement, Acquisition Strategies, Tools, and Methods, and Supply Chain Requirements and Processes.

What to do with this

  1. Assess, document and score against Revision 2. That is what a Level 2 self-assessment and your SPRS entry rest on.
  2. Do not renumber your SSP. Revision 3 identifiers use the form 03.13.11; your evidence should match the revision you are assessed against.
  3. Adopt a Revision 3 practice only where it is free and does not conflict, and note that you did.
  4. Name the baseline you built from. The macOS Security Compliance Project publishes both a Revision 2 (CMMC) baseline and a Revision 3 baseline. Use the first.

Sources: NIST Cybersecurity and Privacy Reference Tool exports for SP 800-171 Revision 2 and Revision 3 (including SP 800-171A Rev 3 determination statements and parameters), counted 10 November 2026; 32 CFR 170.2 on eCFR; DFARS 252.204-7012 as attached to Class Deviation 2026-O0025, Revision 3. The April 2025 DoD parameters memorandum is cited from legal and trade reporting, not read at source for this page. No prediction is made here about when or whether CMMC will adopt Revision 3. Educational material, not legal advice.