Cato Networks
See the Real AI Experience with Cato DEM (2026-10-29) commercialThe section your link pointed to isn't on Cato Networks's page any more, so we've brought you to the top.
Summary
Cato Networks is a commercial SASESASEA network architecture model combining wide-area networking and network security functions into a single cloud-delivered service, letting cyber tools enforce consistent policy regardless of where users or workloads sit. platform, delivered as a cloud service, that converges SD-WANSD-WANSoftware-defined wide-area networking: an approach that decouples WAN routing logic from physical hardware, letting operators centrally control traffic paths across MPLS, broadband, and LTE links to reduce cost and improve resilience., ZTNAZTNAZero Trust Network Access, a framework that grants users access to specific applications only after continuously verifying identity and device posture, replacing broad VPN-style network access with least-privilege connections., and network security into a single managed backbone rather than a stack of point products. It is run by connecting sites, users, and cloud resources into Cato's cloud rather than deploying and patching hardware, which is the pitch to network and security teams who currently stitch together separate WAN and security appliances. Beyond core connectivity, it extends into AI security, enumerating MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. servers, agents, and skills in use across an organization, and enforcing policy across prompts, tool calls, and outputs for agentic systems built on Claude, Bedrock, Copilot Studio, and similar platforms — work aimed at security teams now responsible for governing AI agents rather than just users and devices. Launched in 2015, it ships frequently, with its most recent release 16 days ago.
How Cato Networks helps
Which MCP servers and tools are reachable by agents right now, and what is the combined risk of that surface?
enumerates the MCP servers and tools available to agents across the environment and rolls them up into a single risk view instead of a per-agent list
Which AI agent skills in use need a review before they touch a business workflow?
scans skills present in the environment and flags those that fail posture checks, surfacing them for review before approval
Which hosts are showing behavior that maps to a known attack tactic right now?
tags hosts dynamically from recent activity and denies specific actions tied to MITRE ATT&CK tactics, such as blocking executable downloads on a host that has already contacted a known command-and-control server
Is an agentic attack against an endpoint still unfolding, and what has already been done about it?
shows the finding, the supporting evidence, which controls activated, and current mitigation status live inside the management application
Will policy apply to a Claude session the first time it runs on a new device?
lets policy be written before the agent is even detected, so the first session on an unenrolled device is still covered instead of running unenforced
Are lateral-movement attempts being caught automatically or only after someone reviews the logs?
continuously aggregates telemetry and reasons about host patterns to apply prevention policy in real time, for example denying lateral movement on a host showing both internal discovery and suspicious outbound contact, without waiting on manual action
Languages
Screenshots
From the release notes, newest first. Click one to see it full size.Media
Videos from the release notes, newest first. They play right here.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Cato Networks, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Cato Networks puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
catonetworks.com, every changeCato Networks's home page and 40 more pages as they looked each month from September 2021 to October 2026: 49 renders, 2 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Coverage
Missing something? Tell us
What Cato Networks connects to, runs on and detects, read from its release notes and docs. So far: 5 new detections, 1 new integration, 1 new compliance framework.
7 changes, tracked since Oct 28, 2026.
-
Oct 292026
new AI Agent Experience Monitoring — ChatGPT, Claude, Cursor, OpenAI API, Anthropic API
At launch, coverage includes ChatGPT, Claude, Cursor, and the OpenAI and Anthropic APIs, with additional AI services to be added over time.
-
Oct 282026
new Prompt injection and jailbreak detection for AI agents and custom applications
With LLM01, ASI01
Cato blocks prompt injection and jailbreak attempts before the model or agent acts. The same inspection finds sensitive data in prompts and responses and in files attached to AI apps.
-
Oct 282026
new Sensitive data detection in AI prompts, responses, and file attachments
With LLM02
The same inspection finds sensitive data in prompts and responses and in files attached to AI apps.
-
Oct 282026
new MCP server and AI skill discovery for supply chain risk
With LLM04, ASI04
Cato protects against supply chain risk by discovering MCP servers and skills connected to agents and coding tools, including ones IT never approved, and applying policy to each one.
-
Oct 282026
new Manipulated context detection in live AI interactions
With LLM05
Cato AI Security detects manipulated context in live interactions, while your data pipeline owners protect training and fine-tuning data.
-
Oct 282026
new Agent activity inventory and per-agent policy enforcement
With ASI10
Cato AI Security keeps an inventory of agent activity and applies policy to each agent in line, while your agent platform owns the kill switch.
-
Oct 282026
new OWASP Top 10 for LLM Applications (2026) and OWASP Top 10 for Agentic Applications (2026) coverage mapping
Covers 10: LLM01, LLM02, LLM03, LLM04, LLM05, LLM06 and 4 more
Cato AI Security covers the risks on both lists in three ways: Direct protection: Cato stops the risk in line, before the AI application or agent acts. Shared protection: Cato reduces the risk and works with your app developers on the rest. Platform evidence: Cato logs every AI interaction in an audit-ready format, so your team can investigate and show auditors what happened.
Editors & IDEs 1
Chat & assistant apps 1
Model providers & gateways 2
Nothing first seen in this window. That doesn't mean Cato Networks shipped nothing, only that we found no record of it.
How we count
Read from 2 of 10 release notes and docs updates we hold for Cato Networks. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Cato Networks's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
10 entries
No entries match these filters.
- October 20265
- September 20262
- August 20262
- July 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.