Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
kms_cmk_not_multi_regionProvider: AWS
Service:
kmsSeverity: MEDIUM
Categories:
encryptionResource type:
AwsKmsKeyWhat this check verifies
AWS KMS customer-managed keys in anEnabled state are assessed for the multi-Region setting. The finding highlights keys with the multi-Region property enabled.
Risk
Shared key material across Regions lets access in one Region decrypt data from another, eroding confidentiality and data residency. A misconfigured policy or weaker controls in a replica expand the blast radius. For signing/HMAC keys, compromise enables cross-Region signature forgery, impacting integrity and auditability.Recommendation
Prefer single-Region keys by default; use multi-Region only with a documented need. Apply least privilege and separation of duties; limit who can create or replicate such keys. Isolate per Region/tenant/workload, standardize policy and logging across Regions, and retire multi-Region keys where unnecessary.Remediation
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html#multi-region-concepts
- https://docs.aws.amazon.com/kms/latest/developerguide/mrk-when-to-use.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = kms_cmk_not_multi_region. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks