Half 2 in our collection on workload safety covers why realizing “who” and “what” behind each motion in your setting is turning into essentially the most pressing — and least solved — downside in enterprise safety
In Half 1 of this collection, we reached three conclusions: The battlefield has shifted to cloud-native, container-aware, AI-accelerated offensive instruments — VoidLink being essentially the most superior instance — particularly engineered for the Kubernetes environments; most safety organizations are functionally blind to this setting; and shutting that hole requires runtime safety on the kernel stage.
However we left one important thread underdeveloped: identification.
We referred to as identification “the connective tissue” between runtime detection and operational response. Id is turning into the management airplane for safety, the layer that determines whether or not an alert is actionable, whether or not a workload is allowed, and whether or not your group can reply essentially the most fundamental forensic query after an incident: Who did this, and what may they attain?
Half 1 confirmed that the workloads are the place the worth is, and the adversaries have seen.
Half 2 is concerning the uncomfortable actuality that our identification techniques are unprepared for what’s already right here.
The Assaults from Half 1 Had been Id Failures
Each main assault examined in Half 1 was, at its core, an identification downside.
VoidLink’s main goal is harvesting credentials, cloud entry keys, API tokens, and developer secrets and techniques, as a result of stolen identities unlock all the things else. ShadowRay 2.0 succeeded as a result of the AI framework it exploited had no authentication at all. LangFlow saved entry credentials for each service it related to; one breach handed attackers what researchers referred to as a “grasp key” to all the things it touched.
The sample throughout all of those: attackers aren’t breaking in. They’re logging in. And more and more, the credentials they’re utilizing don’t belong to individuals, they belong to machines.
The Machine Id Explosion
Machine identities now outnumber human identities 82-to-1 within the common enterprise, based on Rubrik Zero Labs. They’re the silent plumbing of recent infrastructure, created informally, not often rotated, and ruled by nobody specifically.
Now add AI brokers. Not like conventional automation, AI brokers make choices, work together with techniques, entry information, and more and more delegate duties to different brokers, autonomously. Gartner tasks a 3rd of enterprise purposes will embrace this sort of autonomous AI by 2028.
A current Cloud Safety Alliance survey discovered that 44% of organizations are authenticating their AI brokers with static API keys, the digital equal of a everlasting, unmonitored grasp key. Solely 28% can hint an agent’s actions again to the human who approved it. And practically 80% can’t inform you, proper now, what their deployed AI brokers are doing or who is answerable for them.
Each one expands the potential injury of a safety breach, and our identification techniques weren’t constructed for this.
What Workload Id Will get Proper — And The place It Falls Brief
The safety business’s reply to machine identification is SPIFFE, and SPIRE, a typical that provides each workload a cryptographic identification card. Fairly than static passwords or API keys that may be stolen, every workload receives a short-lived, routinely rotating credential that proves it’s primarily based on verified attributes of its setting.
Credentials that rotate routinely in minutes turn out to be nugatory to malware like VoidLink, which depends upon stealing long-lived secrets and techniques. Providers that confirm one another’s identification earlier than speaking make it far tougher for attackers to maneuver laterally by your setting. And when each workload carries a verifiable identification, safety alerts turn out to be instantly attributable; you recognize which service acted, who owns it, and what it ought to have been doing.
The place It Breaks Down: AI Brokers
These identification techniques had been designed for conventional software program providers, purposes that behave predictably and identically throughout each operating copy. AI brokers are essentially totally different.
Right this moment’s workload identification techniques sometimes assign the identical identification to each copy of an utility when cases are functionally an identical. In case you have twenty cases of a buying and selling agent or a customer support agent operating concurrently, they usually share one identification as a result of they’re handled as interchangeable replicas of the identical service. This works when each copy does the identical factor. It doesn’t work when every agent is making unbiased choices primarily based on totally different inputs and totally different contexts.
When a kind of twenty brokers takes an unauthorized motion, you should know which one did it and why. Shared identification can’t inform you that. You can’t revoke entry for one agent with out shutting down all twenty. You can’t write safety insurance policies that account for every agent’s totally different conduct. And also you can’t fulfill the compliance requirement to hint each motion to a particular, accountable entity.
This creates gaps: You can’t revoke a single agent with out affecting the complete service, safety insurance policies can’t differentiate between brokers with totally different behaviors, and auditing struggles to hint actions to the accountable decision-maker.
Requirements may finally help finer-grained agent identities, however managing tens of millions of short-lived, unpredictable identities and defining insurance policies for them stays an open problem.
The Delegation Downside No One Has Solved
There’s a second identification problem particular to AI brokers: delegation.
Once you ask an AI agent to behave in your behalf, the agent wants to hold your authority into the techniques it accesses. However how a lot authority? For the way lengthy? With what constraints? And when that agent delegates a part of its activity to a second agent, which delegates a third, who’s accountable at every step? Requirements our bodies are growing options, however they’re drafts, not completed frameworks.
Three questions stay open:
Who’s liable when an agent chain goes flawed? If you happen to authorize an agent that spawns a sub-agent that takes an unauthorized motion, is the accountability yours, the agent developer? No framework gives a constant reply.
What does “consent” imply for agent delegation? Once you authorize an agent to “deal with your calendar,” does that embrace canceling conferences and sharing your availability with exterior events? Making delegation scopes exact sufficient for governance with out making them so granular they’re unusable is an unsolved design downside.
How do you implement boundaries on an entity whose actions are unpredictable? Conventional safety assumes you possibly can enumerate what a system must do and limit it. Brokers motive about what to do at runtime. Limiting them too tightly breaks performance; too loosely creates danger. The precise stability hasn’t been discovered.
Id Makes Runtime Safety Actionable
In Half 1, we shared that Hypershield gives the identical ground-truth visibility in containerized environments that safety groups have lengthy had on endpoints. That’s important, however alone, solely solutions what is going on. Id solutions who is behind it, and for brokers, we have to know why it’s occurring. That’s what turns an alert into an actionable response.
With out identification, a Hypershield alert tells you: “One thing made a suspicious community connection.” With workload identification, the identical alert tells you: “Your inference API service, owned by the information science group, deployed by the v2.4 launch pipeline, appearing on delegated authority from a particular consumer, initiated an outbound connection that violates its approved communication coverage.”
Your group is aware of instantly what occurred, who’s accountable, and precisely the place to focus their response, particularly when threats like VoidLink function at AI-accelerated pace.
The Path Ahead: Zero Belief Should Prolong to Brokers
The muse exists: workload identification requirements like SPIFFE for machine authentication, established protocols like OAuth2 for human delegation, and kernel-level runtime safety like Hypershield for behavioral statement. What’s lacking is the mixing layer that connects these items for a world the place autonomous AI brokers function throughout belief boundaries at machine pace.
It is a zero belief downside. The ideas enterprises have adopted for customers and units should now lengthen to workloads and AI brokers. Cisco’s personal State of AI Safety 2026 report underscores the urgency: Whereas most organizations plan to deploy agentic AI into enterprise capabilities, solely 29% report being ready to safe these deployments. That readiness hole is a defining safety problem.
Closing it requires a platform the place identification, runtime safety, networking, and observability share context and might implement coverage collectively. That’s the structure Cisco is constructing towards. These are the sensible steps each group ought to take:
Make stolen credentials nugatory. Change long-lived static secrets and techniques with short-lived, routinely rotating workload identities. Cisco Id Intelligence, powered by Duo, enforces steady verification throughout customers, workloads, and brokers, eliminating the persistent secrets and techniques that assaults like VoidLink are designed to reap.
Give each detection its identification context. Figuring out a workload behaved anomalously shouldn’t be sufficient. Safety groups have to know which workload, which proprietor, what it was approved to achieve, and what the blast radius is. Common Zero Belief Community Entry connects identification to entry choices in actual time, so each sign carries the context wanted to behave decisively.
Convey AI brokers inside your governance mannequin. Each agent working in your setting must be identified, scoped, and approved earlier than it acts — not found after an incident. Common ZTNA’s automated agent discovery, delegated authorization, and native MCP help make agent identification a first-class safety object reasonably than an operational blind spot.
Construct for convergence, not protection. Layering level instruments creates the phantasm of management. The challenges of steady authorization, delegation, and behavioral attestation require a platform the place each functionality shares context. Cisco Safe Entry and AI Protection are designed to do that work — cloud-delivered, context-aware, and constructed to detect and cease malicious agentic workflows earlier than injury is completed.
In Half 1, we stated the battlefield shifted to workloads. Right here in Half 2: identification is the way you combat on that battlefield. And in a world the place AI brokers have gotten a brand new class of digital workforce, zero belief isn’t only a safety framework, it’s the important framework that protects and defends.
We’d love to listen to what you suppose! Ask a query and keep related with Cisco Safety on social media.
Cisco Safety Social Media
LinkedInFacebookInstagram
