Changelog

Subscribe to Guardrails changelog via RSS or join #changelog on our Slack community to stay updated on everything we ship.

...

aws-cisv6-0 v5.0.2 - CIS controls no longer get stuck in a TBD state in gov cloud accounts

Sep 26, 2026

guardrailsMods

Bug fixes

CIS controls could get stuck in a TBD state and never report a result. In gov cloud and China accounts, the IAM credential report checks were also affected. They now complete and report a state as expected.

aws-cisv5-0 v5.0.3 - CIS controls no longer get stuck in a TBD state in gov cloud accounts

Sep 26, 2026

guardrailsMods

Bug fixes

CIS controls could get stuck in a TBD state and never report a result. In gov cloud and China accounts, the IAM credential report checks were also affected. They now complete and report a state as expected.

aws-cisv4-0 v5.0.2 - CIS controls no longer get stuck in a TBD state in gov cloud accounts

Sep 26, 2026

guardrailsMods

Bug fixes

CIS controls could get stuck in a TBD state and never report a result. In gov cloud and China accounts, the IAM credential report checks were also affected. They now complete and report a state as expected.

aws-cisv3-0 v5.0.10 - CIS controls no longer get stuck in a TBD state in gov cloud accounts

Sep 26, 2026

guardrailsMods

Bug fixes

CIS controls could get stuck in a TBD state and never report a result. In gov cloud and China accounts, the IAM credential report checks were also affected. They now complete and report a state as expected.

aws-cisv2-0 v5.0.8 - CIS controls no longer get stuck in a TBD state

Sep 26, 2026

guardrailsMods

Bug fixes

CIS controls could get stuck in a TBD state and never report a result. They now complete and report a state as expected.

aws-ec2 v5.60.1 - Track when EC2 volumes were last attached or detached

Sep 22, 2026

guardrailsMods

Bug fixes

Guardrails now records when an AWS EC2 volume was last attached or detached, so policies that depend on how recently a volume changed stay in step with what has actually happened to it. For example, set AWS > EC2 > Volume > Active > Last Modified to a Force active if last modified <= ... days value to keep a volume active while its attachment has changed within that window.

aws-ec2 v5.60.0 - Trace EC2 instances back to their source AMIs

Sep 18, 2026

guardrailsMods

What's new?

You can now see which AMIs an EC2 instance was built from, so you can tell an instance that came from an approved base image from one built from scratch. Add ImageAncestryEntries to AWS > EC2 > Instance > CMDB > Attributes and give the Guardrails role the ec2:GetImageAncestry permission. The chain works even when the AMI belongs to another account, and each entry gives you an AMI ID you can look up. The attribute is not enabled by default, so nothing is recorded until you add it.

aws-ec2 v5.59.0 - AMI resources now include the AMI ID as an AKA

Sep 17, 2026

guardrailsMods

What's new?

You can now find an AMI by its AMI ID. AWS > EC2 > AMI resources now include the AMI ID, for example ami-0e8f3b9d098b2d7d4, as an AKA alongside the existing ARN, so the ID can be used anywhere an AKA is accepted, including search, policy settings, filters and the API. AMIs already in the CMDB pick up the new AKA the next time the AWS > EC2 > AMI > CMDB control runs.

AWS mods - Retired unused Usage controls and policies (Batch, CloudFormation, Kinesis, MSK, SageMaker, SNS)

Sep 15, 2026

guardrailsMods

What's new?

The Usage controls and their Usage and Usage > Limit policies have been retired from the resource types in the mods listed below. The Approved > Usage policies are unaffected and remain available.

Released versions:

aws-batch v5.10.0
aws-cloudformation v5.15.0
aws-kinesis v5.13.0
aws-msk v5.9.0
aws-sagemaker v5.16.0
aws-sns v5.22.0

Control Types

Removed

