A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://cloud.google.com/security-command-center/docs/how-to-test-container-threat-detection below:

Testing Container Threat Detection | Security Command Center

Skip to main content Testing Container Threat Detection

Stay organized with collections Save and categorize content based on your preferences.

Premium and Enterprise service tiers

This page explains how to verify that Container Threat Detection is working by intentionally triggering detectors and checking for findings. Container Threat Detection is a built-in service of the Premium and Enterprise tiers of Security Command Center. To view Container Threat Detection findings, it must be enabled in Security Command Center Services settings.

Before you begin

To detect potential threats to your containers, you need to make sure that your clusters are on a supported version of Google Kubernetes Engine (GKE). For more information, see using a supported GKE version.

Enable detectors

The following detectors are disabled by default:

To test these detectors, they must be enabled explicitly.

First, check the status of all detectors:

   export PROJECT=PROJECT_ID
   gcloud alpha scc settings services describe \
       --service=CONTAINER_THREAT_DETECTION \
       --project=${PROJECT}

To enable a specific detector, use the corresponding command below:

Set environment variables

To test detectors, use the Google Cloud console and Cloud Shell. You can set environment variables in Cloud Shell to make it easier to run commands. The following variables are used to test all Container Threat Detection detectors.

  1. Go to the Google Cloud console.

    Go to the Google Cloud console

  2. Select the project that contains the container you want to use to test.

  3. Click Activate Cloud Shell.

  4. In Cloud Shell, set environment variables.

    1. The zone your cluster is in:

      export ZONE=CLUSTER_ZONE

    2. The project your container is in:

      export PROJECT=PROJECT_ID

    3. Your cluster name:

      export CLUSTER_NAME=CLUSTER_NAME

The variables are set. The following sections include instructions for testing Container Threat Detection detectors.

Added Binary Executed

To trigger an Added Binary Executed finding, drop a binary in your container and execute it. This example deploys the latest Ubuntu 24.04 image, copies /bin/ls to another location, and then executes it. The binary's execution is unexpected because the copy of the binary wasn't part of the original container image, even when that image is on Ubuntu 24.04, and containers are meant to be immutable.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Drop a binary and execute it:

This test procedure should create an Added Binary Executed finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

For noise reduction, when you first create a container, Container Threat Detection temporarily filters Added Binary Executed findings. To see all Added Binary Executed findings while a container is being set up, prefix your container name or pod name with ktd-test, as in the example.

Added Library Loaded

To trigger an Added Library Loaded finding, drop a library in your container and then load it. This example deploys the latest Ubuntu 24.04 image, copies /lib/x86_64-linux-gnu/libc.so.6 to another location, and then loads it using ld. The loaded library is unexpected because the copy of the library was not part of the original container image, even if that image is on Ubuntu 24.04, and containers are meant to be immutable.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Drop a library and use ld to load it:

This test procedure should create an Added Library Loaded finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center at the organization level.

For noise reduction, when you first create a container, Container Threat Detection temporarily filters Added Library Loaded findings. To see all Added Library Loaded findings while a container is being set up, prefix your container name or pod name with ktd-test, as in the example.

Collection: Pam.d Modification (Preview)

To trigger a pam.d modification detection, modify one of the host's PAM related files. This example deploys the latest Ubuntu 24.04 image, mounting the host's root file system into the container, and then modifies /etc/pam.d/sshd.

This is a file monitoring detector and has specific GKE version requirements.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a binary that modifies one of the PAM related files on the host.

This test procedure triggers a pam.d modification finding that you can view in Security Command Center and, if you have configured Logging for Container Threat Detection, in Cloud Logging. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center at the organization level.

To trigger an Command and Control: Steganography Tool Detected (Preview) finding, a binary with file manipulation capabilities consistent with steganography tools must execute within a container. This example uses the latest Ubuntu 24.04 image. It copies /bin/ls and renames that to steghide (or another steganography tool like stegano). This behavior is flagged as suspicious because it can indicate an attempt to prepare a container for hiding or extracting data, potentially for malicious purposes.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a steganography tool binary like steghide:

