> [!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.

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

> [!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).

Container Threat Detection observed a malicious URL in the argument list of an
executable process. Attackers can load malware or malicious libraries
through malicious URLs.

[Container Threat Detection](https://docs.cloud.google.com/security-command-center/docs/concepts-container-threat-detection-overview.md.txt) is the source
of this finding.

## How to respond

To respond to this finding, do the following:

### Step 1: Review finding details

1. Open a `Malicious URL Observed` finding as directed in
   [Reviewing findings](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats.md.txt#reviewing_findings). The details panel for the
   finding opens to the **Summary** tab.

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

   - **What was detected** , especially the following fields:
     - **URI**: the malicious URI observed.
     - **Added binary**: the full path of the process binary that received the arguments that contain the malicious URL.
     - **Arguments**: the arguments provided when invoking the process binary.
     - **Environment variables**: the environment variables that were in effect when the process binary was invoked.
     - **Containers**: the name of the container.
     - **Kubernetes pods**: the pod name and namespace.
   - **Affected resource** , especially the following fields:
     - **Resource display name**: the name of the affected resource.
     - **Resource full name** : the [full resource name](https://docs.cloud.google.com/apis/design/resource_names) of the cluster. The full resource name includes the following information:
       - The project that contains the cluster: `projects/PROJECT_ID`
       - The location in which the cluster is located: either `zone/ZONE` or `locations/LOCATION`
       - The name of the cluster: `projects/CLUSTER_NAME`
   - **Related links** , especially the following fields:
     - **VirusTotal indicator**: link to the VirusTotal analysis page.
3. On the **JSON** tab, in the `sourceProperties` attribute,
   note the value of the `VM_Instance_Name` property.

### Step 2: Review cluster and node

1. In the Google Cloud console, go to the **Kubernetes clusters** page.

   [Go to Kubernetes clusters](https://console.cloud.google.com/kubernetes/list)
2. On the Google Cloud console toolbar, select the project that appears in
   **Resource full name** (`resource.name`), if necessary. The project
   name appears after `/projects/` in the full resource name.

3. Click on the cluster name that you noted in **Resource display name**
   (`resource.display_name`) of the finding summary. The **Clusters**
   page opens.

4. In the **Metadata section** on the \*\*Cluster details page, note any
   of the user-defined information that might be helpful in resolving the
   threat, such as information that identifies the cluster owner.

5. Click the Nodes tab.

6. From the listed nodes, select the node that
   matches the value of `VM_Instance_Name` that you noted in the finding
   JSON earlier.

7. On the **Details** tab of the **Node details** page, in the
   **Annotations** section, note the value of the
   `container.googleapis.com/instance_id` annotation.

### Step 3: Review Pod

1. In the Google Cloud console, go to the **Kubernetes Workloads** page.

   [Go to Kubernetes Workloads](https://console.cloud.google.com/kubernetes/workload)
2. On the Google Cloud console toolbar, select the project that you noted
   in the **Resource full name** (`resource.name`) of the cluster in the
   finding summary, if necessary.

3. Click **Show system workloads**.

4. Filter the list of workloads by the cluster name that you noted in
   **Resource full name** (`resource.name`)of the finding summary and, if
   necessary, the pod **Namespace** (`kubernetes.pods.ns`) that you noted.

5. Click on the workload name that matches the value of the `VM_Instance_Name`
   property that you noted in the finding JSON earlier. The **Pod details**
   page opens.

6. On the **Pod details** page, note any information about the Pod that
   might help you resolve the threat.

### Step 4: Check logs

1. In the Google Cloud console, go to **Logs Explorer**.

   <br />

   [Go to Logs Explorer](https://console.cloud.google.com/logs/query)

   <br />

2. On the Google Cloud console toolbar, select the project that appears in
   **Resource full name** (`resource.name`), if necessary.

3. Set **Select time range** to the period of interest.

4. On the page that loads, do the following:

   1. Find Pod logs for your pod (`kubernetes.pods.name`) by using the following filter:
      - `resource.type="k8s_container"`
      - `resource.labels.project_id="PROJECT_ID"`
      - `resource.labels.location="LOCATION"`
      - `resource.labels.cluster_name="CLUSTER_NAME"`
      - `resource.labels.namespace_name="NAMESPACE_NAME"`
      - `resource.labels.pod_name="POD_NAME"`
   2. Find cluster audit logs by using the following filter:
      - `logName="projects/PROJECT_NAME/logs/cloudaudit.googleapis.com%2Factivity"`
      - `resource.type="k8s_cluster"`
      - `resource.labels.project_id="PROJECT_ID"`
      - `resource.labels.location="LOCATION_OR_ZONE"`
      - `resource.labels.cluster_name="CLUSTER_NAME/var>"`
      - `POD_NAME`
   3. Find GKE node console logs by using the following filter:
      - `resource.type="gce_instance"`
      - `resource.labels.instance_id="INSTANCE_ID"`

### Step 5: Investigate the running container

If the container is still running, it might be possible to investigate the
container environment directly.

1. In the Google Cloud console, go to the **Kubernetes clusters** page.

   [Go to Kubernetes clusters](https://console.cloud.google.com/kubernetes/list)
2. Click the name of the cluster shown in `resource.labels.cluster_name`.

3. On the **Clusters** page, click **Connect** , and then click **Run in
   Cloud Shell**.

   Cloud Shell launches and adds commands for the cluster in the
   terminal.
4. Press enter and, if the **Authorize Cloud Shell** dialog appears,
   click **Authorize**.

5. Connect to the container environment by running the following command:

         kubectl exec --namespace=POD_NAMESPACE -ti POD_NAME -c CONTAINER_NAME -- /bin/sh

   Replace `CONTAINER_NAME` with the name of the container
   that you noted in the finding summary earlier.

   This command requires the container to have a shell installed at `/bin/sh`.

### Step 6: Research attack and response methods

1. Check [Safe Browsing site status](https://transparencyreport.google.com/safe-browsing/search) to get details on why the URL is classified as malicious.
2. Review MITRE ATT\&CK framework entries for this finding type: [Ingress Tool Transfer](https://attack.mitre.org/techniques/T1105/).
3. Check the SHA-256 hash value for the binary flagged as malicious on [VirusTotal](https://www.virustotal.com) by clicking the link in **VirusTotal indicator**. VirusTotal is an Alphabet-owned service that provides context on potentially malicious files, URLs, domains, and IP addresses.
4. To develop a response plan, combine your investigation results with the MITRE research and VirusTotal analysis.

### Step 7: Implement your response


The following response plan might be appropriate for this finding, but might also impact operations.
Carefully evaluate the information you gather in your investigation to determine the best way to
resolve findings.

- Contact the owner of the project with the compromised container.
- Stop or [delete](https://docs.cloud.google.com/container-registry/docs/managing#deleting_images) the compromised container and replace it with a [new container](https://docs.cloud.google.com/compute/docs/containers.md.txt).

## 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).