Stay organized with collections
Save and categorize content based on your preferences.
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
A webhook configuration has been detected in your GKE cluster.
Webhooks can intercept and modify Kubernetes API requests, which potentially
allows attackers to persist within your cluster or manipulate resources.
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:
Identify the purpose and origin of the webhook configuration. Verify that
it is from a trusted source and serves a legitimate purpose.
Review the webhook configuration to understand its scope
and the types of requests it intercepts.
Monitor the webhook activity for any suspicious or unauthorized actions.
If the webhook is not necessary or its behavior is
concerning, consider removing or disabling it.
[[["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\nA webhook configuration has been detected in your GKE cluster.\nWebhooks can intercept and modify Kubernetes API requests, which potentially\nallows attackers to persist within your cluster or manipulate resources.\n\nHow to respond\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\nTo respond to this finding, do the following:\n\n1. Identify the purpose and origin of the webhook configuration. Verify that it is from a trusted source and serves a legitimate purpose.\n2. Review the webhook configuration to understand its scope and the types of requests it intercepts.\n3. Monitor the webhook activity for any suspicious or unauthorized actions.\n4. If the webhook is not necessary or its behavior is concerning, consider removing or disabling it.\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)."]]