This test procedure creates a Command and Control: Steganography Tool Detected finding that you can view in Security Command Center and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Credential Access: Access Sensitive Files on Nodes (Preview)

To trigger a Sensitive File Accessed detection, read the host's /etc/shadow file. This example deploys the latest Ubuntu 24.04 image, mounting the host's root file system into the container, and then reads /etc/shadow using cat.

This is a file monitoring detector and has specific GKE version requirements.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a binary that reads the host's /etc/shadow file.

This test procedure triggers a Sensitive File Accessed finding that you can view in Security Command Center and, if you have configured Logging for Container Threat Detection, in Cloud Logging. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center at the organization level.

Credential Access: Find Google Cloud Credentials

To trigger a Credential Access: Find Google Cloud Credentials finding, a binary capable of searching file contents needs to be executed within a container. This example uses the latest Ubuntu 24.04 image. It copies /bin/ls and renames that to grep. The renamed binary is then executed with arguments that specify a search pattern indicative of a form of Google Cloud credentials. This action is flagged as suspicious because it mimics the behavior observed when attempting to locate Google Cloud credentials.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a search tool binary like find with appropriate arguments:

This test procedure should create an Credential Access: Find Google Cloud Credentials finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Credential Access: GPG Key Reconnaissance

To trigger an Credential Access: GPG Key Reconnaissance finding, a binary capable of searching file contents needs to be executed within a container. This example uses the latest Ubuntu 24.04 image. It copies /bin/ls and renames that to find (or another suitable search utility like grep). The renamed binary is then executed with arguments that specify a search pattern indicative of private keys or passwords, or content patterns suggesting passwords or secrets. This action is flagged as suspicious because it mimics the behavior observed when attempting to locate GPG security keys.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a search tool binary like find with appropriate arguments:

This test procedure should create an Credential Access: GPG Key Reconnaissance finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Credential Access: Search Private Keys or Passwords

To trigger an Credential Access: Search Private Keys or Passwords finding, a binary capable of searching file contents needs to be executed within a container. This example uses the latest Ubuntu 24.04 image. It copies /bin/ls and renames that to find (or another suitable search utility like grep). The renamed binary is then executed with arguments that specify a search pattern indicative of private keys or passwords, or content patterns suggesting passwords or secrets. This action is flagged as suspicious because it mimics the behavior observed when attempting to locate sensitive information like private keys or passwords within a containerized environment.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a search tool binary like find with appropriate arguments:

This test procedure should create an Credential Access: Search Private Keys or Passwords finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Defense Evasion: Base64 ELF File Command Lines

To trigger an Defense Evasion: Base64 ELF File Command Line finding, a process must have base64 as an argument and f0VMRgIB as an argument which is the base64 encoded form of ELF. This example uses the latest Ubuntu 24.04 image. base64 is then executed with the -d and f0VMRgIB arguments. This action is flagged as suspicious because it mimics the behavior observed when attempting to decode binary data to execute malicious code.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a search tool binary like find with appropriate arguments:

This test procedure should create two Defense Evasion: Base64 ELF File Command Line findings that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center. Two findings are created because the initial bash -c command as well as the execution of the base64 -d command satisfy the finding criteria.

Defense Evasion: Base64 Encoded Python Script Executed

To trigger an Defense Evasion: Base64 Encoded Python Script Executed finding, a process must have echo or base64 as an argument and aW1wb3J0IH as an argument which is the base64 encoded form of python -c. This example uses the latest Ubuntu 24.04 image. echo is then executed with the aW1wb3J0IH argument. This action is flagged as suspicious because it mimics the behavior observed when attempting to decode binary data to execute malicious code.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a search tool binary like find with appropriate arguments:

This test procedure should create a Defense Evasion: Base64 Encoded Python Script Executed finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Defense Evasion: Base64 Encoded Shell Script Executed

To trigger an Defense Evasion: Base64 Encoded Shell Script Executed finding, a process must have echo or base64 as an argument and IyEvYmluL2Jhc2gK as an argument which is the base64 encoded form of #!/bin/bash. This example uses the latest Ubuntu 24.04 image. echo is then executed with the IyEvYmluL2Jhc2gK argument. This action is flagged as suspicious because it mimics the behavior observed when attempting to decode binary data to execute malicious code.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a search tool binary like find with appropriate arguments:

