You have Sentinel. You have Defender. Here is what fills the autonomous investigation gap between detection and autonomous resolution.
The post D3 Morpheus for Your Microsoft Security Environment appeared first on D3 Security.
The post D3 Morpheus for Your Microsoft Security Environment appeared first on Security Boulevard.
This week’s McKinsey incident should be a wake-up call for every enterprise moving fast to deploy AI.
Not because AI itself is inherently insecure.
But because too many organizations are still thinking about AI security at the model layer, while the real enterprise risk sits in the action layer: the APIs, MCP servers, internal services, and shadow integrations that AI agents can reach, invoke, and manipulate.
That is the part most companies still do not see.
The technical details matter here. Public reporting described an internal AI platform with a broad API footprint, including more than 200 documented endpoints and a set of unauthenticated APIs that could allegedly be reached externally. The same reporting described potential exposure paths to tens of millions of chat messages, hundreds of thousands of files, user accounts, and system prompts. Whether or not every possible impact was realized, the takeaway for security leaders is clear: when internal AI systems are wired into weakly governed APIs, the blast radius can become enormous very quickly.
And this is not an isolated case.
The McDonald’s AI hiring incident points to the same structural problem. Different companies. Different workflow. Same core mistake. Reporting on that case described exposed administrative access, weak authentication practices, and the potential exposure of a massive pool of applicant records. Again, the story was not just about the chatbot. It was about the application and API infrastructure around it.
That is the lesson the market needs to understand.
The real risk is not the LLM. It is what the agent can do.A lot of the AI security market today is focused on prompts, model behavior, jailbreaks, and output controls.
Those matter.
But they are only one layer.
In the enterprise, AI agents do not create value by talking. They create value by taking action. They retrieve data, call APIs, invoke tools, access systems, trigger workflows, and increasingly operate through MCP servers and connected services.
That means the real blast radius of AI is determined by the action layer.
This is why the industry framing of “AI security” is still too narrow. The attack surface is no longer just the model. It is the full connected system around it.
McKinsey and McDonald’s security breaches are the same storyAt first glance, these incidents look different. McKinsey was an internal AI platform. McDonald’s was an AI-powered hiring workflow.
But structurally they are the same. Both point to a growing enterprise reality: organizations are connecting AI systems to internal and external application infrastructure faster than they are securing that infrastructure.
And in many cases, the weakest point is not a sophisticated model exploit. It is a plain old exposed API, weak authentication, forgotten endpoint, misconfigured access control, or third-party integration that quietly became internet reachable.
That is exactly why I believe one of the most dangerous categories emerging right now is shadow APIs connected to agents.
These are internal or lightly governed APIs that were never meant to become part of an external attack surface, but once they are connected to copilots, workflows, MCP servers, browser agents, coding agents, or AI applications, they effectively become part of one.
The company still thinks of them as “internal.” The attacker does not.
The blind spot: shadow APIs plus agent connectivityThis is the gap I worry about most for enterprises today. Every company has APIs it knows about. Many also have APIs it has forgotten, never fully documented, or does not realize are externally reachable.
Now add AI. The moment an agent is connected to those systems, or an MCP server is exposed with access to them, the attack surface expands dramatically.
What used to be obscure, low traffic, and semi-internal becomes:
That is the shift. In the pre-agentic world, a hidden or weakly governed API might sit quietly for months or years. In the agentic world, it only needs to be reachable once.
The new security model enterprises needIf you are deploying AI, you need to stop asking only: Is the model safe? and start asking:
The next generation of AI incidents will come from agents sitting on top of weak action layers: exposed APIs, unauthenticated services, forgotten integrations, and misconfigured MCP servers.
This is exactly why we built Salt SurfaceAt Salt, we have spent years helping enterprises discover and secure APIs they did not know were exposed. That problem now matters even more in the age of AI.
With Salt Surface, organizations can map their exposed API footprint, including AI-related APIs and externally reachable services, without deploying an agent or installing anything in their environment.
If you are building with AI, the first question should not be whether your prompt is protected. It should be whether your action layer is exposed.
The model is not the whole attack surface. The API layer is.
Get your free exposure scanIf you want to know whether your company has exposed APIs, AI-connected endpoints, or internet-reachable services, we will show you. No installation. No heavy lift. Just a domain and you get visibility into the attack surface you need to understand now.
Request your free Salt Surface scan today.
Roey Eliyahu is the Co-Founder and CEO of Salt Security, the leader in Agentic Security.
The post An AI Agent Didn’t Hack McKinsey. Its Exposed APIs Did. appeared first on Security Boulevard.