Get in Touch

Course Outline

Introduction

Cluster Setup

  • Use network security policies to restrict cluster-level access.
  • Use CIS benchmarks to review the security configuration of Kubernetes components (etcd, kubelet, kube-dns, kube-apiserver).
  • Properly configure Ingress objects with 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.
  • Use Role-Based Access Control (RBAC) to minimize exposure.
  • Exercise caution when using service accounts: for example, disable defaults and minimize permissions on newly created ones.
  • Update Kubernetes frequently.

System Hardening

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

Minimize Microservice Vulnerabilities

  • Set up appropriate OS-level security domains, for example, using PSP, OPA, and 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 the base image footprint.
  • Secure your supply chain: whitelist allowed image registries, and 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 level 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.
  • Perform deep analytical investigation and identification of bad actors within the environment.
  • Ensure container immutability at runtime.
  • Use Audit Logs to monitor access.

Summary and Conclusion

Requirements

  • CKA (Certified Kubernetes Administrator) certification

Audience

  • Kubernetes practitioners
 21 Hours

Testimonials (3)

Related Categories