This test procedure should create a Defense Evasion: Base64 Encoded Shell Script Executed finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Defense Evasion: Disable or Modify Linux Audit System (Preview)

To trigger a Disable or Modify Linux Audit Modification detection, modify one of the host's auditing-related configuration files. This example deploys the latest Ubuntu 24.04 image, mounting the host's root file system into the container, and then modifies /etc/systemd/journald.conf.

This is a file monitoring detector and has specific GKE version requirements.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a binary that modifies one of the host's audit-related configuration files, such as /etc/systemd/journald.conf.

This test procedure triggers a Disable or Modify Linux Audit System finding that you can view in Security Command Center and, if you have configured Logging for Container Threat Detection, in Cloud Logging. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center at the organization level.

To trigger a Defense Evasion: Launch Code Compiler Tool In Container (Preview) finding, a code compiler tool must execute within a container. This example uses the latest Ubuntu 24.04 image. It copies /bin/ls and renames that to gcc10 (or another compiler like clang). This behavior is flagged as suspicious because it can indicate an attempt to compile and execute malicious code within the container to evade detection or modify its behavior.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a compiler binary like gcc10 with appropriate arguments:

This test procedure creates a Defense Evasion: Launch Code Compiler Tool In Container finding that you can view in Security Command Center and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Defense Evasion: Root Certificate Installed (Preview)

To trigger a Root Certificate Installed detection, create a root certificate file on the host from a container. This example deploys the latest Ubuntu 24.04 image, mounting the host's root file system into the container. It then creates an empty certificate file in an appropriate directory.

This is a file monitoring detector and has specific GKE version requirements.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Install a certificate file onto the host from a container.

Execution: Added Malicious Binary Executed

To trigger an Execution: Added Malicious Binary Executed finding, drop a malicious binary in your container and execute it. This example deploys the latest Ubuntu 24.04 image, creates a simulated malicious file, and then executes it. The binary's execution is unexpected because the simulated malicious binary wasn't part of the original container image, and the binary is an EICAR test file, a file classified as malicious by the threat intelligence.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Drop the EICAR binary and execute it:

This test procedure should create an Execution: Added Malicious Binary Executed finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

For noise reduction, when you first create a container, Container Threat Detection temporarily filters Execution: Added Malicious Binary Executed findings. To see all Execution: Added Malicious Binary Executed findings while a container is being set up, prefix your container name or pod name with ktd-test, as in the example.

Execution: Container Escape

To trigger an Execution: Container Escape finding, place a binary in your container and execute it. This example deploys the latest Ubuntu 24.04 image, copies /bin/ls to another location, renames it to a suspicious tool (botb-linux-amd64), and executes it with additional arguments. This action is considered suspicious because this execution simulates behavior consistent with a container escape attempt.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Drop a Container Exploitation tool binary like botb-linux-amd64 and execute it:

This test procedure should create an Execution: Container Escape finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Execution: Fileless Execution in /memfd:

To trigger an Execution: Fileless Execution in /memfd: finding, a process must be executed from the /memfd: in-memory file system. This example uses the latest Ubuntu 24.04 image. The /bin/ls utility is copied to an anonymous file in /memfd:. This copied binary is then executed. The execution of a binary under /memfd: is flagged as suspicious because it mimics the behavior of an object trying to execute in memory to avoid file based detections.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Create a privileged container and open bash to execute commands:

This test procedure should create an Execution: Fileless Execution in /memfd: finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Execution: Ingress Nightmare Vulnerability Execution

To trigger an Execution: Ingress Nightmare Vulnerability Execution (Preview) finding, execute the nginx binary in your container. This example deploys the latest Ubuntu 24.04 image, copies /bin/ls to another location, renames it to an Nginx binary (nginx), and executes it with additional arguments referencing the /proc file system. This action is deemed suspicious because it simulates behavior consistent with the Ingress Nightmare exploit (CVE-2025-1974), thereby indicating potential remote code execution.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Create an Nginx binary like nginx and execute it while accessing the /proc file system:

