이 문서에서는 Security Command Center의 위협 발견 항목 유형에 대해 설명합니다. 위협 발견 항목은 위협 감지기가 클라우드 리소스에서 잠재적인 위협을 감지할 때 생성됩니다. 사용 가능한 위협 발견 항목의 전체 목록은 위협 발견 항목 색인을 참고하세요.
개요
Container Threat Detection에서 예기치 않게 하위 셸 프로세스가 생성된 프로세스를 관찰했습니다. 이 이벤트는 공격자가 셸 명령어 및 스크립트를 악용하려고 시도 중임을 나타낼 수 있습니다.
대응 방법
이 발견 항목에 대응하려면 다음을 수행하세요.
1단계: 발견 항목 세부정보 검토하기
발견 항목 검토의 지시에 따라 Unexpected Child Shell 발견 항목을 엽니다. 발견 항목의 세부정보 패널의 요약 탭이 열립니다.
요약 탭에서 다음 섹션의 정보를 검토합니다.
특히 다음 필드를 포함하는 감지된 항목:
상위 프로세스: 예기치 않게 하위 셸 프로세스가 생성된 프로세스입니다.
하위 프로세스: 하위 셸 프로세스
인수: 하위 셸 프로세스 바이너리에 제공된 인수
환경 변수: 하위 셸 프로세스 바이너리의 환경 변수
컨테이너: 컨테이너 이름입니다.
컨테이너 URI: 컨테이너의 이미지 URI
Kubernetes 포드: 포드 이름 및 네임스페이스입니다.
특히 다음 필드를 포함하는 영향을 받는 리소스:
리소스 표시 이름: 영향을 받는 리소스의 이름
리소스 전체 이름: 클러스터의 전체 리소스 이름 전체 리소스 이름에는 다음 정보가 포함됩니다.
클러스터를 포함하는 프로젝트: projects/PROJECT_ID
클러스터가 있는 위치: zone/ZONE 또는 locations/LOCATION
클러스터의 이름: projects/CLUSTER_NAME
특히 다음 필드를 포함하는 관련 링크:
VirusTotal 표시기: VirusTotal 분석 페이지 링크
JSON 탭을 클릭하고 다음 필드를 확인합니다.
+processes: 발견 항목과 관련된 모든 프로세스가 포함된 배열. 이 배열에는 하위 셸 프로세스와 상위 프로세스가 포함됩니다.
+resource:
+project_display_name: 애셋이 포함된 프로젝트의 이름
+sourceProperties:
+VM_Instance_Name: 포드가 실행된 GKE 노드의 이름입니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-05(UTC)"],[],[],null,["| Premium and Enterprise [service tiers](/security-command-center/docs/service-tiers)\n\nThis document describes a threat finding type in Security Command Center. Threat findings are generated by\n[threat detectors](/security-command-center/docs/concepts-security-sources#threats) when they detect\na potential threat in your cloud resources. For a full list of available threat findings, see [Threat findings index](/security-command-center/docs/threat-findings-index).\n\nOverview\n\nContainer Threat Detection observed a process that unexpectedly spawned a child shell\nprocess. This event might indicate that an attacker is trying to abuse shell\ncommands and scripts.\n\nHow to respond\n\nTo respond to this finding, do the following:\n\nStep 1: Review finding details\n\n1. Open an `Unexpected Child Shell` finding as directed in\n [Reviewing findings](/security-command-center/docs/how-to-investigate-threats#reviewing_findings). The details panel for the\n finding opens to the **Summary** tab.\n\n2. On the **Summary** tab, review the information in the following sections:\n\n - **What was detected** , especially the following fields:\n - **Parent process**: the process that unexpectedly created the child shell process.\n - **Child process**: the child shell process.\n - **Arguments**: the arguments provided to the child shell process binary.\n - **Environment variables**: the environment variables of the child shell process binary.\n - **Containers**: the name of the container.\n - **Containers URI**: the image URI of the container.\n - **Kubernetes pods**: the Pod name and namespace.\n - **Affected resource** , especially the following fields:\n - **Resource display name**: the name of the affected resource.\n - **Resource full name** : the [full resource name](/apis/design/resource_names) of the cluster. The full resource name includes the following information:\n - The project that contains the cluster: `projects/`\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e\n - The location in which the cluster is located: either `zone/`\u003cvar translate=\"no\"\u003eZONE\u003c/var\u003e or `locations/`\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e\n - The name of the cluster: `projects/`\u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e\n - **Related links** , especially the following fields:\n - **VirusTotal indicator**: link to the VirusTotal analysis page.\n3. Click the **JSON** tab and note the following fields:\n\n+`processes`: an array containing all processes related to the finding. This array includes the child shell process and the parent process.\n+`resource`:\n+`project_display_name`: The name of the project that contains the assets.\n+`sourceProperties`:\n+`VM_Instance_Name`: the name of the GKE node where the\nPod executed.\n\nStep 2: Review cluster and node\n\n1. In the Google Cloud console, go to the **Kubernetes clusters** page.\n\n [Go to Kubernetes clusters](https://console.cloud.google.com/kubernetes/list)\n2. On the Google Cloud console toolbar, select the project listed in\n `resource.project_display_name`, if necessary.\n\n3. Select the cluster listed in `resource.name`. Note any metadata about\n the cluster and its owner.\n\n4. Click the **Nodes** tab. Select the node listed in `VM_Instance_Name`.\n\n5. Click the **Details** tab and note the\n `container.googleapis.com/instance_id` annotation.\n\nStep 3: Review Pod\n\n1. In the Google Cloud console, go to the **Kubernetes Workloads** page.\n\n [Go to Kubernetes Workloads](https://console.cloud.google.com/kubernetes/workload)\n2. On the Google Cloud console toolbar, select the project that you noted\n in the **Resource full name** (`resource.name`) of the cluster in the\n finding summary, if necessary.\n\n3. Click **Show system workloads**.\n\n4. Filter the list of workloads by the cluster name that you noted in\n **Resource full name** (`resource.name`) of the finding summary and, if\n necessary, the pod **Namespace** (`kubernetes.pods.ns`) that you noted.\n\n5. Click the workload name that matches the value of the `VM_Instance_Name`\n property that you noted in the finding JSON earlier. The **Pod details**\n page opens.\n\n6. On the **Pod details** page, note any information about the Pod that\n might help you resolve the threat.\n\nStep 4: Check logs\n\n1. In the Google Cloud console, go to **Logs Explorer**.\n\n [Go to Logs Explorer](https://console.cloud.google.com/logs/query)\n2. On the Google Cloud console toolbar, select the project listed in\n `resource.project_display_name`.\n\n3. Set **Select time range** to the period of interest.\n\n4. On the page that loads, do the following:\n\n 1. Find Pod logs for `Pod_Name` by using the following filter:\n - `resource.type=\"k8s_container\"`\n - `resource.labels.project_id=\"`\u003cvar class=\"edit\" translate=\"no\"\u003eresource.project_display_name\u003c/var\u003e`\"`\n - `resource.labels.location=\"`\u003cvar class=\"edit\" translate=\"no\"\u003elocation\u003c/var\u003e`\"`\n - `resource.labels.cluster_name=\"`\u003cvar class=\"edit\" translate=\"no\"\u003ecluster_name\u003c/var\u003e`\"`\n - `resource.labels.namespace_name=\"`\u003cvar class=\"edit\" translate=\"no\"\u003ePod_Namespace\u003c/var\u003e`\"`\n - `resource.labels.pod_name=\"`\u003cvar class=\"edit\" translate=\"no\"\u003ePod_Name\u003c/var\u003e`\"`\n 2. Find cluster audit logs by using the following filter:\n - `logName=\"projects/`\u003cvar class=\"edit\" translate=\"no\"\u003eresource.project_display_name\u003c/var\u003e`/logs/cloudaudit.googleapis.com%2Factivity\"`\n - `resource.type=\"k8s_cluster\"`\n - `resource.labels.project_id=\"`\u003cvar class=\"edit\" translate=\"no\"\u003eresource.project_display_name\u003c/var\u003e`\"`\n - `resource.labels.location=\"`\u003cvar class=\"edit\" translate=\"no\"\u003elocation\u003c/var\u003e`\"`\n - `resource.labels.cluster_name=\"`\u003cvar class=\"edit\" translate=\"no\"\u003ecluster_name\u003c/var\u003e`\"`\n - \u003cvar class=\"edit\" translate=\"no\"\u003ePod_Name\u003c/var\u003e\n 3. Find GKE node console logs by using the following filter:\n - `resource.type=\"gce_instance\"`\n - `resource.labels.instance_id=\"`\u003cvar class=\"edit\" translate=\"no\"\u003einstance_id\u003c/var\u003e`\"`\n\nStep 5: Investigate the running container\n\nIf the container is still running, it might be possible to investigate the\ncontainer environment directly.\n\n1. Go to the Google Cloud console.\n\n [Open Google Cloud console](https://console.cloud.google.com/)\n2. On the Google Cloud console toolbar, select the project listed in\n `resource.project_display_name`.\n\n3. Click **Activate Cloud Shell** .\n\n4. Obtain GKE credentials for your cluster by running the\n following commands.\n\n For zonal clusters, run the following: \n\n gcloud container clusters get-credentials \u003cvar class=\"edit\" translate=\"no\"\u003ecluster_name\u003c/var\u003e --zone \u003cvar class=\"edit\" translate=\"no\"\u003elocation\u003c/var\u003e --project \u003cvar class=\"edit\" translate=\"no\"\u003eresource.project_display_name\u003c/var\u003e\n\n For regional clusters, run the following: \n\n gcloud container clusters get-credentials \u003cvar class=\"edit\" translate=\"no\"\u003ecluster_name\u003c/var\u003e --region \u003cvar class=\"edit\" translate=\"no\"\u003elocation\u003c/var\u003e --project \u003cvar class=\"edit\" translate=\"no\"\u003eresource.project_display_name\u003c/var\u003e\n\n5. To launch a shell within the container environment, run the following:\n\n kubectl exec --namespace=\u003cvar class=\"edit\" translate=\"no\"\u003ePod_Namespace\u003c/var\u003e -ti \u003cvar class=\"edit\" translate=\"no\"\u003ePod_Name\u003c/var\u003e -c \u003cvar class=\"edit\" translate=\"no\"\u003eContainer_Name\u003c/var\u003e -- /bin/sh\n\n This command requires the container to have a shell installed at `/bin/sh`.\n\n To view all processes running in the container, run the following command\n in the container shell: \n\n ps axjf\n\n This command requires the container to have `/bin/ps` installed.\n\nStep 6: Research attack and response methods\n\n1. Review MITRE ATT\\&CK framework entries for this finding type: [Command and Scripting Interpreter: Unix Shell](https://attack.mitre.org/techniques/T1059/004/).\n2. 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.\n3. To develop a response plan, combine your investigation results with the MITRE research and VirusTotal analysis.\n\nStep 7: Implement your response\n\n\nThe following response plan might be appropriate for this finding, but might also impact operations.\nCarefully evaluate the information you gather in your investigation to determine the best way to\nresolve findings.\n\n- Contact the owner of the project with the compromised container.\n- Stop or [delete](/container-registry/docs/managing#deleting_images) the compromised container and replace it with a [new container](/compute/docs/containers).\n\nWhat's next\n\n- Learn [how to work with threat\n findings in Security Command Center](/security-command-center/docs/how-to-investigate-threats).\n- Refer to the [Threat findings index](/security-command-center/docs/threat-findings-index).\n- Learn how to [review a\n finding](/security-command-center/docs/how-to-investigate-threats#reviewing_findings) through the Google Cloud console.\n- Learn about the [services that\n generate threat findings](/security-command-center/docs/concepts-security-sources#threats)."]]
