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

A library that was not part of the original container image was loaded.
Attackers might load malicious libraries into existing programs in order to
bypass code execution protections and to hide malicious code. Ensuring that your containers are immutable is an important best practice. This is a low-severity finding, because
your organization might not be following this best practice. There are
corresponding `Execution: Added Malicious Library Loaded` findings when the hash
of the binary is a known indicator of compromise (IoC).

[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 an `Added Library Loaded` 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:
     - **Program binary**: the full path of the process binary that loaded the library.
     - **Libraries**: details about the added library.
     - **Arguments**: the arguments provided when invoking the process binary.
   - **Affected resource** , especially the following fields:
     - **Resource full name** : the [full resource name](https://docs.cloud.google.com/apis/design/resource_names) of the cluster.
   - **Related links** , especially the following fields:
     - **VirusTotal indicator**: link to the VirusTotal analysis page.
3. Click the **JSON** tab and note the following fields:

   - `resource`:
     - `project_display_name`: the name of the project that contains the asset.
   - `sourceProperties`:
     - `Pod_Namespace`: the name of the Pod's Kubernetes namespace.
     - `Pod_Name`: the name of the GKE Pod.
     - `Container_Name`: the name of the affected container.
     - `Container_Image_Uri`: the name of the container image being executed.
     - `VM_Instance_Name`: the name of the GKE node where the Pod executed.
4. Identify other findings that occurred at a similar time for this container. Related findings might indicate that this activity was malicious, instead of a failure to follow best practices.

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

   <br />

2. On the Google Cloud console toolbar, select the project listed in
   `resource.project_display_name`, if necessary.

3. Select the cluster listed in `resource.name`. Note any metadata about
   the cluster and its owner.

4. Click the **Nodes** tab. Select the node listed in `VM_Instance_Name`.

5. Click the **Details** tab and note 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)

   <br />

2. On the Google Cloud console toolbar, select the project listed in
   `resource.project_display_name`, if necessary.

3. Filter on the cluster listed on the **Resource full name** row in the
   **Summary** tab of the finding details and the Pod namespace
   listed in `Pod_Namespace`, if necessary.

4. Select the Pod listed in `Pod_Name`. Note any metadata about the Pod and
   its owner.

### Step 4: Check logs

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

   [Go to Logs Explorer](https://console.cloud.google.com/logs/query)
2. On the Google Cloud console toolbar, select the project listed in
   `resource.project_display_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 `Pod_Name` by using the following filter:
      - `resource.type="k8s_container"`
      - `resource.labels.project_id="resource.project_display_name"`
      - `resource.labels.location="location"`
      - `resource.labels.cluster_name="cluster_name"`
      - `resource.labels.namespace_name="Pod_Namespace"`
      - `resource.labels.pod_name="Pod_Name"`
   2. Find cluster audit logs by using the following filter:
      - `logName="projects/resource.project_display_name/logs/cloudaudit.googleapis.com%2Factivity"`
      - `resource.type="k8s_cluster"`
      - `resource.labels.project_id="resource.project_display_name"`
      - `resource.labels.location="location"`
      - `resource.labels.cluster_name="cluster_name"`
      - `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 running container

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

1. Go to the Google Cloud console.

   <br />

   [Open Google Cloud console](https://console.cloud.google.com/)

   <br />

2. On the Google Cloud console toolbar, select the project listed in
   `resource.project_display_name`, if necessary.

3. Click **Activate Cloud Shell** .
   ![](https://docs.cloud.google.com/static/security-command-center/images/activate-cloud-shell.svg)

4. Obtain GKE credentials for your cluster by running the
   following commands.

   For zonal clusters:

   ```bash
     gcloud container clusters get-credentials cluster_name --zone location --project resource.project_display_name
   ```

   For regional clusters:

   ```bash
     gcloud container clusters get-credentials cluster_name --region location --project resource.project_display_name
   ```
5. Retrieve the added library by running:

   ```bash
     kubectl cp Pod_Namespace/Pod_Name: Added_Library_Fullpath -c Container_Name  local_file
   ```

   Replace <var translate="no">local_file</var> with a local file path to store the added
   library.
6. Connect to the container environment by running:

   ```bash
     kubectl exec --namespace=Pod_Namespace -ti Pod_Name -c Container_Name -- /bin/sh
   ```

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

### Step 6: Research attack and response methods

1. Review MITRE ATT\&CK framework entries for this finding type: [Ingress Tool Transfer](https://attack.mitre.org/techniques/T1105/), [Shared Modules](https://attack.mitre.org/techniques/T1129/).
2. 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.
3. 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.

- If the library was intended to be included in the container, rebuild the container image with the library included. This way, the container can be immutable.
- Otherwise, 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).