cis-aks-v180-3-2-7

name	cis-aks-v180-3.2.7
description	Ensure that the --eventRecordQPS argument is set to 0 or a level which ensures appropriate event capture (Automated)
category	cis-aks
version	1.8.0
author	cyberstrike-official
tags	["cis","aks","kubernetes","azure","kubelet","event-recording","logging"]
cis_id	3.2.7
cis_benchmark	CIS Azure Kubernetes Service (AKS) Benchmark v1.8.0
tech_stack	["kubernetes","azure","aks"]
cwe_ids	[]
chains_with	[]
prerequisites	[]
severity_boost	{}

3.2.7 Ensure that the --eventRecordQPS argument is set to 0 or a level which ensures appropriate event capture (Automated)

Profile Applicability

• Level 2

Description

Security relevant information should be captured. The --eventRecordQPS 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 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:

First, SSH to each node.

Run the following command on each node to find the Kubelet process:

ps -ef | grep kubelet

In the output of the above command review the value set for the --eventRecordQPS argument and determine whether this has been set to an appropriate level for the cluster. The value of 0 can be used to ensure that all events are captured.

If the --eventRecordQPS argument does not exist, check that there is a Kubelet config file specified by --config and review the value in this location. The output of the above command should return something similar to --config /etc/kubernetes/kubelet/kubelet-config.json which is the location of the Kubelet config file.

Open the Kubelet config file:

cat /etc/kubernetes/kubelet/kubelet-config.json

If there is an entry for eventRecordQPS check that it is set to 0 or an appropriate level for the cluster.

Audit Method 2:

If using the api configz endpoint consider searching for the status of eventRecordQPS 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