<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CIS Benchmark :: Tag :: Kubernetes training</title><link>https://k8s-school.fr/labs/k8s/en/tags/cis-benchmark/index.html</link><description/><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2025 Fabrice Jammes - Licensed under CC BY-SA 4.0</copyright><lastBuildDate>Fri, 09 Jan 2026 10:00:00 +1000</lastBuildDate><atom:link href="https://k8s-school.fr/labs/k8s/en/tags/cis-benchmark/index.xml" rel="self" type="application/rss+xml"/><item><title>Hardening with CIS Benchmarks - Running kube-bench Jobs</title><link>https://k8s-school.fr/labs/k8s/en/1_labs/kubebench-10-jobs/index.html</link><pubDate>Fri, 09 Jan 2026 10:00:00 +1000</pubDate><guid>https://k8s-school.fr/labs/k8s/en/1_labs/kubebench-10-jobs/index.html</guid><description>Introduction to CIS Benchmarks The Center for Internet Security (CIS) provides best practices for securing Kubernetes. In this lab, we will use kube-bench, an open-source tool from Aqua Security, to check whether our cluster meets these security recommendations.
Running kube-bench as a Job In a CKS exam or production environment, you often run kube-bench as a Kubernetes Job to scan nodes without SSH access.</description></item><item><title>Hardening with CIS Benchmarks - Security Remediations</title><link>https://k8s-school.fr/labs/k8s/en/1_labs/kubebench-20-remediations/index.html</link><pubDate>Fri, 09 Jan 2026 10:00:00 +1000</pubDate><guid>https://k8s-school.fr/labs/k8s/en/1_labs/kubebench-20-remediations/index.html</guid><description>Practical CKS Exercise Workflow As a CKS candidate, you should practice the complete security hardening workflow manually. This section guides you through the key exercises step by step to remediate security issues found by kube-bench.
Remove the --profiling argument for the scheduler Look for the check 1.4.1: Ensure that the –profiling argument is set to false.</description></item><item><title>Hardening with CIS Benchmarks - Automation and Continuous Compliance</title><link>https://k8s-school.fr/labs/k8s/en/1_labs/kubebench-30-automation/index.html</link><pubDate>Fri, 09 Jan 2026 10:00:00 +1000</pubDate><guid>https://k8s-school.fr/labs/k8s/en/1_labs/kubebench-30-automation/index.html</guid><description>Automation and Continuous Compliance Why is running kube-bench manually not enough for a production environment?
Answers Configuration Drift: A manual change or update could revert security settings. New Benchmarks: CIS updates its recommendations regularly. Visibility: Security teams need centralized reporting, not just CLI logs. Suggested improvement Integrate kube-bench into a CronJob to run every week and send results to a security dashboard like Falco or a SIEM.</description></item></channel></rss>