CMMC and DFARSPublished Last reviewed November 20268 min read
Short answer
As of November 10, 2026, defense contractors pursuing CMMC Level 2 must still meet NIST SP 800-171 Revision 2. 32 CFR 170 defines Level 2 as the 110 Revision 2 requirements, and the DFARS 252.204-7012 class deviation names Revision 2. NIST published Revision 3 in May 2024 with 97 requirements, 17 families and organization defined parameters, but no final rule requires it yet.
Check where you stand: take the CMMC readiness check. About two minutes, no email needed.
November 10, 2026 was supposed to be the day CMMC Phase 2 began. Instead, the question we hear most from defense contractors is simpler. Which version of NIST SP 800-171 do we have to meet right now? The answer is Revision 2. The CMMC Program rule at 32 CFR 170 defines Level 2 as the 110 Revision 2 requirements, the DFARS 252.204-7012 clause DoD uses today names Revision 2, and DoD has said it will enforce Revision 2 while CMMC is paused.
Revision 3 is final and worth planning for, but it is not what you are scored against. Our view is to keep your SPRS score and CMMC evidence on Revision 2, make Revision 3 changes in your system security plan (SSP) and plan of action and milestones (POA&M) where they cost little, and treat the suspension as time to finish the work rather than a reason to stop.
What changed between NIST SP 800-171 Revision 2 and Revision 3?
Revision 3 has fewer requirements, more families and more specific wording. NIST published SP 800-171 Revision 3 on May 14, 2024, together with SP 800-171A Revision 3, the matching assessment procedures.
The requirement count drops from 110 to 97, and the families grow from 14 to 17. Three families are new: Planning (03.15), System and Services Acquisition (03.16) and Supply Chain Risk Management (03.17). Security Assessment became Security Assessment and Monitoring. Numbering changed as well, to a format such as 03.05.07 for Password Management.
Fewer does not mean less work. NIST withdrew some requirements and folded them into others, and its FAQ notes that this grouping produced multipart requirements. Revision 3 also drops the old split between basic and derived requirements and brings its wording closer to the SP 800-53 controls it was tailored from.
The change you will feel most is organization defined parameters (ODPs). Selected requirements now contain a value you must fill in. Password Management asks for the composition and complexity rules your organization sets. Policy and Procedures (03.15.01) and the SSP requirement (03.15.02) each ask for a review frequency. NIST says that if an agency does not specify a value, the contractor must assign one, and once set, the value becomes part of the requirement that an assessor tests.
| Item | Revision 2 | Revision 3 |
|---|---|---|
| Published | February 2020, with updates as of January 28, 2021 | May 14, 2024 |
| Security requirements | 110 | 97 |
| Families | 14 | 17, adding Planning, System and Services Acquisition, and Supply Chain Risk Management |
| Structure | Basic and derived requirements | One set, several of them multipart |
| Organization defined parameters | Not used | Included in selected requirements |
| Assessment procedures | SP 800-171A (June 2018) | SP 800-171A Revision 3 (May 2024) |
| Basis for CMMC Level 2 and SPRS today | Yes | No |
Which revision do 32 CFR 170 and DFARS 252.204-7012 point to today?
Both point to Revision 2. Section 170.14 of the CMMC Program rule says the security requirements in CMMC Level 2 are identical to NIST SP 800-171 R2, and section 170.2 incorporates the February 2020 Revision 2 and the June 2018 SP 800-171A by reference. The scoring method in section 170.24 assigns its 5, 3 and 1 point values to the 110 Revision 2 requirements. No amendment has moved any of this to Revision 3.
DFARS 252.204-7012 got there by a different route. The codified clause, dated May 2024, requires the version of NIST SP 800-171 in effect at the time the solicitation is issued and does not name a revision. Left alone, that wording would have tied new solicitations to Revision 3 once it was final. On May 2, 2024, less than two weeks before NIST finalized Revision 3, DoD issued class deviation 2024-O0013 to keep contractors on Revision 2.
That position has carried forward. Under the Revolutionary FAR Overhaul, DoD moved its cybersecurity clause prescriptions into a new DFARS Part 240 through class deviation 2026-O0025, and the 252.204-7012 text in that deviation names Revision 2 in paragraph (b)(2)(i). The deviation stays in effect until it is rescinded or written into the DFARS. Older contracts may carry an earlier version of the clause, so read the clause and its date in each one.
What did the CMMC Phase 2 suspension change, and what did it leave in place?
It stopped the move to third party certification assessments. It did not change the standard. On July 13, 2026, the department, which now issues these notices as the Department of War, suspended CMMC Phase 2 and set up a CMMC reform task force. The program is paused in Phase 1 and may only require self assessments, at Level 1 and Level 2. No restart date has been announced, and DoD has said only that it is reviewing the program.
DoD was explicit about what stays in place:
- All Phase 1 self assessment requirements, including results and affirmations in SPRS when a solicitation calls for them.
- Enforcement of NIST SP 800-171 Revision 2 through self assessments and selected government led assessments.
- The DFARS 252.204-7012 duty to protect covered defense information, which includes reporting cyber incidents within 72 hours of discovery.
Is DoD officially moving contractors to Revision 3?
Not yet. The clearest official signal is a proposed rule, and proposed rules can change.
On June 23, 2026, the FAR Council published a proposed rule under the Revolutionary FAR Overhaul (FAR Case 2026-001). Its proposed clause 52.240-7 would require contractor systems that handle CUI to comply with NIST SP 800-171 Revision 3, applying ODP values that DoD has published, with the CUI for each contract identified on a new standard form. The preamble says the rule aligns to ODP values that will be codified in 32 CFR part 170 through DoD rulemaking. Comments closed July 23, 2026.
As of today there is no final FAR rule, no amendment to 32 CFR 170 and no DFARS clause that requires Revision 3. You will find articles that describe a Revision 3 deadline as settled. Until a final or interim rule appears in the Federal Register, treat any date as a forecast.
How should you score and document while Revision 2 still applies?
Score against Revision 2 and document toward Revision 3. Mixing the two is how errors end up in SPRS.
- Keep your SPRS score and any Level 2 (Self) assessment on the 110 Revision 2 requirements and the 32 CFR 170.24 method. Our post on a defensible SPRS self assessment score covers the evidence each claim needs.
- Add a Revision 3 column to your SSP that maps each Revision 2 requirement to its new number. NIST publishes a Revision 2 to Revision 3 change analysis spreadsheet that does most of the mapping.
- Write down the parameter values you already follow, such as password rules and policy review frequencies, and compare them with the DoD values.
- Put Revision 3 work in its own labeled section of the POA&M. A Revision 3 gap is not a NOT MET under 32 CFR 170, and the POA&M limits in 170.21 (at least 88 of 110, closed within 180 days) apply to Revision 2 items only.
Some Revision 3 items cost little if you do them now. Rules of behavior with documented acknowledgment before access (03.15.03) can run through Microsoft Entra terms of use in Conditional Access, which logs who accepted and when. Unsupported system components (03.16.02) start with the device inventory in Microsoft Intune. External system services (03.16.03) means writing down what you require of your managed service provider and cloud services and who does what, which also helps your Revision 2 scoping. A short supply chain risk management plan (03.17.01) gives the new family a starting point. Our NIST SP 800-171 implementation work keeps both views in one SSP.
How should you use the time the suspension bought?
Finish the Revision 2 work as if an assessor were coming next quarter. The suspension paused a deadline. It did not change what your SPRS affirmation represents or what 7012 requires.
Close the gaps that keep your score below 88 first, then work down your POA&M. Fix the 5 point requirements early, such as multifactor authentication (IA.L2-3.5.3) and audit logging (AU.L2-3.3.1), because they move the score most. A well built POA&M also matters to program offices: we built a Level 2 POA&M that an Air Force Research Laboratory program office accepted as the basis for releasing CUI.
Then budget Revision 3 as a planned project for next year: documentation for the new families, decisions on parameter values and written requirements for your suppliers. If certification assessments return in some form, you will not be starting over. If you have not had a recent CMMC Level 2 gap assessment, start there. Our CMMC compliance work picks up from the findings.
If you want a second opinion on what to score now and what to plan for Revision 3, book a 30 minute call with our team.
Frequently asked questions
Can we implement Revision 3 now and skip Revision 2?
Not for scoring. Assessments under 32 CFR 170 test the 110 Revision 2 requirements against the June 2018 SP 800-171A objectives. Revision 3 renumbered, merged and withdrew requirements, so an SSP written only to Revision 3 still needs a mapping that lets an assessor find evidence for every Revision 2 requirement.
Will our SPRS score change when DoD adopts Revision 3?
Possibly, but nobody can say how yet. The point values in 32 CFR 170.24 are assigned to Revision 2 requirements, and there is no official Revision 3 scoring method today. A change would come through DoD rulemaking, so keep scoring with the current method until a published rule says otherwise.
Who decides the values for organization defined parameters?
The agency can set them, guide your choices or leave them to you. If no value is specified, NIST says the contractor must assign one. DoD has posted its own values for Revision 3, and the June 2026 proposed FAR rule points to them, so they are the sensible reference for defense work.
Does the Phase 2 suspension change our incident reporting duties?
No. DoD said the suspension does not remove the requirement to protect covered defense information under DFARS 252.204-7012. That clause still requires NIST SP 800-171 Revision 2 on covered systems and reporting of cyber incidents to DoD within 72 hours of discovery, whether or not a contract requires CMMC certification.
We are building a CUI enclave from scratch. Which revision should we design for?
Design to pass a Revision 2 assessment and choose settings that already meet Revision 3 where it costs nothing extra. Set and record parameter values as you configure, add the planning and supply chain documents early, and keep a crosswalk in the SSP so a later move to Revision 3 is an update, not a rebuild.