Skip to main content

💼 1.10 Ensure KMS Encryption Keys Are Rotated Within a Period of 90 Days - Level 1 (Automated)

  • Contextual name: 💼 1.10 Ensure KMS Encryption Keys Are Rotated Within a Period of 90 Days - Level 1 (Automated)
  • ID: /frameworks/cis-gcp-v1.3.0/01/10
  • Located in: 💼 1 Identity and Access Management

Description​

Google Cloud Key Management Service stores cryptographic keys in a hierarchical structure designed for useful and elegant access control management.

The format for the rotation schedule depends on the client library that is used. For the gcloud command-line tool, the next rotation time must be in ISO or RFC3339 format, and the rotation period must be in the form INTEGER[UNIT], where units can be one of seconds (s), minutes (m), hours (h) or days (d).

Similar​

  • Sections
    • /frameworks/cis-gcp-v2.0.0/01/10
    • /frameworks/cis-gcp-v1.2.0/01/10
  • Internal
    • ID: dec-c-c88dfb44

Similar Sections (Take Policies From)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS GCP v1.2.0 → 💼 1.10 Ensure KMS encryption keys are rotated within a period of 90 days - Level 1 (Automated)1
💼 CIS GCP v2.0.0 → 💼 1.10 Ensure KMS Encryption Keys Are Rotated Within a Period of 90 Days - Level 1 (Automated)1

Similar Sections (Give Policies To)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS GCP v1.2.0 → 💼 1.10 Ensure KMS encryption keys are rotated within a period of 90 days - Level 1 (Automated)1
💼 CIS GCP v2.0.0 → 💼 1.10 Ensure KMS Encryption Keys Are Rotated Within a Period of 90 Days - Level 1 (Automated)1

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlags

Policies (1)​

PolicyLogic CountFlags
📝 Google KMS Crypto Key is not rotated every 90 days 🟢1🟢 x6