Encryption and key guardrails enforce the setting, and break clients that cannot meet it
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
13 guardrails in the library address encryption and keys: 7 AWS, 3 Azure, 3 Google Cloud. The first in the list, "Deny KMS key deletion", denies scheduling KMS key deletion and deleting aliases, custom key stores and imported key material unless the caller is the privileged role.
All risk classes ยท Download the library
Guardrails in this class enforce encryption on write and in transit, and protect keys from deletion. The library holds 13, 7 for AWS. They break whatever cannot meet the requirement. Requiring server-side encryption on S3 uploads makes upload requests that omit the header fail for every principal in the affected accounts. Resource control policies that require HTTPS or TLS 1.2 also deny callers outside the organization, including trusted partners, and AWS warns that deny-based RCPs can block unintentionally. A 30-day KMS deletion window fails any shorter schedule, and denying key deletion means routine key cleanup needs the privileged role.
What these guardrails break
- Deny KMS key deletion (AWS): Routine key cleanup, including alias deletion, needs the privileged role in every affected account.
- Enforce a 30-day KMS key deletion window (AWS): Scheduling key deletion with a pending window under 30 days fails for every principal in the affected accounts, because the policy has no exception condition.
- Deny disabling default EBS encryption (AWS): The README says to enable encryption by default in your accounts before implementing this policy.
- Require server-side encryption on S3 uploads (AWS): Upload requests that omit the server-side encryption header fail for every principal in the affected accounts; the policy has no exception condition.
- Require HTTPS for access to resources (AWS): Callers outside the organization, including trusted partners, are also denied if they connect over an unencrypted connection, because RCPs apply regardless of whether the principal belongs to the organization.
- Require TLS 1.2 or later for S3 (AWS): Clients limited to older TLS versions, including principals outside the organization, are denied; AWS warns deny-based RCPs can unintentionally block use of AWS services without needed exceptions.
- Deny S3 customer-provided encryption keys (SSE-C) (AWS): Uploads that use customer-provided keys are denied for all callers; AWS warns deny-based RCPs can unintentionally block use of AWS services without needed exceptions.
- Storage accounts should have the specified minimum TLS version (Azure): Storage accounts below the minimum are rejected: deny returns 403 on create and update.
- Key vaults should have deletion protection enabled (Azure): Purge protection enforces a mandatory retention period: no one in your organization or Microsoft can purge the vault during the soft delete retention period.
- OS and data disks should be encrypted with a customer-managed key (Azure): You take on key lifecycle work: the definition says you have full control and responsibility for the key lifecycle, including rotation and management.
- Restrict which services may create resources without CMEK (Google Cloud): Google documents that enforcement is not retroactive and that existing non-CMEK resources must be reconfigured or recreated manually.
- Restrict unencrypted HTTP access to Cloud Storage (Google Cloud): Google documents that the Cloud Storage XML API allows unencrypted HTTP by default, so clients using it over HTTP are refused once the constraint is enforced.
- Restrict key destruction to disabled key versions (Google Cloud): Google documents that the constraint applies to both new and existing key versions.
Where Act is behind
Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.
Related pages
Sources
- Deny KMS key deletion, read 10 Nov 2026
- Enforce a 30-day KMS key deletion window, read 10 Nov 2026
- Deny disabling default EBS encryption, read 10 Nov 2026
- Require server-side encryption on S3 uploads, read 10 Nov 2026
- Require HTTPS for access to resources, read 10 Nov 2026
- Require TLS 1.2 or later for S3, read 10 Nov 2026
- Deny S3 customer-provided encryption keys (SSE-C), read 10 Nov 2026
- Storage accounts should have the specified minimum TLS version, read 10 Nov 2026
Last reviewed 16 Nov 2026.