Back to all scenarios
Scenario #270
Security
Kubernetes v1.23, AWS EKS

Absence of Pod Security Policies

Without Pod Security Policies, pods were deployed with insecure configurations, increasing the attack surface.

Find this helpful?
What Happened

Pods were deployed without restrictions, allowing configurations such as running as root, using host networking, and mounting sensitive host paths, which posed security risks.

Diagnosis Steps
  • 1Reviewed pod specifications for security configurations.
  • 2Identified insecure settings in multiple deployments.
  • 3Assessed the potential impact of these configurations.
Root Cause

Lack of enforced Pod Security Policies to govern pod configurations.

Fix/Workaround
• Implemented Pod Security Policies to enforce security standards.
• Restricted the use of privileged containers and host resources.
• Educated development teams on secure pod configurations.
Lessons Learned

Enforcing Pod Security Policies helps maintain a secure and compliant cluster environment.

How to Avoid
  • 1Define and enforce Pod Security Policies.
  • 2Regularly review pod configurations for adherence to security standards.
Previous ScenarioNext Scenario