The compliance funnel narrows twice. The gate almost everyone skipped was never paused.

Certificates, posted scores and verified scores count three different populations, and the distance between the first two is where the real exposure sits. Tens of thousands of companies that handle controlled unclassified information appear to have no current score on file — an obligation in force since November 2020 that no pause has ever touched.

Two numbers appeared in this brief last week: 2,362 final Level 2 certificates, and 78.2% of surveyed contractors continuing toward certification or already holding one. Reading them side by side invites a conclusion that neither supports. The first is a count from the certificate register. The second is a percentage of respondents to a single survey whose sample size was not disclosed and which, like every voluntary compliance survey, over-represents companies already engaged with compliance work. Different denominators, and neither of them is “the industry.”

The useful way to look at it is as a funnel with three gates. Each one measures something different, and only one of them has ever been paused.

The gateWho is through itWhat it actually proves
Says — you owe a self-assessment and an annual affirmationBetween roughly 76,600 and 128,400 entities handle CUI, depending on which Department estimate you useNothing yet. This is the obligation, not the evidence.
Scores — a current NIST SP 800-171 score posted in SPRS42% of contractors surveyed in 2025 and 59% in 2026 said they had one — survey figures from self-selected samples, not register dataThat you did the arithmetic and signed your name to the result.
Proves — a third party checked the work2,362 final Level 2 certificates, plus 71 conditionalThat someone outside your company verified it. These are the only externally validated 110s in existence.

Run the two survey figures against the two population estimates and the number of CUI-handling companies with no current score lands somewhere between roughly 33,000 and 75,000. The range is wide because the error runs in both directions: survey samples skew toward firms already doing compliance work, which understates the gap, while the population estimates may include companies that only ever handled federal contract information and never owed a numeric score, which overstates it. Nobody outside the Department knows the true figure, and anyone quoting you a precise one is guessing. The order of magnitude is not in doubt.

Here is why the middle gate is the one to care about. What was suspended on July 13 was the third gate — the requirement that an accredited third party verify your work before you could win certain contracts. The second gate was never paused, never deferred and never softened. The SPRS self-assessment and the annual affirmation have been a condition of DFARS-covered contracts since November 2020. A missing score is not a deadline you have yet to reach. It is a representation you have been making — or failing to make — for six years.

And a score is a representation, not a status. Two settlements on the public record make the point without CMMC needing to exist at all: one contractor self-scored a perfect 110, a government assessment later put the real figure at −170, and the 280-point gap resolved for $507,144; another paid just over $2 million over the state of a single network. Neither case turned on a certificate. Both turned on what the company had said about itself.

One clarification worth having: a CMMC Level 1 self-assessment produces no number at all. It is recorded as met or not met across the fifteen basic safeguarding requirements. The −203-to-110 numeric score is a Level 2 construct, tied to the 110 requirements of NIST SP 800-171. So every statistic you read about “SPRS scores” is a statement about Level 2 — which means that if you handle CUI and you go looking for your number, it should be there. If it is not, that absence is the finding.

One more honesty note, since the certificate figure is the number most often quoted back at this audience: those Level 2 totals count certificates issued against assessed information systems, not unique certified companies — a firm with two in-scope enclaves can appear twice, and nobody publishes a company count. The top of this funnel is an estimate, the middle is a survey, and the bottom is a register of systems. Be suspicious of anyone who hands you a clean percentage.

So what: open SPRS this week and write down three things: the score, the date it was posted, and the level it was posted at. If any of the three is missing, or if the date predates your last material network change, you have found this week’s priority — and it is not a planning exercise, it is a filing. Certification is the gate the Department paused. The score is the gate it never touched, and it is the one with your signature on it.

While the certificate machinery waits, the government spent the first week of October publishing the floor

Two documents landed in the first eight days of October. Neither is a rule and neither creates an obligation — and together they are the clearest signal yet about where the technical bar is heading, including into a part of your operation that CMMC does not currently reach at all.

