> [!NOTE]
> Premium and Enterprise (Deprecated) [service tiers](https://docs.cloud.google.com/security-command-center/docs/service-tiers.md.txt)

> [!CAUTION]
> The Security Command Center Enterprise service tier will shut down on May 21, 2027. If your organization uses the Enterprise service tier, then the organization will automatically move to the Premium service tier on or after May 21, 2027. Contact your account representative or a [Google Cloud sales specialist](https://cloud.google.com/contact) if you have questions.


> [!WARNING]
>
> **Preview**
>
>
> This feature is
>
> subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the
> [Service Specific
> Terms](https://docs.cloud.google.com/terms/service-terms#1).
>
> Pre-GA features 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).

<br />

This document describes a threat finding type in Security Command Center. Threat findings are generated by
[threat detectors](https://docs.cloud.google.com/security-command-center/docs/concepts-security-sources.md.txt#threats) when they detect
a potential threat in your cloud resources. For a full list of available threat findings, see [Threat findings index](https://docs.cloud.google.com/security-command-center/docs/threat-findings-index.md.txt).

## Overview

A process ran a Kubernetes attack tool within the agentic workload. This
indicates a potential attempt to exploit vulnerabilities in the Kubernetes
environment. Attackers often use these tools to escalate privileges, perform
lateral movement, or compromise other resources within the cluster.

The severity of this finding is `Critical`. This event suggests
a deliberate attempt to gain control over Kubernetes components, such as the API
server, nodes, or workloads. Attackers might use these tools to bypass security
controls, manipulate configurations, or exfiltrate sensitive data.

[Agent Platform Threat Detection](https://docs.cloud.google.com/security-command-center/docs/agent-engine-threat-detection-overview) is the
source of this finding.

## How to respond

To respond to this finding, do the following:

### Review finding details

1. Open the `Execution: Kubernetes Attack Tool Execution` finding as directed in
   [Reviewing
   findings](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats#reviewing_findings).
   Review the details on the **Summary** and **JSON** tabs.

2. On the **Summary** tab, review the information in the following sections:

   - **What was detected** , especially the following fields:
     - **Program binary**: the absolute path of the executed binary
     - **Arguments**: the arguments passed during binary execution
   - **Affected resource** , especially the following fields:
     - **Resource full name** : the [full resource name](https://docs.cloud.google.com/apis/design/resource_names) of the affected AI agent (a [`ReasoningEngine`](https://docs.cloud.google.com/vertex-ai/generative-ai/docs/reference/rest/v1/projects.locations.reasoningEngines#ReasoningEngine) resource)
3. On the **JSON** tab, note the following fields:

   - `resource`:
     - `project_display_name`: the name of the project that contains the affected AI agent
   - `finding`:
     - `processes`:
       - `binary`:
       - `path`: the full path of the executed binary
     - `args`: the arguments that were provided when the binary was executed
4. Identify other findings that occurred at a similar time for the affected
   AI agent. Related findings might indicate that this activity was malicious,
   instead of a failure to follow best practices.

5. Review the settings of the affected AI agent.

6. Check the logs for the affected AI agent.

### Research attack and response methods

1. Review MITRE ATT\&CK framework entry for this finding type: [Obtain Capabilities: Tool](https://attack.mitre.org/techniques/T1588/002/).
2. To develop a response plan, combine your investigation results with MITRE research.

### Implement your response


For response recommendations, see [Respond to AI
threat findings](https://docs.cloud.google.com/security-command-center/docs/respond-ai-threats).

<br />

## What's next

- Learn [how to work with threat
  findings in Security Command Center](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats).
- Refer to the [Threat findings index](https://docs.cloud.google.com/security-command-center/docs/threat-findings-index.md.txt).
- Learn how to [review a
  finding](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats#reviewing_findings) through the Google Cloud console.
- Learn about the [services that
  generate threat findings](https://docs.cloud.google.com/security-command-center/docs/concepts-security-sources#threats).