← Back to InsightsCompliance

Was CMMC Really Too Expensive? What the RFI Found

· 5 min read

Open compliance binder, laptop and calculator on a desk overlooking a precision machining floor

Mostly no. The Department of War’s own industry survey puts the average cost of CMMC itself at about $47,000, and the money most suppliers worry about goes to the NIST SP 800-171 controls underneath it, which have been required since 2017.

That finding comes from the task force the DoW set up when it suspended CMMC Phase II on July 13, 2026. The task force summarized the responses to its Request for Information (RFI) in early September. Federal News Network obtained that summary and reported on it in a two-part series on October 26 and 27, 2026. The department hasn’t commented on the results, and Phase II still has no restart date.

In July we laid out what the suspension did and didn’t change. The RFI results fill in the other half: why the program stopped, and what the government is likely to ask of suppliers when it starts again.

Three reasons for the pause, checked against the answers

The DoW gave three reasons for stopping the program. Here’s how each held up once 997 responses came in, 509 of them from defense contractors.

Cost. In July the SBA Administrator said CMMC compliance could cost as much as $600,000. Respondents described something different. The costs they named were mostly NIST 800-171 costs: government cloud licensing, enclaves, and the specialized staff to run them. Inconsistent CUI marking was another top driver, because every unmarked or over-marked document widens what has to be protected. Third-party assessors came in fifth on the list of cost drivers, and the DoW noted that assessment prices fell during CMMC’s first year. Both dollar figures in this post are the government’s numbers, not our pricing.

Paperwork. The overhead respondents ranked highest was the System Security Plan, followed by FIPS-validated encryption. Both are NIST 800-171 requirements, so pausing the certification step doesn’t remove either one.

Assessor capacity. Industry figures based on Cyber AB data show Phase I never used more than about half of the available assessment capacity. By September, 2,433 companies held a Level 2 certification, roughly five times what the department expected in the first year.

CMMC still isn’t cheap for a small supplier. But the expensive part is the security work, and that work was owed before CMMC existed.

Nothing in the summary says to scrap the program. Most of it is about making the same requirements clearer and easier to meet, on three timelines:

  • Within about 90 days: restart Phase II with a narrower group of contractors, give assessors and consultants more consistent guidance, and publish assessor availability numbers.
  • Within 6 to 12 months: credit overlapping ISO 27001 work, reduce how much CUI gets pushed to primes and subcontractors in the first place, and extend the window for open POA&M items to 270 days (that one needs rulemaking).
  • A year or more out: publish approved configurations and templates, support machine-readable evidence, and look at free tools. Grants, subsidies, and tax credits came up as well, though the DoW said it can’t put those in place on its own. If funding is what you’re waiting on, read what we found about CMMC grants first.

The task force also recommended finishing the move to NIST SP 800-171 Revision 3, which has been on hold since the current DoW CIO took office last December.

The change the department itself flagged as having the most potential is clearer CUI marking. A planned FAR rule would add a standard form to each contract describing what CUI will be shared and how it has to be protected. For a supplier in the aerospace and defense supply chain, that’s the one to watch. A clear answer on what CUI you actually receive decides how much of your network has to meet all 110 controls, and scope is what drives cost.

What to do while the program is on hold

The duty to protect CUI under DFARS 252.204-7012 still applies, and so does the score you affirm in SPRS. A supplier who has cut security spending because the audit is paused is still exposed on both, including under the False Claims Act.

Here’s where we’d put the time:

  1. Pin down your CUI. Go through your contracts, flowdown clauses, and the drawings and specs you actually receive. Know what’s marked, what should be, and where it lands on your network. If the answer turns out smaller than you assumed, your scope shrinks with it.
  2. Make your SSP match the network. The System Security Plan and the systems it describes drift apart more often than most owners expect. Controls get changed, replaced, or dropped, and the document doesn’t follow. A plan that describes controls the network doesn’t have is propping up a score you can’t defend.
  3. Keep your POA&M dated and real. If the 270-day window comes through, a plan with actual owners and dates is what you’ll be measured against.
  4. Build on Revision 2 for now. Revision 3 isn’t required yet, and a well-documented NIST 800-171 Revision 2 environment is the shortest path to it.

We carry compliance obligations of our own every year, so we’ve had to make this call ourselves. When a deadline moves, waiting rarely makes the work cheaper, because whatever gets put off ends up done in a hurry.

Where we fit

We’re a CMMC Registered Practitioner Organization. We do the readiness work (scoping, the SSP, the POA&M, and standing up the controls), and we don’t perform certification assessments, which only an accredited C3PAO can do. We deliver CMMC Readiness Services together with Managed IT, because the documents and the live systems have to be run by the same team or they drift apart.

If you want a straight read on where your SPRS score and your network disagree, book a 30-minute readiness call. Bring your SSP and your current score. We’ll tell you what you’re on the hook for today and what can wait for the restart. The call costs nothing.

Want this handled for your business? Book a 30-minute call and we'll give you a straight read on where you stand.

Book a call

FAQs

Is CMMC cancelled?

No. The Department of War suspended the CMMC Phase II third-party assessment requirement on July 13, 2026, pending a review. Phase I self-assessments still apply, and so do NIST SP 800-171 and DFARS 252.204-7012. As of late October 2026, no restart date has been announced.

What does CMMC actually cost a small defense supplier?

The DoW's RFI put the average cost of complying with CMMC itself at about $47,000. The larger cost is meeting the NIST SP 800-171 controls underneath it, and that depends almost entirely on how much of your network handles CUI. Scoping your CUI first is the most reliable way to get a real number for your business.

Do I still need a current SPRS score while CMMC is paused?

Yes, if your contracts include the DFARS clauses that require a NIST SP 800-171 assessment. The suspension paused the third-party certification step, not self-assessments. The score you affirm in SPRS is a legal statement, so it needs to match what's actually running on your network.

Will CMMC Phase II come back?

The DoW task force recommended restarting Phase II within about 90 days for a narrower group of contractors. The department hasn't announced a decision. Plan as if third-party assessments will return in some form.

Should I wait for NIST 800-171 Revision 3 before doing anything?

No. Revision 2 is the standard being enforced today. The task force recommended finishing the move to Revision 3, but a well-documented Revision 2 environment is the shortest path there whenever the switch happens.

Talk it through with us

Book a 30-minute exploratory call. We'll tell you where your environment stands and what we'd fix first. If we're not the right fit, we'll say so.

Book a call

Practical IT tips, by email

Short, practical IT and security tips for business owners, written by the team that runs our clients' IT.