Send events to CrowdStrike Falcon Next-Gen SIEM
Devices send events over HTTPS directly to Falcon Next-Gen SIEM. No extra software needed.
What you need
- An Enterprise plan.
- Falcon Next-Gen SIEM with Administrator or Connector Manager rights.
- For Splunk, pick Splunk HEC as the destination in step 2.
Step 1: Create the connector in Falcon
- Open Next-Gen SIEM > Data ingestion > Data connectors > Add connection.
- Pick HEC / HTTP Event Connector.
- Choose a parser. A parser that starts with
parseJson()is enough. - Save, then click Generate API key. Copy the API URL and the API key.
Step 2: Enter it in the console
- Open Settings > SIEM (Falcon / Splunk).
- Set Destination to CrowdStrike Falcon Next-Gen SIEM.
- Paste the URL into API URL. It must start with
https://. - Paste the key into API key.
- Leave Sourcetype (optional) empty, so the connector's parser applies.
- Click Save SIEM settings.
The console never shows the key again. If you change the host in the URL, enter the key again.
Step 3: Check that events arrive
In Falcon, the connector status turns Active. This search shows all PoisonZero events:
observer.vendor = "PoisonZero"
On a device, run poison0 doctor. The SIEM line names the Falcon host:
SIEM export: hec to <host> (hec from the console)
| What you see | What to do |
|---|---|
SIEM export: off | The device has not taken the setting yet. Wait for the next config poll, or apply a new client config on a private device. |
hec from the console is invalid | The device rejected the setting. Run poison0 doctor as administrator to see the reason. |
run doctor as administrator for details | The service has not reported its state yet. Run poison0 doctor as administrator. |
poison0 doctor shows hec, but nothing arrives | Check the API key and use the API URL exactly as Falcon shows it. The service log names the rejected batches. |
What is sent
Every audit event, allow included. Filter on event.action:
| event.action | Meaning |
|---|---|
quarantine_reversible | PoisonZero quarantined a dangerous change. It can be restored. |
detected_kept | PoisonZero found a suspicious change and left the file unchanged. |
allow | A checked change was accepted. Hide it if you only want findings. |
toolgate_denied | exec0 blocked a tool call of an agent. |
leak0_blocked | leak0 blocked a tool call or prompt that would leak a secret. |
leak0_dlp_incident | leak0 DLP reported an incident in Compliance mode. |
File content, prompts and evidence quotes never leave the device. All fields and actions: SIEM export.
Cloud and private devices
- Cloud devices apply the setting at the next config poll, without a restart.
- Private devices take it from the signed client config at the next service start.
Read next
SIEM export (local files, private devices, setup without the console). Incidents and audit. OpenTelemetry export. Google Security Operations (Google SecOps, SIEM).