This test procedure creates an Execution: Ingress Nightmare Vulnerability Execution finding that you can view in Security Command Center and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center

To trigger an Execution: Kubernetes Attack Tool Execution finding, place a binary in your container and execute it. This example deploys the latest Ubuntu 24.04 image, copies /bin/ls to another location, renames it to a suspicious tool (amicontained), and executes it. This action is considered suspicious because it simulates behavior consistent with a potential Kubernetes attack tool execution attempt.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Drop a Kubernetes Attack tool binary like amicontained and execute it:

This test procedure should create an Execution: Kubernetes Attack Tool Execution finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

To trigger an Execution: Local Reconnaissance Tool Execution finding, place a binary in your container and execute it. This example deploys the latest Ubuntu 24.04 image, copies /bin/ls to another location, renames it to a suspicious tool (linenum.sh), and executes it. This action is considered suspicious because executing the renamed binary simulates behavior consistent with a local reconnaissance attempt.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Introduce a Local Reconnaissance tool binary like linenum.sh and execute it:

This test procedure should create an Execution: Local Reconnaissance Tool Execution finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Execution: Malicious Python Executed

Preview

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

To trigger an Execution: Malicious Python Executed finding, you can execute Python in the following procedure in your container.

The procedure deploys the latest Python image, copies Python code that appears malicious, and then executes it. To trigger a detection, the Python code must appear malicious to the detector.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute the following script in a new container.

    This Python code originated from a honeypot. However, it was modified so that it does not execute the malicious binary. Running the script won't cause malicious activity in your container. The binary at the referenced URL does not exist and attempting to follow the URL results in a 404 error. This is expected. The attempt to download, decode, and execute a binary using an inline script is what triggers the detection.

This test procedure creates an Execution: Malicious Python Executed finding that you can view in Security Command Center and in Cloud Logging if you configured logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Execution: Modified Malicious Binary Executed

To trigger an Execution: Modified Malicious Binary Executed finding, modify a malicious binary in your container and execute it. This example deploys the latest Ubuntu 24.04 image, modifies /bin/ls to an EICAR testing malicious file, and then executes it. The binary's execution is unexpected because the created /bin/ls is modified during container runtime as an EICAR testing malicious binary, and the EICAR binary is a known malicious file according to the threat intelligence.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Drop the EICAR binary and execute it:

This test procedure should create an Execution: Modified Malicious Binary Executed finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

For noise reduction, when you first create a container, Container Threat Detection temporarily filters Execution: Modified Malicious Binary Executed findings. To see all Execution: Modified Malicious Binary Executed findings while a container is being set up, prefix your container name or pod name with ktd-test, as in the example.

Execution: Netcat Remote Code Execution In Container

To trigger an Execution: Netcat Remote Code Execution In Container event, a binary capable of network communication (like netcat itself, or a renamed copy of another utility) needs to be present and executed inside the container. This example deploys the latest Ubuntu 24.04 image as a base. It copies the /bin/ls binary and renames that copy to netcat (a network utility). This renamed binary is then executed with arguments appropriate for network interaction. This activity is flagged as suspicious because it mimics the behavior often observed during actual remote code execution attempts within containerized environments.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Introduce a network communication tool binary like netcat and execute it with appropriate arguments:

This test procedure should create an Execution: Netcat Remote Code Execution In Container finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Execution: Possible Arbitrary Command Execution through CUPS (CVE-2024-47177)

To trigger an Execution: Possible Arbitrary Command Execution through CUPS (CVE-2024-47177) finding, the execution of a shell process by the foomatic-rip must take place. This example uses the latest Ubuntu 24.04 image. It copies /bin/bash to /tmp/foomatic-rip. This renamed and copied binary is ran as a shell script to create a child shell command. This behavior is flagged as suspicious because it can indicate an attempt to execute arbitrary workloads on compromised systems.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute the command with appropriate arguments:

