| 1 | --- |
| 2 | title: Integrations |
| 3 | description: Source-by-source setup guides and expectations for what data, dashboards, and alerts you get in CoPilot. |
| 4 | --- |
| 5 | |
| 6 | This section is a **catalog**. |
| 7 | |
| 8 | Pick a source, follow a short setup guide, then validate that: |
| 9 | |
| 10 | - logs are ingesting |
| 11 | - dashboards populate (after provisioning) |
| 12 | - alerting can be enabled (built-in or custom) |
| 13 | |
| 14 | If you’re brand new, start with the guided checklist: [Start here](/getting-started/start-here). |
| 15 | |
| 16 | --- |
| 17 | |
| 18 | ## The mental model |
| 19 | |
| 20 | Almost every integration follows this pattern: |
| 21 | |
| 22 | 1. **Ingest** events (API integration or syslog) |
| 23 | 2. Store events in your SIEM datastore (Wazuh Indexer / OpenSearch-backed) |
| 24 | 3. (Often) build alerts in **Graylog** → alerts land in `gl-events*` |
| 25 | 4. CoPilot shows alerts in **Incident Management → Alerts** → operators open **Cases** |
| 26 | |
| 27 | --- |
| 28 | |
| 29 | ## First-wave integrations |
| 30 | |
| 31 | - [Wazuh (endpoints)](/integrations/wazuh) |
| 32 | - [Office 365](/integrations/office-365) |
| 33 | - [Mimecast](/integrations/mimecast) |
| 34 | - [Huntress](/integrations/huntress) |
| 35 | - [CrowdStrike](/integrations/crowdstrike) |
| 36 | |
| 37 | ## Network connectors (syslog) |
| 38 | |
| 39 | - [Network connectors overview](/integrations/network-connectors) |
| 40 | - Fortinet: [FortiGate](/integrations/network-connectors/fortigate) |
| 41 | - Palo Alto Networks: [PAN-OS](/integrations/network-connectors/palo-alto) |
| 42 | - Cisco: [ASA](/integrations/network-connectors/cisco-asa) |