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

Walkthrough video showing how to onboard CrowdStrike logs to Panther

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

  1. Log in to your CrowdStrike Falcon console.

  2. Navigate to the API Clients and Keys page.

  3. Click Create new credentials under the FDR AWS S3 Credentials and SQS Queue section.

  4. Copy the Client ID, Secret ID, and SQS URL and store them in a secure location. You will need them in the next steps.

The Crowdstrike admin console is open to the "API Clients and Keys" screen. Under the header "FDR AWS S3 Credentials and SQS Queue" there is a red circle around the Client ID, Created Date, and SQS URL.

Step 2: Create a new CrowdStrike Source in Panther

  1. In the left-hand navigation bar of your Panther Console, click Configure > Log Sources.

  2. Click Create New.

  3. Select CrowdStrike from the list of available log sources. Click Start Setup.

  4. 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. The image shows the configuration fields for the Crowdstrike integration in the Panther Console. There are fields for Name, SQS URL, AWS Access Key, and AWS Access Secret.

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

    The success screen reads, "Everything looks good! Panther will now automatically pull & process logs from your account"
    • 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.

      The "Trigger an alert when no events are processed" toggle is set to YES. The "How long should Panther wait before it sends you an alert that no events have been processed" setting is set to 1 Day

Panther-built detections

See Panther's built in rules for CrowdStrike in panther-analysis in Github.

Supported log types

Required fields in the schema are listed as "required: true" just below the "name" field.

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.FDREvent logs with commonly referenced fields, such as event_simpleName.

  • Expedite investigations by leveraging the indicators extracted from each FDR event type and stored inCrowdstrike.FDREvent.

FDR events

The FDR data stream sends the following two types of events:

How fdr_event_type is set

Not 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):

  1. If event_simpleName is present, fdr_event_type = event_simpleName

  2. If event_type is present, fdr_event_type = event.event_type

  3. If ExternalApiType is present, fdr_event_type = event.ExternalApiType

    • Crowdstrike.DetectionSummary and Crowdstrike.ActivityAudit log types define this ExternalApiType field.

  4. 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.

  5. 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.

Reference: CrowdStrike Documentation on User Logon Logoff.

Last updated

Was this helpful?