| 1 | --- |
| 2 | title: Cato Networks |
| 3 | description: Ingest Cato Networks SASE events into the SOCFortress SIEM stack. |
| 4 | --- |
| 5 | |
| 6 | ## What this integration is |
| 7 | |
| 8 | This integration ingests **Cato Networks** events into your SOCFortress SIEM stack using the Cato API (commonly via the `eventsFeed` capability). |
| 9 | |
| 10 | Vendor reference: |
| 11 | - Cato API docs: https://api.catonetworks.com/documentation/ |
| 12 | |
| 13 | --- |
| 14 | |
| 15 | ## Data path (how it flows) |
| 16 | |
| 17 | 1) Cato Networks → events API feed |
| 18 | 2) CoPilot collector → SIEM ingestion (indexing/search) |
| 19 | 3) Optional: alerting and incident workflows |
| 20 | |
| 21 | --- |
| 22 | |
| 23 | ## Prerequisites |
| 24 | |
| 25 | - Cato Management Application access |
| 26 | - API key created with appropriate permissions |
| 27 | - Event feed enabled (Administration → Event Integrations) |
| 28 | |
| 29 | --- |
| 30 | |
| 31 | ## Credentials you’ll need |
| 32 | |
| 33 | From Cato: |
| 34 | - **Account ID** (from the URL) |
| 35 | - **API key** |
| 36 | |
| 37 | API key notes: |
| 38 | - Choose **View permissions** for read-only ingestion. |
| 39 | - Copy the key immediately when generated (can’t be retrieved later). |
| 40 | |
| 41 | --- |
| 42 | |
| 43 | ## CoPilot setup (recommended workflow) |
| 44 | |
| 45 | 1) Provision the customer. |
| 46 | 2) Add **Cato Networks** integration under the customer. |
| 47 | 3) Provide account ID + API key. |
| 48 | 4) Validate that events begin flowing. |
| 49 | |
| 50 | --- |
| 51 | |
| 52 | ## Success criteria |
| 53 | |
| 54 | - [ ] Events show up for the expected customer |
| 55 | - [ ] You can correlate an event in Cato with an event in the SIEM |
| 56 | |
| 57 | --- |
| 58 | |
| 59 | ## Troubleshooting |
| 60 | |
| 61 | - Confirm “Event Feed Enabled” is toggled on. |
| 62 | - Confirm the API key is not expired/revoked. |
| 63 | - Validate the account ID is correct and in-scope. |