{{item.title}}
{{item.text}}
{{item.text}}
As more work is delegated to machines and agents, organizations require stronger oversight of non-human identities.
Machine credentials that are stored, trusted, or scoped incorrectly can turn a narrow foothold into enterprise-wide exposure.
CIOs, CTOs, CISOs, and IAM leaders should know which non-human identities exist, where their credentials reside, how far access extends, and whether automated actions can be traced to an accountable human owner.
Governing non-human identities should be elevated to an enterprise security and resilience priority, not treated merely as a credential management task.
Recent headlines highlight autonomous agents acting beyond their boundaries. But they overlook a security gap organizations should address to limit the impact of this and other types of compromise: the governance of non-human identities and the credentials they use. As more activity shifts to automation, poorly managed or overly broad credentials can amplify the impact of a compromise, especially when machine access can span multiple systems or environments. This is more than a data access/exposure issue. The consequences of unauthorized non-human identities rooting around in enterprise systems extend to operational disruption, third-party risk, regulatory impact, and weakened resilience.
One high-profile incident involving agents demonstrates the risk of poorly governed credentials. After gaining initial access, an agent discovered and used credentials associated with other non-human identities, including service-account tokens, cloud credentials, static passwords, signing keys, and other forms of machine authentication. These credentials allow automated systems to act on behalf of the organization and, if they’re compromised, they can give an attacker persistent, high-impact access across critical systems and data.
Yet many identity and access management programs still focus primarily on people: joiners, leavers, movers, access requests, and periodic reviews for human users. That essential work no longer covers the full risk surface. Machines, workloads, applications, APIs, agents, and third parties can assume roles, delegate authority, and traverse trust relationships across the enterprise. Organizations should move to governing an expanding, interconnected identity environment and away from isolated credential controls.
The population of non-human identities is growing quickly. Some estimates suggest they outnumber human users by a ratio of about 100:1, and it’s only going to grow. Yet these identities often lack the visibility, ownership, and access review applied to workforce identities, which can leave unmanaged access paths across the enterprise.
In the incident described above, an agent acting outside its authorized boundaries compromised a server handling routine file processing. The agent encountered multiple forms of authentication credentials, including a Kubernetes service-account token, temporary cloud credentials, a static database password, and a mesh-network authentication key. Most consequentially, it also encountered a signing key that could issue credentials.
The credentials were not tightly bound to the systems they originated from and, in some cases, were broadly trusted, allowing the attacker to contact the main cluster. Given the way permissions were scoped, the same credential was trusted across multiple clusters and granted administrator-level access. From there, the same credentials opened paths to additional clusters across multiple environments. The credential and trust architecture allowed a compromise in one workload to expand across multiple security boundaries.
Heterogeneous technology environments widen that exposure. Most enterprises now operate across multiple clouds, SaaS platforms, Kubernetes, on-premises systems, managed service providers, and third-party platforms—each with different identity, credential, authorization, logging, and revocation models.
Containing that exposure can be difficult for your organization without a clear view of the credentials that have access to your systems.
Many organizations still struggle to answer core hygiene questions. What credentials exist? Where do they reside? Should they be there?
Credentials that are scattered, duplicated, or embedded in places they don’t belong create easy paths for attackers. Credential visibility should also extend across the trust chain. Once authenticated, what additional roles, credentials, services, or downstream systems can a non-human identity reach?
In the example above, automated defenses helped detect misuse, but the response still depended on identity context: what acted, which credentials were involved, and whether that activity could be traced to an accountable system or team.
Better credential placement, narrower scoping, shorter-lived authentication, stronger workload identity controls, and tighter trust boundaries can materially reduce how far and how fast an unauthorized automated activity can spread across your systems. For AI agents in particular, the audit trail should include who initiated the task, which agent and runtime acted, which identity or credential was used, and which downstream systems or services were invoked.
CISOs, CIOs, and IAM leaders should help their boards and senior leaders understand where credential risk could expand exposure and what to prioritize. Boards and senior leaders don’t need every technical detail. The more detailed credential and control questions should sit with the CISO, CIO, and IAM leadership teams, supported by executive oversight.
The following practical questions can help focus board and senior leadership discussions:
Widespread damage from a compromise involving misaligned agents is not inevitable. Strong IAM fundamentals, applied to non-human identities as rigorously as to people, give CISOs concrete steps to strengthen their defenses and limit the impact when an intrusion does occur.
{{item.text}}
{{item.text}}