Detections
Analytics

4.1.5 Ensure that Service Account Tokens are only mounted where necessary

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Service accounts tokens should not be mounted in pods except where the workload running in the pod explicitly needs to communicate with the API server

Mounting service account tokens inside pods can provide an avenue for privilege escalation attacks where an attacker is able to compromise a single pod in the cluster.

Avoiding mounting these tokens removes this attack avenue.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Modify the definition of pods and service accounts which do not need to mount service account tokens to disable it.

Impact:

Pods mounted without service account tokens will not be able to communicate with the API server, except where the resource is available to unauthenticated principals.

See Also

https://workbench.cisecurity.org/benchmarks/24112

Item Details

Category: CONFIGURATION MANAGEMENT

References: 800-53|CM-6, 800-53|CM-7, CSCv7|14.7

Plugin: GCP

Control ID: d3e54f692b095fb16f2de513b4430ff6cddc50f63f6a278d6db730bbf375953c