Skip to content
Cloud Governance Tools

Restrict key destruction to disabled key versions

Restrict key destruction to disabled key versions is a Google Cloud guardrail written in organization Policy Service. Allows destruction only of key versions that are already in the disabled state. What it breaks: google documents that the constraint applies to both new and existing key versions.

More encryption and keys guardrails ยท About Organization Policy Service

constraints/cloudkms.disableBeforeDestroy
This boolean constraint, when enforced, only allows the destruction of key versions that are in the disabled state. By default, key versions that are in the enabled state and key versions that are in the disabled state can be destroyed. When this constraint is enforced, it applies to both new and existing key versions.
Blocks
Allows destruction only of key versions that are already in the disabled state. (legacy managed constraint, boolean.)
Breaks
Google documents that the constraint applies to both new and existing key versions. (source)
Test before applying
As for every Organization Policy Service guardrail: how to test before enforcing
Mechanism
Organization Policy Service (managed and legacy constraints): Resources in the organization, folder or project where the policy is set and its descendants; Google says application of new policies is usually not retroactive.
Taken from
provider documentation, provider documentation

What the source says

"This boolean constraint, when enforced, only allows the destruction of key versions that are in the disabled state." (read 10 Nov 2026).

On what it breaks: "When this constraint is enforced, it applies to both new and existing key versions."

Sources

  1. Restrict key destruction to disabled key versions, read 10 Nov 2026
  2. How to test it first, read 10 Nov 2026

Last reviewed 16 Nov 2026.