The blast radius problem makes this urgent. Houston Harrison, Abnormal AI Chief Information Security Officer, describes what a compromised, over-permissioned agent actually means for an organization: "If you have autonomous agents broadly connected in your environment—agents that can perform tasks, take calls broadly from your workforce—that's the first place I'm going as an attacker. I'm going there to stage persistence, deliver payloads, figure out what actions I can perform, provision access."
The blast radius isn't a corner of the environment. It's the whole thing.
Traditional governance controls weren't built to prevent this. Titus traces the systematic failure: "We over-entitled non-human identities because we didn't have a lot of telemetry—just logs out of service accounts and nested accounts and sub-nested accounts. We never had good hygiene there."
The operational reason for that hygiene failure is more specific than it sounds. Jesus Garcia, Abnormal AI's Solutions Architect, describes what happens when a security team tries to rotate a service account that's been in production for five or six years: "Sometimes the current owner wasn't the person that implemented it. There's no documentation. They don't know all the locations where that username and password has been hard-coded in."
"There's hesitation — almost a confrontation between IT and security teams — when trying to perform just basic password hygiene tasks. And while IT and security is discussing all this, the malicious actors are there to take full advantage."
— Jesus Garcia, Solutions Architect, Abnormal AI
The access review process that worked for human identities—periodic audits, entitlement reports, the occasional regulator finding—has no equivalent for machine identities in most environments. You can't review what you can't see, and you can't see what you never thought to track.