AWS > Batch > Compute Environment > Usage
AWS > Batch > Job Definition > Usage
AWS > Batch > Job Queue > Usage
AWS > CloudFormation > Hook > Usage
AWS > CloudFormation > Stack > Usage
AWS > CloudFormation > StackSet > Usage
AWS > Kinesis > Consumer > Usage
AWS > Kinesis > Stream > Usage
AWS > MSK > Cluster > Usage
AWS > MSK > Serverless Cluster > Usage
AWS > SageMaker > Notebook Instance > Usage
AWS > SageMaker > Project > Usage
AWS > SNS > Subscription > Usage
AWS > SNS > Topic > Usage

Policy Types

Removed

AWS > Batch > Compute Environment > Usage
AWS > Batch > Compute Environment > Usage > Limit
AWS > Batch > Job Definition > Usage
AWS > Batch > Job Definition > Usage > Limit
AWS > Batch > Job Queue > Usage
AWS > Batch > Job Queue > Usage > Limit
AWS > CloudFormation > Hook > Usage
AWS > CloudFormation > Hook > Usage > Limit
AWS > CloudFormation > Stack > Usage
AWS > CloudFormation > Stack > Usage > Limit
AWS > CloudFormation > StackSet > Usage
AWS > CloudFormation > StackSet > Usage > Limit
AWS > Kinesis > Consumer > Usage
AWS > Kinesis > Consumer > Usage > Limit
AWS > Kinesis > Stream > Usage
AWS > Kinesis > Stream > Usage > Limit
AWS > MSK > Cluster > Usage
AWS > MSK > Cluster > Usage > Limit
AWS > MSK > Serverless Cluster > Usage
AWS > MSK > Serverless Cluster > Usage > Limit
AWS > SageMaker > Notebook Instance > Usage
AWS > SageMaker > Notebook Instance > Usage > Limit
AWS > SageMaker > Project > Usage
AWS > SageMaker > Project > Usage > Limit
AWS > SNS > Subscription > Usage
AWS > SNS > Subscription > Usage > Limit
AWS > SNS > Topic > Usage
AWS > SNS > Topic > Usage > Limit

aws-bedrock v6.1.0 - Identify unallowed foundation models

Sep 15, 2026

guardrailsMods

What's new?

You can now check foundation models against a list of allowed models. Set AWS > Bedrock > Foundation Model > Allowed > Custom to Check: Allowed, then define the list as a calculated policy on AWS > Bedrock > Foundation Model > Allowed > Custom > Rules. Rules match on provider, model ID and exact model version, so you can allow a whole provider, a single model version, or every version of a model family. Both policies default to Skip, so nothing is raised until you set them.

Control Types

Added

AWS > Bedrock > Foundation Model > Allowed
AWS > Bedrock > Foundation Model > Allowed > Custom

Policy Types

Added

AWS > Bedrock > Foundation Model > Allowed
AWS > Bedrock > Foundation Model > Allowed > Custom
AWS > Bedrock > Foundation Model > Allowed > Custom > Rules

azure-aifoundry v5.2.0 - Check and enforce content filters on RAI policies

Sep 14, 2026

guardrailsMods

What's new?

Added the Azure > AI Foundry > RAI Policy > Content Filters control and policies to check or enforce the content filters on an RAI policy, with a sub-policy per filter on the input and output sides (Disabled, Enabled, Enabled and blocking), a Severity Threshold for each harm category, and a Mode. Each filter sub-policy defaults to Skip, so only the filters you set are checked and Enforce: Configured corrects only those.

Control Types

Added

Azure > AI Foundry > RAI Policy > Content Filters

Policy Types

Added

Azure > AI Foundry > RAI Policy > Content Filters
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Hate
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Hate > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Indirect Attack
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Indirect Attack Spotlighting
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Jailbreak
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Profanity
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Selfharm
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Selfharm > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Sexual
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Sexual > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Violence
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Violence > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Mode
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Hate
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Hate > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Profanity
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Protected Material Code
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Protected Material Text
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Selfharm
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Selfharm > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Sexual
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Sexual > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Ungrounded Material
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Violence
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Violence > Severity Threshold

Action Types

Added

Azure > AI Foundry > RAI Policy > Set Content Filters

