---
title: Cato SASE
description: "## What is Cato SASE? SASE (Secure Access Service Edge) by Cato Networks is a cloud-native, enterprise networking and security product. SASE converges SD-WAN and Security Service Edge (SSE) functions, including FWaaS, CASB, DLP, SWG, and ZTNA, into a unified, cloud-native service. SASE…"
url: "https://lucidum.io/docs/cato-sase/"
updated: "2026-07-29"
category: Connectors / List of Connectors / C
---

# Cato SASE

## What is Cato SASE?

SASE (Secure Access Service Edge) by Cato Networks is a cloud-native, enterprise networking and security product. SASE converges SD-WAN and Security Service Edge (SSE) functions, including FWaaS, CASB, DLP, SWG, and ZTNA, into a unified, cloud-native service. SASE provides a single cloud-based network that connects and secures any physical, cloud, or mobile enterprise resource, in any location.

## Why Should You Use the Cato SASE Connector?

The Cato SASE connector provides visibility into the assets in your environment. You can use this visibility to:

- ensure assets are managed per your security policies
- derive relationships between assets, users, applications, and data

## How Does This Connector Work?

Meridian executes read-only requests to the Cato SASE REST API and ingests only meta-data about Cato SASE devices. Meridian does not retrieve any data stored on your assets.

## Configuring the Connector in Meridian

| Field | **Description** | **Example** |
| --- | --- | --- |
| URL | The URL for the Cato SASE API. | https://api.catonetworks.com |
| Account ID | Optional parameter. The Cato SASE account ID (not the account name). If not supplied, Meridian uses the API Key to determine the account ID | 123456789 |
| API Key | A Service API key that provides read access to device data and user data. For details on creating a Service API key in Cato SASE, see: [https://support.catonetworks.com/hc/en-us/articles/4413280536081-Generating-API-Keys-for-the-Cato-API#h_01KFBQWK0FJW98P31G27WH93F6](https://support.catonetworks.com/hc/en-us/articles/4413280536081-Generating-API-Keys-for-the-Cato-API#h_01KFBQWK0FJW98P31G27WH93F6)   | p7g444S3IZ5wmFvmzWmx14qACXdzQ25b |

## Source Documentation

### Creating Credentials

To create a Service API key:

[https://support.catonetworks.com/hc/en-us/articles/4413280536081-Generating-API-Keys-for-the-Cato-API#h_01KFBQWK0FJW98P31G27WH93F6](https://support.catonetworks.com/hc/en-us/articles/4413280536081-Generating-API-Keys-for-the-Cato-API#h_01KFBQWK0FJW98P31G27WH93F6)

### Required Permissions

The Cato SASE token key must have Viewer permissions. When creating the Service API Key, select **Downgrade To View**.

### API Documentation

[https://support.catonetworks.com/hc/en-us/sections/13977250815389-Cato-API](https://support.catonetworks.com/hc/en-us/sections/13977250815389-Cato-API)

[https://api.catonetworks.com/documentation/#introduction](https://api.catonetworks.com/documentation/#introduction)