Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

One of our most-loved features is Salt Cloud Connect. In a world of complex deployments, it’s a breath of fresh air: an agentless discovery model that delivers under 10-minute deployment and rapidly gathering API-specific info in cloud platforms. Customers plug it in, and in minutes, not weeks, they get a “traffic-free”, complete inventory of their APIs across AWS, Azure, GCP, Kong, and Mulesoft. This “ease of use” provides a “wow” moment of immediate visibility.

Threat researchers recently disclosed a severe vulnerability in a Figma Model Context Protocol (MCP) server, as reported by The Hacker News. While the specific patch is important, the discovery itself serves as a critical wake-up call for every organization rushing to adopt AI. This incident provides a blueprint for a new class of attacks that target the very infrastructure powering the AI Agent Economy. To understand the risk, we must first look at the mechanics of this emerging threat.

AI adoption has fundamentally redefined the role of APIs. They are no longer just conduits for data; they have become the “AI action plane” for autonomous systems. Every AI workflow, agent, and tool call now rides on an API, exposing a critical truth: you cannot secure AI without first securing your APIs. The H2 2025 State of API Security report reveals that this dependency is dangerously outpacing current security practices.

Receiving recognition from one leading analyst firm is a notable achievement. When two firms acknowledge your leadership, it clearly establishes a consistent pattern of market dominance. Following its designation as an Overall Leader in the KuppingerCole 2025 Leadership Compass for API Security, Salt Security has achieved the highest rating in the 2025 EMA PRISM Report for API Security.

It’s been a rough few weeks for burger chains. First, McDonald’s McHire chatbot was caught serving up candidate data through insecure APIs. Then Restaurant Brands International (RBI), home of Burger King, Tim Hortons, and Popeyes, had its APIs flame-broiled by attackers who discovered they could generate tokens without authentication, escalate privileges, and even eavesdrop on live drive-thru audio. When APIs become the secret sauce, leaving them unprotected is a recipe for disaster.

In our last post, we introduced the Model Context Protocol (MCP), the "brain" or "mission briefing" that guides an AI agent's actions. Most security teams are just getting familiar with prompt injection, the equivalent of tricking an AI with a single, misleading command. But that's like stopping a pickpocket at the door when a master spy is already inside, rewriting the mission plans. As AI agents become autonomous, the attacks become more profound.

In this series, we examined the vital connection between AI and APIs, highlighting what makes a leader in the API security market through the 2025 KuppingerCole Leadership Compass. Now, we turn to the core strategy of true API security: the full-lifecycle approach, where security is a continuous, integrated process rather than a single action.

In our previous post, we highlighted a key insight from the 2025 KuppingerCole Leadership Compass: securing AI depends on securing APIs first. The report emphasizes that as AI use grows, the attack surface for APIs becomes more complex and risky. With many solutions available, navigating vendor claims can be challenging, making independent expert analysis extremely valuable.

Over the last year, I’ve spent countless hours with CISOs, CTOs, and security architects talking about a new wave of technology that’s changing the game faster than anything we’ve seen before: Agentic AI and Model Context Protocol (MCP) servers. If you think AI is still in the “cool demos and pilot projects” stage, think again. We’re already seeing autonomous agents reasoning, remembering, and taking actions in live production environments.