Azure Kubernetes Pods Deleted
editAzure Kubernetes Pods Deleted
editIdentifies the deletion of Azure Kubernetes Pods. Adversaries may delete a Kubernetes pod to disrupt the normal behavior of the environment.
Rule type: query
Rule indices:
- filebeat-*
- logs-azure*
Severity: medium
Risk score: 47
Runs every: 5 minutes
Searches indices from: now-25m (Date Math format, see also Additional look-back time)
Maximum alerts per execution: 100
References:
Tags:
- Elastic
- Cloud
- Azure
- Continuous Monitoring
- SecOps
- Asset Visibility
Version: 100 (version history)
Added (Elastic Stack release): 7.16.0
Last modified (Elastic Stack release): 8.5.0
Rule authors: Austin Songer
Rule license: Elastic License v2
Potential false positives
editPods 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.
Investigation guide
editRule query
editevent.dataset:azure.activitylogs and azure.activitylogs.operation_name :"MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/PODS/DELETE" and event.outcome:(Success or success)
Threat mapping
editFramework: MITRE ATT&CKTM
-
Tactic:
- Name: Impact
- ID: TA0040
- Reference URL: https://attack.mitre.org/tactics/TA0040/
Rule version history
edit- Version 100 (8.5.0 release)
-
- Formatting only
- Version 5 (8.4.0 release)
-
-
Updated query, changed from:
event.dataset:azure.activitylogs and azure.activitylogs.operation_name :"MICROSOFT.KUBERNETES/CONNECTEDCLUSTERS/PODS/DELETE" and event.outcome:(Success or success)
-
- Version 3 (8.1.0 release)
-
- Formatting only
- Version 2 (8.0.0 release)
-
- Formatting only