Kubernetes Admission Controller Modification
Detects when a modification (create, update or replace) action is taken that affects mutating or validating webhook configurations, as they can be used by an adversary to achieve persistence or exfiltrate access…
Description
Detects when a modification (create, update or replace) action is taken that affects mutating or validating webhook configurations, as they can be used by an adversary to achieve persistence or exfiltrate access credentials.
Detection logic
Detection requirements
- Platform
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source product
- kubernetes
- Log source service
- audit
Known benign triggers
- Automated processes may need to take these actions and may need to be filtered.
- Modifying the Kubernetes Admission Controller may need to be done by a system administrator.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| kubernetes.io/docs/reference/config-api/apiserver-audit.v1/ | 5 |
| security.padok.fr/en/blog/kubernetes-webhook-attackers | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- eed82177-38f5-4299-8a76-098d50d225ab
- Tagged by the source as
- attack.credential-accessattack.initial-accessattack.persistenceattack.privilege-escalationattack.stealth
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1