kubernetes pentest kubernetes analyze

DevOps Community

Skill notes

Overview

Kubernetes penetration testing systematically evaluates cluster security by simulating attacker techniques against the API server, kubelet, etcd, pods, RBAC, network policies, and secrets. Using tools like kube-hunter, Kubescape, peirates, and manual kubectl exploitation, testers identify misconfigurations that could lead to cluster compromise.

When to Use

When conducting security assessments that involve performing kubernetes penetration testing When following incident response procedures for related security events When performing scheduled security testing or auditing activities When validating security controls through hands-on testing

Prerequisites

Authorized penetration testing engagement Kubernetes cluster access (various levels for different test scenarios) kube-hunter, kubescape, kube-bench installed kubectl configured Network access to cluster components

Kubernetes Attack Surface

Component · Port · Attack Vectors API Server · 6443 · Auth bypass, RBAC abuse, anonymous access Kubelet · 10250/10255 · Unauthenticated access, command execution etcd · 2379/2380 · Unauthenticated read, secret extraction Dashboard · 8443 · Default credentials, token theft

MITRE ATT&CK for Kubernetes

Phase · Techniques Initial Access · Exposed Dashboard, Kubeconfig theft, Application exploit Execution · exec into container, CronJob, deploy privileged pod Persistence · Backdoor container, mutating webhook, static pod Privilege Escalation · Privileged container, node access, RBAC abuse

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
Guided setup
External API key
Not required
Operating systems
Linux
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

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

01
Step 1: External Reconnaissance

Step 1: External Reconnaissance

02
Step 2: Automated Scanning with kube-hunter

Step 2: Automated Scanning with kube-hunter

03
Step 3: CIS Benchmark Assessment with kube-bench

Step 3: CIS Benchmark Assessment with kube-bench

04
Step 4: Framework Compliance with Kubescape

Step 4: Framework Compliance with Kubescape

05
Step 5: RBAC Exploitation Testing

Step 5: RBAC Exploitation Testing

06
Step 6: Secret Extraction Testing

Step 6: Secret Extraction Testing

07
Step 7: Pod Exploitation

Step 7: Pod Exploitation

08
Step 8: Network Policy Testing

Step 8: Network Policy Testing

Discussion

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