What 2026 SASE analyst placements tell an AI security buyer, and what they do not

Cato Networks states it was named a Leader in the 2026 Gartner Magic Quadrant for SASE Platforms for the third consecutive year, citing the report dated 28 July 2026.

Source: Cato Networks news: Leader in the 2026 Gartner Magic Quadrant for SASE Platforms · Read 7 Oct 2026

Palo Alto Networks' Prisma SASE page states "A 4X Gartner Magic Quadrant Leader for SASE Platforms". Its Prisma Access page uses a different count, which appears to refer to a different report name, so we cite only the Prisma SASE page.

Source: Palo Alto Networks: Prisma SASE · Read 7 Oct 2026

Zscaler states it was recognized as a Leader in the 2026 Gartner Magic Quadrant reports for SASE and SSE.

Source: Zscaler: Zero Trust SASE · Read 7 Oct 2026

Netskope states it is a 2026 Magic Quadrant Leader for SASE Platforms and for Security Service Edge.

Source: Netskope: 2026 Gartner Magic Quadrant reports for SASE Platforms and SSE · Read 7 Oct 2026

Fortinet states it was recognized as a Challenger in the 2026 Gartner Magic Quadrant for SASE Platforms.

Source: Fortinet: FortiSASE · Read 7 Oct 2026

Cisco's SASE page says Cisco was named a SASE Leader, without naming the analyst firm or report in the page text.

Source: Cisco: SASE solution · Read 7 Oct 2026

Analyst reports change names over the years, and vendors count consecutive placements in different ways: some count only the current report name, some include its predecessors, some count related reports. That is why one vendor's own pages can give two different numbers. The count is a marketing choice; the current placement is the fact.

A SASE Magic Quadrant evaluates the whole platform: networking, security services, operations and the vendor's strategy. AI security features are a small and recent part of that, and they change faster than the annual report. A Leader placement tells you the platform underneath the AI controls is considered mature by one analyst firm. It does not tell you whether a vendor can redact a prompt, decode MCP traffic or stop a coding agent's tool call.

If you plan to put AI controls inside your SASE or SSE cloud, the platform matters: its reach, its operations and its roadmap carry the AI features. In that case the SASE placement is one input among several. If you are buying a standalone AI security layer, the SASE placement says little. In both cases, judge the AI controls on what the vendor states and what a pilot shows. The checks on this site are a starting list.

We quote placements only as each vendor states them on its own page, with the report date where the page gives it. Gartner does not endorse any vendor, product or service depicted in its research publications, and this site is not affiliated with Gartner.

If you will run AI controls inside a SASE or SSE platform, ask the questions that the placement does not answer. Where does inspection of AI traffic happen, and is it in the same location as the rest of your traffic? Are the AI features available in every region the vendor serves, or only some? How are AI detection models updated, and how often? Which parts of the AI security offer came from acquisitions, and are they managed in the same console yet? Cato Networks, for example, publishes on its newsroom a report that it agreed to acquire Aim Security in 2025 to expand into AI security, which is useful context when you ask how the pieces fit together.

Source: Cato Networks newsroom: Bloomberg report on the Aim Security acquisition · Read 7 Oct 2026