CMMC is the Department of Defense program that verifies contractors protect federal contract information and controlled unclassified information. The program rule (32 CFR Part 170) took effect December 16, 2024, and the DFARS contract rule took effect November 10, 2025, starting Phase 1 self-assessments. Phase 2 third-party assessments were scheduled for November 10, 2026 but were suspended in July 2026 pending a program review, while Phase 1 and NIST SP 800-171 Rev. 2 obligations remain in force.
CMMC compliance is how the Department of Defense checks that the companies in its supply chain actually protect the information it shares with them. If your Massachusetts firm machines parts, writes software, does engineering work or provides services under a defense contract or subcontract, CMMC requirements are either in your contracts already or likely to arrive through your prime contractor.
The timeline has been confusing, and 2026 made it more so. The program rule took effect in December 2024, contract clauses started appearing in November 2025, and the third-party assessment phase scheduled for November 10, 2026 was suspended in July 2026 pending a program review. This guide explains where things stand as of November 2026 and what a small contractor should be doing regardless. It is general information, not legal advice; confirm your obligations with your contracts counsel and contracting officer.
What CMMC protects: FCI and CUI
CMMC is built around two types of information.
- Federal contract information (FCI) is information not intended for public release that is provided by or generated for the government under a contract, as defined in FAR 52.204-21. That clause lists 15 basic safeguarding requirements.
- Controlled unclassified information (CUI) is information that requires safeguarding or dissemination controls under law, regulation or government-wide policy, but is not classified. The National Archives maintains the CUI Registry, which lists the categories and markings.
For small manufacturers and engineering firms, CUI commonly shows up as controlled technical drawings, specifications and export-controlled data sent by a prime. If you are not sure whether you hold CUI, start by asking your prime what they are sending you and how it is marked.
The two rules: 32 CFR Part 170 and the DFARS clause
CMMC 2.0 rests on two separate rules, and people mix them up.
- The program rule, 32 CFR Part 170, defines the levels, assessment process and requirements. It was published October 15, 2024, and the Federal Register notice states it is effective December 16, 2024.
- The acquisition rule, in the DFARS (48 CFR), puts CMMC into contracts through the clause at DFARS 252.204-7021. It was published September 10, 2025 and took effect November 10, 2025, which started Phase 1 of the rollout, according to Squire Patton Boggs and other law firm summaries.
Separately, DFARS 252.204-7012 has required covered contractors to safeguard covered defense information using NIST SP 800-171 for years, and DFARS 252.204-7019 requires a current NIST SP 800-171 assessment, not more than three years old, posted in SPRS before award. Those obligations exist whether or not a contract carries a CMMC level.
CMMC levels and assessment types
| Level | Protects | Requirements | Assessment | Frequency |
|---|---|---|---|---|
| Level 1 (Self) | FCI | 15 requirements from FAR 52.204-21 | Self-assessment | Annual, results in SPRS |
| Level 2 (Self) | CUI | 110 requirements from NIST SP 800-171 Rev. 2 | Self-assessment | Every three years, plus annual affirmation |
| Level 2 (C3PAO) | CUI | Same 110 requirements | Certified third-party assessment organization | Every three years, plus annual affirmation |
| Level 3 (DIBCAC) | CUI in higher-priority programs | Level 2 plus 24 selected requirements from NIST SP 800-172 | Government assessment by DCMA DIBCAC, after a Final Level 2 (C3PAO) | Every three years, plus annual affirmation |
Under the program rule, all 15 Level 1 requirements must be fully met, with no POA&M allowed. After each assessment, and annually after reaching a final status, a senior company official (the Affirming Official) affirms compliance in SPRS. That affirmation is a statement to the government, so it should only be signed when it is true.
Where CMMC compliance deadlines stand in November 2026
The program rule laid out four phases tied to the DFARS effective date. Here is the original schedule and its status as best we can confirm it.
| Phase | Original start date | What it adds | Status as of November 2026 |
|---|---|---|---|
| Phase 1 | November 10, 2025 | Level 1 (Self) and Level 2 (Self) in applicable solicitations | In effect |
| Phase 2 | November 10, 2026 | Level 2 (C3PAO) in applicable solicitations | Suspended July 13, 2026 |
| Phase 3 | November 10, 2027 | Level 3 (DIBCAC) requirements | Covered by the suspension of pending milestones |
| Phase 4 | November 10, 2028 | Full implementation | Covered by the suspension of pending milestones |
On July 13, 2026, the Department of Defense, which now also uses the name Department of War, suspended implementation of Phase 2 along with pending and future CMMC milestones, and set up a CMMC reform task force to review the program within 60 days. The DoW CIO CMMC page describes the program as paused in Phase 1, and the department's implementing memo says solicitations may include only Level 1 (Self) or Level 2 (Self) requirements during the review. According to Crowell and Moring's summary, the department said Phase 1 self-assessments "remain firmly in place," contractors remain bound by DFARS 252.204-7012, and it would keep enforcing NIST SP 800-171 Rev. 2. A follow-up memo directed that active solicitations and contracts with Level 2 (C3PAO) or Level 3 requirements be amended to remove them.
As of late October 2026, industry trackers reported that the task force's review had closed in September, its report had not been made public, and Phase 2 remained suspended with no restart date. We could not confirm any official change after that. Policy here is moving, so check the DoD CIO CMMC page and talk to your contracting officer before making plans that depend on dates.
Our view: the suspension changes when third-party certification may be required, not whether CMMC compliance work is needed or whether you must protect CUI. The 110 requirements, your SPRS score and your affirmation obligations did not go away, and the program rule itself is still on the books.
NIST SP 800-171 Rev. 2 vs Rev. 3
NIST published Revision 3 of SP 800-171 on May 14, 2024. A couple of weeks earlier, DoD issued a class deviation so that DFARS 252.204-7012 would keep pointing to Revision 2, as Crowell and Moring explained. The CMMC program rule also defines Level 2 using Rev. 2.
For a small contractor in late 2026, the practical answer is to build and assess against Rev. 2, because that is what your contracts and any CMMC assessment use. Rev. 3 reorganizes and adds detail to the controls, so it is worth reading as a preview, but do not rebuild your system security plan around it until DoD actually adopts it.
SPRS scores and what they mean
SPRS is the government system where your NIST SP 800-171 assessment results live. Under the DoD Assessment Methodology, a basic self-assessment starts at 110 points and subtracts a weighted value for each requirement not met. Heavily weighted gaps can drive the score below zero, as low as -203.
A few points that catch small firms:
- The score has to reflect reality. Primes and DoD can see it, and the annual affirmation puts a company official's name behind it.
- Your system security plan (SSP) is required. CA.L2-3.12.4, the requirement to have one, cannot be put on a POA&M.
- Scope matters. A small firm can often shrink the assessment scope by keeping CUI in one controlled environment instead of spread across every laptop and file share.
POA&Ms: what can wait and what cannot
A plan of action and milestones (POA&M) lets a contractor reach a Conditional Level 2 status with a few open items. Under 32 CFR 170.21 the rules are tight:
- Your assessment score divided by the total number of Level 2 requirements must be at least 0.8, which works out to 88 of 110.
- No requirement worth more than 1 point can be on the POA&M. The one exception is SC.L2-3.13.11 (CUI encryption), when encryption is in use but not FIPS-validated.
- Several specific requirements can never be on a POA&M, including the system security plan and some physical access controls.
- Open items must be closed and verified within 180 days of the Conditional status date, or the conditional status expires.
- Level 1 never allows a POA&M.
In plain terms: you cannot POA&M your way past MFA, encryption, logging or access control gaps, since most of those carry higher point values. Fix the big items first.
Why CMMC matters for Massachusetts subcontractors
Massachusetts has a substantial defense contracting base. A UMass Donahue Institute study commissioned by MassDevelopment and the state's Military Asset and Security Strategy Task Force found that defense contract work supported more than 88,000 workers and contributed more than $20 billion to the Massachusetts economy in fiscal year 2013, per MassDevelopment's 2015 release. That is older data, but it is the most recent statewide study we found.
Much of that work flows through small suppliers: machine shops, electronics assemblers, engineering consultancies, software shops and service firms. They are often several tiers below the prime. 32 CFR 170.23 requires primes to flow CMMC requirements down to every subcontract tier based on what each subcontractor handles: Level 1 (Self) for FCI only, at least Level 2 (Self) for CUI, and Level 2 (C3PAO) where the prime's contract requires it.
In practice, primes can move faster than the regulation. A prime that is responsible for flowing requirements down has good reason to ask suppliers for SPRS scores, SSPs and evidence of MFA before a clause forces the issue, and a subcontractor that can answer those questions quickly is easier to keep on a bid. For many small engineering and construction firms, the first sign of CMMC can be a supplier security questionnaire rather than anything from a contracting officer.
What a small contractor should do now
The suspension is a chance to catch up, not a reason to stop. This order works for most firms under 100 people.
- Confirm what you handle. Ask your primes whether you receive FCI, CUI or both, and get it in writing.
- Define your scope. Decide which systems, people and locations touch CUI, and look for ways to shrink that footprint.
- Write or update your system security plan for that scope. It cannot be put on a POA&M.
- Run an honest self-assessment against the 110 NIST SP 800-171 Rev. 2 requirements, score it with the DoD methodology, and post or update it in SPRS.
- Fix high-value gaps first: MFA, encryption, audit logging, access control, incident response and configuration management.
- Choose your environment. Many small firms use a Microsoft 365 setup designed for CUI rather than securing everything. Licensing and cloud selection matter here, so get advice before you buy.
- Document evidence as you go, so a later third-party assessment, if it comes, is mostly a review of records you already have.
- Calendar your annual affirmation and treat it as a formal sign-off.
For the general Microsoft 365 hardening that supports many NIST requirements, our Microsoft 365 security checklist is a good start, though CUI environments need more than a standard tenant.
If you want help scoping CUI, building an SSP or preparing for an assessment, our IT consulting team handles the planning and documentation, and our cybersecurity services handle the technical controls. We work with contractors across the state as part of our managed IT services in Massachusetts.
Frequently asked questions
What is CMMC compliance?
CMMC (Cybersecurity Maturity Model Certification) is the Department of Defense program for verifying that contractors and subcontractors protect federal contract information (FCI) and controlled unclassified information (CUI). It sets three levels with different requirements and assessment types, and contracts specify which level a company needs. Results are recorded in the Supplier Performance Risk System (SPRS), and an affirming official must confirm compliance annually.
Is CMMC Phase 2 in effect?
Not as of this writing. Phase 2, which would have required third-party (C3PAO) Level 2 certification in applicable contracts starting November 10, 2026, was suspended on July 13, 2026 while a task force reviewed the program. Reporting through late October 2026 indicated Phase 2 remained suspended, with Phase 1 self-assessments still required. Check the DoD CIO CMMC page and your contracting officer for current status.
Does CMMC use NIST SP 800-171 Revision 2 or Revision 3?
Revision 2. The CMMC program rule defines Level 2 using the 110 requirements of NIST SP 800-171 Rev. 2, and a May 2024 DoD class deviation kept DFARS 252.204-7012 tied to Rev. 2 even after NIST published Rev. 3 on May 14, 2024. DoD said during the 2026 review it would keep enforcing Rev. 2. Rev. 3 may be adopted later through rulemaking.
What SPRS score do I need?
There is no single passing score for posting a basic self-assessment, but a low score can hurt you competitively and must be accurate. For a Conditional CMMC Level 2 status, your assessment score must be at least 80 percent of the maximum (88 of 110), and open items must be on an allowable POA&M closed within 180 days. A final status requires every requirement to be met.
Do subcontractors need CMMC?
Yes, if they handle FCI or CUI under a covered contract. 32 CFR 170.23 requires prime contractors to flow CMMC requirements down to all subcontract tiers. A subcontractor handling only FCI needs Level 1 (Self). One handling CUI needs at least Level 2 (Self), or Level 2 (C3PAO) when the prime contract requires it. Subcontractors under a Level 3 prime need at least Level 2 (C3PAO).
Sources and references
- Federal Register: Cybersecurity Maturity Model Certification (CMMC) Program final rule, 32 CFR Part 170 (October 15, 2024)
- 32 CFR 170.21: Plan of Action and Milestones requirements (Cornell LII)
- 32 CFR 170.23: Application to subcontractors (Cornell LII)
- DFARS 252.204-7019: Notice of NIST SP 800-171 DoD Assessment Requirements
- FAR 52.204-21: Basic Safeguarding of Covered Contractor Information Systems
- National Archives: About Controlled Unclassified Information (CUI)
- DoW CIO: Cybersecurity Maturity Model Certification (CMMC)
- DoW CIO: Implementing the suspension of CMMC Phase II (memo 26-P-1023)
- Squire Patton Boggs: The CMMC DFARS final rule goes live
- Crowell and Moring: Department of War immediately suspends CMMC Phase II requirements, launches 60-day reform review
- Secureframe: CMMC news and updates (accessed November 2026)
- Crowell and Moring: DoD issues class deviation linking DFARS 7012 to NIST SP 800-171 Rev. 2
- MassDevelopment: New reports reveal Massachusetts defense contract work contributed $20 billion to economy (December 18, 2015)