This test procedure creates an Execution: Possible Arbitrary Command Execution through CUPS (CVE-2024-47177) finding that you can view in Security Command Center and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Execution: Possible Remote Command Execution Detected

To trigger an Execution: Possible Remote Command Execution Detected (Preview) finding, the execution of a command or binary commonly associated with remote command execution must be observed within a container. This example uses the latest Ubuntu 24.04 image. It copies /bin/ls and renames that to touch (or another tool like find). This renamed binary is then executed with arguments appropriate for remote command execution. This behavior is flagged as suspicious because it can indicate an attempt to establish unauthorized remote access to or from the container.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a binary like touch with appropriate arguments:

This test procedure creates an Execution: Possible Remote Command Execution Detected finding that you can view in Security Command Center and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Execution: Program Run with Disallowed HTTP Proxy Env

To trigger an Execution: Program Run with Disallowed HTTP Proxy Env finding, execute a program within a container, setting an HTTP proxy environment variable to a disallowed value. This example uses the latest Ubuntu 24.04 image. The /bin/ls utility is copied and renamed to /tmp/curl. This renamed binary is then executed with a disallowed value set for an HTTP proxy environment variable (for example, HTTP_PROXY, http_proxy). The combination of program execution and the presence of a disallowed HTTP proxy environment is flagged as suspicious, as it suggests an attempt to communicate through an unauthorized proxy.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a network-capable binary, like curl, and execute it with a disallowed HTTP proxy environment variable:

This test procedure should create an Execution: Program Run with Disallowed HTTP Proxy Env finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Execution: Socat Reverse Shell Detected

To trigger an Execution: Socat Reverse Shell Detected finding, a process reverse shell connection must be established by the socat utility. This example uses the latest Ubuntu 24.04 image. The socat utility is installed and a local tcp listener is created and then bound to by the socat utility. The reverse shell created by socat is flagged as suspicious because it allows an attacker to run arbitrary workloads on the system.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Create a container and open bash to execute commands:

  4. Install the socat utility

      apt update && apt install socat -y

  5. Create a listener using socat

      (socat UNIX-LISTEN:/tmp/shell.sock STDOUT &)

  6. Wait about for the listener to establish itself. It takes a little less than 10 seconds.

  7. Bind to the unix socket to establish a reverse shell connection

      socat UNIX-CONNECT:/tmp/shell.sock EXEC:/bin/bash,pty,stderr,setsid,sigint,sane

  8. This may return an error, but that is okay as long as it will briefly establish a connection beforehand.

This test procedure should create an Execution: Socat Reverse Shell Detected finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Execution: Suspicious Cron Modification (Preview)

To trigger a Suspicious Cron Modification detection, modify the host's /etc/crontab file from a container. This example deploys the latest Ubuntu 24.04 image, mounting the host's root file system into the container. It then updates the crontab file.

This is a file monitoring detector and has specific GKE version requirements.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a command to modify the host's /etc/crontab file.

To trigger an Execution: Suspicious OpenSSL Shared Object Loaded finding, execute the openssl engine command with an argument that is a file that ends with the .so extension. This example uses the latest Ubuntu 24.04 image. The /bin/ls utility is copied and renamed to /tmp/openssl. This renamed binary is then executed with the engine and fake .so file arguments. The execution of openssl engine with a .so file is flagged as suspicious because it mimics the behavior of a shared object being loaded to execute malicious code.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a network-capable binary, like curl, and execute it with a disallowed HTTP proxy environment variable:

This test procedure should create an Execution: Suspicious OpenSSL Shared Object Loaded finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

To trigger an Exfiltration: Launch Remote File Copy Tools In Container finding, execute a common remote file copy tool within a container. This example uses the latest Ubuntu 24.04 image. The /bin/ls utility is copied and renamed to /tmp/rsync and then executed to retrieve a file from a remote, potentially malicious, source. The execution of such a tool with remote file retrieval arguments within a container is flagged as suspicious, as it could indicate an attempt to download and execute malicious code or exfiltrate data.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a remote file copy tool, like rsync, and execute it:

This test procedure should create an Exfiltration: Launch Remote File Copy Tools In Container finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Impact: Detect Malicious Cmdlines

