| 1 | --- |
| 2 | title: Fortinet FortiGate (syslog) |
| 3 | --- |
| 4 | |
| 5 | ## What you get (high level) |
| 6 | |
| 7 | - Firewall traffic logs |
| 8 | - Threat/UTM logs (depending on FortiGate config) |
| 9 | - Admin/audit events (optional) |
| 10 | |
| 11 | ## Data path (how it flows) |
| 12 | |
| 13 | FortiGate → syslog → ingestion/collector → Graylog parsing/routing → storage/indexing → alerts (`gl-events*`) → CoPilot Alerts/Cases. |
| 14 | |
| 15 | ## Setup (wireframe) |
| 16 | |
| 17 | - Configure FortiGate to send syslog to your collector. |
| 18 | - Ensure parsing and tenant-aware routing are in place. |
| 19 | |
| 20 | ## Success criteria |
| 21 | |
| 22 | - [ ] You can find fresh FortiGate events |
| 23 | - [ ] You can identify the sending device |
| 24 | - [ ] Events are tenant-aware |
| 25 | |
| 26 | ## Starter alerts |
| 27 | |
| 28 | - Excessive denies from a single source |
| 29 | - Inbound connections to sensitive services |
| 30 | - Admin login/config change events |
| 31 | |
| 32 | ## Troubleshooting |
| 33 | |
| 34 | - Confirm FortiGate syslog destination and facility/severity |
| 35 | - Confirm the collector is reachable from the FortiGate |
| 36 | - Confirm key parsing fields exist downstream |