Cybersecurity Awesomeness Podcast · Enterprise Management Associates

Cybersecurity Awesomeness Podcast - Episode 138

December 12, 2025·16 min·1 clip
With 20 years of experience, Eric Swalke argues you can't secure APIs with code fixes alone because attackers will always find new ways to exploit business logic.
Chris Steffen opens the show with Eric Swalke from Salt Security. They spend most of the episode on API security, and the conversation stays grounded in practical concerns. The first thread is discovery: if a company does not know where its APIs are, it is already behind. That matters even more once AI and agents enter the picture, because those systems sit on the same API layer. Chris presses on the gap between organizations that know they are API-driven and organizations that have actually mapped the risk. Eric keeps coming back to the same basic point: the nervous system under modern software is still the API layer. The pair also talk through standards and the way teams sometimes assume a standard exists, so the problem must be handled. It does not. A major part of the discussion is the old question of shift left versus runtime protection. They treat secure coding as necessary, and they also argue for posture governance and runtime visibility so real traffic and misuse can be seen. The episode makes room for AI coding assistants too. If the tool is helping write the code, it can also widen the surface area. The conversation keeps tying that reality back to discovery, visibility, and control. There is also back-and-forth about agentic systems. Those projects do not escape the API problem; they depend on it. By the end, the episode lands on a simple operating idea: treat APIs as core defense work, not an afterthought. It closes like a security conversation between people who expect the mess and still want something usable out of it.

As heard by us

The risk is not just the API teams know about, but the one they have not mapped.

Chris Steffen and Eric Swalke spend the episode on API discovery, visibility, and the security gap that opens once AI projects lean on the same plumbing.

Read the full review in PlayNext →

Why you'd press play

API security gets real when AI agents and developers share the same plumbing.

Read the full recommendation in PlayNext →
Listen to the show on