Defensive Evasion: Static Pod Created

This document describes a threat finding type in Security Command Center. Threat findings are generated by threat detectors when they detect a potential threat in your cloud resources. For a full list of available threat findings, see Threat findings index .

Overview

Someone created a static Pod in your GKE cluster. Static Pods run directly on the node and bypass the Kubernetes API server, which make them more difficult to monitor and control. This could be used by attackers to evade detection or maintain persistence.

How to respond

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.

To respond to this finding, do the following:

1. Review the static Pod's manifest file and its purpose. Verify that it is legitimate and necessary.
2. Evaluate if the static Pod's functionality can be achieved through a regular Pod managed by the Kubernetes API server.
3. If the static Pod is required, ensure that it follows security best practices and has minimal privileges.
4. Monitor the static Pod's activity and its impact on your cluster.

What's next

• Learn how to work with threat findings in Security Command Center .
• Refer to the Threat findings index .
• Learn how to review a finding through the Google Cloud console.
• Learn about the services that generate threat findings .