A platform team is giving a new team its own namespace in a shared cluster and must keep it isolated.
The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.
Fintech: Locking down a shared cluster. Developers could read each other's secrets in a shared cluster. RBAC per team, Pod Security Admission, encrypted secrets and network policies between namespaces. Each team sees only its own resources and a pen test found no cross-team access.
Healthcare: Only trusted images in production. An image with a known critical vulnerability reached production. Images are scanned and signed in CI, and an admission policy blocks anything unsigned or vulnerable. Unsigned and vulnerable images can no longer run in production.
SaaS: Catching an attack in progress. A compromised pod started mining cryptocurrency and nobody noticed for days. Falco runtime rules and audit logs raise alerts within seconds, with a playbook to isolate and rebuild. A similar attack in a later drill was detected and contained in minutes.
Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.
About 10 hours of hands-on work, and it fits best after week 6 of the KCSA (Kubernetes and Cloud Native Security Associate) course.
Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.