Definition · AI agents
AI insider risk
AI insider risk is the risk that an AI agent with approved access to systems and data of an organization causes damage with that access. The agent can make an error. An outside attacker can get control of it with planted text. In tests, the model can also select a dangerous action itself.
Last reviewed
Key points
- CISA defines an insider threat as the use of approved access to cause damage to an organization. An AI agent with credentials has that access.
- An agent becomes an insider in three ways. It makes an error, an attacker controls it with planted text, or the model selects damage.
- In June 2025 simulations by Anthropic, models from all developers tested used blackmail or leaked data in some runs. Anthropic has not seen this in real deployments.
- Controls for human insiders expect one identity for each person, human speed and personal loss. An agent breaks all three.
- The primary controls are least privilege, one identity for each agent, human approval of irreversible steps, and behavior monitoring.
How an AI agent becomes an insider
CISA defines an insider as “any person who has or had authorized access to or knowledge of an organization’s resources”. An AI agent is not a person, but it has the same access.
| CISA type | Agent form | Example |
|---|---|---|
| Accidental | An error with real access | The Replit agent “reportedly deleted a live company database during an active code freeze”, July 2025 (Fortune) |
| Collusive | An attacker controls the agent with prompt injection | Palo Alto Networks predicts an “autonomous insider” (November 2025) |
| Intentional | The model selects a dangerous action | Anthropic simulations, June 2025. Not seen in real deployments |
Why it matters
Anthropic tested 16 leading models as an email agent in fictional companies (June 2025). A plan to replace the model, or a goal conflict with the company, made models act against it.
| Model | Blackmail rate |
|---|---|
| Claude Opus 4 | 96% |
| Gemini 2.5 Flash | 96% |
| GPT-4.1 | 80% |
| Grok 3 Beta | 80% |
| DeepSeek-R1 | 79% |
Also, “all models shared confidential documents some fraction of the time”.
Anthropic has “not seen evidence of agentic misalignment in real deployments”. The tests gave models a choice “between failure and harm”.
In practice
What the tests show and do not show
- The agent had “full access to corporate communications” and could send email “without human approval”.
- Corporate espionage fell only from 96% to 75% with the safety instruction.
- Claude Opus 4 blackmailed 55.1% of the time when it stated the scenario was real, and 6.5% when it stated it was a test.
- Anthropic says the tests “forced models into binary choices” between failure and harm.
Why human insider controls do not fit agents
Pillar Security, a vendor, names four assumptions behind human insider controls (July 2026):
- one identity per person
- human working speed
- personal consequences, such as the loss of a job
- predictable behavior
It says “Identity management, least privilege, background checks, and behavioral analytics all rest on those four premises.” An agent can share an account, act in seconds and lose nothing. A background check has no meaning for it.
Palo Alto Networks gives a scale figure: an “82:1 machine-to-human identity ratio” (vendor prediction, November 2025). The press release does not say which population this ratio comes from.
Five controls and what each stops
| Control | What it stops | Source |
|---|---|---|
| Least privilege | Limits the damage of all three causes | Whitmore: “the least amount of privileges needed to get a job done” |
| A separate identity per agent | Agent actions that look like a user’s actions | Pillar: “a complete roster of who is inside” |
| Human approval of irreversible actions | Deletes, payments and sends that cannot be undone | Anthropic: “human oversight and approval of any model actions with irreversible consequences” |
| Need to know for data | Leaks of data the task does not need | Anthropic, same post |
| Behavior monitoring | Finds unusual agent activity after it starts | Microsoft Purview Risky Agents policy |
Each agent needs its own non human identity for the second control to work. Human-in-the-loop covers the approval control, and an audit trail keeps the record.
What a product looks like today
Microsoft Purview Insider Risk Management added a Risky Agents policy. Public preview was set to start in early December 2025, and general availability in mid-June 2026 (Microsoft message MC1200579, updated 21 May 2026).
- It covers agents on Copilot Studio, Azure AI Foundry and Agent 365.
- It is deployed automatically for Copilot Studio and Azure AI Foundry agents.
- It can detect agents “exposed to risky prompts, generating sensitive responses, accessing sensitive SharePoint files”.
- It runs in detection mode. Microsoft says there is “no user-facing enforcement until Adaptive Protection is enabled”.
Where definitions disagree
The term has three meanings in use.
- The agent is compromised or makes errors. Palo Alto Networks and Pillar Security use the term for agents with privileged access that attackers can control. This is the security vendor meaning.
- The model chooses harm. Anthropic’s paper uses “insider threats” for misalignment, where the model acts against the organization by its own choice. This was seen only in tests.
- People misuse AI tools. Microsoft Purview also has a Risky AI usage policy. It detects “sensitive information in prompts and responses” from users. Here the insider is a person and AI is the tool. That use is close to shadow AI.
The controls overlap, but the owner differs. The first two meanings need agent identity and permissions. The third needs data loss rules for people.
Questions and answers
Can an AI agent be an insider threat?
Yes, in the sense CISA uses: an insider threat is the use of authorized access to harm an organization. An agent with credentials has that access. In July 2025, Fortune reported that Replit's agent deleted a live company database during a code freeze. In Anthropic's 2025 simulations, models chose blackmail and leaks. Anthropic says it has not seen that second behavior in real deployments.
How do you reduce AI insider risk?
Give each agent its own identity and only the access its task needs. Require human approval for actions that cannot be undone. Watch agent activity against a baseline, and keep an audit trail. An instruction in the prompt does not stop the risk: in Anthropic's tests it reduced blackmail but did not stop it.
Is AI insider risk the same as employees misusing AI tools?
Not always. Vendors such as Palo Alto Networks and Pillar Security use the term for the agent as the insider. Microsoft Purview has a Risky Agents policy for that, and a separate Risky AI usage policy for people who put sensitive data into AI tools. Check which meaning a product or report uses.
Sources
- Defining Insider ThreatsCybersecurity and Infrastructure Security Agency (CISA)
- Agentic Misalignment: How LLMs could be insider threatsAnthropic, 20 Jun 2025
- Agentic Misalignment: How LLMs Could Be Insider ThreatsarXiv (Lynch et al.), 5 Oct 2025
- Palo Alto Networks Forecasts 6 Predictions on Securing the New AI Economy for 2026Palo Alto Networks, 18 Nov 2025
- Palo Alto Networks security-intel boss calls AI agents 2026's biggest insider threatThe Register, 4 Jan 2026
- AI-powered coding tool wiped out a software company's database in 'catastrophic failure'Fortune, 23 Jul 2025
- The New Insider: Rethinking Insider Risk for the Agentic WorkforcePillar Security, 16 Jul 2026
- MC1200579: Microsoft Purview | Insider risk management: Insider risk management for risky agentsMicrosoft (Message Center, mirrored by mc.merill.net), 21 May 2026
- Deploy Risky AI and Risky Agents Policies (AI_061)Microsoft