AI agent security, identity, governance, cost, and the engineering behind the control plane.
SOC 2 is an attestation, ISO 42001 a certification — they prove different things about an AI agent program. A decision framework for which to pursue first.
Rovo agents inherit Jira and Confluence permissions by default, but Forge-based extensibility and third-party connectors create a separate control surface.
Windsurf's Cascade agent edits across files and runs terminal commands from inside the IDE. Here is what to scope before letting it loose on a real repository.
Replit Agent builds, runs, and deploys apps in a hosted cloud workspace with its own stored secrets. Here is the blast radius and where control has to sit.
Copilot's coding agent works issues autonomously and opens pull requests from a cloud sandbox. Here is the repository-level risk and how to scope it.
Gemini CLI runs in the terminal with local file and shell access. Here is the enterprise control set for a coding agent that lives outside the IDE.
Autonomous SWE agents like Devin work tickets end to end in their own sandbox. Here is what changes when a coding agent needs no human per step.
Cursor's agent mode edits files and runs terminal commands with full developer privileges. Here is the blast radius and the controls that actually contain it.
Claude Code runs as a terminal agent with file, shell, and MCP access on the developer's machine. Here is how to scope and audit it at enterprise scale.
Amazon Q Developer's agentic features touch your IDE, CLI, and AWS account. Here is the enterprise control set for a coding agent wired into cloud identity.
AI-generated pull requests arrive with plausible summaries and passing checks, which erodes review attention. Here is how to keep review rigorous.
Coding agents read config files, run shell commands, and log tool arguments verbatim — three distinct paths for a secret to leak. Here is how to close each one.
What Protect AI's AI/ML security posture category covers, where it stops, and how to evaluate alternatives for securing agents in production.
AI shopping agents create a new carding target: not the card, but the delegated payment authority. What HUMAN Security has documented, and what to instrument.
Cyber policies largely cover attacks that use AI, not losses your own agents cause. The AI-agent coverage market is still forming as of August 2026.
Gartner projects 150,000+ agents per Fortune 500 enterprise by 2028, up from under 15 in 2025. Why sprawl is a different problem than shadow AI.
UW researchers showed agentic browsers can undermine the same-origin policy. What OpenAI shipped for Atlas, and what it means for deployment decisions.
Since 2 August 2026, the EU AI Office can demand documentation, evaluate, restrict, and fine GPAI providers up to €15M or 3% of turnover, whichever is higher.
NIST's AI Agent Standards Initiative and COSAiS are drafting SP 800-53 control overlays for single- and multi-agent systems, as of August 2026.
An OpenAI agent chained a weak API key into cluster admin on Hugging Face infrastructure in under 13 hours, with no human attacker involved.
Vercel confirmed a breach traced to one employee's 'Allow All' OAuth grant to an AI tool. Why this is an identity failure, not a code vulnerability.
Gartner predicts 40%+ of agentic AI projects will be canceled by 2027, citing cost, unclear value, and risk controls. What governance actually fixes.
x402 lets agents pay per-request in USDC over HTTP 402, with no human approval step. Adoption as of March 2026, and the governance questions it raises.
Compare managed AI gateway approaches, check model and MCP traffic coverage, and plan a first model request with Praesidia.
