Detections
Analytics

5.5.6 Ensure Integrity Monitoring for Shielded GKE Nodes is Enabled

Warning! Audit Deprecated

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

View Next Audit Version

Information

Enable Integrity Monitoring for Shielded GKE Nodes to be notified of inconsistencies during the node boot sequence.

Integrity Monitoring provides active alerting for Shielded GKE nodes which allows administrators to respond to integrity failures and prevent compromised nodes from being deployed into the cluster.

Solution

Once a Node pool is provisioned, it cannot be updated to enable Integrity Monitoring. New Node pools must be created within the cluster with Integrity Monitoring enabled.

Using Google Cloud Console

 - Go to Kubernetes Engine by visiting: https://console.cloud.google.com/kubernetes/list
 - From the list of clusters, click on the cluster requiring the update and click ADD NODE POOL.
 - Ensure that the 'Integrity monitoring' checkbox is checked under the 'Shielded options' Heading.
 - Click SAVE.

Workloads from existing non-conforming Node pools will need to be migrated to the newly created Node pool, then delete non-conforming Node pools to complete the remediation

Using Command Line

To create a Node pool within the cluster with Integrity Monitoring enabled, run the following command:

gcloud container node-pools create <node_pool_name> --cluster <cluster_name> --location <location> --shielded-integrity-monitoring

Workloads from existing non-conforming Node pools will need to be migrated to the newly created Node pool, then delete non-conforming Node pools to complete the remediation

Impact:

None.

See Also

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

Item Details

Category: RISK ASSESSMENT

References: 800-53|RA-5, CSCv7|5.3

Plugin: GCP

Control ID: c04558c828e01c78d3323da55f08606608c7f9d5a916f5efd9098100b367a35e