Ensure KMS keys are in supported regions
KMS keys should be created in regions that meet compliance requirements.
Security Impact
Keys in non-compliant regions may violate data residency requirements.
How to Remediate
Create KMS keys in approved regions. Key rings cannot be moved after creation.
Affected Resources
Compliance Frameworks
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 GDPR, HIPAA, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- gcp-kms-4
- Service
- Google Cloud KMS
- Category
- Compliance
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your GCP environment for this and 79+ other security checks.
Start Free TrialRelated Google Cloud KMS Checks
View all checksEnsure KMS cryptokeys are not anonymously accessible
Ensure KMS key rotation is enabled
Ensure separation of duties for KMS admin and key user roles
Ensure KMS key destruction is protected
Ensure HSM protection is used for sensitive keys