| 1 | --- |
| 2 | title: SentinelOne (syslog over TLS) |
| 3 | description: Forward SentinelOne alerts/events to the SIEM using TLS (mutual auth). |
| 4 | --- |
| 5 | |
| 6 | ## What this connector is |
| 7 | |
| 8 | This connector forwards **SentinelOne** alerts and events to your SIEM using **TLS-encrypted syslog** with **mutual authentication**. |
| 9 | |
| 10 | Detailed guide: |
| 11 | - https://socfortress.supportbench.net/article/sentinelone-syslog-forwarder-to-siem-stack |
| 12 | |
| 13 | --- |
| 14 | |
| 15 | ## Architecture |
| 16 | |
| 17 | ``` |
| 18 | SentinelOne Cloud → TLS (mutual auth) → SIEM Stack |
| 19 | ``` |
| 20 | |
| 21 | --- |
| 22 | |
| 23 | ## Setup steps (high level) |
| 24 | |
| 25 | ### 1) Configure Syslog integration in SentinelOne |
| 26 | |
| 27 | - Log into the SentinelOne console |
| 28 | - Go to **Settings → Integrations** |
| 29 | - Select **Syslog** |
| 30 | |
| 31 | Set: |
| 32 | - **Host:** SIEM FQDN/IP |
| 33 | - **Port:** typically 6514 for TLS |
| 34 | - Enable **Use TLS secure connection** |
| 35 | - Syslog format: **RFC-5424** |
| 36 | |
| 37 | ### 2) Upload certificates (mutual TLS) |
| 38 | |
| 39 | You’ll typically upload: |
| 40 | - Root CA certificate |
| 41 | - Client certificate |
| 42 | - Client private key |
| 43 | |
| 44 | ### 3) Firewall rules |
| 45 | |
| 46 | Ensure inbound rules allow SentinelOne cloud endpoints to reach your syslog listener, and that internal routing allows traffic to Graylog. |
| 47 | |
| 48 | ### 4) Select event types |
| 49 | |
| 50 | In the integration’s Notifications tab, select which event categories to forward. |
| 51 | |
| 52 | ### 5) Test |
| 53 | |
| 54 | Use **Test Connection** and confirm events arrive in the SIEM. |
| 55 | |
| 56 | --- |
| 57 | |
| 58 | ## Troubleshooting |
| 59 | |
| 60 | - TLS handshake failures: validate PEM formats, chain, and expiry. |
| 61 | - Missing events: confirm event types selected + verify ingestion parsing. |
| 62 | - Connectivity: confirm firewall/NAT and correct port. |