This topic provides an overview of Key Access Justifications. For information on creating and managing external keys, see Cloud EKM overview.
Key Access Justifications works by adding a field to your Cloud EKM requests that allows you to view the reason for each request. With select external key management partners, you can automatically approve or deny these requests, based on the justification.
Enabling Key Access Justifications
In order to enable an organization for Key Access Justifications, submit the access request form.
Managing access to your externally-managed keys
Key Access Justifications provides a reason every time your externally-managed keys are accessed. Reasons are only visible when keys are externally-managed. Keys stored in Cloud KMS or Cloud HSM will not show a visible reason when accessed by your service. When a key is stored in your external key manager, you will receive a justification for both service based access (for supported services), as well as direct API access.
Once you are onboarded for Key Access Justifications and use an externally-managed key, you will immediately receive justifications for every key access.
Why would my keys be accessed?
Google Cloud encryption-at-rest works by encrypting your data stored on Google Cloud with an encryption key that lives outside the service where the data is stored. For example, if you encrypt data in Cloud Storage, the service only stores the encrypted information you have stored, whereas the key used to encrypt that data is stored in the Cloud KMS (if you are using customer-managed encryption keys (CMEK)) or in your external key manager (if you are using Cloud External Key Manager).
When you use a Google Cloud service, you want your applications to continue working as described, and this will require your data to be decrypted. For example, if you run a query using BigQuery, the BigQuery service needs to decrypt your data in order to analyze it. In order to do this, BigQuery will need to call the key manager in order to decrypt the data.
For a list of justifications, see Key Access Justifications Reasons.
Viewing and acting on justifications
Whenever your information is encrypted or decrypted, Key Access Justifications sends you a justification describing the reason for the access. Software by our Cloud EKM partners enables you to set policy to automatically approve or deny access based on the content of the justifications. Please see the relevant documentation for your chosen key manager for more information on how to set policy. The following partners support Key Access Justifications:
The justification reason codes listed below cover different scenarios than the Access Transparency codes so will not match them.
Justification reason codes
||Customer uses their account to perform any access to their own data which their IAM policy authorizes.|
||Customer uses their account to perform any access to their own data which their IAM policy authorizes. At the same time, a Google administrator has reset the root-access account associated with the user's organization, or a Google-initiated breakglass operation has affected the accessed resource.|
||Google personnel access customer data to help optimize the structure of the data
or quality for future uses by the customer. These accesses can be for indexing, structuring, precomputation, hashing, sharding and
caching customer data. This also includes backing up data for disaster recovery or data
integrity reasons, and detecting errors that the
backup data could remedy.
Note that where the customer has delegated a managed control plane operation to Google, such as the creation of a managed instance group, all managed operations will show as system operations. Services such as the managed instance group manager that trigger downstream decryption operations do not have access to clear-text customer data.
||Google accesses customer data to help optimize the structure of the data or quality for future uses by the customer. These accesses can be for indexing, structuring, precomputation, hashing, sharding and caching customer data. This also includes backing up data for disaster recovery or data integrity reasons, and detecting errors that the backup data could remedy. At the same time, a Google-initiated breakglass operation has affected the accessed resource.|
No reason is expected for this key request for the following reasons:
||Customer-initiated support, for example, "Case Number: ####".|
Refers to Google-initiated access for system management and troubleshooting. Google personnel can make this type of access for the following reasons:
||Google-initiated access in response to a legal request or legal process, including when responding to legal process from the customer that requires Google to access the customer's own data.|
||Google-initiated access for security, fraud, abuse, or compliance
Refers to Google-initiated access to maintain system reliability. Google personnel can make this type of access for the following reasons:
||You have Key Access Justifications enabled but no justification is available for this request. The reason could be a transient error, a bug, or some other circumstance.|
|No justification field present||Key Access Justifications isn't enabled for you.|
Key Access Justifications exclusions
Key Access Justifications only applies to:
- Operations on encrypted data. For the fields within a given service that are encrypted by an externally managed key, please see the documentation for the given service you are using.
- The transition from data-at-rest to data-in-use. While Google continues to apply protections to your data-in-use, the Key Access Justifications governs the transition from data-at-rest to data-in-use only
- CMEK exemptions.
- BigQuery ML and BigQuery BI Engine are excluded.
- Compute Engine/Persistent Disk
- Local SSD and auto-restart are excluded.
- Machine image operations are excluded.
|Google Kubernetes Engine||GA|
- Read where you can get support for Key Access Justifications.