Hello listeners. Today we are kicking off a new series entitled the AI Control Loop,

how enterprises govern the AI they've already deployed, sponsored by our friends at Wallarm.

Wallarm is the AI control platform for Enterprise AI, protecting every AI workload, API, and application

in production, giving CSOs the

governance they need and CIOs the speed they demand.

Organizations choose Wallarm for a complete inventory of APIs, AI agents, and AI apps,

using patented AI ML-based threat detection and blocking that operates at production traffic speeds.

Today's episode is entitled AI Security IS API Security, and joining us is Tim Erland, VP of Product Marketing at Wallarm.

We discussed the foundational link between AI security and API security, digging into the role that APIs play in the dev, deployment, and operations of AI.

We explore how they contribute to the risk profile of AI transformation projects and how securing APIs is critical for successful AI transformation.

Tim, thank you for being on the show today. Thanks for being on Code Story. My pleasure. I'm happy to be here. Really excited to dive into Wallarm and all the things there and our topic for today, which today's episode is entitled, AI Security is API Security. Really excited to dive into all things there. Before we do, tell me in my audience a little bit about you.

Sure. My name's Tim Erlin. I'm the VP of Product and Security Strategist at Wallarm.

I've been at Wallarm about three years. I've been in cybersecurity for 20 plus years and really joined Wallarm because I saw this gap in the market around API security.

It was a gap that I tried to get into in the past or tried to solve in the past. And I felt like Wallarm really was well positioned to address something that just seemed like it was missing in the space. So that's why I dove into API security. Amazing. That's very cool. What do you do for fun? Fun? I play soccer and I'm mountain bike as much as I can. Nice. Very cool. So you're obviously in good shape. Both of those are very grueling,

grueling sports. I do both of those things much more slowly than I would like to.

Okay, cool. Let's dive into the meat of it then. My first question is around AI security. And when

people hear AI security, they often think first about models,

prompts, or training data. Why do you argue that AI security starts with APIs?

So I think to answer that question, you just have to start thinking about how AI works,

not from a model standpoint, but from an interaction standpoint. So when you connect to an AI works, not from a model standpoint, but from an interaction standpoint.

So when you connect to an AI tool, you're connecting over an API.

That web interface that you might be using, ultimately that's a web interface backed

...