cis-oke-v150-3-1-2

name	cis-oke-v150-3.1.2
description	Ensure that the proxy oke_kubelet_conf.json file ownership is set to root:root (Automated)
category	cis-oke
version	1.5.0
author	cyberstrike-official
tags	["cis","oke","kubernetes","oci","worker-node","configuration-files","permissions"]
cis_id	3.1.2
cis_benchmark	CIS Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) Benchmark v1.5.0
tech_stack	["kubernetes","oci","oke"]
cwe_ids	[]
chains_with	[]
prerequisites	[]
severity_boost	{}

3.1.2 Ensure that the proxy oke_kubelet_conf.json file ownership is set to root:root (Automated)

Profile Applicability

• Level 1

Description

If kubelet is running, ensure that the file ownership of its oke_kubelet_conf.json file is set to root:root.

Rationale

The oke_kubelet_conf.json file for kubelet controls various parameters for the kubelet service in the worker node. You should set its file ownership to maintain the integrity of the file. The file should be owned by root:root.

Impact

None

Audit Procedure

Method 1 SSH to the worker nodes To check to see if the Kubelet Service is running:

sudo systemctl status kubelet

The output should return Active: active (running) since... Run the following command on each node to find the appropriate oke_kubelet_conf.json file:

ps -ef | grep kubelet

The output of the above command should return something similar to --kubeconfig /var/lib/kubelet/oke_kubelet_conf.json which is the location of the oke_kubelet_conf.json file. Run this command to obtain the oke_kubelet_conf.json file ownership:

stat -c %U:%G /var/lib/kubelet/oke_kubelet_conf.json

The output of the above command gives you the oke_kubelet_conf.json file's ownership. Verify that the ownership is set to root:root.

Method 2 Create and Run a Privileged Pod. You will need to run a pod that is privileged enough to access the host's file system. This can be achieved by deploying a pod that uses the hostPath volume to mount the node's file system into the pod. Here's an example of a simple pod definition that mounts the root of the host to /host within the pod:

apiVersion: v1
kind: Pod
metadata:
  name: file-check
spec:
  volumes:
    - name: host-root
      
         
         
  
      
       
       [, ]