To trigger an Impact: Detect Malicious Cmdlines (Preview) finding, the execution of a command line with known malicious patterns or arguments must be observed within a container. This example uses the latest Ubuntu 24.04 image. It involves copying the /bin/ls binary and renaming that copy to ipfs. The renamed binary is then executed. This behavior is flagged as suspicious because it can indicate an attempt to execute malicious code or bypass security controls.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a binary like ipfs:

This test procedure creates an Impact: Detect Malicious Cmdlines finding that you can view in Security Command Center and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Impact: Remove Bulk Data From Disk

To trigger an Impact: Remove Bulk Data From Disk finding, place a binary capable of data deletion or overwriting in your container and execute it. This example uses the latest Ubuntu 24.04 image. It involves copying the /bin/ls binary and renaming that copy to shred (or a similar utility designed for secure file deletion). The renamed binary is then executed. This action is flagged as suspicious because it mimics the behavior often seen when attempts are made to remove large amounts of data from a disk within a containerized environment.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Introduce a file or data deletion binary like shred and execute it:

This test procedure should create an Impact: Remove Bulk Data From Disk finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Impact: Suspicious crypto mining activity using the Stratum Protocol

To trigger an Impact: Suspicious crypto mining activity using the Stratum Protocol finding, a binary needs to be executed within a container with arguments that resemble those used by crypto mining software communicating using the Stratum protocol. The example uses the latest Ubuntu 24.04 image. It copies /bin/ls and renames that copy to a mock binary (presumably to simulate a crypto miner). This renamed binary is then executed with arguments that include stratum+tcp or similar Stratum protocol indicators. This activity is flagged as suspicious because it mimics the network communication patterns of crypto mining software within containerized environments.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Introduce a utility binary like curl and execute it with arguments that resemble those used by crypto mining software communicating using the Stratum protocol:

This test procedure should create an Impact: Suspicious crypto mining activity using the Stratum Protocol finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

You might also see an additional finding for the bash command that you run in this test. This behavior is normal, and you can ignore the additional finding.

Malicious Script Executed

To trigger a Malicious Script Executed finding, you can execute the script in the following procedure in your container.

The procedure deploys the latest Ubuntu 24.04 image, copies a script that appears malicious, and then executes it. To trigger a detection, a script must appear malicious to the detector.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute the following script in a new container.

    This inline Bourne shell script originated from a honeypot. However, it has been modified so that it does not execute the malicious binary, so running the script won't cause malicious activity in your container. The binary at the referenced URL may have been removed and attempting to follow the URL will result in a 404 error. This is expected. The attempt to download, decode, and execute a binary using an inline script is what triggers the detection.

This test procedure creates a Malicious Script Executed finding that you can view in Security Command Center and in Cloud Logging if you've configured logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Malicious URL Observed

To trigger a Malicious URL Observed finding, execute a binary and provide a malicious URL as an argument.

The following example deploys an Ubuntu 24.04 image and executes /bin/curl to access a sample malware URL from the Safe Browsing service.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute curl and provide a malicious URL as an argument:

This test procedure triggers a Malicious URL Observed finding that you can view in Security Command Center and, if you have configured Logging for Container Threat Detection, in Cloud Logging. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center at the organization level.

Persistence: Modify ld.so.preload (Preview)

To trigger a ld.so.preload modification detection, modify the host's /etc/ld.so.preload file. This example deploys the latest Ubuntu 24.04 image, mounting the host's root file system into the container, and then updates /etc/ld.so.preload.

This is a file monitoring detector and has specific GKE version requirements.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Execute a binary that modifies the host's /etc/ld.so.preload file.

This test procedure triggers a ld.so.preload modification finding that you can view in Security Command Center and, if you have configured Logging for Container Threat Detection, in Cloud Logging. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center at the organization level.

Privilege Escalation: Abuse of Sudo For Privilege Escalation (CVE-2019-14287)

