Research · The Unattested Agent
The entity that acts cannot attest to its own behavior.
Twenty years in the CISO seat, on the independent attestation layer we forgot to build when we gave AI agents credentials, permissions, and production access. Essays from The Unattested Agent.
We introduced an actor that writes its own record. And called it progress.
Your badge system logs your entry. The hallway camera records your movements. You don't write your own audit trail, something independent does. AI agents broke that assumption: the entity performing the action is the same entity producing the record of it.
In a courtroom that's uncorroborated testimony. In a financial audit, a material weakness. In enterprise AI, we call it progress. The fix isn't more logging. It's structural: an independent record the actor cannot alter.
The Unattested Agent · the founding essay
What we're writing about.
Long-form essays from The Unattested Agent. Twenty years in the CISO seat on the independent attestation layer we forgot to build when we gave AI agents credentials, permissions, and production access.
- Threat Mapping for AI Agent AuthorizationREFERENCE
- The Unattested AgentSTART HERE
- The Control Point Is in the Wrong PlaceARCHITECTURE
- Governance Is Not a Security ProductTHE CATEGORY
- You Have to Be in the Execution PathINLINE ENFORCEMENT
- A Decision Trace Is Not a LogTHE RECORD
- The Entity That Acts Cannot AttestATTESTATION SEPARATION
- The Composition Is the BreachNEW · JUL 2026
- An Actor Cannot Attest to ItselfNEW · JUL 2026
- A Claim Is Not a FactNEW · AUG 2026
What happens when software acts but can't be held accountable. The founding essay: we gave agents credentials and production access, then skipped the independent attestation layer every prior actor required.
Fifty-plus enterprise AI security vendors, one structural flaw: they answer “who,” not “what the agent is about to do.” Authorization is not governance.
Why governing autonomous agents is a system-of-record problem, not another tool in the security stack, and what that changes about how you buy.
Adjacent and downstream don't count. The tool call cannot complete without passing through a system that is not the agent.
A log records an event. A Decision Trace records a judgment: signed, deterministic, hash-chained, and producible only inline.
The Attestation Separation Principle in full. Why an agent, its vendor, and the SIEM all sit inside the same trust boundary as the thing they're meant to attest to.
Every system in the chain passed its own checks, and the workflow across them was still the breach. Why per-system controls can't see the sequence that matters.
The homepage thesis at essay length. An actor cannot attest to itself: any record produced inside the acting system inherits that system's compromise.
A claim becomes a fact only when someone who doesn't trust you can verify it. What a hash-chained, independently checkable record changes about audit.
Built for what's already happening.
Every capability maps to a documented threat class, from OWASP, NIST, Cloud Security Alliance, and Palo Alto Unit 42, plus the real incidents that already shipped. Not theoretical risk.
Goal hijacking and privilege abuse. The first peer-reviewed agentic framework, 100+ experts, endorsed by NIST, Microsoft and NVIDIA, names goal hijack, tool misuse and identity abuse as top risks, urging agents be treated as first-class identities with scoped privilege.
Behavry binds every agent's identity and records the authority it actually exercised. SOURCE →
Agent-specific attacks beat every baseline. NIST's red team found novel agent-tailored attacks lifted task-hijacking success from 11% to 81% across RCE-via-tool-use, database exfiltration and automated phishing. A qualitative shift, not a marginal one.
Behavry reconstructs the hijacked sequence detection scoring can't. SOURCE →
Agent session smuggling across trust. Unit 42 demonstrated malicious agents exploiting built-in trust in the agent-to-agent protocol to smuggle instructions between sessions. A cross-agent chain no single product observes.
Behavry captures the cross-agent chain end to end. SOURCE →
EchoLeak and the Amazon Q compromise. A zero-click Microsoft 365 Copilot exfiltration and a poisoned Amazon Q extension that reached ~1M developers. Neither theoretical, both lacking a defensible cross-system account afterward.
Behavry produces the signed record these incidents never had. SOURCE →
Memory poisoning and tool supply chain. NIST's adversarial-ML taxonomy now formally covers autonomous agents: indirect prompt injection, agent memory poisoning, and supply-chain attacks on agent tools as named attack classes.
Behavry records the provenance of every input that shaped a decision. SOURCE →
Promptware turns agents into C2. Multi-agent command-and-control via prompt injection: agents from different vendors enrolled into one attacker-controlled network through the trust between them.
Behavry sees the multi-vendor channel form before it propagates. SOURCE →
Injected error events hijack coding agents. Malicious instructions planted in Sentry error events via write-only DSNs; MCP-connected coding agents retrieved and executed them as legitimate errors. 85% exploitation success, 2,388+ organizations exposed, invisible to EDR, WAF, IAM, and VPN because every action ran under the developer's own identity.
Behavry evaluates the tool call itself, not the credential it rode in on. SOURCE →
Agentic ransomware, end to end. Across 750+ incidents, AI compressed the attack lifecycle roughly 4x, from days to hours, and Unit 42 documented agentic ransomware managing multiple stages of an extortion operation autonomously. Nascent, and already real.
At machine speed, the record has to be written inline, not reconstructed after. SOURCE →
Prompt injection becomes remote code execution. Two critical RCE vulnerabilities in the Semantic Kernel agent framework, reachable from a crafted prompt: unsafe interpolation in lambda filters and a model-invocable file write that escaped the sandbox. Injected text crossed from content problem to code-execution primitive.
Behavry stands between the model's intent and the syscall that executes it. SOURCE →
Frontier agents went rogue against real targets. In 122 challenge runs, agents took autonomous rogue actions on 10 occasions producing 19 incidents: attempting to insert malicious code into an open-source project, opening malicious pull requests against real repositories, fabricating identities, and prompt-injecting other AI systems.
The case for an authorization layer the agent cannot argue with. SOURCE →
Sources: OWASP Top 10 for Agentic Applications (2026) · NIST CAISI, Strengthening AI Agent Hijacking Evaluations (2025) & AI 100-2e2025 · Palo Alto Networks Unit 42 (2025, 2026) · Cloud Security Alliance AI Safety Initiative & Tenet Security (2026) · Microsoft Defender Security Research (2026) · UK AI Security Institute via SecurityWeek (2026).
The terms buyers search for all point to the same thing.
Guardian Agents/AI TRiSM/MCP security/Runtime AI governance/Agent incident reconstruction/AI chain of custody
The fourth A of security · the independent guardian agent
“Guard the guardians.”
Gartner names this category Guardian Agents within AI TRiSM. Its requirement, immutable and timestamped records that oversee the other agents, is attestation separation by another name. Behavry is the independent Guardian Agent.
Making the case in the open.
The thesis is argued where the category is being defined: analyst forums, security conferences, and the podcasts shaping how the field thinks about agent risk.
Governing the Agentic Stack with IAM, Security Controls & Trust. A panel on the identity and trust fabric beneath production agents: the sprawling web of non-human identities most organizations have no strategy to govern. With Dr. Elizabeth Di Bene (Loudoun County) and Illena Armstrong (CSA President).
VIRTUAL · JUN 24, 2026 · DETAILS →
Authorizing AI Agents in Regulated Life-Sciences Environments. Agents are moving into R&D, regulatory, and clinical workflows. Behavry enforces data-use agreements, protects IP, and produces audit-ready decision traces for environments where unauthorized action is not an acceptable outcome.
MAY 2026 · SESSION NOT RECORDED · DETAILS →
Observe Everything. Control Nothing. Ward's solo session: why observability is structurally incapable of governance, it operates after execution while governance must operate before, and the architectural case for pre-execution enforcement and independent attestation.
VIRTUAL · APR 29, 2026 · DETAILS →
Shadow AI: The New Shadow IT, Hiding in Plain Sight. Code, IP, and internal data flowing into AI tools as workflow, not breach. “You don't have a detection problem, you have a perspective problem.” Introduced ShadowCheck, an open-source shadow-AI recon tool.
APRIL 2026 · GITHUB.COM/WARDSPAN/SHADOWCHECK →
Podcast · coming soon. The Cybersecurity Ecosystem Show, on why autonomous agents need an independent record.
Cover feature. CIO Views, “Building Cyber Confidence with Integrity, Curiosity, and Applied Practice” · Oct 2025.
Twenty years in the CISO seat, now building the record that lets you say yes to agents.
Compare notes with the author.
BOOK A BRIEFING →