Get in Touch

Course Outline

Cluster Setup

  • Implement network security policies to limit cluster-level access.
  • Leverage the CIS benchmark to audit the security configurations of Kubernetes components (etcd, kubelet, kubedns, kubeapi).
  • Configure Ingress objects with appropriate security controls.
  • Secure node metadata and endpoints.
  • Limit the use of and access to GUI elements.
  • Validate platform binaries prior to deployment.

Cluster Hardening

  • Restrict access to the Kubernetes API.
  • Apply Role-Based Access Controls (RBAC) to minimize exposure.
  • Exercise caution with service accounts by disabling defaults and minimizing permissions on new ones.
  • Ensure Kubernetes is updated regularly.

System Hardening

  • Reduce the host OS footprint to decrease the attack surface.
  • Minimize IAM roles.
  • Limit external network access.
  • Utilize kernel hardening tools such as AppArmor and seccomp appropriately.

Minimizing Microservice Vulnerabilities

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

Supply Chain Security

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

Monitoring, Logging, and Runtime Security

  • Conduct behavioral analytics on syscall processes and file activities at the host and container levels to detect malicious actions.
  • Identify threats across physical infrastructure, applications, networks, data, users, and workloads.
  • Detect all phases of attacks regardless of their origin or spread.
  • Perform deep analytical investigations to identify bad actors within the environment.
  • Guarantee container immutability at runtime.
  • Utilize Audit Logs to monitor access patterns.

Requirements

  • CKA (Certified Kubernetes Administrator) certification

Target Audience

  • Kubernetes practitioners
 21 Hours

Number of participants


Price per participant

Testimonials (4)

Upcoming Courses

Related Categories