Skip to content
Cloud Governance Tools

Act Security puts guardrails into production at 5.9, 1st of 16

Act Security is 1st of 16 on how safely a platform puts a guardrail into production, at 5.9 of 10. It scores 7 on safe to enforce and 7 on one change for a class of risk, the two criteria weighted 30 each here.

See the full ranking · Read the method

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.

Act says it writes a guardrail as a policy in the cloud's own mechanism and delivers it as a pull request. Act's pages describe two shapes: broad explicit-deny guardrail campaigns for whole attack categories, with built-in exceptions, and explicit-allow ring-fencing around selected crown jewel applications and data. Act's blog places the controls at the AWS Organizations and service control policy level, and names Security Groups, NSGs, SCPs, RCPs and private endpoints as the native boundaries it refers to. Act says one policy change can remove thousands of access paths.

Act says it tests before a change ships: each change is run against a digital twin built from cloud configuration data, then in audit mode against audit-log events, before enforcement. Act is read-only to the customer's cloud, so the change reaches production through the customer's Terraform or CloudFormation, a ticket or a coding agent. SACR's report on Act lists limits: rarely used or undocumented dependencies may go untested, and violations management and time-bound waivers were presented as near-term roadmap. Act's free IAM Simulate library evaluates a request against supplied identity, resource, SCP, RCP and permissions boundary policies, for AWS only.

How Act puts a guardrail into production

Safe to enforce: 7 of 10, weight 30

Each change is tested against a digital twin built from cloud configuration data and run in audit mode against audit-log events before enforcement. This is on the vendor's own material only, and rare dependencies may go untested.

  • "Simulation: Test changes against a digital twin to see their exact impact before enforcing, ensuring nothing breaks." (Act's own material, read 10 Nov 2026)
  • "Audit mode : Run changes in audit mode as long as needed to confirm no legitimate access is revoked." (Act's own material, read 10 Nov 2026)

One change, a class of risk: 7 of 10, weight 30

Act runs broad explicit-deny guardrail campaigns for whole attack categories and explicit-allow ring-fencing, applied at the AWS Organizations and SCP level. This is on the vendor's own material only.

  • "Broad explicit-deny policies that block entire attack categories, including unauthorized cross-environment movement, data exfiltration, and external overexposure" (Act's own material, read 10 Nov 2026)
  • "Least privilege, explicitly-allow policies, applied selectively to crown jewel applications and sensitive data." (Act's own material, read 10 Nov 2026)

Uses the cloud's own controls: 6 of 10, weight 10

Act enforces through named native controls (security groups, NSGs, SCPs, RCPs, private endpoints) delivered via infrastructure as code, with no new infrastructure. For AI agents it also enforces on the agent and the gateway.

  • "Act enforces boundaries through your cloud's own native controls, using Infrastructure-as-Code. No agents and no new infrastructure to maintain." (Act's own material, read 10 Nov 2026)
  • "Act’s differentiation is therefore less about a unique enforcement mechanism, as it relies on the cloud’s native controls" (softwareanalyst.io, counted as vendor material, read 10 Nov 2026)

Stays fixed: 4 of 10, weight 10

Act documents drift detection with a diff against cloud versions, a one-line CI/CD blocking claim that does not say what is checked, and a Terraform provider for its own configuration. Exception handling in the customer's tools and rollback are credited only as roadmap or open discussion. Wiz and Sonrai also score 4.

  • "CI/CD integration: Block risk from shipping in CI/CD, with no downtime or disruption to operations." (Act's own material, read 10 Nov 2026)
  • "let users request blocked access directly within their existing tools, so security can approve or deny in one click." (Act's own material, read 10 Nov 2026)

Removes access, not only reports it: 3 of 10, weight 15

Changes are delivered as infrastructure-as-code pull requests that the customer applies. The product is read-only, and direct enforcement is still under discussion.

  • "Simulate each policy change first to validate its impact before it reaches production, then apply it through your own cloud-native controls." (Act's own material, read 10 Nov 2026)
  • "Native enforcement : Deploy directly as pull requests to your existing Infrastructure-as-Code (Terraform, CloudFormation) using the cloud-native controls you already own." (Act's own material, read 10 Nov 2026)

All seven scores

Weighted total 5.9 (5.86 before rounding) on this site's weights.
CriterionWeight hereScoreWeighted points
Removes access, not only reports it1530.45
Safe to enforce3072.10
One change, a class of risk3072.10
Stays fixed1040.40
Identity, network and AI access together260.12
Uses the cloud's own controls1060.60
Evidence for auditors330.09

Act in the five situations

Strongest, in one sentence

Act removes broad classes of access by simulating guardrail and ring-fence policies against a digital twin and delivering them as pull requests to the customer's IaC using cloud-native controls. (source)

Sources

  1. act.security, read 10 Nov 2026
  2. act.security/platform, read 10 Nov 2026
  3. softwareanalyst.io/reports/the-ciso-s-guide-to-cloud-security-intent-enforcement, read 10 Nov 2026
  4. act.security/resources/ai-agent-security-access-chain, read 10 Nov 2026
  5. act.security/resources/zero-trust-ai-agents, read 10 Nov 2026
  6. raw.githubusercontent.com/act-security/terraform-provider-act/main/README.md, read 10 Nov 2026
  7. act.security/resources/network-and-identity-each-see-half-your-cloud-your-attack, read 10 Nov 2026

Last reviewed 16 Nov 2026.