Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Watch five AI agents tackle a CTF and start coordinating with one another. Learn how to detect risky agent behavior using @goteleport graphs, risk scoring, and custom classifiers. Ben Arent explores lessons from the Hugging Face incident, then demonstrates how agent identity, scoped access, and activity monitoring help secure AI agents running against infrastructure.

70% of organizations give AI more access than a human in the same role would get. Not surprising when it is common for a team to click “always” when an agent asks to be allowed once or always allowed. That means the agent holds that access in perpetuity and turns into agent over-provisioning. Makes you wonder: Does an agent have more access to your organization's stack than it should and more access than the people who deploy them?

In this video, we'll look at a few key updates from Teleport's latest release v18.11.

We asked eight security and product leaders who's accountable when an agent ships to production and breaks something. Nobody said the model. Harish Gaggar named the reason. An agent runs on permissions someone approved and configuration someone set. Ron Reiter drew the line in the same place, accountability sits with whoever decided what the agent could actually do. As agents act across more systems, the accountability trail gets harder to follow. Most teams cannot determine which human granted an agent access.

What part of your profession do you hope AI takes over? What should it never touch? Security practitioners and technology leaders landed in the same place: hand off the tedious work, and keep human judgment on anything that affects blast radius. That's the skills reckoning. As AI absorbs the repetitive work, the expertise that decides what an agent is allowed to reach becomes more valuable.