What SMB Defense Contractors Need to Know About CMMC Now

If you sell to the Department of Defense, or to a prime contractor who does, you’ve probably heard two contradictory things about CMMC this year: that it’s a hard deadline you can’t miss, and that it’s been paused. Both are true, just not at the same time. The Cybersecurity Maturity Model Certification program is live, partially suspended, and still enforceable in the parts that matter most, and sorting out which rule applies to your business right now takes more than a glance at a headline.

What CMMC actually requires

CMMC sets three certification levels tied to the sensitivity of the information a contractor handles. Level 1 covers companies that only touch Federal Contract Information and requires a basic self-assessment against 15 security practices. Level 2, where most small and mid-sized contractors land, requires full implementation of the 110 controls in NIST SP 800-171 for any business that processes Controlled Unclassified Information. Level 3 adds a smaller set of enhanced controls from NIST SP 800-172 for the highest-sensitivity work and is assessed directly by the Defense Contract Management Agency.

The requirement doesn’t come from CMMC alone. It flows from DFARS clause 252.204-7012, which has required contractors handling CUI to safeguard it and report cyber incidents within 72 hours since well before CMMC existed. CMMC was built to verify that contractors were actually doing what 7012 already required them to do.

Where the rollout stands right now

The CMMC acquisition rule took effect on November 10, 2025, opening Phase 1 of a planned four-phase schedule. Since that date, contracting officers have been authorized to include Level 1 and Level 2 self-assessment requirements in new Department of War solicitations and contract option years.

Phase 2 was supposed to follow on November 10, 2026, making third-party C3PAO certification a condition of award for most contracts touching CUI. That didn’t happen on schedule. On July 13, 2026, the Department of War suspended the Phase 2 transition along with every other pending CMMC milestone, and stood up a CMMC Reform Task Force to conduct what the department’s CIO called a top-to-bottom review of the program.

The task force met for the first time within days of the announcement and collected industry feedback through a public request for information, with responses due in mid-August and a final set of recommendations delivered to the CIO around 60 days later. As of this writing, no new Phase 2 date has been announced. If your contracts officer or your prime hasn’t mentioned a C3PAO certification requirement yet, this is why.

The pause doesn’t mean the obligations went away

It’s tempting to read “CMMC paused” as “cybersecurity compliance paused.” That’s not what happened. The suspension applies specifically to the Phase 2 transition to mandatory third-party certification. Every baseline requirement a defense contractor already owed under DFARS 252.204-7012, including full implementation of NIST SP 800-171 and 72-hour incident reporting, remains fully in force and enforced. The Department of Justice’s Civil Cyber-Fraud Initiative, which uses the False Claims Act to pursue contractors who misrepresent their cybersecurity posture, hasn’t paused either and continued settling cases during the review window.

That distinction matters for a small manufacturer or engineering firm trying to decide how much to invest right now. The paperwork requirement to prove compliance through a formal third-party assessment is on hold. The underlying requirement to actually have the 110 controls in place is not, and a contracting officer or a prime’s audit team can still ask for evidence of it at any point.

What subcontractors are still being asked to do

The government’s own rollout schedule and what prime contractors are asking of their supply chains aren’t always the same thing. Several large primes began flowing down Level 2 certification expectations to subcontractors well ahead of the official Phase 2 date, and some have continued to hold suppliers to those internal deadlines even after the government paused its own. If you supply parts, services, or software to a prime rather than contracting directly with the US Government, check your flow-down clauses and any supplier letters you’ve received in the past year. Your actual deadline may be set by your prime’s risk tolerance, not by the federal rollout calendar.

Practical steps while the rules are in motion

Waiting for certainty before acting is the most expensive option available. A Level 2 compliance effort realistically takes six to eighteen months depending on how much of your environment touches CUI and how far your current setup is from the 110-control baseline, so businesses that wait for a final Phase 2 date before starting will be behind regardless of when it lands.

  • Confirm whether your contracts or subcontracts actually involve Controlled Unclassified Information, since that determines whether Level 1 or Level 2 applies to you.
  • Run a gap assessment against the full NIST SP 800-171 control set now, rather than waiting for a C3PAO date to reappear on the calendar.
  • Keep your System Security Plan and Plan of Action and Milestones current and dated, since this documentation is what a contracting officer or a prime’s audit will ask to see first.
  • Review flow-down language in active subcontracts and supplier letters for certification deadlines your prime may be enforcing independent of the federal schedule.
  • Treat the 72-hour incident reporting obligation under DFARS 7012 as active today, because it is, regardless of where CMMC Phase 2 lands.

Businesses already building compliance costs into next year’s planning can see how that fits alongside other obligations like HIPAA or PCI DSS in our guide to building an IT budget that holds up. A lot of the control work required for CMMC Level 2, documented access controls, monitored endpoints, tested backups, overlaps directly with what carriers now expect before issuing a cyber insurance policy, covered in more detail in our breakdown of current cyber insurance requirements.

Where this leaves a small defense contractor

The federal government reserves the right to reinstate, revise, or replace Phase 2 once the Reform Task Force’s recommendations become public, and every signal points toward a program that gets adjusted rather than abandoned. Treating the suspension as a reason to stop working toward NIST SP 800-171 compliance is a bet that the requirement disappears entirely, which isn’t where the evidence points.

If you’re not sure whether your current environment would hold up against a Level 2 control set, or whether your prime’s flow-down requirements have quietly moved ahead of the federal timeline, a managed IT partner can run a gap assessment and help you build a realistic roadmap instead of guessing at a moving deadline.

Need Help Getting Started?

Let Us Know