kubernetes hardening podsecurity exploit

DevOps Community

Skill notes

Overview

Pod Security Standards (PSS) define three levels of security policies -- Privileged, Baseline, and Restricted -- enforced by the Pod Security Admission (PSA) controller built into Kubernetes 1.25+. PSA replaces the deprecated PodSecurityPolicy and provides namespace-level enforcement with three modes: enforce, audit, and warn.

When to Use

When deploying or configuring implementing kubernetes pod security standards capabilities in your environment When establishing security controls aligned to compliance requirements When building or improving security architecture for this domain When conducting security assessments that require this implementation

Prerequisites

Kubernetes cluster 1.25+ (PSA GA) kubectl configured with cluster-admin access Understanding of Linux capabilities and security contexts

Three Security Profiles

Profile · Purpose · Restrictions Privileged · Unrestricted, system workloads · None Baseline · Prevents known escalations · No hostNetwork, hostPID, hostIPC, privileged containers, dangerous capabilities Restricted · Hardened best practices · Non-root, drop ALL caps, seccomp required, read-only rootfs recommended

Three Enforcement Modes

Mode · Behavior enforce · Rejects pods that violate the policy audit · Logs violations in audit log but allows pod warn · Returns warning to user but allows pod

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Label Namespaces for PSA

Step 1: Label Namespaces for PSA

02
Step 2: Apply Labels to Existing Namespaces

Step 2: Apply Labels to Existing Namespaces

03
Step 3: Create Compliant Pod Specs

Step 3: Create Compliant Pod Specs

04
Step 4: Gradual Migration Strategy

Step 4: Gradual Migration Strategy

05
Step 5: Dry-Run Enforcement Testing

Step 5: Dry-Run Enforcement Testing

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.