To trigger a Privilege Escalation: Abuse of Sudo For Privilege Escalation (CVE-2019-14287) finding, execute the sudo binary with the -u#-1 parameter. This example copies the /bin/ls binary to imitate the sudo binary and executes it with the specified parameter.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Start a binary with /bin/echo redirection to the Google public DNS:

This test procedure creates a Privilege Escalation: Abuse of Sudo For Privilege Escalation (CVE-2019-14287) finding you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center at the organization level.

Privilege Escalation: Fileless Execution in /dev/shm

To trigger an Privilege Escalation: Fileless Execution in /dev/shm finding, a process must be executed from the /dev/shm in-memory file system. This example uses the latest Ubuntu 24.04 image. The /bin/echo utility is copied to /dev/shm/echo. This renamed binary is then executed. The execution of a file under /dev/shm is flagged as suspicious because it mimics the behavior of an object trying to execute in memory to avoid file based detections.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Create a privileged container and open bash to execute commands:

  4. Copy echo to /dev/shm and make it executable using chmod

      cp /bin/echo /dev/shm
  chmod 777 /dev/shm/echo

  5. Remount the /dev/shm to enable execution

      mount -o remount,exec /dev/shm

  6. Execute echo from /dev/shm

      /dev/shm/echo "Hello from /dev/shm"

This test procedure should create an Privilege Escalation: Fileless Execution in /dev/shm finding that you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.

Privilege Escalation: Polkit Local Privilege Escalation Vulnerability (CVE-2021-4034)

To trigger a Privilege Escalation: Polkit Local Privilege Escalation Vulnerability (CVE-2021-4034) finding, execute a pkexec binary with the GCONV_PATH environment variable set as a non-root user. This example copies the /bin/ls binary to imitate the pkexec binary and executes it with the specified parameter as user ID 1000.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Start a binary with /bin/echo redirection to the Google public DNS:

This test procedure creates a Privilege Escalation: Polkit Local Privilege Escalation Vulnerability (CVE-2021-4034) finding you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center at the organization level.

Privilege Escalation: Sudo Potential Privilege Escalation (CVE-2021-3156)

To trigger a Privilege Escalation: Sudo Potential Privilege Escalation (CVE-2021-3156) finding, execute the sudo binary as a non-root user with the -s parameter and a parameter that ends with \`. This example copies the/bin/lsbinary to imitate thesudo` binary and executes it with the specified parameters.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Start a binary with /bin/echo redirection to the Google public DNS:

This test procedure creates a Privilege Escalation: Sudo Potential Privilege Escalation (CVE-2021-3156) finding you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center at the organization level.

Reverse Shell

To trigger a Reverse Shell finding, start a binary with stdin redirection to a TCP connected socket. This example copies /bin/echo to /tmp/sh, then starts /tmp/sh with redirection to the Google public DNS 8.8.8.8 on the DNS port. Nothing is printed when you run this example. To prevent any external code injection through a man-in-the-middle (MITM) attack, this example doesn't use the /bin/sh binary.

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Start a binary with /bin/echo redirection to the Google public DNS:

This test procedure creates a Reverse Shell finding you can view in Security Command Center, and in Cloud Logging if you've configured Logging for Container Threat Detection. Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center at the organization level.

Unexpected Child Shell

To test the Unexpected Child Shell detector, you can create a process tree that includes a child shell process.

The following example creates an consul->dash process tree, which can be detected by the Unexpected Child Shell detector. This test is safe because it uses only built-in binaries. This example does the following:

  1. Creates a copy of the sh process and names it consul.
  2. Copies the echo process and names it dash.
  3. Invokes the copied dash process in the copied consul process.

To trigger an Unexpected Child Shell finding, do the following:

  1. Set environment variables.

  2. Use Cloud Shell to access the cluster control plane:

    gcloud container clusters get-credentials $CLUSTER_NAME \
    --zone $ZONE \
    --project $PROJECT

  3. Use the mock consul process to invoke a mock shell:

This test procedure creates an Unexpected Child Shell finding that you can view in Security Command Center. If Logging is configured for Container Threat Detection and you have Security Command Center Premium or Enterprise activated at the organization level, then you can view the finding in Cloud Logging too.

What's next

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-14 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4