MKE must enable kernel protection.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-260933 | CNTR-MK-000990 | SV-260933r966156_rule | CCI-001084 | medium |
| Description | ||||
| System kernel is responsible for memory, disk, and task management. The kernel provides a gateway between the system hardware and software. Kubernetes requires kernel access to allocate resources to the Control Plane. Threat actors that penetrate the system kernel can inject malicious code or hijack the Kubernetes architecture. It is vital to implement protections through Kubernetes components to reduce the attack surface. | ||||
| STIG | Date | |||
| Mirantis Kubernetes Engine Security Technical Implementation Guide | 2024-08-27 | |||
Details
Check Text (C-260933r966156_chk)
Verify kernel protection.
When using Kubernetes orchestration, change to the /etc/sysconfig/ directory on the Kubernetes Control Plane using the command:
grep -i protect-kernel-defaults kubelet
If the setting "protect-kernel-defaults" is set to false or not set in the Kubernetes Kubelet, this is a finding.
When using Swarm orchestration:
Linux: Execute the following command as a trusted user on the host operating system:
docker ps --quiet --all | xargs docker inspect --format '{{ .Name }}: CapAdd={{ .HostConfig.CapAdd }} CapDrop={{ .HostConfig.CapDrop }}'
The command will output all Linux Kernel Capabilities.
If Linux Kernel Capabilities exceed what is defined in the System Security Plan (SSP), this is a finding.
Fix Text (F-64570r966155_fix)
When using Kubernetes orchestration, edit the Kubernetes Kubelet file in the /etc/sysconfig directory on the Kubernetes Control Plane. Set the argument "--protect-kernel-defaults" to "true".
Reset Kubelet service using the following command:
service kubelet restart
When using Swarm orchestration, review and remove nonsystem containers previously created by these users that allowed capabilities to be added or must be removed using:
docker container rm [container]