Azure Kubernetes Services (AKS) Kubernetes Pods Deleted
Identifies the deletion of Azure Kubernetes Pods. Adversaries may delete a Kubernetes pod to disrupt the normal behavior of the environment.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ESXiIaaSLinuxmacOSNetwork DevicesWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source category
- event_index
Known benign triggers
- 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. Pods deletions by unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
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 |
|---|---|
| docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#microsoftkubernetes | 7 |
From the source
- At source
- Open at source
- Upstream identifier
- 83a1931d-8136-46fc-b7b9-2db4f639e014
- Tagged by the source as
- Data Source: AzureData Source: Azure Activity LogsDomain: CloudDomain: ContainersNoise: LowPerformance: FastPlatform: AzurePlatform: KubernetesResources: Investigation GuideRule Type: Custom Query (KQL)Tactic: ImpactUse Case: Asset Visibility
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3