Assigned
Status Update
Comments
ba...@google.com <ba...@google.com>
ba...@google.com <ba...@google.com> #2
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
Description
How this might work: Either through a deny policy or organization policy, this would allow people in charge of Cloud KMS CMEK to control who can and cannot destroy key materials.
If applicable, reasons why alternative solutions are not sufficient: Organization Policies do not currently cover this issue [1] and custom roles are not feasible given a large number of users this would apply to.Constraints will deny users the ability to access all keys, however, it is not applicable to basic roles like owners [2].
Other information (workarounds you have tried, documentation consulted, etc):
[1]
[2]