> [!WARNING]
> **Preview**
>
>
> This product is subject to the "Pre-GA Offerings Terms" in the General Service
> Terms section of the
> [Service Specific Terms](https://cloud.google.com/terms/service-terms#1)
> and the
> [Generative AI Service Specific Terms](https://cloud.google.com/terms/service-terms#20),
> as well as the
> [Additional Terms
> for Generative AI Preview Products](https://cloud.google.com/trustedtester/aitos?e=48754805).
>
>
> When you use this product with AI Agents, the terms applicable to AI Agents in
> the Agreement apply.
>
>
> Pre-GA products are available "as is" and might have limited support. For more
> information, see the
> [launch stage descriptions](https://cloud.google.com/products/#product-launch-stages).

> [!CAUTION]
> **Caution:** This product is available to approved users that are signed in to their browser with an allowlisted email address. To request access to use this product, read this page to understand the prerequisites and complete the form at the bottom of this page.

Agent Anomaly Detection provides a dynamic, reasoning-based oversight
and audit layer designed specifically for autonomous enterprise AI agents.
Unlike conventional application security tools that only scan static code for
vulnerabilities or inspect network traffic at the perimeter,
Agent Anomaly Detection evaluates the live reasoning traces,
tool interactions, and execution flows of agents using built-in
detectors to detect suspicious intent, policy violations, and behavioral
anomalies.

The core of Agent Anomaly Detection is a multi-layered
anomaly analysis framework that analyzes agent session activity
asynchronously. By ingesting OpenTelemetry logs and execution traces, the
service determines whether an agent is operating outside of its intended
boundaries without introducing execution latency into your live agent workflows.

## Key benefits

Agent Anomaly Detection includes these features:

| Benefit or Feature | Description |
|---|---|
| **Asynchronous near real-time security** | Telemetry (logs and traces) is processed out-of-band, maintaining fast agent response times. A multi-layered analysis model allows for maintaining cost efficiency with near real-time assessments. |
| **Reasoning-based intent analysis** | Anomaly analysis reasons over flagged traces to differentiate complex business logic from unauthorized action. |
| **Comprehensive threat detection** | Audits agent-specific security risks out of the box with default detectors that capture [threat patterns outlined in the OWASP Top 10 for Agentic Security Threats](https://docs.cloud.google.com/gemini-enterprise-agent-platform/agent-anomalies-overview.md.txt#threat-categories), including tool misuse, privilege abuse, cascading agent failures, rogue behaviors, and resource exhaustion. |
| **Integration with Security Command Center** | Anomaly findings for agents on Google Cloud are surfaced directly in Security Command Center for centralized security management, search, and incident tracking. For information on Security Command Center, see [Overview of Security Command Center](https://docs.cloud.google.com/security-command-center/docs/activate-scc-overview.md.txt). **Note:** This integration requires one of the [Security Command Center-supported tiers](https://docs.cloud.google.com/security-command-center/docs/service-tiers.md.txt): Standard, Premium, or Enterprise. |
| **Integration with Cloud Monitoring** | Detection and coverage metrics are written to Cloud Monitoring, where you can chart them, add them to dashboards, and use them in alerting policies. For details, see [Monitor anomaly metrics in Cloud Monitoring](https://docs.cloud.google.com/gemini-enterprise-agent-platform/audit/agent-anomalies#cloud-monitoring). |

## What's new

The following feature was added to Agent Anomaly Detection
(Preview) on **November 12, 2026** : support for agents built with
ADK for Python 2.12.0 or later that run outside Google Cloud,
such as on Amazon Web Services (AWS) or Microsoft Azure. The agent exports its
traces and logs to your Google Cloud project and authenticates with Workload
Identity Federation. For details, see
[Agent Anomaly Detection: Safeguarding Agents Across Any Cloud](https://docs.cloud.google.com/gemini-enterprise-agent-platform/audit/agent-anomalies-other-clouds).

The following feature was added to Agent Anomaly Detection
(Preview) on **November 2, 2026**: support for automatic agent enrollment, which
automatically enables monitoring for eligible agents discovered in your
project.

The following features were added to the Agent Anomaly Detection
preview functionality on **October 22, 2026**:

- **Support for ADK on Google Kubernetes Engine** : Monitor agents built with Agent Development Kit (ADK) (version 2.1.0 or later) and deployed on your [GKE](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/kubernetes-engine-overview.md.txt) clusters (`GKE_WORKLOAD`).
- **Support for Cloud Run** : Monitor agents deployed as [Cloud Run](https://docs.cloud.google.com/run/docs/overview/what-is-cloud-run.md.txt) services (`CLOUD_RUN_SERVICE`). By exporting OpenTelemetry traces to Cloud Trace and logs to Cloud Logging, Cloud Run services are automatically discovered and listed on the Settings page, where you can enable them for Agent Anomaly Detection.

## Multi-layered detection system

To balance assessment coverage and cost, Agent Anomaly Detection uses a multi-layered detection system that analyzes agent logs to identify and report on anomalous sessions:

- **Layer 1 (Lightweight ML detectors)**: High-speed statistical and lightweight machine learning models identify initial outliers and downstream telemetry trends to down-sample baseline traffic.
- **Layer 2 (Anomaly analysis)**: Anomaly analysis evaluates flagged sessions asynchronously to render threat verdicts and natural language explanation reasoning.
- **Layer 3 (Invocation-level analysis)**: Performs a deep-dive analysis of individual tool executions, execution states, and parameter histories within the conversation trace.

## Availability

Agent Anomaly Detection is available for agents meeting the following
criteria. Agents that meet the criteria are automatically recognized as
**monitored agents** by Agent Anomaly Detection (the service is
aware of the agent's existence, but nothing is run on the agent's logs and no
costs are incurred unless the agent is enabled). Monitored agents can be
**enabled** for active anomaly analysis either automatically upon discovery
(when automatic agent enrollment is enabled on the regional
`AgentAnomalyDetectionScope`) or manually per agent in the
Google Cloud console or through the API.

- **Compatible runtime** : Deployed on Agent Runtime (Reasoning Engine), Cloud Run (`CLOUD_RUN_SERVICE`), Google Kubernetes Engine (`GKE_WORKLOAD`), or another cloud platform such as Amazon Web Services (AWS) or Microsoft Azure (`AGENT_TYPE_OTHER`). For agents on other cloud platforms, see [Agent Anomaly Detection: Safeguarding Agents Across Any Cloud](https://docs.cloud.google.com/gemini-enterprise-agent-platform/audit/agent-anomalies-other-clouds).
- **ADK version**: Built using ADK for Python, version 2.1.0 or later (2.12.0 or later for agents outside Google Cloud).
- **Logging and observability buckets** : Both buckets must be in the same location as your Agent Anomaly Detection scope (such as the US or EU multi-region). For a scope in the US multi-region, they can also be in the `global` location (such as the default `_Default` logging bucket). For a scope in the EU multi-region, use a logging bucket in the `eu` location.
- **Telemetry capture** : OpenTelemetry tracing and logging are enabled using the ADK. Agents outside Google Cloud must export spans and logs through the Telemetry API (`telemetry.googleapis.com`).
- **Metadata capture**: Raw telemetry is configured to capture prompt input and response output contents.
- **Active tracing** : The `enable_tracing` flag is not explicitly set to `false` in the ADK configuration.
- **Permissions and access** : Regional scanners' service accounts hold sufficient reader permissions over the active logs and observability buckets. The log bucket should have [Log Analytics and Observability Analytics enabled](https://docs.cloud.google.com/logging/docs/log-analytics.md.txt).
- **Active data flow**: The agent must have active data; the system cannot verify configuration or enroll an agent that has no telemetry data.

Agents that don't meet these criteria aren't discoverable by
Agent Anomaly Detection and don't appear in the list of
monitored agents to enable.

## Threat categories

Agent Anomaly Detection continuously monitors agent activities
and flags risks across key categories aligned with agentic security frameworks:

- **Tool misuse (OWASP ASI02)**: Detects when tools are used in unsafe or unintended ways, such as through dangerous tool chaining, parameter manipulation, or indirect prompt injection.
- **Identity privilege abuse (OWASP ASI03)**: Identifies unauthorized actions resulting from dynamic trust delegation, persona forgery, memory escalation, or confused deputy vulnerabilities.
- **Agentic cascading failures (OWASP ASI08)**: Monitors fault propagation, infinite execution loops, oscillating retries, and feedback loop amplifications across agent workflows.
- **Rogue agents (OWASP ASI10)**: Flags when an agent abandons its declared role, bypasses safety guardrails, or deviates from assigned system instructions.
- **Resource exhaustion**: Detects intentional or runaway over-consumption of compute, LLM tokens, or network bandwidth.

## Opt-in to try Agent Anomaly Detection

To opt-in to try Agent Anomaly Detection, complete this form:
[Agent Anomaly Detection access request form](https://forms.gle/rS5haEt4mHPFnRqe9).

## Use Agent Anomaly Detection

If you're already opted in to use Agent Anomaly Detection, see
[Agent Anomaly Detection](https://docs.cloud.google.com/gemini-enterprise-agent-platform/audit/agent-anomalies)
for usage instructions.