> ## Documentation Index
> Fetch the complete documentation index at: https://docs.forge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Cato Networks

> Route supported AI traffic through Forge and enforce broad AI access directly in Cato.

The Cato Networks integration combines content-aware gateway routing with
native network enforcement. Supported AI protocols can be decrypted and
rerouted to Forge. The larger Forge AI catalog is governed directly through
Cato policy and observed through the Events feed.

## Enforcement modes

| Mode                       | Coverage                                                            | Traffic path                                                                          | Forge visibility                                                                           |
| -------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| Content-aware routing      | Supported desktop AI, developer APIs, browser AI, and MCP protocols | Cato TLS inspection and routing send matching traffic to the Forge LLM or MCP Gateway | Supported content, sessions, identity, and inline policy decisions                         |
| Native catalog enforcement | Thousands of classified AI destinations                             | Cato applies Internet Firewall or Application Control policy locally                  | Destination, identity, action, policy state, inventory, and analytics from provider events |

Native enforcement minimizes added latency and does not send decrypted traffic
to Forge. Content-aware routing is reserved for protocols where Forge can
reconstruct and govern the interaction.

## Content routing

Forge provisions the inspection CA and a bounded TLS-inspection and routing
configuration for the selected AI destinations. Managed clients must trust the
inspection CA through the organization's existing certificate-management
process.

The Forge rerouter classifies the decrypted protocol and directs model and
browser traffic to the LLM Gateway and MCP traffic to the MCP Gateway. The
gateway applies identity, access, and content controls before calling the
original upstream.

Forge previews inspection scope, route targets, excluded traffic, provider
changes, verification, and rollback before apply. Certificate pinning, TLS
bypass, QUIC, ECH, and routes outside the configured Cato scope remain explicit
coverage gaps.

## Native policies

Forge compiles broad Access policies into the applicable Cato Internet Firewall
or Application Control rule. The compiled rule retains subject, destination,
application/category, action, logging, and ordering semantics supported by
Cato.

Policy read access supports provider-state comparison and change preview.
Publishing requires a separate write credential, explicit confirmation,
provider readback, and rollback verification.

The policy executes in Cato's network path. Forge receives its decision later
through the Events feed and uses that evidence for inventory, attribution, and
analytics.

## Sources

| Source          | Imported evidence                                                                 |
| --------------- | --------------------------------------------------------------------------------- |
| Events feed     | Network, URL, application, action, destination, identity, inspection, and routing |
| Audit feed      | Administrative and policy-change history                                          |
| Account context | Account snapshot, metrics, sites, users, and groups                               |
| Entity lookup   | Provider references used to enrich users, sites, and devices                      |
| Policy readback | Internet Firewall, Application Control, TLS inspection, and routing state         |
| Source health   | Capability status, checkpoints, lag, and collection errors                        |

Collection preserves Cato markers and advances them only after the bounded
batch is persisted. Records that cannot be safely correlated remain unresolved
with their provider entity references.

## Connection

| Field         | Description                                                              |
| ------------- | ------------------------------------------------------------------------ |
| Account ID    | Cato account in scope                                                    |
| Base URL      | Cato GraphQL API endpoint                                                |
| API key       | Write-only service credential for the enabled read or write capabilities |
| Poll interval | Scheduled event and configuration collection interval                    |
| Source key    | Stable connector instance retained in evidence provenance                |

## Setup

1. Connect the Cato account and test event, audit, entity, policy, TLS, routing,
   and source-health capabilities independently.
2. Enable content-aware routing for the supported AI destinations in scope.
3. Review and confirm the CA, TLS-inspection scope, Forge routing target,
   exclusions, provider readback, and rollback plan.
4. Compile broad Access policies into Cato for the remaining AI catalog.
5. Verify a routed gateway session and a separate native Cato policy event in
   Forge.

Cato events alone do not prove prompt, response, or tool visibility. Content
inspection requires a verified route through a Forge gateway.