Certified Kubernetes Security Specialist (CKS) - Practice Exam Part 7

30 minutes
  • 2 Learning Objectives

About this Hands-on Lab

This lab provides practice scenarios to help prepare you for the Certified Kubernetes Security Specialist (CKS) exam. You will be presented with tasks to complete, as well as server(s) and/or an existing Kubernetes cluster to complete them in. You will need to use your knowledge of Kubernetes to successfully complete the provided tasks, much like you would on the real CKS exam. Good luck!

Learning Objectives

Successfully complete this lab by achieving the following learning objectives:

Create a Falco Rules File

There is a Pod on the worker node called monitor in the default namespace. Its only container is also called monitor.

  1. On the worker node, create a Falco rules file at /home/cloud_user/monitor_rules.yml.

  2. Configure a rule to detect spawning processes within the container. The output should be in the format [timestamp],[container id],[container image name],[uid],[process name]. (The priority should be NOTICE; no [ ] are needed in the output).

Log Activity from a Suspicious Container
  1. Run Falco for 45 seconds or so to check for activity in the container.
  2. Save the output to a file located at /home/cloud_user/falco_output.log on the worker node.

Additional Resources

Use the provided environment to complete the tasks detailed in the learning objectives.

You can access all components of the cluster from the CLI server. The control plane server is k8s-control, and the worker is k8s-worker1. If you need to log in to the control plane server, for example, just use ssh k8s-control from the CLI server.

You can also use kubectl from the CLI server, control plane node, or worker to interact with the cluster. In order to use kubectl from the CLI server, you will need to select the acgk8s cluster to interact with, like so: kubectl config use-context acgk8s.

kubectl is aliased to k, and kubernetes autocompletion is enabled. You can use the k alias like so: k get pods.

Extra Falco Rules Information: Here are some examples of the main types of behavior falco can detect: https://falco.org/docs/examples/

Falco provides a more comprehensive list in the falco_rules.yaml file. You can view the falco_rules.yaml contents at: https://github.com/falcosecurity/rules/blob/main/rules/falco_rules.yaml

What are Hands-on Labs

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Sign In
Welcome Back!

Psst…this one if you’ve been moved to ACG!

Get Started
Who’s going to be learning?