On October 1, the Department of War’s Office of the Chief Information Officer launched a campaign called “Brilliant at the Basics” for Cybersecurity Awareness Month, covering fundamentals across both information technology and operational technology environments. CIO Kirsten Davies framed it plainly: “Cybersecurity starts with the basics.” What makes it relevant here rather than a poster campaign is the audience line — it names defense industrial base partners explicitly, including small, medium and nontraditional businesses, promises tailored guidance for them, and says it will highlight low-cost and no-cost cybersecurity support programs aligned to the IT and OT practices the Department issued in July.

The four weekly themes — a serviceable self-check: Be Aware: know your digital environment and find the vulnerabilities in it, across IT networks, OT infrastructure and government-furnished equipment. Be Vigilant: strong authentication, disciplined credential habits, anti-phishing. Be Secure: reduce internet-facing systems, encrypt connections, apply patches, and allow only authorized equipment onto defense networks. Be Connected: report suspicious activity quickly and act on cyber tasking orders.

Then on October 8, the National Security Agency published a Cybersecurity Information Sheet titled Hardening Department of War Critical Operational Technology Environments with Zero Trust Principles. Its stated audience is National Security Systems, Department of War and — named directly — Defense Industrial Base network system owners and operators. Trade reporting counts 26 high-impact activities, written to work on legacy equipment that cannot natively support modern security tooling.

The prescriptions are concrete: remove direct internet connections to operational technology wherever possible; phishing-resistant multifactor authentication and privileged access management; hard scrutiny of vendor connections; an accurate OT asset inventory with named owners and criticality ratings; macro- and microsegmentation with monitoring; smart controllers shielded behind external controls, with default passwords changed and unused logic disabled; protected engineering workstations and human-machine interfaces; OT telemetry fed into monitoring; passive validation preferred over active testing; and patching sequenced by exposure, with compensating controls where a patch has to wait.

Notice what that list is not. Nothing in CMMC Level 2 asks you to inventory the programmable logic controllers on your shop floor or to disable unused logic in a smart controller. The Department’s CIO has been arguing since August that operational technology is the harder problem and that protecting federal data is “table stakes” — this is the first time that argument has arrived as a technical document with the defense industrial base written into the audience line. The overlap with what you already owe is larger than it looks, too: reducing internet-facing systems, patching by exposure, keeping an accurate asset inventory, segmenting and monitoring the network are all requirement families sitting behind your SPRS score today. What is new is the scope — the same expectations, pointed at machines that have never been inside the boundary.

So what: build the list you almost certainly do not have. One inventory of every operational-technology device — controllers, machine tools, test rigs, engineering workstations, human-machine interfaces — sitting inside or adjacent to the boundary where controlled data lives, each with an owner and a criticality rating. That inventory is the first thing NSA’s sheet asks for, and it is the first thing any future scope expansion would ask for too. It is a week of work now against a scramble later. In the meantime the four weekly themes make a self-check your own auditors will recognize line for line.

One agency already built a harder version of this, and it did not pause anything

“Paused” describes one program at one department. It is worth knowing what the rest of the government has been doing with the same subject matter — because at least one agency has gone considerably further, without rulemaking, without a phase-in, and without much notice.

On January 5, 2026, the General Services Administration introduced an IT security procedural guide titled Protecting Controlled Unclassified Information (CUI) in Nonfederal Systems and Organizations Process. Contractors whose systems process, store or transmit CUI under GSA contracts are required to implement NIST SP 800-171 Revision 3 — not the Revision 2 baseline the Department of War is operating under — alongside selected draft SP 800-172 requirements and certain SP 800-53 Revision 5 privacy controls.

The mechanics are stricter than CMMC Level 2 in nearly every dimension that costs money. Nine “showstopper” controls — access control, multifactor authentication and boundary protection among them — must be in place before approval, with gaps elsewhere documented in a plan of action and milestones. Approval runs through five phases and a stack of documents: a system security and privacy plan, a privacy threshold assessment, a privacy impact assessment, an architecture review checklist, a supply chain risk management plan and a security assessment report. There is no self-assessment route to approval — a third-party assessment is required, by a FedRAMP-accredited assessor or one GSA approves. Cyber incidents involving CUI must be reported to GSA within one hour of identification, against the 72 hours you are used to. Reassessment runs every three years, with quarterly scan reporting in between.

