Zero trust has a big AI agent problem ahead
Experts argue agentic AI undermines zero trust: chained authorized actions create exfiltration paths, unregistered agents evade identity controls, and agent-to-agent messages stay opaque.
Security practitioners including Nik Kale (CoSAI), Krti Tallam (Kamiwaza.ai), and Mike Wilkes (Aikido Security) argue that agentic AI breaks zero trust assumptions because individually authorized actions can compose into unauthorized outcomes, such as chained reads and writes creating an exfiltration path. Most enterprise agents are unregistered shadow IT or third-party launched, subagents inherit privileges without recognized identity, and agent-to-agent communication, sometimes embedding instructions in media files, remains invisible to security teams. Proposed mitigations include short-lived delegated credentials modeled on OpenPGP subkeys, rate limits, sandboxing, approval gates, and immutable activity trails.
Linux Foundation takes on TRACE, a hardware-backed runtime evidence specification for AI agents
The Linux Foundation adopts TRACE, an OPAQUE-contributed spec giving AI agents hardware-attested, cryptographically verifiable runtime and compliance evidence.
The Linux Foundation accepted the TRACE (Trust, Runtime Attestation and Compliance Evidence) specification contributed by OPAQUE, developed with AMD, Intel, Microsoft, and the Technology Innovation Institute. TRACE binds runtime environment, software, policies, data classifications, and tool usage into a portable, cryptographically verifiable artifact, composing existing standards such as RATS, EAT, SLSA, SCITT, SPIFFE, and EAR. It recorded nearly 135,000 PyPI downloads within 10 weeks of its June 2026 introduction, and its technical workstream will be hosted by the Coalition for Secure AI.