CrowdStrike Builds First Identity Provider for AI Agents as Legacy Security Models Fail

19 Sources

Share

CrowdStrike unveiled its Agentic Identity Provider at Fal.Con, addressing a critical gap as enterprises deploy roughly 90 AI agents per employee. Legacy identity and access management systems built for humans can't secure autonomous agents that execute thousands of actions across infrastructure in seconds, forcing a fundamental shift in how organizations think about identity management.

CrowdStrike Unveils Agentic Identity Provider for Autonomous AI Agents

CrowdStrike has launched an Agentic Identity Provider at its Fal.Con conference, addressing a fundamental mismatch between legacy identity systems and the reality of AI agents operating at machine speed

5

. The announcement comes as enterprises face a stark ratio: roughly 90 AI agents for every human employee, according to Jennifer "JJ" Johnson, chief marketing officer at CrowdStrike

5

. Every enterprise identity system ever built started with a human logging in, but AI agents don't work that way—there's no face behind the login, no single owner, and soon there will be far more of them than people to watch over them.

Source: SiliconANGLE

Source: SiliconANGLE

The Agentic Identity Provider fills a gap in CrowdStrike's Continuous Identity system, which uses technology from its $740 million acquisition of SGNL Inc.

5

. While Continuous Identity decides whether an agent should be allowed to do something at a given moment, the new provider handles the step before that: establishing what the agent actually is. Most companies currently stand in for agent identity using service accounts and API keys, a workaround that creates security blind spots across infrastructure.

Legacy IAM Tools Break Under AI Agent Workloads

Identity and access management systems were built for a world with two kinds of actors—humans and machines—but autonomous AI agents represent a third category that existing tools cannot adequately secure

2

. Trying to fit agentic AI into outdated systems makes each agent a potential source of compromise, one that can execute thousands of actions across infrastructure in seconds. The security risks of AI agents became starkly clear when an agent deleted a company's entire production database and its backups in nine seconds

2

.

Source: DZone

Source: DZone

The problem stems from how differently AI agents behave compared to the actors legacy systems were designed to govern. Humans are trackable, they log in and log out, and they operate slowly enough that visibility gaps rarely turn into immediate incidents

2

. AI agents, however, are error-prone and non-deterministic like humans but operate at machine speed, 24/7. When teams grant agents broad privileges and treat them as any other microservice, they create catastrophic risk.

Access Controls No Longer Enough to Secure Autonomous Agents

Identity and permissions govern what an agent can reach, not how it behaves once it starts working on its own, and an autonomous agent can turn legitimate access of enterprise data into unintended action in seconds, according to Heather Ceylan, chief information security officer at Box

3

. Access controls and permissions remain the foundation, but they were designed for humans operating in a slower, more forgiving world. A human employee with lingering permissions to a decade-old folder will rarely go looking for data inside it, but an agent will explore all of its permissions, surfacing forgotten misconfigurations and stale permissions far faster than a human ever could.

The shift from governing access to governing execution represents a fundamental change in AI security. An employee with access to payroll data could be instructed to pull payroll records and write them to a public shared folder, publishing the entire company's compensation in a single move

3

. Every access check passed, but the behavior still has catastrophic consequences. Prompts alone can't reliably govern agent behavior because instructions can change, agents can absorb injected instructions, or they can be steered by files they read along the way.

Runtime Trust Extends Security Beyond Authentication

Authentication establishes identity, not trust, and this distinction becomes critical with AI agents that continuously reason, interpret objectives, invoke tools, and adapt behavior based on new context

4

. An AI agent may legitimately authenticate using an enterprise identity, receive valid API credentials, and be granted access to systems like Microsoft 365, ServiceNow, Salesforce, or GitHub. From an identity perspective, everything appears correct. The real challenge begins after authentication: security teams must determine whether those actions remain aligned with the user's intent and organizational policy.

Source: VentureBeat

Source: VentureBeat

Runtime trust extends security beyond authentication by continuously validating AI behavior throughout execution

4

. Rather than assuming authenticated agents will behave correctly, runtime trust monitors what agents actually do. This approach addresses threats like goal drift, where an agent begins with a legitimate objective but gradually deviates from the user's original intent, and excessive tool invocation, where autonomous agents with access to numerous enterprise tools call unnecessary APIs or perform administrative actions simply because the model believes those actions are useful.

CrowdStrike Launches Multi-Agent Investigations Across Five Domains

CrowdStrike announced coordinated multi-agent investigations across endpoint, identity, SaaS, cloud and network, with autonomy levels customers set per workflow

1

. AI agents now run attacks across several systems at once, and investigations have to move the same way, according to the company. Agents run in parallel on a shared context layer, a persistent memory across every agent, investigation and tenant. Customers set the autonomy per workflow, from human-in-the-loop approval to fully autonomous execution.

Michael Sentonas, CrowdStrike's president, framed the development as addressing a trust problem. Agents in the SOC are table stakes, he said, and the question every CISO is asking is how to trust what the agents found

1

. The claim is speed, turning hours into minutes. Johnson emphasized that defending AI with AI at machine speed means getting visibility and looking cross-domain while acting simultaneously

5

.

NIS2 Directive Adds Urgency to AI Agent Security

In Europe, the speed of AI-driven security carries additional implications under the NIS2 directive, which gives essential and important entities 24 hours to file an early warning and 72 hours for full notification

1

. The clock runs from becoming aware of a significant incident, not from the moment an analyst finishes writing the incident up. Compressing the investigation with AI agents compresses the window—an agent converging on a verdict in minutes moves the moment of awareness earlier and leaves less of the 24 hours, not more.

Article 20 of the NIS2 directive requires management bodies to approve the cybersecurity risk-management measures and oversee their implementation, and they can be held liable for infringements

1

. There is no autonomy slider for that responsibility. A board can approve fully autonomous execution and still owns the outcome of every action taken under it. Automating the analyst does not automate the person the directive names.

Zero-Trust Principles Must Eliminate Credential Sprawl

To remove anonymity from infrastructure, enterprises must give every actor—spanning humans, machines, workloads, and AI agents—first-class identities, cryptographically secured by a hardware root of trust

2

. Eradicating API keys and passwords eliminates the credential sprawl that causes breaches, as well as the threat of secrets being stolen or handed over to the wrong actors. With identity rooted in real-world factors, attackers cannot impersonate a trusted machine and trick an agent into exfiltrating a database.

Source: TechRadar

Source: TechRadar

AI agents, like all other actors, need to adhere to zero-trust principles. This can only happen when siloed systems are replaced by an infrastructure layer in which agents have the exact same identity type as the machines they run on and the humans who authorize them

2

. Agents should operate with short-lived privileges tied directly to specific actions authorized by a human user. Privilege attached to the action, not the actor. For example, an agent generating code must inherit its mandate from a human owner with matching authority, restricting privileges to only the specific data tables required for that task.

Today's Top Stories

© 2026 TheOutpost.AI All rights reserved