What problem does it solve?
Reduce the attack surface of containerized applications by eliminating unsafe image practices, preventing containers from running as root, and enforcing cluster-level controls to stop privilege escalation and lateral movement.
Core Features & Use Cases
- Docker image hardening: guidance on multi-stage builds, minimal base images, removing secrets from layers, and running as non-root.
- Kubernetes security contexts: examples to enforce runAsNonRoot, drop capabilities, read-only root filesystems, fsGroup, and seccomp profiles.
- Network policy & admission controls: design of pod-level NetworkPolicy rules and OPA/Gatekeeper policy suggestions to restrict ingress/egress and enforce organizational policies.
- Scanning and validation: recommended use of Trivy for image, manifest, and cluster scanning to detect HIGH/CRITICAL issues.
- Use Case: Harden a microservice image in CI, ensure the deployment manifest enforces non-root execution and seccomp, and apply NetworkPolicies limiting traffic to only ingress controllers and database pods.
Quick Start
Scan the jarvis-fresh image and the k8s manifests for HIGH/CRITICAL findings, ensure the container runs as a non-root user with dropped capabilities and a read-only root filesystem, and add a NetworkPolicy that only allows ingress from the ingress-nginx pods and egress to the postgres pod and DNS.