CrowdStrike Logs
Connecting CrowdStrike logs to your Panther Console
Overview
Panther supports pulling logs directly from CrowdStrike events by integrating with the CrowdStrike Falcon Data Replicator (FDR).
As of Panther version 1.52, all new CrowdStrike log source configurations will use the Crowdstrike.FDREvent schema.
CrowdStrike logs video walkthrough
How to onboard CrowdStrike logs to Panther
Prerequisites
You must have an active subscription to FDR, and it must be enabled in CrowdStrike.
There is no minimum version of FDR required.
Step 1: Create FDR API Keys
Log in to your CrowdStrike Falcon console.
Navigate to the API Clients and Keys page.
Click Create new credentials under the FDR AWS S3 Credentials and SQS Queue section.
Copy the Client ID, Secret ID, and SQS URL and store them in a secure location. You will need them in the next steps.

Step 2: Create a new CrowdStrike Source in Panther
In the left-hand navigation bar of your Panther Console, click Configure > Log Sources.
Click Create New.
Select CrowdStrike from the list of available log sources. Click Start Setup.
Fill in the fields below:
Name: Enter a descriptive name for the source, e.g.
CrowdStrike Falcon.SQS URL: Enter the URL for the CrowdStrike-managed SQS queue, previously copied.
AWS Access Key, AWS Access Secret: Enter the AWS access key and secret that you copied in the previous steps.

Click Setup. You will be directed to a success screen:

You can optionally enable one or more Detection Packs.
The Trigger an alert when no events are processed setting defaults to YES. We recommend leaving this enabled, as you will be alerted if data stops flowing from the log source after a certain period of time. The timeframe is configurable, with a default of 24 hours.

Panther-built detections
See Panther's built in rules for CrowdStrike in panther-analysis in Github.
Supported log types
Crowdstrike.FDREvent
Crowdstrike.FDREvent contains all event types produced by the FDR. Including all types of events in a single log type helps to:
Provide ongoing ingestion flexibility and reduce maintenance efforts.
For example, if CrowdStrike adds a new event type, you may not need to rewrite existing detection logic and data queries.
Simplify querying of CrowdStrike logs by enriching all
Crowdstrike.FDREventlogs with commonly referenced fields, such asevent_simpleName.Expedite investigations by leveraging the indicators extracted from each FDR event type and stored in
Crowdstrike.FDREvent.
FDR events
The FDR data stream sends the following two types of events:
Primary events
These events include information related to threat hunting, archiving data, warehousing data, and SIEM activity.
A complete list of primary event types supported by
Crowdstrike.FDREventcan be viewed on CrowdStrike's documentation on streaming API events.
Secondary events
These events include additional environment information.
A complete list of secondary event types supported by
Crowdstrike.FDREventcan be viewed on CrowdStrike's documentation on data for seeing additional environment information.
How fdr_event_type is set
fdr_event_type is setNot all FDR events contain the same fields. To accommodate this, the value of fdr_event_type is assigned dynamically, according to the following rules (ordered by precedence):
If
event_simpleNameis present,fdr_event_type=event_simpleNameIf
event_typeis present,fdr_event_type=event.event_typeIf
ExternalApiTypeis present,fdr_event_type=event.ExternalApiTypeCrowdstrike.DetectionSummaryandCrowdstrike.ActivityAuditlog types define thisExternalApiTypefield.
If the FDR event is a secondary event,
fdr_event_type= the event type as described in CrowdStrike's documentation on seeing additional environment information.In this case, the resulting log type is still
Crowdstrike.FDREvent.
If none of the above conditions are met,
fdr_event_type=unknown
For more information, see CrowdStrike's FDR setup documentation.
Legacy log types
Existing CrowdStrike log source configurations set up prior to Panther version 1.52 will continue to function using the legacy log types below, until you transition them to Crowdstrike.FDREvent. Please contact your Panther support team if you would like assistance with this transition.
Crowdstrike.AIDMaster
Sensor and Host information provided by Falcon Insight.
Reference: CrowdStrike Documentation on Falcon Data Replicator.
Crowdstrike.ActivityAudit
Contains activity audit information.
Reference: CrowdStrike Documentation on Streaming API Event Authentication.
Crowdstrike.AppInfo
Detected Application Information provided by Falcon Discover.
Reference: CrowdStrike Documentation on Falcon Data Replicator AppInfo.
Crowdstrike.CriticalFile
This event is generated every time a critical file is accessed or modified.
Reference: CrowdStrike Documentation on CriticalFile.
Crowdstrike.DNSRequest
This event is generated for every attempted DNS name resolution on a host.
Reference: CrowdStrike Documentation on DNSRequest.
Crowdstrike.DetectionSummary
Detection Summary events include multiple detections, when multiple malicious behaviors are detected.
Reference: CrowdStrike Documentation on Streaming API Detection Summary.
Crowdstrike.GroupIdentity
Provides the sensor boot unique mapping between GID, AuthenticationId, UserPrincipal, and UserSid. Available only for the Mac platform.
Reference: CrowdStrike Documentation on Group Identity Events.
Crowdstrike.ManagedAssets
Sensor and Host information provided by Falcon Insight (Network Information: IP Address, LAN/Ethernet Interface, Gateway Address, MAC Address).
Reference: CrowdStrike Documentation on Falcon Data Replicator Managed Assets.
Crowdstrike.NetworkConnect
This event is generated when an application attempts a remote connection on an interface.
Reference: CrowdStrike Documentation on NetworkConnect.
Crowdstrike.NetworkListen
This event is generated when an application establishes a socket in listening mode.
Reference: CrowdStrike Documentation on NetworkListen.
Crowdstrike.NotManagedAssets
Unmanaged Host discovery information provided by Falcon Insight.
Reference: CrowdStrike Documentation on Falcon Data Replicator Notmanaged Assets.
Crowdstrike.ProcessRollup2
This event (often called "PR2" for short) is generated for a process that is running or has finished running on a host and contains information about that process.
Reference: CrowdStrike Documentation on ProcessRollup2.
Crowdstrike.ProcessRollup2Stats
When a process finishes running, the sensor generates and sends a ProcessRollup2 event. Mac and Linux sensors send far more ProcessRollup2 events than Windows (roughly 20x as many), so rather than send events for every process on those hosts, the sensor sends an initial ProcessRollup2 event, followed 10 minutes later by a ProcessRollup2Stats event with a SHA256 hash and the count of how many times the hash executed in the last 10 minutes.
Reference: CrowdStrike Documentation on ProcessRollup2Stats.
Crowdstrike.SyntheticProcessRollup2
A synthetic version of the process rollup (PR2) event.
Reference: CrowdStrike Documentation on SyntheticProcessRollup2.
Crowdstrike.Unknown
This schema contains all the Crowdstrike events that don't match to any of the registered types.
Reference: CrowdStrike Documentation on API Event Types.
Crowdstrike.UserIdentity
The UserIdentity event is generated when a user logs in to a host. It conveys important security-related characteristics associated with a user to the CrowdStrike cloud, such as the user name. It’s normally generated once per security principal, and is thus not on its own a sign of a suspicious activity. Available for Mac & Windows platforms.
Reference: CrowdStrike Documentation on User Identity Events.
Crowdstrike.UserInfo
User Account & Logon information provided by Falcon Discover.
Reference: CrowdStrike Documentation on Falcon Data Replicator UserInfo.
Crowdstrike.UserLogonLogoff
Contains the UserLogon and UserLogoff events.
Last updated
Was this helpful?

