The rapid adoption of autonomous AI systems is introducing a new class of enterprise security risks. Research from Palo Alto Networks Unit 42 reveals how misconfigurations in Vertex AI Agent Engine could allow malicious AI agents to access sensitive cloud resources beyond their intended scope.

This discovery highlights a growing concern for organizations deploying AI-driven automation without robust security controls.
How the “Double Agent” AI Attack Works
Unit 42 demonstrated a sophisticated attack scenario in which a seemingly legitimate AI agent can secretly extract its own credentials and escalate privileges within a cloud environment. This effectively turns the AI into a “double agent” – operating as both a trusted enterprise tool and a hidden insider threat.
The issue stems from overly broad permissions assigned to service accounts linked to AI agents. By exploiting these permissions, attackers can:
Access sensitive data stored in cloud storage environments
Retrieve confidential deployment configurations
Gain visibility into restricted internal AI infrastructure
Importantly, this is not a single vulnerability but a chain of design gaps and misconfigurations that collectively expand the agent’s access footprint.
Why AI Agents Are a New Security Risk
As enterprises scale AI adoption, autonomous agents are increasingly trusted with critical tasks and data access. Unlike traditional software, these systems operate independently, often without continuous human oversight.
This creates a fundamental shift in cybersecurity dynamics:
AI agents can act autonomously across multiple systems and services
Compromised agents behave like trusted insiders rather than external attackers
Over-permissioned AI significantly expands the enterprise attack surface
These characteristics make AI agents uniquely dangerous when security controls are weak or improperly configured.
Security Gaps and Misconfiguration Risks
The research underscores how default permission settings can unintentionally expose enterprise environments. Service accounts with excessive privileges allow AI agents to move laterally across systems and access resources that were never intended to be exposed.
This highlights a broader architectural issue in modern cloud environments – security risks increasingly emerge from how components interact rather than from isolated vulnerabilities.
Even when individual systems function correctly, their combined behavior can introduce serious exposure.
Mitigation Strategies for Enterprise AI Deployments
Following responsible disclosure, Google updated its documentation to clarify how permissions and service accounts should be managed within Vertex AI.
Organizations deploying AI agents should adopt a security-first approach:
Enforce least-privilege access using custom service accounts such as BYOSA (Bring Your Own Service Account)
Restrict OAuth scopes to prevent unnecessary access
Conduct rigorous pre-deployment security reviews
Treat AI agents with the same scrutiny as production-grade software
Advanced security platforms like Prisma AIRS, Cortex AI-SPM, and Cortex Cloud Identity Security can help organizations identify and mitigate these emerging risks.

