Obsidian AI Agent Security Academy

The practitioner's guide to securing AI agents

From MCP server risks to machine identity and runtime guardrails — everything security engineers and CISOs need to govern agentic AI without slowing adoption.

xxx
Articles
·
xxx
Security Pillars
·
Updated
June 1, 2026
All (0)
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
300×
increase in AI agent activity, 2025
40%
of agents carry medium-to-critical risk
800+
risky agents in avg enterprise environment
25–50×
native tools built to see agent identity
Source: Obsidian Security Research, 2026

The six pillars of AI agent security

Get new AI agent security research in your inbox.
New articles, threat research, and CISO briefings — no spam, unsubscribe any time.
See every AI agent in your environment — in 30 minutes.
Obsidian surfaces agent inventory, toxic combinations, and MCP server activity across 8 platforms. No connector required.
Get a Demo
No setup required · 30-min session

Trusted by leading security teams

AI agent security: frequently asked questions

What is AI agent security?

AI agent security is the practice of governing, monitoring, and enforcing policy over autonomous AI systems — agents — that take actions inside business applications without direct human instruction for each step. It differs from traditional application security because agents hold persistent credentials, execute multi-step workflows, and access sensitive SaaS systems at a scale and speed that human oversight cannot track manually.

How is AI agent security different from prompt security?

Prompt security governs what human users submit to language models: filtering sensitive data, detecting injection attempts, blocking harmful outputs. AI agent security governs what autonomous agents do after they receive their instructions — which credentials they use, which SaaS applications they access, which actions they chain.

What is a toxic combination in AI agent security?

A toxic combination occurs when multiple medium-severity risk factors exist simultaneously on a single agent, compounding into a critical-priority finding. Example: embedded admin credentials + org-wide public access + disabled creator account = critical blast radius, no owner.