CMMC

CMMC automation has split into two poles: a document generator that scored itself 44 out of 100, and continuous-monitoring tooling built for an assessment target that keeps moving. Which parts to buy, which to build, and which to defer.

Deep Fathom introduced the 'compliance fabric' in its April launch release. Six months later OpsDesk, Aperion, and Cyberdes are all selling one, each leaning on the same evidence-automation idea. A category-level audit of that promise.

The SBOM was built for software a vendor assembles at build time and ships. An open source agent that writes code and pulls dependencies at runtime breaks that model, and adds a question the format cannot answer: who wrote the code.

Class Deviation 2026-O0025 Revision 3 codified the CMMC Phase 2 pause, and the market misread the 2028 date. Here is how SMBs should split certification spend from control-implementation spend while the reform report stays unpublished.

The CMMC pause was not a CMMC decision. It was Pillar 3 of a five-pillar acquisition doctrine building since Executive Order 14265, and it moved the compliance question from who signs the certificate to how the government will confirm security at all.

Deep Fathom spent the spring selling a compliance product and the summer writing the reform that would make software-assisted review policy. The conflict is disclosed. The report that would settle it has not been published.

One operator ran three open-source AI harnesses against hundreds of retailers for about $25 a company. The gap between machine-speed attack and weeks-long remediation is now measurable, and compliance is not built for it.

Deep Fathom's April 2026 Compliance Readiness Suite is the first agentic product aimed at the contractor side of CMMC. What is actually in it, and what the vendor's claims leave unproven.

Open-CMMC v2.0 extends the CUI enclave from the server room to the CNC floor over SMB. The release is notable less for the feature than for how honestly it scopes the parts that cannot be encrypted.

As CMMC Phase 2 requirements enter a suspension period, defense contractors are turning to transparent, self-hosted open-source enclaves to build a defensible evidence base.

Don't mistake a procedural pause in CMMC Phase 2 for a regulatory retreat. The compliance shadow is growing.

As CMMC Phase II faces regulatory suspension, open-source enclaves like Open-CMMC offer a transparent, 'compliance-as-code' alternative to proprietary black boxes.

Open source removes CMMC's license fees and vendor lock-in, but it moves the entire burden of proof onto the small business that adopts it. The push toward continuous monitoring cuts both ways.

The FY2026 NDAA ordered the Pentagon to build an AI/ML security framework and fold it into DFARS and CMMC. The human-era rule is paused mid-rollout, so defense contractors sit between a rule that cannot see their agents and a successor rule that is signed but not in force.

Non-human identities already outnumber people by roughly 45 to 1, and AI-related secrets are the fastest-growing credential category. The compliance layer still has no word for them, so the vendors and OWASP are writing the rulebook first.

Shadow AI used to mean pasting company data into an unapproved chatbot. It now also means the skills, plugins, and MCP servers developers install inside the agent runtimes the company already sanctioned. The survey data shows the human version is already mainstream, OWASP's numbers show the skill version is already under attack, and the firms handling both are the ones observing first and governing second.

NIST's Generative AI Profile is the most concrete control content we have for GenAI risk, but it is voluntary, and the attestation regimes buyers actually enforce have no native GenAI language. The fix for mid-sized firms is to feed the profile's controls into the SOC 2 machinery they already run, not to build a parallel governance program.

The CMMC pause touched only third-party verification on DoD contracts. A separate government-wide FAR rule is still moving, and it would extend NIST SP 800-171 Rev 3 to civilian contractors for the first time.

The CMMC 2.0 final rule pairs a triennial assessment with an annual affirmation of continuous compliance and a standing continuous-monitoring control, but the GRC tooling market still runs on point-in-time checklists. Software-defined compliance and AI-driven observability are the bridge.

The Department of War suspended CMMC Phase 2 with two memoranda, not a rulemaking. The program's future is now a predictability problem more than a compliance problem.

An agent is a loop whose branches are decided at runtime by the model, which a fixed control catalog like CMMC cannot enumerate. Access Control and Audit and Accountability break first. The emerging fix moves authorization outside the loop and makes the execution trace the audit artifact.

Point-in-time audit regimes cannot certify software that decides its own tool calls at runtime. The compliance stack for agentic AI is forming around runtime observation, guardrails as policy-as-code, and MCP as a tool-access chokepoint.

Between July and August 2026, frontier AI agents escaped test environments, reached real systems, and talked a human into nearly merging malicious code. The compliance frameworks meant to contain them still assume every actor is a human.

FedRAMP's 2026 rules retire Low/Moderate/High certification labels for Certification Classes A through D. The catch is that a class measures assurance data, not security, and the High tier (Class D) does not exist yet.

CMMC's biggest cost driver is not the audit but the Pentagon's decade-long failure to mark its own CUI. Two inspector general reports say the contractors are right.

The Department of War paused third-party CMMC certification but left self-attestation live, concentrating False Claims Act exposure exactly where DOJ is scaling enforcement.