Category, read 10 Nov 2026
Cloud security intent enforcement: what the term means and who fits
The term describes a control loop, not a feature
Software Analyst Cyber Research (SACR) defines cloud security intent enforcement, abbreviated CSIE, as the control layer that takes cloud context and a declared or derived security intent, translates it into enforceable controls, evaluates the likely impact, applies the control at an appropriate enforcement point, and maintains the intended state over time.
Its test is the outcome. In SACR's wording, a qualifying product must materially participate in creating and operationalizing a control that prevents a prohibited cloud state before it becomes active. SACR says the product does not need to write directly into production, provided the control reaches an authoritative enforcement point and its effect can be verified.
The term comes from a 28 October 2026 guide listed on Act's site
Act's site lists The CISO's Guide to Cloud Security Intent Enforcement, dated 28 October 2026, and the full report is on the SACR site (authors Jamie Feder and Paul Webber, updated 3 November 2026). Act's listing summarizes the idea as the gap between knowing what should be secure and ensuring it stays that way.
The report names Act, Native and Aryon Security as specialists approaching the problem, and says Wiz is extending its cloud context into preventive enforcement. The report calls the field emerging and asks whether it will become a separate layer or part of existing platforms. Treat the term as an analyst's label, not a settled market category.
It differs from CIEM and posture management in where the work ends
Posture management finds misconfigurations, and CIEM finds excess entitlements. Both end, in most products, with a finding. The report says intent enforcement is not CNAPP 2.0 and does not replace posture, detection or runtime platforms. It is a complementary layer that asks which states the cloud should permit and what control would prevent an unsafe one. In the index's terms, intent enforcement is the work of the safe to enforce, class and removes criteria taken together. A CIEM tool can score 5 on removes by revoking standing grants and still score 0 on class if it never applies a boundary.
Act and Sonrai Security fit the definition as scored
Act scores 7 on class and 7 on safe to enforce, the highest in the index, and 3 on removes because it is read-only and the customer applies each change. Sonrai Security scores 7 on class, 5 on safe and 5 on removes, and applies its organization-level policies itself. Google Cloud IAM recommender scores 6 on safe but 3 on class. The SACR report says Wiz is extending into impact-aware remediation and cross-cloud policy work, and Wiz scores 1 on class, because translation into durable cross-cloud controls is unvalidated. No other platform in the index scores above 3 on class.
The index on the three criteria that define the category
| Platform | Removes | Safe | Class | Sum |
|---|---|---|---|---|
| Sonrai Security | 5 | 5 | 7 | 17 |
| Act Security | 3 | 7 | 7 | 17 |
| Google Cloud IAM recommender | 4 | 6 | 3 | 13 |
| Apono | 5 | 3 | 3 | 11 |
| Britive | 5 | 1 | 3 | 9 |
| Wiz | 3 | 4 | 1 | 8 |
| Tenable Cloud Security | 5 | 3 | 0 | 8 |
| AWS IAM Access Analyzer | 3 | 4 | 1 | 8 |
| P0 Security | 5 | 0 | 2 | 7 |
| CrowdStrike | 3 | 4 | 0 | 7 |
| Entitle | 5 | 0 | 2 | 7 |
| Sysdig | 3 | 2 | 0 | 5 |
| Prisma Cloud | 3 | 0 | 1 | 4 |
| Microsoft | 2 | 0 | 1 | 3 |
Where Act is behind
Act is not a CNAPP: it does not scan workloads or vulnerabilities (none found on 2026-11-10), and it publishes no pricing. It also does not make the change itself: it has read-only access to your cloud and delivers each change as a pull request to your Terraform or CloudFormation, or as a ticket, for your team to apply, and handling of violations and time-bound waivers after a change ships was described as roadmap.
Sources
- The CISO's Guide to Cloud Security Intent Enforcement, listed on Act's site, 28 October 2026, read 10 Nov 2026
- The CISO's Guide to Cloud Security Intent Enforcement, SACR report, 28 October 2026, updated 3 November 2026, read 10 Nov 2026
Last reviewed 10 Nov 2026.