CyberKit

Privileged Container

A container run with host-level capabilities that erase most isolation.

What it is

A container launched with elevated privileges and broad host capabilities, effectively granting it the access of the host rather than a constrained sandbox, removing most of the boundaries that normally separate a container from its host.

Why it matters

Privileged containers are a leading container-escape enabler, so finding one is both a serious misconfiguration to remediate and a likely escalation path to examine during an incident.

In practice

A responder notes a debugging container left running in privileged mode, the exact route the intruder used to reach the host filesystem.

What to look for

  • Pod specs with privileged true or added capabilities like SYS_ADMIN.
  • Host network, host PID or host path mounts.
  • Workloads that do not need any of that but have it anyway.

Common mistake

Granting privilege to fix a permissions error. It usually works, and it removes almost all isolation.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Trivy Open source

    Scans images, file systems and code for known vulnerabilities and secrets.

  • Falco Open source

    Detects suspicious behavior inside running containers and Kubernetes.

  • Sigstore Open source

    Signs and verifies software artifacts so you can prove where a build came from.

  • CrowdStrike Falcon Cloud Security Commercial

    Protects cloud workloads and containers, from build to runtime.

Read next

  • Container Escape: Breaking out of a container's isolation to reach the host or other workloads.
  • Pod Security: Constraints that limit the privileges and host access a pod may request.

Sources