Cisco's vice president of product for identity says the company is finding unsanctioned AI agents almost everywhere it looks. "There are shadow agents running in almost every environment we look at," the executive warned.
Duo Agentic Identity is the product that executive oversees. The pitch is simple: give autonomous agents the same kind of identity controls companies already use for people.
A warning from the identity group, with a SKU attached
IT leaders are stuck in a real bind. Teams spin up autonomous agents faster than security groups can inventory them. You do not want to freeze experiments and miss a productivity window. You also do not want unknown software acting on its own with a borrowed API key.
Shadow IT used to mean a SaaS login on a personal card. Shadow agents are that problem with initiative. They call tools. They write tickets. They touch data. A password manager entry is not an identity. A script with a token in a repo is not a user.
Cisco bought Duo in 2018 to be in the business of proving a person is a person. Agentic Identity extends that habit to software that behaves like a junior employee. I will say the quiet part: this is a vendor talking its book. The inventory problem is still real.
ZDNET ran the conversation as paid content produced with a sponsor. Read the claims with that label in mind. A line about shadow agents in almost every inspected environment is still a useful description of what a lot of companies are about to trip over.
Agents with keys are not employees
Human identity stacks grew up around hire dates, laptops, and MFA prompts. Agents do not get onboarded. They get cloned. They persist after the intern who launched them leaves. They request a new model endpoint on a Saturday.
The public already treats AI at work as a jobs story. Pew's cross-country poll found fewer jobs as the modal answer almost everywhere it asked. Security teams are living the other half of that anxiety: the software is here, it is acting, and nobody named it in an org chart.
Developer tools now advertise multiple agents in one workspace. Claude Code's projects update is that pitch from the builder side. Cisco is the adult in the hallway asking who signed for each one.
I would not wait for a perfect standard. I would start an inventory this quarter: where agents run, which credentials they hold, which systems they can write to, and who can kill them. If you cannot answer those four, you already have shadow agents. Cisco is just the one saying it into a microphone.
Keep the warning. Discount the brochure.
Duo Agentic Identity will live or die on whether it maps to the messy ways teams actually launch agents: cloud consoles, laptops, CI jobs, browser plugins. A product that only understands a tidy service account will miss the intern's laptop.
Labs spent a summer talking about rogue agents and then talking about pacing the frontier. Big labs wanting to slow that race is a policy mood. Most companies do not have a frontier model. They have a helpdesk bot with too much permission.
Paid content will always resolve in a purchase path. The useful residue is the sentence about environments Cisco inspects. Treat it as a prompt to look at your own, not as a peer-reviewed census of the internet.
Ask identity vendors how they revoke an agent that was never a user. Ask developers to stop stuffing long-lived keys in chat logs. If Duo's product helps with the first job, buy it after a trial, not after a sponsored essay.
The next tell is a customer named on the record who is not Cisco. The tell after that is an incident write-up where an unsanctioned agent actually moved money or mail. Those write-ups are coming. The only question is whether your name is in one.
Shadow IT had a playbook: discover the app, SSO it, or kill it. Agents break that playbook because they are not always a vendor you can call. They are a local process, a cloud function, a browser extension that bought itself another token at 2 a.m. Duo can sell a control plane for that. Someone still has to populate the inventory.
If your CISO needs a sentence for the board, use Cisco's, with the paid-content asterisk attached. Then put a date on an internal census. Without the census, Agentic Identity is a logo on a slide.