Lock Down Container Syscalls With Seccomp Profiles
Run a Deployment under the container runtime's seccomp profile, roll out a custom profile to the worker nodes, and fix a profile that blocks a syscall the application needs.
Focused, hands-on DevOps and server-side problems with hints, feedback, and automated solution checks.
Run a Deployment under the container runtime's seccomp profile, roll out a custom profile to the worker nodes, and fix a profile that blocks a syscall the application needs.
The platform team is rolling out Pod Security Admission. A monitoring agent is already blocked, the storefront team needs a staged rollout, and payments must move to the strictest level without losing its running service.
Harden a container by implementing a read-only root filesystem with specific writable volumes for nginx. This is a critical security practice to prevent runtime modifications.
The security team has identified that a deployment needs hardening with proper security context settings. Apply security best practices including user ID, privilege escalation control, and Linux capabilities.