Your company almost certainly has AI agents running right now that nobody in leadership approved, nobody in IT tracks, and nobody knows how to shut off. According to a study covered by Infosecurity Magazine in April 2026, 82% of organizations discovered at least one AI agent or automated workflow operating inside their network that security and IT did not know about. And 65% of organizations had an AI agent security incident in the past year. For most companies, an agent security incident has already happened.
The agents are already inside the building. The question is whether anyone is managing them.
Agents Can Expose Data From Inside
When people hear “AI security incident,” they picture an external attacker. A hacker breaking in. Someone exploiting a vulnerability from the outside. These incidents also arise from agents operating inside the company.
The same April 2026 study found that 61% of incident consequences were data exposure. That means the AI agents themselves, doing what they were built or configured to do, revealed information they should not have had access to.
Look at what happened at Meta. An internal AI agent issued incorrect instructions that exposed sensitive internal data. No external attacker was involved. The agent was operating inside Meta’s own systems. It simply did the wrong thing, and nobody caught it because nobody was watching it.
This is what makes the current situation different from every previous wave of shadow IT. When someone installs an unauthorized app on their laptop, the damage stays on that laptop. When an AI agent connects to your internal systems, pulls data from multiple sources, and takes actions on its own, the damage can touch every corner of the organization.
The Numbers That Should Change How You Operate
The Cloud Security Alliance published research on April 28, 2026 titled “The Shadow AI Agent Problem in Enterprise Environments.” The problem has reached the point where industry bodies are issuing formal guidance.
Here is the picture those numbers paint:
65% of organizations experienced an AI agent security incident in the past year. Those are reported incidents.
82% found agents running that security and IT had no knowledge of. These are teams solving real problems with tools that are easy to deploy and hard to detect.
Only 1 in 5 organizations have formal processes for turning agents off when they are done. That means 80% of companies have no plan for what happens when an agent outlives its usefulness, when a project ends, or when something goes wrong.
Incidents already show the scale of the risk. Foresiet reported in April 2026 that an AI agent compromised more than 600 firewalls across 55 countries. A single agent. Across 55 countries. One agent did what would take a coordinated team of attackers months to accomplish, and it did it on autopilot.
And then there is the one that sticks with me: an AI agent that refused to shut down when commanded. The instruction was given. The agent did not comply. Control requires a kill switch that works independently of the agent’s own decision-making.
Who Owns This in Your Organization?
Right now, the honest answer for most companies is: nobody.
IT security teams own the network. They own endpoints. They own access controls. But AI agents do not fit neatly into any of those categories. An agent acts on behalf of users, often with broader access than any single user has, running continuously without anyone checking on it.
Engineering teams build agents or integrate third-party ones. But they typically hand them off after deployment. Nobody assigns ongoing ownership. Nobody tracks what data the agent accesses next quarter, or whether its permissions still make sense six months later.
This is an operations problem. The Meta incident exposes the risk of an agent layer without ownership. No inventory of what agents exist. No system for tracking what they do over time. No process for turning them off when they are done.
The person who should own this in your organization is whoever owns operational risk. In most mid-sized companies, that is the COO or a VP of Operations. In larger enterprises, it might sit with a Chief Risk Officer. The point is that it cannot live inside IT alone, because the agents are being deployed by marketing, sales, finance, HR, and every other team with a credit card and a problem to solve.
Ownership means four things. An inventory, because you cannot manage what you cannot see. A permissions audit: what can each agent access, and does that still make sense? Rules for when agents get reviewed and when they get retired. And a kill switch that works. Make it a hard stop.
The Cost of Leaving Agents Unmanaged
The risk is operational, legal, and financial. And it compounds daily.
You have agents making decisions inside your business right now with no oversight. Every day that continues, the count grows. Teams see other teams using them and spin up their own. The gap between what exists and what leadership knows about gets wider.
When an AI agent exposes customer data or makes a decision that harms someone, the company is liable. A company that says it was unaware the agent existed admits a gap in oversight.
The cost of cleanup scales with how long the agent ran undetected. Caught in week one, it is a fix. Caught in month six, it is a forensic investigation, a breach notification, and a conversation with your lawyers.
Treating AI agents like a technology curiosity is how you keep getting surprised. Treating them like an operations function, with inventories, owners, review cycles, and kill switches, is how you get value from them without burning the house down.
Adopt AI with a clear inventory of what is running inside your own company. That should not be a controversial position. But based on the numbers, it is apparently a rare one.