services / Azure / Kubernetes PodSecurityPolicies

PodSecurityPolicies are cluster-scoped Kubernetes admission-control objects that constrain which pod security attributes (privileged mode, host namespaces, hostPath volumes, capabilities, runAsRoot) are permitted when workloads are admitted to the cluster.

These are cluster-wide security-enforcement guardrails; weakening or bypassing them enables container breakout to node and cluster-admin level compromise.

Microsoft.​ContainerService/​aiManagers/​policy/​podsecuritypolicies/​use/​action

The 'use' verb authorizes a subject to run pods governed by that PodSecurityPolicy; on a permissive policy this lets an attacker schedule privileged/host-access pods, enabling node breakout and privilege escalation.

Risks

1. Privilege escalation (CRITICAL)

Scope: CRITICAL

This privilege may grant access to sensitive data from a significant fraction of organizational functions, allow interruption of critical organizational services, or its exploit could lead to significant privilege escalation.

Links