Get in Touch

Course Outline

Cluster Setup

  • Implement Network security policies to limit cluster-level access
  • Leverage CIS benchmarks to audit the security configuration of Kubernetes components (etcd, kubelet, kubedns, kubeapi)
  • Configure Ingress objects with appropriate security controls
  • Safeguard node metadata and endpoints
  • Reduce the use of and access to GUI elements
  • Validate platform binaries prior to deployment

Cluster Hardening

  • Limit access to the Kubernetes API
  • Utilize Role-Based Access Controls (RBAC) to minimize exposure
  • Manage service accounts carefully, such as disabling defaults and restricting permissions on new accounts
  • Maintain frequent Kubernetes updates

System Hardening

  • Reduce the host OS footprint to lower the attack surface
  • Streamline IAM roles
  • Limit external network access
  • Apply kernel hardening tools like AppArmor and seccomp appropriately

Minimizing Microservice Vulnerabilities

  • Establish appropriate OS-level security domains using tools like PSP, OPA, or security contexts
  • Manage Kubernetes secrets effectively
  • Employ container runtime sandboxes in multi-tenant settings (e.g., gvisor, kata containers)
  • Enforce pod-to-pod encryption via mTLS

Supply Chain Security

  • Keep base image footprints minimal
  • Protect the supply chain by whitelisting approved image registries and signing/validating images
  • Apply static analysis to user workloads (e.g., Kubernetes resources, Dockerfiles)
  • Scan images for identified vulnerabilities

Monitoring, Logging, and Runtime Security

  • Conduct behavioral analytics of syscall processes and file activities at host and container levels to identify malicious actions
  • Identify threats across physical infrastructure, applications, networks, data, users, and workloads
  • Detect every phase of an attack, regardless of its origin or propagation method
  • Carry out deep analytical investigations to identify malicious actors within the environment
  • Maintain container immutability during runtime
  • Use Audit Logs to track access activities

Requirements

  • CKA (Certified Kubernetes Administrator) certification

Target Audience

  • Kubernetes practitioners
 21 Hours

Number of participants


Price per participant

Testimonials (3)

Upcoming Courses

Related Categories