Kubernetes STIG Version Comparison
Kubernetes Security Technical Implementation Guide
There are 93 differences between versions v1 r0.1 (Dec. 1, 2020) (the "left" version) and v1 r2 (July 23, 2021) (the "right" version).
Check CNTR-K8-000280 was removed from the benchmark in the "right" version. The text below reflects the old wording.
This check's original form is available here.
The Kubernetes API Server must enable Role-Based Access (RBAC) as the authorization mode.
Change to the /etc/kubernetes/manifests directory on the Kubernetes Master Node. Run the command: grep -i --authorization-mode * If the setting authorization-mode is not set in the Kubernetes API Server manifest file or is not set to “RBAC”, this is a finding.
To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., networks, web servers, and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. RBAC is the method within Kubernetes to control access of users and applications. Kubernetes uses roles to grant authorization to resources. RBAC is the default configuration for Kubernetes.
Edit the Kubernetes API Server manifest file in the /etc/kubernetes/manifests directory on the Kubernetes Master Node. Set the value of “--authorization-mode” to “RBAC”.