An organization requires that encryption keys stored in Google Cloud KMS are regularly rotated every 90 days to comply with security policies. The security team wants to ensure that newly written data uses the newest key version while previously encrypted data remains decryptable without manual re-encryption. Which configuration approach should you use in Cloud KMS?
- Configure an automated key rotation schedule with a 90-day rotation period on the target CryptoKey.Answer
- BDelete the existing Key Ring every 90 days and recreate a new Key Ring with a new CryptoKey.
- CAssign the primitive Owner role to an automated script to destroy old key versions every 90 days.
- DGrant IAM permissions at the Organization level so resource hierarchy inheritance automatically rotates keys across all sub-projects.
Answer
Configure an automated key rotation schedule with a 90-day rotation period on the target CryptoKey.
Configuring an automated key rotation schedule directly on the CryptoKey allows Google Cloud KMS to generate a new primary key version automatically every 90 days. New encryption operations use the active primary version, while older key versions remain available so existing data can still be decrypted.
Step-by-Step Solution
Key Concept
Cloud KMS CryptoKey Automated Key Rotation