Azure Kubernetes Pods Deleted
Identifies the deletion of Azure Kubernetes Pods.
Detection logic
Detection requirements
- Log source product
- azure
- Log source service
- activitylogs
Known benign triggers
- Pods deletions from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
- Pods may be deleted by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment.
MITRE ATT&CK mappings
Not mapped to ATT&CK.
References
| Reference | Cited by |
|---|---|
| github.com/elastic/detection-rules/blob/065bf48a9987cd8bd826c098a30ce36e6868ee46/rules/integrations/azure/impact_kubernetes_pod_deleted.toml | Only this detection cites it |
| learn.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#microsoftkubernetes | 29 |
From the source
- At source
- Open at source
- Upstream identifier
- b02f9591-12c3-4965-986a-88028629b2e1
- Tagged by the source as
- attack.impact
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1