The Kubernetes API Server must enable Node,RBAC as the authorization mode. (Cat II impact)
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. Node,RBAC is the method within Kubernetes to control access of users and applications. Kubernetes uses roles to grant authorization API requests made by kubelets. Satisfies: SRG-APP-000033-CTR-000090, SRG-APP-000033-CTR-000095
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 configured in the Kubernetes API Server manifest file or is not set to "Node,RBAC", this is a finding.
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 "Node,RBAC".
The information system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies.