Get in Touch

Course Outline

Introduction

Cluster Setup

  • Utilize network security policies to restrict cluster-level access.
  • Apply CIS benchmarks to review the security configuration of Kubernetes components (etcd, kubelet, kubedns, kubeapi).
  • Properly configure Ingress objects with appropriate security controls.
  • Protect node metadata and endpoints.
  • Minimize the use of and access to GUI elements.
  • Verify platform binaries before deployment.

Cluster Hardening

  • Restrict access to the Kubernetes API.
  • Implement Role-Based Access Controls to minimize exposure.
  • Exercise caution when using service accounts, e.g., disable defaults, minimize permissions on newly created ones.
  • Regularly update Kubernetes.

System Hardening

  • Minimize the host OS footprint (reduce attack surface).
  • Minimize IAM roles.
  • Minimize external access to the network.
  • Appropriately utilize kernel hardening tools such as AppArmor, seccomp.

Minimize Microservice Vulnerabilities

  • Set up appropriate OS-level security domains, e.g., using PSP, OPA, security contexts.
  • Manage Kubernetes secrets.
  • Use container runtime sandboxes in multi-tenant environments (e.g., gvisor, kata containers).
  • Implement pod-to-pod encryption using mTLS.

Supply Chain Security

  • Minimize base image footprint.
  • Secure your supply chain: whitelist allowed image registries, sign and validate images.
  • Use static analysis of user workloads (e.g., Kubernetes resources, Dockerfiles).
  • Scan images for known vulnerabilities.

Monitoring, Logging, and Runtime Security

  • Perform behavioral analytics of syscall processes and file activities at the host and container levels to detect malicious activities.
  • Detect threats within physical infrastructure, applications, networks, data, users, and workloads.
  • Detect all phases of an attack regardless of where it occurs and how it spreads.
  • Conduct deep analytical investigation and identification of bad actors within the environment.
  • Ensure immutability of containers at runtime.
  • Use Audit Logs to monitor access.

Summary and Conclusion

Requirements

  • CKA (Certified Kubernetes Administrator) certification

Audience

  • Kubernetes practitioners
 21 Hours

Number of participants


Price per participant

Testimonials (3)

Upcoming Courses

Related Categories