AWS mods - Retired unused Usage controls and policies (Backup, EFS, EKS, EMR, Route 53, S3, Secrets Manager, SQS)

Sep 14, 2026

guardrailsMods

What's new?

The Usage controls and their Usage and Usage > Limit policies have been retired from the resource types in the mods listed below. The Approved > Usage policies are unaffected and remain available.

Released versions:

aws-backup v5.16.0
aws-efs v5.13.0
aws-eks v5.11.0
aws-emr v5.12.0
aws-route53 v6.12.0
aws-s3 v5.35.0
aws-secretsmanager v5.13.0
aws-sqs v5.22.0

Control Types

Removed

AWS > Backup > Backup Plan > Usage
AWS > Backup > Backup Vault > Usage
AWS > EFS > FileSystem > Usage
AWS > EFS > Mount Target > Usage
AWS > EKS > Cluster > Usage
AWS > EKS > Node Group > Usage
AWS > EMR > Cluster > Usage
AWS > EMR > Security Configuration > Usage
AWS > Route 53 > Hosted Zone > Usage
AWS > S3 > Bucket > Usage
AWS > Secrets Manager > Secret > Usage
AWS > SQS > Queue > Usage

Policy Types

Removed

AWS > Backup > Backup Plan > Usage
AWS > Backup > Backup Plan > Usage > Limit
AWS > Backup > Backup Vault > Usage
AWS > Backup > Backup Vault > Usage > Limit
AWS > EFS > FileSystem > Usage
AWS > EFS > FileSystem > Usage > Limit
AWS > EFS > Mount Target > Usage
AWS > EFS > Mount Target > Usage > Limit
AWS > EKS > Cluster > Usage
AWS > EKS > Cluster > Usage > Limit
AWS > EKS > Node Group > Usage
AWS > EKS > Node Group > Usage > Limit
AWS > EMR > Cluster > Usage
AWS > EMR > Cluster > Usage > Limit
AWS > EMR > Security Configuration > Usage
AWS > EMR > Security Configuration > Usage > Limit
AWS > Route 53 > Hosted Zone > Usage
AWS > Route 53 > Hosted Zone > Usage > Limit
AWS > S3 > Bucket > Usage
AWS > S3 > Bucket > Usage > Limit
AWS > Secrets Manager > Secret > Usage
AWS > Secrets Manager > Secret > Usage > Limit
AWS > SQS > Queue > Usage
AWS > SQS > Queue > Usage > Limit

aws-bedrock v6.0.3 - Settings control no longer clears guardrail configuration it does not manage

Sep 14, 2026

guardrailsMods

What's new?

The AWS > Bedrock > Guardrail > Settings control now reports one row per setting, showing whether each is OK, in Alarm or skipped, with the guardrail's current value and the value your policy expects. Settings you have not configured are listed as skipped.

Bug fixes

Enforce: Configured no longer clears parts of a guardrail's configuration that none of your sub-policies manage, such as the actions and enablement flags AWS keeps on content filters, denied topics and PII entities. Those are now left as they are, and the control no longer treats them as a mismatch, so a guardrail that already matches your policies stays OK instead of being re-enforced on every cycle.

aws-ec2 v5.58.1 - Faster processing of real-time EC2 instance events

Sep 10, 2026

guardrailsMods

Bug fixes

Improved the internal GraphQL queries used by the EC2 controls and actions, for faster processing of real-time instance events.

aws-events v5.18.1 - Fixed incorrect cleanup of Event Handlers [Global] rules and targets when the CMDB is scoped to Guardrails infrastructure

Sep 09, 2026

guardrailsMods

Bug fixes

Rules and targets created by the Event Handlers [Global] stack are now kept in the CMDB when AWS > Events > Rule > CMDB or AWS > Events > Target > CMDB is set to Enforce: Enabled for Guardrails infrastructure only. Previously they were removed when AWS > Turbot > Event Handlers [Global] > Events > Rules > Name Prefix was set to its own value. Other rules and targets are still removed, and accounts using the default Enforce: Enabled are unaffected.

