Insecure Kubernetes Workload Configurations

Insecure Kubernetes Workload Configurations

One privileged pod, and the whole node is open.

What Is Insecure Kubernetes Workload Configurations?

A pod that runs privileged with the node's filesystem mounted has no real isolation. You'll start with a shell in a compromised routing pod, read another team's database password off the node, then give the workload a restricted security context and enforce the restricted Pod Security profile on its namespace, so the cluster itself refuses the next privileged manifest. Maps to OWASP Kubernetes Top Ten K01, Insecure Workload Configurations.

What You'll Learn in Insecure Kubernetes Workload Configurations

Insecure Kubernetes Workload Configurations — Training Steps

  1. A pod that sees the node

    Bob already has a shell inside one of Kelvorra's route-optimizer pods, through a file-upload bug in the service. A shell in a container should be a small prize. He reads the workload's manifest, which the service ships in its own image, to see how small. Kelvorra runs freight routing for carriers. Several teams share each cluster node.

  2. Two settings that remove the walls

    A container is a process the kernel fences off. Two lines in this manifest take the fence down.

  3. Root, with every capability

    Bob checks who he is inside the container and what the kernel lets him do.

  4. Other teams' pods on the same node

    The kubelet keeps every pod's mounted volumes, Secrets included, under one directory on the node. Through the host mount, that directory is in Bob's reach.

  5. Read the billing database password

    Bob opens the billing team's mounted Secret. He never touched the billing service, its namespace or the Kubernetes API.

  6. Check your understanding

  7. A container reading the node

    Kelvorra's runtime detection flags a process inside a routing pod reading files under the kubelet's pod directory on the node.

  8. Open the workload

    Alice opens the route-optimizer manifest from the platform repository.

  9. Give the container a real security context

    Alice removes the host mount and privileged mode and replaces them with a restricted security context: a non-root user, no privilege escalation, a read-only root filesystem and every capability dropped.

  10. Read the restricted context

    The container now runs as an unprivileged user with nothing extra from the kernel.

Security Framework Coverage

OWASP Kubernetes Top 10

  • K01:2025 Insecure Workload Configurations

CWE

  • CWE-250 Execution with Unnecessary Privileges
  • CWE-269 Improper Privilege Management

MITRE ATT&CK

  • T1611 Escape to Host

CIS Controls

  • CIS 4 Secure Configuration of Enterprise Assets and Software

NIST CSF

  • PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
  • PR.PS Platform Security

NICE Framework

  • IO-WRL-005 Systems Administration
  • DD-WRL-001 Cybersecurity Architecture