Skip to main content

WeAreDevelopers World Congress North America. September 24, 2026, Stage 5.

Securing AI agent infrastructure

Identity, attestation, and behavioral trust at scale

Abdel Fane, Founder and CEO, OpenA2A

Slides from the September 24, 2026 session (PDF, 15 slides)

Three commands

The commands from the last slide. No account needed. Each tool works on its own.

  • Find what is running. Lists the AI assistants, MCP servers and credential references in a repository and the machine-wide configs it reads.
    Read the docs
  • Wrap one agent. Gives the agent an Ed25519 keypair, a capability grant, and an audit trail. Calls outside the grant are refused before they run.
    Read the docs
  • Break it on purpose. Damn Vulnerable AI Agent: deliberately vulnerable agents to attack locally.
    Read the docs

The demo from the talk

Same code, run twice. The second run has an identity: the agent is registered, granted logs:read and tickets:create, runs its job, and then tries http:post. In strict enforcement mode the SDK raises ActionDeniedError before the side effect, and the refusal is recorded on the audit trail.

from aim_sdk import secure

agent = secure("soc-triage-agent")

The demo project from the stage is not published; the SDK calls it makes are. The AIM docs cover registering an agent, granting capabilities, and reading the audit trail.

Resources from the talk

Tools

Specs

Sources cited in the slides

Research

Questions about the talk: info@opena2a.org