Get in Touch

Course Outline

Cluster Setup

  • Implement network security policies to restrict cluster-level access.
  • Utilise the CIS benchmark to review the security configuration of Kubernetes components (etcd, kubelet, kubedns, kubeapi).
  • Configure Ingress objects appropriately with security controls.
  • Safeguard node metadata and endpoints.
  • Limit the usage of, and access to, GUI elements.
  • Verify platform binaries prior to deployment.

Cluster Hardening

  • Limit access to the Kubernetes API.
  • Apply Role Based Access Controls to minimise exposure.
  • Exercise caution when using service accounts, for example by disabling defaults and minimising permissions on newly created accounts.
  • Ensure frequent updates to Kubernetes.

System Hardening

  • Reduce the host OS footprint to minimise the attack surface.
  • Limit IAM roles.
  • Minimise external network access.
  • Appropriately deploy kernel hardening tools such as AppArmor and seccomp.

Minimise Microservice Vulnerabilities

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

Supply Chain Security

  • Minimise the base image footprint.
  • Secure the supply chain by whitelisting allowed image registries, and signing and validating images.
  • Apply static analysis to user workloads (e.g., Kubernetes resources, Dockerfiles).
  • Scan images for known vulnerabilities.

Monitoring, Logging and Runtime Security

  • Conduct behavioural analytics of syscall processes and file activities at the host and container level to identify malicious activities.
  • Detect threats within physical infrastructure, applications, networks, data, users, and workloads.
  • Identify all phases of an attack, regardless of its origin or method of spread.
  • Carry out deep analytical investigations to identify and profile bad actors within the environment.
  • Ensure the immutability of containers at runtime.
  • Utilise audit logs to monitor access.

Requirements

  • CKA (Certified Kubernetes Administrator) certification

Audience

  • Kubernetes practitioners
 21 Hours

Number of participants


Price per participant

Testimonials (4)

Provisional Upcoming Courses (Require 5+ participants)

Related Categories