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).
| Rank | Vendor | Total (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) |
|---|---|---|---|---|---|---|---|---|---|
| 1st | HiddenLayer | 71.0 | 8 | 9 | 4 | 6 | 9 | 6 | 7 |
| 2nd | Cisco | 66.5 | 7 | 8 | 5 | 7 | 8 | 5 | 5 |
| 3rd | Lasso Security | 63.5 | 7 | 7 | 5 | 7 | 7 | 3 | 8 |
| joint 4th | Bay | 62.5 | 8 | 6 | 5 | 8 | 7 | 0 | 7 |
| joint 4th | Operant AI | 62.5 | 7 | 7 | 4 | 7 | 7 | 4 | 7 |
| joint 4th | Straiker | 62.5 | 7 | 7 | 5 | 7 | 5 | 3 | 8 |
| 7th | Palo Alto Networks | 58.5 | 6 | 7 | 4 | 6 | 4 | 6 | 7 |
| 8th | Pillar Security | 55.5 | 7 | 7 | 0 | 6 | 7 | 4 | 8 |
| 9th | Check Point | 55.0 | 5 | 6 | 5 | 6 | 4 | 6 | 7 |
| 10th | CrowdStrike | 52.0 | 6 | 7 | 0 | 6 | 7 | 4 | 7 |
| 11th | Aim Security | 50.5 | 6 | 7 | 0 | 6 | 5 | 3 | 8 |
| 12th | Zenity | 50.0 | 7 | 6 | 0 | 4 | 6 | 4 | 8 |
| 13th | Cloudflare | 46.0 | 5 | 5 | 0 | 6 | 6 | 6 | 6 |
| 14th | SentinelOne (Prompt Security) | 45.5 | 5 | 6 | 0 | 6 | 4 | 4 | 7 |
| 15th | Microsoft | 45.0 | 4 | 6 | 0 | 6 | 6 | 6 | 6 |
| 16th | Noma Security | 41.5 | 5 | 6 | 0 | 4 | 4 | 3 | 7 |
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:
- Developers run coding agents with shell, file and package access: pick HiddenLayer (74.5). Bay is 3rd at 67.5. A coding agent acts on the machine, so stopping named actions there before they complete weighs most.
- A company shipping a customer-facing LLM application: pick HiddenLayer (68.0). Bay is joint 3rd at 63.5. An inline control in a customer path must be fast and fail predictably, so latency and failure mode weigh more.
- Staff use agents inside SaaS and cloud workspaces that act on company data: pick HiddenLayer (77.5). Bay is joint 4th at 67.0. Agents in SaaS act far from the endpoint, so coverage across layers weighs as much as what is stopped.
- A regulated company that must prove what was blocked and respond to incidents: pick HiddenLayer (77.0). Bay is joint 3rd at 66.5. Proving control means an audit trail and a response path, so detection and response weighs most after what is stopped.
- A lean team that must have runtime control in place this quarter: pick HiddenLayer (69.5). Bay is 2nd at 69.0. A lean team with a deadline needs the lightest deployment that still stops actions.
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.