cis-oke-v170-3-2-7

name	cis-oke-v170-3.2.7
description	Ensure that the --event-qps argument is set to 0 or a level which ensures appropriate event capture (Automated)
category	cis-oke
version	1.7.0
author	cyberstrike-official
tags	["cis","oke","kubernetes","oci","worker-node","kubelet"]
cis_id	3.2.7
cis_benchmark	CIS Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) Benchmark v1.7.0
tech_stack	["kubernetes","oci","oke"]
cwe_ids	[]
chains_with	[]
prerequisites	[]
severity_boost	{}

CIS OKE Benchmark v1.7.0 - Control 3.2.7

Profile Applicability

• Level: 1

Description

Security relevant information should be captured. The --event-qps flag on the Kubelet can be used to limit the rate at which events are gathered. Setting this too low could result in relevant events not being logged, however the unlimited setting of 0 could result in a denial of service on the kubelet.

Rationale

It is important to capture all events and not restrict event creation. Events are an important source of security information and analytics that ensure that your environment is consistently monitored using the event data.

Impact

Setting this parameter to 0 could result in a denial of service condition due to excessive events being created. The cluster's event processing and storage systems should be scaled to handle expected event loads.

Audit Procedure

Audit Method 1

If using a Kubelet configuration file, check that there is an entry for --event-qps set to 0 or a value equal to or greater than 0.

First, SSH to the relevant node.

Run the following command on each node to find the appropriate Kubelet config file:

find / -name kubelet.service

The output of the above command should return the file and location /etc/systemd/system/kublet.service which is the location of the Kubelet service config file.

Open the Kubelet service config file:

sudo more etc/systemd/system/kubelet.service

Verify that the --event-qps=0.

Audit Method 2

If using the api configz endpoint consider searching for the status of "eventRecordQPS": 0 by extracting the live configuration from the nodes running kubelet.

Set the local proxy port and the following variables and provide proxy port number and node name;

HOSTNAME_PORT="localhost-and-port-number"
NODE_NAME="The-Name-Of-Node-To-Extract-Configuration" # from the output of "kubectl get nodes"

kubectl proxy --port=8001 &

export HOSTNAME_PORT=localhost:8001 (example host and port number)
export NODE_NAME=10.0.10.4 (example node name from )

curl -sSL