AI Runtime Security Tools

AI runtime security tools ranking

HiddenLayer ranks first among 16 AI runtime security tools with 71.0 out of 100 on 16 Nov 2026. Bay is joint 4th with 62.5. Totals are weighted sums of seven criteria, led by the actions a tool stops before they complete, and each total traces to dated facts.

Facts read on .

The short answer

HiddenLayer leads the site ranking at 71.0 of 100. Bay is joint 4th at 62.5. HiddenLayer is ahead mainly on layers covered (9 against 6, worth 6.0 points at weight 20).

Site ranking: scores out of 10 per criterion, totals out of 100
RankVendorTotal (of 100)Action types stopped before they complete (weight 30)Layers covered (weight 20)Latency and failure mode (weight 15)Deployment (weight 15)Detection and response (weight 5)Transparency (weight 10)Proof (weight 5)
1stHiddenLayer71.08946967
2ndCisco66.57857855
3rdLasso Security63.57757738
joint 4thBay62.58658707
joint 4thOperant AI62.57747747
joint 4thStraiker62.57757538
7thPalo Alto Networks58.56746467
8thPillar Security55.57706748
9thCheck Point55.05656467
10thCrowdStrike52.06706747
11thAim Security50.56706538
12thZenity50.07604648
13thCloudflare46.05506666
14thSentinelOne (Prompt Security)45.55606447
15thMicrosoft45.04606666
16thNoma Security41.55604437

Re-rank with your own weights

The ranking above is the published one. Sliders appear here when scripts run; they start at the published weights and show what your weights would give, without changing the published ranking. Restore the published weights.

Who should pick what

With no particular situation, the published ranking applies and HiddenLayer comes first. For a specific situation the weights change, and so can the order:

What would change this ranking

Top pair. Cisco rising from 7 to 9 on action types stopped before they complete (weight 30, so each point moves a total by 3.0) would put Cisco above HiddenLayer; the gap is 4.5 points.

Bay's next place. Bay rising from 8 to 9 on action types stopped before they complete (weight 30, so each point moves a total by 3.0) would put Bay above Lasso Security; the gap is 1.0 points.

A score changes only when a sourced fact changes, and the weights were fixed before the scores. The method page lists the weights, anchors and rules.

How is the ranking built?

The total is a weighted sum of seven scores from 0 to 10, divided by 10, so totals run from 0 to 100. Action types stopped weighs 30, layers covered 20, latency and failure mode 15, deployment 15, transparency 10, detection and response 5 and proof 5.

A vendor claim alone earns at most 7 on any criterion. Only a second source, such as third-party coverage or public documentation observed directly, can earn 8 to 10.

What does the ranking not measure?

The ranking does not measure detection accuracy, false positive rates or bypass resistance, because no vendor publishes those figures in a form that can be compared. Third-party testing of that kind is the largest gap in this market.

Latency and failure mode are scored only as published. A vendor with no published figure scores low on that criterion even if its product is fast in practice.

Why do totals differ by situation?

Each situation page keeps the same 0 to 10 scores and changes only the weights, for example giving latency 25 for a customer-facing app. The leader can change because the question changed, not because a score moved.

Re-rank sliders let you set your own weights. A link restores the published ones.