← Back to InsightsCompliance

CMMC Paused? Your SPRS Score Still Counts as a Claim

· 5 min read

Open compliance binder with a pen and reading glasses on a desk overlooking a machining floor

The CMMC Phase II pause (you’ll also see it written Phase 2) left your SPRS score exactly where it was. If your company holds a defense contract that involves CUI, the NIST SP 800-171 score you posted in SPRS is a statement to the government, and every invoice you send leans on it. Since June 2026 the Justice Department has announced four False Claims Act settlements over cybersecurity statements like that. Two of them came this month.

What the pause changed, and what it left alone

On July 13, 2026, the Department of War suspended Phase II of CMMC, the step that would have made third-party C3PAO certification a condition of award starting November 10. Phase I stayed. Level 1 and Level 2 self-assessments are still required, DFARS 252.204-7012 still sits in your contract, and the 110 controls in NIST SP 800-171 still apply to any system that touches CUI. The Department also said it will keep enforcing the standard through self-assessments and select government-led assessments. As of mid-November, no restart date has been announced and the reform task force’s report hasn’t been published. We keep the running status in our post on the Phase II suspension.

A lot of suppliers heard “paused” and moved the work into next year’s budget. We hear that read more often than we’d like. The reasoning is understandable, but it misses who does the enforcing. CMMC is a Department of War program. False Claims Act cases come from the Justice Department, and DOJ paused nothing.

What DOJ settled in June and November

On November 3, 2026, DOJ announced that two related aerospace and defense contractors in Delaware agreed to pay $13 million to resolve False Claims Act allegations tied to Army, Missile Defense Agency and NASA contracts. That is the government’s figure for the settlement, and the alleged gaps behind it were ordinary ones:

  • CUI was stored with a cloud provider that wasn’t held to the FedRAMP Moderate equivalent.
  • System security plans weren’t developed and kept current.
  • NIST SP 800-171 and 800-53 controls weren’t fully implemented.
  • Plans of action were missing for years at a time.
  • No current NIST SP 800-171 assessment was on file with the Department.

No breach is reported anywhere in the announcement. The person who brought the case was the companies’ own former director of cybersecurity, and his share is $2.35 million. These are allegations, and there was no determination of liability.

That’s a large company. The June case sits closer to home for a Tier 2 or Tier 3 supplier in the aerospace and defense supply chain. On June 18, 2026, DOJ announced that a Huntsville, Alabama defense contractor agreed to pay $507,144 over two Navy contracts. When the Defense Contract Management Agency assessed the company’s environment, the score came back at negative 170, on a scale that runs from 110 down to negative 203. Law-firm write-ups of the settlement agreement say the company had reported a perfect 110 on its own self-assessment. DOJ’s announcement mentions no whistleblower. The government assessed the company and found the gap itself. Here too, the claims are allegations only.

Two more settlements were announced in the same stretch, one on September 1 and one on November 13, according to legal press coverage. Four in five months, during a pause.

Why your SPRS score is the claim

DOJ’s theory in these cases is short. The contract required the controls. The company said, through its score and its invoices, that the controls were in place. By the government’s account, they weren’t.

Phase I puts a name on that statement. Under 32 CFR 170.22, a senior official at your company affirms in SPRS that you’re still compliant, after each self-assessment and every year after that. In a lot of smaller companies, that official is the owner.

We know what that kind of signature weighs. We sign tax filings in multiple states every month, and we don’t sign a number without seeing what’s behind it. A cybersecurity score deserves the same treatment as a tax return.

Where the score and the network drift apart

The usual cause is drift, and rarely anyone lying. Someone scored the company two or three years ago, often from a template SSP, and the network kept changing. A new file-sharing tool went in. A cloud backup was never checked against FedRAMP. A POA&M item got marked for “next quarter” and stayed there. We see it on the networks we take over more often than you’d expect: the SSP describes one business and the live systems describe another.

There’s a second thing owners miss. The person who knows your real score is whoever runs your IT, and in the November 3 case that person filed the lawsuit. If your IT lead has told you the posted score is wrong, start with that conversation.

This is also why we only take on CMMC readiness work for companies where we also run Managed IT Services. The SSP and the live systems have to be kept by the same team, or the document starts drifting the week after it’s written. We’re a Cyber AB Registered Practitioner Organization (RPO), so we get companies ready for assessment. Certifying is the C3PAO’s job, and we don’t do it.

What to check this month

Pull three things:

  1. The score posted in SPRS, and the date on it.
  2. Your current SSP.
  3. Your open POA&M items.

Read them against the network you run today, including every cloud service that holds CUI.

If everything lines up, write down how you verified it and set a date to do it again. A gap calls for a different order of operations. Close the controls you can, then correct the record. We’re an IT and compliance readiness firm and can’t give legal advice, so if the gap is wide, bring your attorney in before you change anything in SPRS.

Want a second set of eyes first? Book a 30-minute exploratory call and bring your SPRS score and the date on your SSP. We’ll tell you where we’d expect the two to disagree and what it would take to close the gap.

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 still required while Phase II is paused?

Yes, in part. Phase I is in force, so Level 1 and Level 2 self-assessments and the annual affirmation in SPRS still apply. What the Department of War suspended on July 13, 2026 is the requirement for third-party C3PAO certification as a condition of award. DFARS 252.204-7012 and NIST SP 800-171 were not suspended.

What is an SPRS score?

SPRS is the Supplier Performance Risk System, the Department of War database where a contractor posts the result of its NIST SP 800-171 self-assessment. The score runs from 110 (all 110 controls in place) down to negative 203. Contracting officers can see it, and a senior company official affirms it.

Can a small subcontractor end up in a False Claims Act case over cybersecurity?

The June 2026 settlement involved a Huntsville, Alabama contractor with two Navy contracts, which paid $507,144 by the Justice Department's figures. Subcontractors that handle CUI inherit the same DFARS requirements from the prime through flowdown clauses. Whether a specific situation creates liability is a question for your attorney.

Does there have to be a breach for the government to bring a case?

No breach is reported in the Justice Department's June 18 or November 3, 2026 announcements. Both describe controls that were required by contract and allegedly not in place. Both are allegations, with no determination of liability.

How often do we have to re-affirm our SPRS score?

Under 32 CFR 170.22, an affirming official submits an affirmation in SPRS when a self-assessment is completed and annually after that. A Level 1 self-assessment is repeated every year. A Level 2 self-assessment is good for up to three years, with the affirmation still due each year.

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.