Send CrowdStrike Falcon logs to LogPulse

Raw Falcon sensor telemetry through the Falcon Data Replicator: process starts, detections, logons and persistence, with hostnames resolved from the aidmaster files.

In short
To send CrowdStrike Falcon logs to LogPulse, add CrowdStrike Falcon under Configure → Sources → Cloud. LogPulse reads the Falcon Data Replicator (S3 and SQS) itself, without an agent. Events land in the endpoint, network, dns indexes with source crowdstrike and fill the Endpoint, Authentication, Alert data models.

Overview

How CrowdStrike Falcon data reaches LogPulse
Vendor
Falcon Data Replicator (S3 and SQS)
Collect
Integration pollerreads new events, maps the fields
Store
index=endpoint
index=network
index=dns
  1. Falcon Data Replicator (S3 and SQS) to Integration poller
  2. Integration poller to index=endpoint
  3. Integration poller to index=network
  4. Integration poller to index=dns

LogPulse signs in to CrowdStrike Falcon with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.

What you need

  • Falcon Data Replicator turned on for your CID (ask CrowdStrike support if it is not)
  • The FDR SQS URL, client ID and secret from the Falcon console
  • In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.

1. Create a credential in CrowdStrike Falcon

Field in LogPulseWhere you find it
SQS queue URLShown in the Falcon console under Support and resources, Falcon data replicator.
Client ID (access key)The FDR client ID from the same page in the Falcon console.
SecretStored encrypted and never shown again.
Falcon API URL (optional)Your Falcon cloud: api.crowdstrike.com (US-1), api.us-2.crowdstrike.com, api.eu-1.crowdstrike.com. Empty means US-1.
Falcon API client ID (optional)An API client with the Hosts scope, Read and Write. The FDR key above cannot contain hosts.
Falcon API client secret (optional)Stored encrypted and never shown again.

2. Add the integration in LogPulse

Go to Configure → Sources → Cloud and choose CrowdStrike Falcon. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.

Tip: Secrets are stored encrypted and never shown again. To change one, paste a new value; the rest stays.

What arrives

Data sourceIndexSourceSourcetypeWhat it holds
Process eventsendpointcrowdstrikecrowdstrike_processProcessRollup2: every process start with image, command line, parent and hash.
Detectionsendpointcrowdstrikecrowdstrike_detectionFalcon detection summaries with severity, tactic and technique.
User logonsendpointcrowdstrikecrowdstrike_logonUserLogon and UserLogonFailed2 with logon type and remote IP.
Persistenceendpointcrowdstrikecrowdstrike_persistenceScheduled tasks, ASEP registry changes, services and newly written executables.
Network connections (off by default)networkcrowdstrikecrowdstrike_networkNetworkConnect, ReceiveAccept and Listen events. High volume.
DNS requests (off by default)dnscrowdstrikecrowdstrike_dnsDomain lookups per process. High volume.

The index is the kind of data and the source is the product, so detection rules for that kind of data find CrowdStrike Falcon without changes.

Note: CrowdStrike drops sensor data in an S3 bucket and announces each batch on an SQS queue. LogPulse reads the queue, downloads each batch and keeps only the event types you turned on; the rest is dropped before it counts towards your volume.
Note: Falcon Data Replicator must be turned on for your CID. Ask CrowdStrike support when it is not.
Note: The Falcon API client is optional and separate: it is only used when you let LogPulse contain a host as a response action.

Fields and data models

Data modelWhat you get
EndpointProcessRollup2, persistence and network events with the endpoint fields, and hostnames from the aidmaster files.
AuthenticationUserLogon and UserLogonFailed2 as success and failure.
AlertFalcon detection summaries in the shared alert shape.

Events are mapped to the data models above, with the same field names as other sources of the same kind. See field names.

The original record of CrowdStrike Falcon is kept with each event under raw, so nothing the vendor sent is lost.

3. Check the data

The first events arrive within a few minutes. Check what came in:

earliest=-1h index IN (endpoint, network, dns) source IN (crowdstrike)
| stats count by index, source, sourcetype

The integration page in LogPulse shows when it last read events and the last error, if any.

Troubleshooting

The connection test names what is wrong. These are the answers you are most likely to see.

What you seeWhat to do
AWS refused the key. Use the FDR client ID and secret from the Falcon console (Support and resources, Falcon data replicator) and the SQS URL shown there.Copy all three values again from that page in the Falcon console.
sqsQueueUrl must be https://sqs.<region>.amazonaws.com/<account>/<queue>Copy the SQS URL from the same page in the Falcon console.
There is no FDR page in the Falcon console.Falcon Data Replicator is not turned on for your CID. Ask CrowdStrike support to enable it.
The test passes but no events arrive.Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. CrowdStrike Falcon may also simply have had nothing new.

Frequently asked questions

How do I send CrowdStrike Falcon logs to LogPulse?
Add the CrowdStrike Falcon cloud integration under Configure, Sources, Cloud in LogPulse and fill in SQS queue URL, Client ID (access key), Secret. LogPulse reads the Falcon Data Replicator (S3 and SQS) itself, every five minutes by default; there is nothing to install.
Which permissions does LogPulse need in CrowdStrike Falcon?
Falcon Data Replicator turned on for your CID (ask CrowdStrike support if it is not). The FDR SQS URL, client ID and secret from the Falcon console. Read access is enough for collecting logs.
Which index does CrowdStrike Falcon data go to?
The index is the kind of data: endpoint, network, dns. The source is the product: crowdstrike. Each data source has its own sourcetype, listed on this page.
Which data models does CrowdStrike Falcon fill?
Endpoint, Authentication, Alert. Detection rules and dashboards written for a data model work on CrowdStrike Falcon without changes.
Why is Network connections and DNS requests off by default?
To keep your daily ingest down until you need it: Network connections, DNS requests are high volume or of use to fewer teams. Tick the data source in the integration to switch it on.
Does every Falcon event count towards my LogPulse volume?
No. LogPulse keeps only the event types of the data sources you turned on and drops the rest before it is stored.