Skip to content
Cloud Governance Tools

How platforms are ranked on putting a guardrail into production

Sixteen platforms are scored 0 to 10 on seven criteria whose weights were fixed on 10 Nov 2026, before any score existed. Safe to enforce and one change for a class of risk carry 30 each. Totals are weighted means rounded to one decimal, and every fact is dated and linked to the page it came from.

See the ranking ยท Download the data

What these weights produce

Act is first at 5.9, ahead of Sonrai Security at 5.7.

Scope: security governance, the guardrail layer. Cost governance is out. The seven criteria and their weights are published with this method and were fixed before any vendor was scored: safe to enforce 30, one change for a class of risk 30, removes access rather than only reporting it 15, stays fixed 10, uses the cloud's own controls 10, evidence for auditors 3, and identity, network and AI coverage together 2. The weights favor the question this site exists to answer: can the guardrail be shown to be safe before it ships, and does one policy cover a whole class of risk.

A score is an integer from 0 to 10 for one criterion. The total is the sum of score times weight divided by the sum of the weights, rounded to one decimal. Every fact behind a score carries a quote, the page it came from and the date it was read, 10 Nov 2026. Every fact in the evidence files is labeled as coming from a vendor's own material or an analyst report about the vendor, so no score can exceed 7. A capability not found in the pages read is recorded as "none found on 2026-11-10", never as an absence.

Each situation page ranks the same sixteen platforms on the mean of this site's weights and the situation's own weights, both fixed in advance. Act is scored by the same rules as every other platform. Where a platform's strength is documented, the page states it in one sentence from its evidence.

The seven criteria and the weights this site uses

Weights sum to 100, fixed on 10 Nov 2026 and committed before any vendor was scored. These weights produce the main ranking; situation pages use the mean described below.
CriterionWhat is scoredWeight
Removes access, not only reports itDoes the product end with an enforced change that takes access away, or with a finding for someone else to act on15
Safe to enforceIs each change simulated against the real environment before it ships, with the impact shown30
One change, a class of riskBoundaries and guardrails that remove many paths at once, as opposed to permission-by-permission clean-up30
Stays fixedPrevents drift: violations checked before production, exceptions handled in the team's own tools, with proof10
Identity, network and AI access togetherDoes the model of reachability cover all three, including AI workloads and agents2
Uses the cloud's own controlsEnforcement through native mechanisms the customer already owns, with nothing new in the request path10
Evidence for auditorsMapped controls and continuous evidence for the named frameworks3

The scale and the rules, in brief

Each criterion is scored 0 to 10 from the vendor's evidence: 0 means none found on the read date, 7 is the ceiling for anything resting on the vendor's own material, and 8 to 10 need a source the vendor does not control. Scoring was blind, from evidence with product names removed. The total is the weighted mean on the weights above, to one decimal; equal totals share a rank and are listed by the unrounded total.

  • Weights, criteria and the vendor set were committed before the first score, and the scores were produced from evidence packets with product names replaced by codes.
  • Equal totals at one decimal are shown as joint, and the order inside a tie follows the unrounded total.
  • The Simulation Coverage Matrix records what each platform shows before a guardrail ships, from the same evidence.

Situation weights

Each situation page ranks on the mean of this site's weights and the situation's own weights, both fixed here before scoring.

Published weights: the mean of this site's weights and the situation's own weights, both fixed before scoring.
SituationRemovesSafeClassFixedId+Net+AINativeAudit
An AWS-heavy organization with hundreds of accounts and years of accumulated access202527.512.53.57.54
A multi-cloud enterprise with separate teams per cloud17.522.522.5158.512.51.5
A regulated company that must prove access boundaries for PCI DSS, HIPAA or NIST 800-5317.522.520153.57.514
A company putting AI agents into production this year17.522.5201018.57.54
A small cloud security team buried under posture findings it cannot clear22.522.527.512.53.57.54

The ranking these weights produce

Weights in the header row sum to 100. Scores 0 to 10 from the evidence read 10 Nov 2026; weighted total to one decimal; "=" marks a joint rank, listed by the unrounded total.
RankPlatformTotalRemoves (15)Safe (30)Class (30)Fixed (10)Id+Net+AI (2)Native (10)Audit (3)
1Act Security5.93774663
2Sonrai Security5.75574474
3AWS Control Tower4.25165464
4Google Cloud IAM recommender4.14632452
5Turbot3.95255536
6Apono3.65333454
7Britive3.05133454
8=AWS IAM Access Analyzer2.93414242
8=Wiz2.93414626
10=P0 Security2.35023453
10=CrowdStrike2.33404406
10=Tenable Cloud Security2.35304505
13=Entitle2.05023423
13=Sysdig2.03204436
15Prisma Cloud1.73014535
16Microsoft1.12012605

Act is first at 5.9, ahead of Sonrai Security at 5.7.

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.

What would change this ranking

Sonrai Security would move ahead of Act Security if its score on safe to enforce rose by 1 point (from 5 to 6) with nothing else changing. A score changes only when a sourced fact changes, and every change is listed on the corrections page.

Read dates and refresh

Every vendor page behind this edition was read on 10 Nov 2026. Claims older than 60 days are re-read; a score changes only when a sourced fact changes, and every change is listed on the corrections page with the old and new values.

Sources

  1. Act platform page (read for the client facts, scored like every other vendor), read 10 Nov 2026
  2. act.security, read 10 Nov 2026
  3. act.security/platform, read 10 Nov 2026

Last reviewed 16 Nov 2026.