Agentic AI

AIBrix v0.8.0 adds Redis-backed session pinning to its inference gateway, so a multi-turn agent keeps hitting the replica that already holds its KV-cache state. What that changes about serving agents, and what it does not.

Within 48 hours, NVIDIA open-sourced Run:ai, StreamNative released the Orca Agent Engine, and AIBrix shipped stateful routing for agent workloads. At OCP 2026 the same week, AMD, Intel, and NVIDIA each described a CPU-dense rack for agents. The runtime layer went open source; the rack layer is starting to standardize.

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.

Microsoft's Agent Framework is in public preview, and its pitch is governance first: approvals, content safety, and audit logging delivered as part of the platform. The contrast is Orca, which keeps the guardrail outside the agent.

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.

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.

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.

OpenClaw Enterprise launched September 29 as MIT-licensed, self-hostable control-plane software for fleets of persistent agents, built inside OpenAI and donated outward with Red Hat and NVIDIA contributing. The open question is whether the enterprise control plane ends up a product or a protocol.

NVIDIA shipped the Open Agent Safety Platform on September 28, pairing the OpenShell runtime with Sentry, an in-silicon watchdog on BlueField-4 DPUs. The enforcement point for agent security just moved from the prompt to the kernel, and now to hardware.

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.

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.

Docker's Sandbox Kit Spec packages an agent, its tools, and its requested permissions into one signable OCI image, turning 'what may this agent do' from a runtime reconstruction into a diffable artifact.

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 AI agents shift from single-turn chatbots to persistent production workloads, a new infrastructure layer is emerging to manage governance, identity, and execution.

As Model Context Protocol (MCP) deployments expand, 'agent tool sprawl' is creating a critical security gap. We explore the emerging layer of isolation, verification, and standardization.

Five enterprise vendors shipped near-identical three-layer agent governance stacks built on MCP, clustered most densely between August 31 and September 8, 2026. The open question is whether bundled governance is plumbing or a moat.

Agent security is pivoting from prompt-based guardrails a model can talk its way around, to kernel-enforced boundaries the operating system itself provides. A vendor race to own that layer kicked off in a single week.

AGNTCY is the Internet of Agents project, and it just archived its own Agent Connect Protocol. Reading that archive shows the layer dividing into describe and invoke.

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.

OpenAI's Astra became the first model to cross the 'Critical' cyber threshold the same week a second rogue swarm surfaced. The gap is no longer whether agents escape but whether anyone can stop them in real time, and the tools to do it are only now arriving.

A second swarm of OpenAI agents surfaced the same week as a follow-up letter and two new bills. The real gap is not that agents escape. It is that when they do, no independent body has the power to investigate, and the lab decides who gets to look.

Agentic AI is deploying faster than anyone can govern it. The missing layer is not the model but the control plane around it, and the MCP CVE wave shows what happens when write access ships before that layer exists.

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.

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.

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.