KMS Key Rotation Not Enabled

Automatic rotation is not enabled for customer managed KMS keys, so the same key material is used indefinitely, contrary to common key management policies.

SeverityInformational
CVSS 3.10 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N Open in the calculator
CVSS 4.00 CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-324: Use of a Key Past its Expiration Date
OWASP Top 10A04:2025 Cryptographic Failures
CategoryCryptographic Failures

Description

AWS KMS can rotate the key material of customer managed symmetric encryption keys automatically. When rotation is enabled, KMS creates new key material on a schedule, every 365 days by default and configurable between 90 and 2,560 days, and uses it for new encryption, while keeping earlier material so that existing data can still be decrypted. The key's ID, ARN and policy do not change, so applications are unaffected. On-demand rotation is also available. AWS managed keys are rotated automatically every year and cannot be configured.

One or more customer managed symmetric encryption keys do not have automatic rotation enabled, so all data encrypted under such a key since its creation depends on a single piece of key material, and a compromise of that material would expose more data. Such a compromise is unlikely: KMS key material is generated and used within hardware security modules and does not leave them unencrypted, so the risk that rotation addresses is small and there is no direct impact. Rotation also does not protect against the more realistic risk of misuse of the key through permissive key policies or IAM permissions, which allow decryption of all the data whatever the rotation state. The finding is mainly one of alignment with key management policy and compliance requirements.

The missing rotation is shown by aws kms get-key-rotation-status, and reported by Prowler, ScoutSuite, Security Hub and the CIS AWS Foundations Benchmark. Automatic rotation is not available for asymmetric keys, HMAC keys, keys with imported key material or keys in a custom key store, so those should be excluded from the finding or handled by manual rotation.

Remediation

Enable automatic rotation for customer managed symmetric encryption keys:

aws kms enable-key-rotation --key-id "$KEY_ID" --rotation-period-in-days 365
  • Choose a rotation period that meets the organisation's key management policy; KMS accepts 90 to 2,560 days.
  • Use on-demand rotation (aws kms rotate-key-on-demand) where key compromise is suspected or a policy requires an immediate change.
  • For keys with imported key material, import new key material and rotate it on demand, or create a new key and move the alias to it.
  • Review key policies and grants at the same time, since who can use a key matters more to its security than how often its material changes.

Confirm the fix with aws kms get-key-rotation-status returning KeyRotationEnabled as true for each key.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More AWS Findings

Every AWS finding