Kubernetes Privileged Pod Created via Pod Creation Requests
Flags Kubernetes pod creates where container capabilities are set to all, indicating possible privileged access setup.
- Product
- kubernetes
- Category
- application
- Author
- Leo Tsaousis (@laripping) (SigmaHQ), DRL 1.1
- Published
- 2024-03-26
- Updated
- 2026-07-31
ATT&CK techniques
Priv EscRecon
Resource Dev
Initial Access
Execution
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact
What it detects
This rule flags Kubernetes API requests that create pods with wildcarded capabilities, indicating a privileged container configuration. Privileged pods can access host resources with elevated privileges, which attackers may use to increase impact from an initial foothold. It relies on Kubernetes audit log entries showing a pod create action with the matched capabilities field.
Reporting behind it
- microsoft.github.iohttps://microsoft.github.io/Threat-Matrix-for-Kubernetes/techniques/Privileged%20container/
- docs.aws.amazon.comhttps://docs.aws.amazon.com/guardduty/latest/ug/guardduty_finding-types-kubernetes.html#privilegeescalation-kubernetes-privilegedcontainer
- elastic.cohttps://www.elastic.co/guide/en/security/current/kubernetes-pod-created-with-hostnetwork.html
- elastic.cohttps://www.elastic.co/guide/en/security/current/kubernetes-container-created-with-excessive-linux-capabilities.html
- github.comhttps://github.com/SigmaHQ/sigma/blob/master/rules/application/kubernetes/audit/kubernetes_audit_privileged_pod_creation.yml
Changelog
v5- v5Candidate ingested via manual entry.2026-07-31
- v4Candidate ingested via manual entry.2026-07-31
- v3Candidate ingested via manual entry.2026-07-31
- v2Candidate ingested via manual entry.2026-07-31
- v1No changelog recorded for this version.2026-07-30
Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.
title: Kubernetes Privileged Pod Created via Pod Creation Requests
id: c701fd66-ca82-47b1-87f7-f41a7931674e
status: test
description: This rule flags Kubernetes API requests that create pods with wildcarded capabilities, indicating a privileged container configuration. Privileged pods can access host resources with elevated privileges, which attackers may use to increase impact from an initial foothold. It relies on Kubernetes audit log entries showing a pod create action with the matched capabilities field.
references:
- https://microsoft.github.io/Threat-Matrix-for-Kubernetes/techniques/Privileged%20container/
- https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_finding-types-kubernetes.html#privilegeescalation-kubernetes-privilegedcontainer
- https://www.elastic.co/guide/en/security/current/kubernetes-pod-created-with-hostnetwork.html
- https://www.elastic.co/guide/en/security/current/kubernetes-container-created-with-excessive-linux-capabilities.html
- https://github.com/SigmaHQ/sigma/blob/master/rules/application/kubernetes/audit/kubernetes_audit_privileged_pod_creation.yml
author: Leo Tsaousis (@laripping), Huntrule Team
date: 2024-03-26
tags:
- attack.t1611
- attack.privilege-escalation
logsource:
category: application
product: kubernetes
service: audit
detection:
selection:
verb: create
objectRef.resource: pods
capabilities: "*"
condition: selection
falsepositives:
- Unknown
level: low
license: DRL-1.1
related:
- id: c5cd1b20-36bb-488d-8c05-486be3d0cb97
type: derived