
| June 18 | 8 a.m. PDT | 2 p.m. BST | 1 p.m. AEST |
| 45 minutes |
An AI agent just deleted data. Do you know why, who authorized it, what path it took — and how to stop it before it does more?
As AI agents move into engineering workflows, employee experiences, and enterprise operations, one thing is becoming clear: agents need to be treated as first-class identities. Not service accounts. Not API keys. Identities. With owners, lineage, authorization, and a way to stop them when risk changes.
We introduced the blueprint for the secure agentic enterprise to help organizations answer three critical questions: Where are my agents? What can they connect to? What can they do? Now see how those questions turn into controls.
Join Todd McKinnon, CEO and co-founder of Okta, and Harish Peri, SVP and GM for AI Security, for a special edition of Okta Streamcast on what agent governance looks like when identity is the control point.
This is where the blueprint gets practical: finding agents, tracing delegation, authorizing action, and stopping risk before it spreads. See exactly how these controls work in practice — from securing AI coding assistants like Claude Code, M365 Copilot, and Cursor and governing agent-to-agent handoffs, to AI agent authorization and containing rogue agent behavior with kill switch.
Join us to see where the blueprint goes next — and how its three questions translate into controls for governing agents across the enterprise.
