CRITICALCIS 1.11

Ensure KMS cryptokeys are not anonymously accessible

Cloud KMS keys should not grant access to allUsers or allAuthenticatedUsers.

Security Impact

Publicly accessible keys can be used by anyone to encrypt/decrypt data.

How to Remediate

Remove allUsers and allAuthenticatedUsers from KMS key IAM policies.

Affected Resources

cloudkms.googleapis.com/CryptoKey

Compliance Frameworks

CIS GCP v1.3.0SOC 2PCI-DSSHIPAA

How TigerGate Helps

TigerGate continuously monitors your GCP environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Google Cloud KMS resources across your GCP projects every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for CIS GCP v1.3.0, SOC 2, PCI-DSS compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
gcp-kms-1
Service
Google Cloud KMS
Category
Access Control
Severity
CRITICAL
CIS Benchmark
1.11

Automate This Check

TigerGate automatically scans your GCP environment for this and 79+ other security checks.

Start Free Trial