Teleport Launches Beams — Trusted Agent Runtimes For Infrastructure
Learn More

MASTERCLASS SERIES

ARCHITECT TRACK

The Technical Deep Dive

How to secure non-deterministic AI workloads, implement secure MCP, and turn Kubernetes into your identity control plane

What You'll Learn

  • Why deterministic → non-deterministic is the fundamental shift (and why infrastructure isn't ready)

  • The "toddler with root access" problem: what happens when AI agents have unlimited permissions

  • How certificate-based authentication becomes the perfect fit for AI workloads

  • MCP's security gaps (OWASP top 10 AI threats) and how Secure MCP solves 5-6 of them

  • Why Kubernetes is the AI platform (and how to unify access for humans + machines)

4 minutes, 34 seconds

Featuring Teleport Engineering Leaders

Background image

Key Technical Insights

"Agentic AI is like a toddler with root access"

If you don't provide limited access, AI will probe everything. It might rm -rf your root directory. It might dump your database. If you give the permissions, the LLM will use them. This isn't malicious—it's how non-deterministic agents work.

"Deterministic → non-deterministic is the fundamental shift"

Traditional CI/CD: input A → output B. Predictable. Testable. AI agents: make decisions on your behalf. The path changes every time. Infrastructure built for deterministic code isn't ready for non-deterministic agents.

"Certificate-based auth is the perfect fit for AI workloads"

Ephemeral certificates let you define: who you are, how long you exist, what you can access—all in a cryptographic passport. For non-deterministic AI that changes every run, dynamic scoping on every task is crucial.

"MCP didn't solve OWASP top 10 AI threats out of the box"

MCP brought large adoption for providing context to LLMs. But young protocols lack enterprise features. Vanilla MCP had no answer for agentic security threats. Secure MCP covers 5-6 of the top 10 threats through identity-based access.

"Sam Altman was right: Kubernetes is the AI platform"

OpenAI runs ChatGPT on Kubernetes. Everything they do is Kubernetes-first. The same tools that define access for humans can define access for AI agents. One control plane, one identity model, humans and machines.

"The easy button for Kubernetes access (for humans AND AI)"

Defining roles, the who/what/why/how of Kubernetes access—same technology, same knobs, whether it's a human engineer or an AI workload. Unified access eliminates tool sprawl and identity fragmentation.

Related Insights

00:60

The Secure MCP Problem

Why giving static tokens to AI agents creates persistent attack surfaces—and how to eliminate them.

00:45

Non-Human = Human Identities

How to treat machines the same as humans with short-lived credentials and ephemeral access.

00:50

Certificate-Based Architecture

How X.509 certificates and SPIFFE become the foundation for unified identity across your entire platform.

00:43

2026: AI Goes to Production

Why 2026 is the year AI graduates from labs to production at scale—and what that means for infrastructure.

Questions for Your Team

Technical discussion starters:

1. Do we currently give AI agents static tokens or long-lived credentials? What's the blast radius if they leak?

2. How are we scoping permissions for non-deterministic workloads? Can we define access per-task, or is it all-or-nothing?

3. If we're using MCP, have we addressed the OWASP top 10 AI threats? Which ones are still gaps?

4. Do we have a unified identity layer for Kubernetes, or are we managing humans and machines separately?

5. What would it take to move from static credentials to certificate-based ephemeral identity across our AI workloads?