Description
The [Cato Networks](https://www.catonetworks.com/) connector pushes security and networking telemetry from the Cato Management Application into Microsoft Sentinel in near real time, using the Codeless Connector Framework (CCF) Push pattern. Data lands in a custom Log Analytics table, ready for hunting, analytics, and visualization. See the [Cato Event Schema](https://knowledge.catonetworks.com/docs/cato-event-schema) for the fields carried on each record.
- Declared status
- 1
- Declared author / publisher
- Cato Networks
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
read and write permissions are required.
Workspace
Workspace
Microsoft Entra
Permission to create an app registration in Microsoft Entra ID. Typically requires Entra ID Application Developer role or higher.
Microsoft Azure
Permission to assign Monitoring Metrics Publisher role on data collection rule (DCR). Typically requires Azure RBAC Owner or User Access Administrator role.
Cato Management Application
An administrator account on the Cato Management Application with permission to create a Microsoft Sentinel data-out connector.
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
1. Create ARM Resources and Provide the Required Permissions
This connector enables the Cato Cloud to push events directly to Microsoft Sentinel via the Azure Monitor Logs Ingestion API.
Deploy Cato Networks connector resources
2. Configure the connector in the Cato Management Application
In the Cato Management Application, go to Resources > Integrations > Configured Integrations, click New, select Microsoft Sentinel, and enter the values below. For full setup instructions, see [Integrating Cato Events with Microsoft Sentinel](https://knowledge.catonetworks.com/docs/integrating-cato-events-with-microsoft-sentinel).
Tenant ID (Directory ID)
Entra App Registration Application ID
Entra App Registration Secret
Data Collection Endpoint Uri
Data Collection Rule Immutable ID
Events Stream Name
3. Keeping the schema up to date
Cato periodically adds fields to its event schema. Because upgrading this solution leaves your connector's existing custom table and Data Collection Rule unchanged, new fields must be applied separately using the dedicated schema update template.
Related content
Links established from declared identifiers and solution manifests.
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- File
- Solutions/CatoNetworks/Data Connectors/CatoNetworks_PUSH_CCP/CatoNetworks_ConnectorDefinition.json ↗
- Commit
9800e51↗- Source identifier
CatoNetworksEventsPush
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC