AI Agents Are Causing Security Incidents at 65% of Businesses. Here’s How to Not Be Next
New research from the Cloud Security Alliance and Token Security landed this year, and the number should stop you mid-scroll: 65% of organizations have already had a cybersecurity incident caused by an AI agent. Not a hacker. Not a phishing email. An AI tool they set up themselves.
Here’s the part that should really get your attention if you run a small or mid-sized business. Most of those incidents didn’t come from some sophisticated attack. They came from permission creep. A bot got access to something it didn’t need, nobody noticed, and it did what bots do: exactly what it was told, at scale, without asking questions.
What’s actually going wrong
Break down the data and three patterns show up again and again.
Sensitive data exposure hit 61% of affected companies. An agent pulled information it had access to and put it somewhere it shouldn’t have gone. Operational disruption hit 43%. A workflow broke, or worse, it kept running and made the problem bigger. And 41% of incidents involved the agent taking an action nobody authorized. Sending something. Changing something. Deleting something.
Now here’s the control gap that explains all of it. 63% of organizations can’t enforce purpose limitations on their AI agents, meaning the bot can technically do more than it was built to do. And 60% can’t shut a misbehaving agent down once it starts causing problems. You read that right. Six in ten companies have no kill switch.
Only 19% of organizations treat their AI agents with the same governance rigor they’d apply to a human employee with system access. Think about that for a second. You wouldn’t hand a new hire the keys to your CRM, your calendar, and your client database on day one with zero oversight. Most businesses are doing exactly that with their automations.
Why this hits small businesses harder
Big companies have security teams auditing agent permissions every quarter. Most small businesses don’t have that bandwidth. You set up an automation to save time, it works, and you move on to the next fire. Nobody goes back and checks what that bot can still touch six months later.
That’s the trap. It’s not that small businesses are using AI wrong. It’s that nobody built in a process to check the work.
What to actually do about it
You don’t need an enterprise security team to fix this. You need a system.
Start by auditing what your automations can actually access, not what you think they can access. Pull the permission list for every bot, every integration, every workflow connected to your CRM or your client data. If a workflow only needs to read a calendar, it shouldn’t also have write access to your database.
Build in a way to pause or kill any automation fast. If something starts behaving strangely, you need a switch, not a support ticket.
Treat every AI agent like you’d treat a new employee. Give it the minimum access it needs to do its job, document what it’s allowed to touch, and review that list on a schedule. Quarterly is a reasonable starting point for most small operations.
And don’t skip documentation. If an insurer or a client ever asks how you’re managing AI risk, “we thought about it” isn’t an answer. A one-page write-up of what’s automated, what data it touches, and who reviews it goes a long way.
The bigger point
This isn’t an argument against using AI in your business. Automation is still one of the best ways for a small business to compete with companies ten times its size. The problem shows up when businesses bolt on tools without diagnosing what’s actually happening underneath them first.
That’s the whole idea behind how we approach this at Cyber Dogs AI. Find the leak before you add more pressure to the pipe. An automation that isn’t governed isn’t saving you time, it’s quietly building a liability you won’t notice until something breaks.
If you’re not sure what your current automations can access or whether anyone’s watching them, that’s worth a real look before you add one more tool to the stack.