Ensure That Cloud KMS Cryptokeys Are Not Anonymously or Publicly Accessible

HighLevel 1Manual reviewgcp

Description

It is recommended that the IAM policy on Cloud KMS cryptokeys should restrict anonymous and/or public access. Granting permissions to allUsers or allAuthenticatedUsers allows anyone to access the dataset. Such access might not be desirable if sensitive data is stored at the location. In this case, ensure that anonymous and/or public access to a Cloud KMS cryptokey is not allowed.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

From Google Cloud CLI 1. List all Cloud KMS Cryptokeys. gcloud kms keys list --keyring=[key_ring_name] --location=global -- format=json | jq '.[].name' 2. Ensure the below command's output does not contain allUsers or allAuthenticatedUsers. gcloud kms keys get-iam-policy [key_name] --keyring=[key_ring_name] -- location=global --format=json | jq '.bindings[].members[]'

How it is fixed

Fix method: Guidance or infrastructure patch

From Google Cloud CLI 1. List all Cloud KMS Cryptokeys. gcloud kms keys list --keyring=[key_ring_name] --location=global -- format=json | jq '.[].name' 2. Remove IAM policy binding for a KMS key to remove access to allUsers and allAuthenticatedUsers using the below command. gcloud kms keys remove-iam-policy-binding [key_name] -- keyring=[key_ring_name] --location=global --member='allAuthenticatedUsers' -- role='[role]' gcloud kms keys remove-iam-policy-binding [key_name] -- keyring=[key_ring_name] --location=global --member='allUsers' --role='[role]'

Properties

Operating systems: Any
Tags: access-controlcloudcryptogcp
Reference: CIS Google Cloud Platform Foundation Benchmark v5.0.0 - 1.10 Ensure That Cloud KMS Cryptokeys Are Not Anonymously or Publicly Accessible