Compliance

The DoD's suspension of CMMC Phase 2 is a tactical pause, not a regulatory repeal. Contractors face a growing 'compliance debt' as CUI frameworks evolve faster than certification processes.

The SBA put assessor supply at about 100 without saying what the count measured, and the department used the same figure the same day. Four days later the accreditation body counted over 1,000 certified assessors. The ratio in the press release described a population and a label, not a queue.

NIST's 27 October design tenets answer how much autonomy an agent should have by handing risk thresholds to the deploying organization. OWASP's AISVS already tests much of the machinery, including when a human must approve an irreversible action. Neither document tells you what your thresholds are, or how much escalation a reviewer can absorb before approval becomes habit.

TRACE shipped a signed record that proves who wrote it and not what the chip did, and its own documentation says so. Its sponsor wound down seven weeks after the Linux Foundation adopted it, and the compliance frameworks it was built for have no slot for it.

The CMMC Reform Task Force's summary, obtained by Federal News Network, recommends restarting Phase 2 on a narrower population within a 90-day horizon and widening POA&Ms from 180 to 270 days. The narrowing runs through a CUI marking rule that has not published, and the summary was assembled in three days without the program office's involvement.

NIST's one substantive agent document of October 2026 was joint-agency incident practices for agent misbehavior, aimed at frontier labs and disclaiming compliance use. The benchmark guidance and the identity practice guide are still drafts, and an executive order renamed the program without changing the definitions inside it.

The Phase 2 pause cut the schedule assessment firms were hiring and pricing against. Named assessors describe layoffs and cancellations, the accreditation body's own numbers show capacity still growing, and the one figure that moved the wrong way is the number of assessments in progress.

The first surveys since the CMMC Phase 2 pause show the compliance drift mostly did not happen. About 78% of contractors kept going; a roughly 22% minority slowed, and the pullback was in certification spend, not controls.

A contractor can inherit 80 to 90 percent of its CMMC controls from an MSP or cloud platform. The shortcut solves the cost and assessor bottleneck, and it concentrates the residual risk in a customer responsibility matrix most small firms can't read.

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.

Microsoft's Agent Control Specification and CSA's AARM both name the runtime-governance layer, from opposite ends. AARM writes mandatory requirements, including universal pre-execution interception and tamper-evident receipts. ACS writes the interface: lifecycle hooks, normalized verdicts, fail-closed enforcement. What was a gap diagnosis now has two competing specs.

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.

Project Gatekeeper is the Army's pilot of a commercial DevSecOps platform that lets vendors bring frontier AI models into the ATO pipeline. The evidence it generates still has to survive a human risk-acceptance decision, and no speed result has been measured yet.

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.

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.

As AI agents enter the Defense Industrial Base, they create a massive compliance blind spot. Traditional security models like sandboxing won't satisfy CMMC 2.0's data-layer requirements.

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.

Zero trust replaced the perimeter for enterprise IT, but autonomous agents stress it in new ways: authority delegated to a non-human principal, non-deterministic behavior, and an agent's instructions indistinguishable from its data. The response is forming on two tracks, containment and identity, and this post maps zero trust's pillars onto agentic controls.

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.

NIST's Center for AI Standards and Innovation launched the AI Agent Standards Initiative in February 2026, the first federal program targeting autonomous-agent governance. Here is what it signals, the compliance gap it exposes, and how organizations should prepare before voluntary guidance hardens into procurement and audit requirements.

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.

Three years of LLM security were spent on the input. The next boundary is proving what an agent did after the prompt left the model, which means turning execution traces into audit trails that are complete, tamper-evident, and portable across vendors.

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.