Your organization wants full control of the keys used to encrypt data at rest in their Google Cloud environments. Keys must be generated and stored outside of Google and integrate with many Google…

Question

Options

• AUse customer-supplied encryption keys (CSEK) with keys generated on trusted external systems.
• BCreate a KMS key that is stored on a Google managed FIPS 140-2 level 3 Hardware Security
• CUse Cloud External Key Management (EKM) that integrates with an external Hardware Security
• DCreate a Cloud Key Management Service (KMS) key with imported key material. Wrap the key for

• A
  7% (4)
• B
  3% (2)
• C
  71% (41)
• D
  19% (11)

Explanation

Cloud External Key Management (EKM) allows organizations to use encryption keys that are generated, stored, and managed entirely outside of Google Cloud in a third-party key management system (typically backed by an external HSM). Google Cloud services, including BigQuery, integrate natively with Cloud EKM, meaning the key never leaves the external system - Google only receives a reference to the key and calls out to it at encryption/decryption time. Option A (CSEK) requires providing the raw key material directly with each API call and has limited service integration - it does not work with BigQuery. Option B (Cloud KMS with Google-managed HSM) keeps the key inside Google's infrastructure, violating the 'outside of Google' requirement. Option D (importing key material into Cloud KMS) copies the key into Google's KMS, meaning Google stores it - this does not satisfy 'generated and stored outside of Google.'

No community discussion yet for this question.