Execution: Suspicious Exec or Attach to a System Pod
Stay organized with collectionsSave and categorize content based on your preferences.
This document describes a threat finding type in Security Command Center. Threat findings are generated bythreat detectorswhen they detect
a potential threat in your cloud resources. For a full list of available threat findings, seeThreat findings index.
Overview
Someone used theexecorattachcommands to get a shell or execute a command
on a container running in thekube-systemnamespace. These methods are
sometimes used for legitimate debugging purposes. However, thekube-system
namespaceis intended for system objects created by Kubernetes, and unexpected
command execution or shell creation should be reviewed. For more details, see
the log message for this alert.
How to respond
To respond to this finding, do the following:
Review the audit logs in Cloud Logging to determine if this was expected
activity by the principal.
Determine whether there are other signs of malicious activity by the
principal in the logs.
[[["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-09-04 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| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nSomeone used the `exec` or `attach` commands to get a shell or execute a command\non a container running in the `kube-system` namespace. These methods are\nsometimes used for legitimate debugging purposes. However, the `kube-system\nnamespace` is intended for system objects created by Kubernetes, and unexpected\ncommand execution or shell creation should be reviewed. For more details, see\nthe log message for this alert.\n\nHow to respond\n\nTo respond to this finding, do the following:\n\n1. Review the audit logs in Cloud Logging to determine if this was expected activity by the principal.\n2. Determine whether there are other signs of malicious activity by the principal in the logs.\n\nReview the [guidance for using the principle of least privilege](/kubernetes-engine/docs/best-practices/rbac#least-privilege) for the RBAC roles and cluster roles that allowed this access.\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)."]]