Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow users to bring their own KMS key to encrypt the VM attached disks. #4

Closed
bschaatsbergen opened this issue Dec 30, 2022 · 0 comments · Fixed by #22
Closed

Allow users to bring their own KMS key to encrypt the VM attached disks. #4

bschaatsbergen opened this issue Dec 30, 2022 · 0 comments · Fixed by #22

Comments

@bschaatsbergen
Copy link
Contributor

bschaatsbergen commented Dec 30, 2022

Currently, users of Google Cloud Platform (GCP) Virtual Machines (VMs) are only able to encrypt the attached disks of their VMs using a Google-managed key that is stored in Cloud Key Management Service (KMS).

Benefits

Increased security By allowing users to bring their own KMS key, they have the option to use a key that is stored in their own KMS, rather than relying on a Google-managed key. This can provide an additional layer of security, as the user has full control over the management and rotation of their own key.

Industry best practices: Many organizations have established security policies that require the use of customer-managed keys for data encryption. Allowing users to bring their own KMS key would enable GCP users to comply with these policies and align with industry best practices for data security.

@bschaatsbergen bschaatsbergen changed the title Allow users to bring their own KMS key to encrypt the boot disk. Allow users to bring their own KMS key to encrypt the VM attached disks. Jan 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant