Skip to content
Compliant

When the "optional" document becomes the one everyone reads

The short answer

Practices cut from CMMC 1.0 have returned as voluntary guidance The unenforceable document is being read as the clearest signal of direction Risk reduction still matters, but its cost is what the pause aimed to relieve

One document lit by a spotlight among others

When the "optional" document becomes the one everyone reads

Something strange is quietly happening in defense cybersecurity, and it's worth naming plainly.

In July, the Department of Defense (still its legal name, whatever the signage at war.gov says) paused CMMC's third-party assessment requirement and stood up a task force to review the program. Alongside that pause, the CIO's office published "Brilliant at the Basics": two top-ten lists of cybersecurity practices, one for IT and one for operational technology.

Here's the part that stops you. Several of these "basic" practices aren't new. Some lived in the original CMMC 1.0, got stripped out when the program was slimmed to 2.0, largely because they were judged too costly and burdensome for small businesses, and have now reappeared in a voluntary campaign with no rule, no clause, no scoring, and no certification behind them.

So follow the path. A requirement clears formal rulemaking. It's removed through formal rulemaking. Then it walks back in through a webpage.

And the second half is stranger. Because the campaign obligates no one, technically it's just guidance. Yet the entire compliance industry is now reading it line by line, precisely because it's the clearest signal of where the department's head is while the binding rules are treated as if they're up for grabs. The enforceable documents get read as provisional; the unenforceable one gets read as prophecy.

Here's the tension nobody should wave away. Phishing-resistant MFA, real asset inventory, tested backups, these reduce risk, and adversaries aren't waiting on a task force. But that security costs money, and the cost of implementing NIST 800-171 is the exact burden Phase 2 was paused to relieve. So the relief and the reappearing requirements point in opposite directions.

I'm suspicious of anyone who claims a tidy conclusion right now. In the meantime, the most-read document in defense cybersecurity is the one nobody's required to read.

If you're trying to figure out how to navigate this shifting environment, or just want to talk through what it means for your program, reach out to me or the team at The Vizius Group. Happy to help you make sense of it.

#CMMC #DFARS #DefenseIndustrialBase #GovCon #Cybersecurity

Where we can help

Related offering · Compliant

CUI & ITAR Enclave Design and Build

"How much of the company really has to be in scope?"

Free tool · about 2 minutes

Take the blind spot check

Four questions for a quick read, then go deeper on your weakest area.

More in Compliant

Compliant

The Revolutionary FAR Overhaul deserves a place on your list

While attention is on CMMC, the Revolutionary FAR Overhaul may renumber every Part 52 provision and clause, which would break clause matrices and templates. Kyl notes that FAR 52.204-21's 15 FCI controls overlap with CMMC Level 1 without being the same obligation, and that public comment is open.

Kyl Gaston · 1 min read

Compliant

FCI, CUI, ITAR, EAR, FAR, DFARS: the cheat sheet

Kyl argues that confusing federal data and contract terms (FCI, CUI, ITAR, EAR, FAR, DFARS) can end a contract. The terms overlap but aren't interchangeable, and the post links to a plain-English breakdown of all six.

Kyl Gaston · 1 min read

Compliant

CMMC Phase II is suspended, but NIST 800-171 is not

On the July 13, 2026 suspension of CMMC Phase II, Kyl explains that only the DFARS 7021 certification gate is paused. DFARS 7012, which requires NIST 800-171, and the SPRS self-assessment duties still apply, and a proposed FAR CUI rule could widen 800-171.

Kyl Gaston · 1 min read

All Compliant posts · All Insights

Talk to a Principal Engineer

Got a question one of these posts didn't answer? Ask the engineer who would do the work.