And there is no phase-in. Practitioner analyses published in the spring noted that the requirements can appear in a new solicitation or be added to an existing contract at a contracting officer’s discretion, and that CMMC and FedRAMP packages do not transfer across — the baseline is a revision ahead, the document set differs, the assessor pool differs. A company holding a Level 2 certificate and a GSA schedule has two compliance programs, not one.

This is also a preview: the FAR CUI rule still awaiting a final version would push a Revision 3 baseline and a standard CUI identification form across civilian agencies government-wide — a milder, broader version of what GSA has already done for itself. The civilian side is not waiting for the Department of War to finish rethinking its program.

So what: check whether any contract or live bid in your portfolio sits on the civilian side and touches controlled unclassified information. If one does, your Revision 2 posture is not the standard being applied to it, your self-assessment is not the evidence being accepted, and your 72-hour incident clock is not the one that runs. Most defense suppliers carrying a GSA schedule have never reconciled the two regimes, and the discovery usually happens inside a solicitation response, on somebody else’s deadline. Doing it this month costs you an afternoon.

What to do this week

The theme this issue: the obligations nobody paused are the ones with your name on them.

  • Pull your SPRS record and write down three things. The score, the date it was posted, and the level. Missing or stale on any one of them is this week’s priority, ahead of everything else on this list.
  • Say out loud which gate you are actually through. Owing a self-assessment, having posted one, and having had one verified are three different positions. Only the last is evidence — and only the middle one is overdue.
  • Inventory your operational technology. Every controller, machine tool, test rig, engineering workstation and HMI in or adjacent to the controlled-data boundary, with an owner and a criticality rating. Item one on NSA’s October 8 sheet.
  • Check the civilian side of your portfolio. Any GSA or other civilian-agency work touching CUI runs on a Revision 3 baseline, a third-party assessment and a one-hour incident report. Your DoD package does not transfer.
  • Write the one-page incident card. Who declares an incident, who files to the Department inside 72 hours, who would file to CISA under the rule now in White House review, and where the preserved evidence lives. Names on each line, not role titles.

Quick hits

  • Oct 1, 2026
    A second incident-reporting clock reached the White House.
    CISA sent the final CIRCIA rule to the Office of Information and Regulatory Affairs on October 1, after missing a statutory deadline in 2025 and its own targets in May and September. The statute sets a 72-hour report for covered cyber incidents and a 24-hour report after a ransom payment — the second of which has no analogue in DFARS 252.204-7012. The exemption for entities already reporting comparable information to another federal agency only operates once CISA and that agency have an agreement in place, and none exists yet, so the realistic planning assumption is two reports to two agencies for one incident. Interagency review can run 90 days or longer, so publication is likely early next year — exactly enough time to work out who in your company would file what, calmly.
  • Oct 5, 2026
    NIST published a free, state-by-state finder for local cybersecurity help.
    The agency’s small business engagement lead launched a Small Business Cybersecurity Support Program Finder: an interactive map and alphabetized table of local non-profit programs offering cybersecurity education, risk assessments, penetration tests, compliance consulting and incident preparedness. NIST is explicit that the list is not exhaustive and that it does not vouch for the programs on it. For a supplier with no budget line for any of this, it is a starting shortlist rather than an answer — the implementation, the score and the affirmation stay yours either way.

Not sure where your organization stands?

CUI Vault gives you a live, always-audit-ready picture of your CUI environment and NIST 800-171 posture — so headlines like today’s are a footnote, not a fire drill. Reach out to your NtelSec team to talk through your current gaps.

This briefing is a general-information summary of publicly reported CMMC and CUI developments. It is not legal advice; consult your compliance counsel before making contractual or certification decisions.
Talk to us about CUI Vault All issues