AI agent security solutions for the gateway layer
Palo Alto Networks ranks first for the gateway layer, a proxy or API control point between agents and models, tools or MCP servers. The view puts 30 points on that layer. Bay says it decides on the device with no proxy; none found on 16 Nov 2026 for a gateway, so it sits last here.
Facts read on .
The short answer
Palo Alto Networks leads the view "Ranked for the gateway layer" at 68.0 of 100. Bay is 16th at 47.0. Palo Alto Networks is ahead mainly on coverage: gateway layer (8 against 0, worth 24.0 points at weight 30).
Why these weights
A buyer securing agents at the gateway layer first weighs coverage of that layer as all five layer weights together, and keeps the other criteria as on the site ranking.
| Coverage: endpoint layer | Coverage: browser layer | Coverage: cloud workspace layer | Coverage: identity layer | Coverage: gateway layer | Stops the action | Visibility | Deployment | Policy and governance | Transparency | Proof |
|---|---|---|---|---|---|---|---|---|---|---|
| 0 | 0 | 0 | 0 | 30 | 20 | 15 | 10 | 10 | 10 | 5 |
| Rank | Vendor | Total (of 100) | Coverage: endpoint layer (weight 0) | Coverage: browser layer (weight 0) | Coverage: cloud workspace layer (weight 0) | Coverage: identity layer (weight 0) | Coverage: gateway layer (weight 30) | Stops the action (weight 20) | Visibility (weight 15) | Deployment (weight 10) | Policy and governance (weight 10) | Transparency (weight 10) | Proof (weight 5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1st | Palo Alto Networks | 68.0 | 3 | 6 | 8 | 4 | 8 | 6 | 6 | 7 | 5 | 7 | 8 |
| 2nd | Operant AI | 65.5 | 8 | 6 | 8 | 5 | 7 | 7 | 7 | 7 | 7 | 3 | 6 |
| 3rd | Lasso Security | 65.0 | 6 | 2 | 6 | 3 | 7 | 7 | 7 | 7 | 6 | 3 | 7 |
| 4th | CrowdStrike | 64.5 | 7 | 5 | 1 | 8 | 7 | 7 | 7 | 6 | 6 | 3 | 8 |
| 5th | Microsoft | 63.0 | 8 | 2 | 7 | 7 | 6 | 6 | 7 | 7 | 6 | 7 | 5 |
| 6th | Island | 62.5 | 7 | 7 | 3 | 7 | 7 | 7 | 7 | 5 | 5 | 3 | 8 |
| 7th | Zenity | 62.0 | 7 | 1 | 7 | 7 | 7 | 7 | 7 | 5 | 5 | 3 | 7 |
| 8th | WitnessAI | 61.5 | 5 | 2 | 2 | 2 | 8 | 7 | 6 | 5 | 4 | 2 | 7 |
| 9th | Check Point | 61.0 | 4 | 5 | 6 | 1 | 6 | 6 | 7 | 6 | 4 | 7 | 7 |
| 10th | Cisco | 60.0 | 7 | 1 | 5 | 6 | 6 | 7 | 5 | 6 | 6 | 6 | 5 |
| 11th | Aim Security | 59.5 | 7 | 6 | 4 | 2 | 6 | 7 | 7 | 5 | 5 | 3 | 8 |
| 12th | Pillar Security | 58.5 | 7 | 0 | 2 | 2 | 5 | 7 | 7 | 6 | 7 | 3 | 6 |
| 13th | Noma Security | 57.0 | 6 | 1 | 7 | 6 | 6 | 6 | 7 | 5 | 5 | 3 | 7 |
| 14th | Straiker | 53.5 | 7 | 7 | 8 | 7 | 3 | 7 | 7 | 8 | 5 | 3 | 8 |
| 15th | SentinelOne (Prompt Security) | 48.0 | 5 | 4 | 3 | 2 | 4 | 5 | 7 | 5 | 4 | 3 | 7 |
| 16th | Bay | 47.0 | 8 | 6 | 5 | 6 | 0 | 9 | 7 | 8 | 6 | 1 | 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.
What would change this ranking
Top pair. Operant AI rising from 7 to 8 on coverage: gateway layer (weight 30, so each point moves a total by 3.0) would put Operant AI above Palo Alto Networks; the gap is 2.5 points.
Bay's next place. Bay rising from 0 to 1 on coverage: gateway layer (weight 30, so each point moves a total by 3.0) would put Bay above SentinelOne (Prompt 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.
Which are best for the gateway layer?
Palo Alto Networks ranks first for the gateway layer on 16 Nov 2026. The view weighs gateway coverage at 30 points and sets the other four layers to 0.
A gateway sits on the traffic path, so it sees every call that is routed through it and can block, mask or log before the call completes. It sees nothing that bypasses it.
What should the gateway layer cover?
Check whether the vendor runs its own gateway, plugs into one you already run (Kong, Envoy, LiteLLM and similar), or enforces on the network. Check whether MCP calls and tool calls pass through it as well as model prompts.
Ask what happens when the gateway fails. Cisco documents a fail-closed default for its Kong plugin; other vendors publish nothing on the point.
What if a solution has no gateway?
Then it acts somewhere else, and that can be a better fit. Bay says it decides on the device with no proxy, and with none found on 16 Nov 2026 for a gateway it scores 0 on this layer, and a team with managed laptops may prefer that. A team whose agents run on servers and call tools over the network needs a control point on that path.
Use the Agent Control Point Map to see the moment each vendor acts.