gcp-computeengine v5.26.2 - Fixed the Shielded VM configuration control erroring on running instances

Sep 08, 2026

guardrailsMods

Bug fixes

The GCP > Compute Engine > Instance > Shielded Instance Configuration control no longer errors on every run when set to Enforce against a running instance. GCP only accepts Shielded VM configuration changes while an instance is stopped, so the control now applies the configuration once the instance is stopped. It also reports which of Secure Boot, vTPM and Integrity Monitoring does not match, and reports invalid when Integrity Monitoring is required without vTPM.
The GCP > Compute Engine > Instance > CMDB control now also refreshes while an instance is starting or stopping, so its status settles to the instance's real state.

aws v5.47.2 - Improved real-time event handling for automated workflows and cross-account API calls

Sep 08, 2026

guardrailsMods

Bug fixes

Improved real-time event handling on AWS for events created by automated workflows and cross-account API calls. Some of these events were being silently discarded, which could leave the resources they touch stale in Guardrails and evaluated by controls on out-of-date data. All customers with AWS workloads are recommended to move to this version.

gcp-vertexai v5.5.0 - Fixed Allowed Regions policies stuck in an error state on Vertex AI resources

Sep 04, 2026

guardrailsMods

Bug fixes

The Allowed > Region > Regions policies on GCP > Vertex AI > Endpoint, Model, Notebook Runtime Template and Deployment Resource Pool no longer get stuck in an error state. They were failing because the service-level default they inherit from did not exist; the new GCP > Vertex AI > Allowed Regions [Default] policy fills that gap and inherits from GCP > Project > Allowed Regions [Default], so you can set the regions allowed for Vertex AI resources centrally from the project.

Policy Types

Added

GCP > Vertex AI > Allowed Regions [Default]

gcp-notebooks v5.5.0 - Fixed the Workbench instance allowed regions policy stuck in an error state

Sep 04, 2026

guardrailsMods

Bug fixes

The GCP > Notebooks > Instance > Allowed > Region > Regions policy no longer stays stuck in an error state. It inherited from a service-level default that did not exist; the new GCP > Notebooks > Allowed Regions [Default] policy supplies it, inheriting from GCP > Project > Allowed Regions [Default] so the regions allowed for Workbench instances resolve to the project's Regions list by default and can be tightened centrally.

Policy Types

Added

GCP > Notebooks > Allowed Regions [Default]

gcp-apigateway v5.0.1 - API Gateway allowed regions now follow the project's Allowed Regions default

Sep 04, 2026

guardrailsMods

Bug fixes

The regions allowed for API Gateway gateways now follow your project's GCP > Project > Allowed Regions [Default] policy, the same project-level Allowed default every other GCP service uses.

What's new?

Added the Azure > AI Foundry > RAI Policy > Content Filters control and policies to check or enforce the content filters on an RAI policy, with a sub-policy per filter on the input and output sides (Disabled, Enabled, Enabled and blocking), a Severity Threshold for each harm category, and a Mode. Each filter sub-policy defaults to Skip, so only the filters you set are checked and Enforce: Configured corrects only those.

Control Types

Added

Azure > AI Foundry > RAI Policy > Content Filters

Policy Types

Added

Azure > AI Foundry > RAI Policy > Content Filters
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Hate
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Hate > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Indirect Attack
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Indirect Attack Spotlighting
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Jailbreak
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Profanity
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Selfharm
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Selfharm > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Sexual
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Sexual > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Violence
Azure > AI Foundry > RAI Policy > Content Filters > Input Filter > Violence > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Mode
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Hate
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Hate > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Profanity
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Protected Material Code
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Protected Material Text
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Selfharm
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Selfharm > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Sexual
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Sexual > Severity Threshold
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Ungrounded Material
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Violence
Azure > AI Foundry > RAI Policy > Content Filters > Output Filter > Violence > Severity Threshold

Action Types

Added

Azure > AI Foundry > RAI Policy > Set Content Filters