Skip to main content
The Falcon Data Replicator (FDR) API provides access to event schemas that define the structure of security events streamed from CrowdStrike to external destinations like SIEM platforms, data lakes, and analytics tools.

Overview

Falcon Data Replicator enables:
  • Event streaming: Real-time replication of security events to external systems
  • Schema discovery: Understand event structures and available fields
  • SIEM integration: Configure data ingestion for security analytics platforms
  • Data lake population: Stream events to cloud storage for long-term retention
FDR uses a schema-based approach where events are defined by their structure (fields) and categorized by platform and event type.

Schema Overview

Get complete schema

Get-FalconReplicatorSchema
Returns all FDR schema information including fields and events. Example

Events

Events represent different types of security telemetry captured by the Falcon sensor.

Search for events

Get-FalconReplicatorEvent
string
Falcon Query Language expression to limit results
string
Property and direction to sort results. Options:
  • name.asc, name.desc
  • description.asc, description.desc
  • platform.asc, platform.desc
  • version.asc, version.desc
int
Maximum number of results per request
int
Position to begin retrieving results
switch
Retrieve detailed information
switch
Repeat requests until all available results are retrieved
switch
Display total result count instead of results
Example: List all Windows events
Example: Search for process-related events

Get event details by ID

Get-FalconReplicatorEvent
string[]
required
Event identifier(s)
Example

Fields

Fields represent individual data elements within events (e.g., process name, file hash, IP address).

Search for fields

Get-FalconReplicatorField
string
Falcon Query Language expression to limit results
string
Property and direction to sort results. Options:
  • name.asc, name.desc
  • description.asc, description.desc
  • type.asc, type.desc
  • universal.asc, universal.desc
  • values.asc, values.desc
int
Maximum number of results per request
int
Position to begin retrieving results
switch
Retrieve detailed information
switch
Repeat requests until all available results are retrieved
switch
Display total result count instead of results
Example: Find hash-related fields
Example: Search for IP address fields

Get field details by ID

Get-FalconReplicatorField
string[]
required
Field identifier(s)
Example

Common Workflows

Discover available events by platform

Map event schemas for SIEM

Find universal fields

Identify fields by data type

Build event field inventory

Analyze schema coverage

Prepare SIEM field mapping

Validate event availability

Understanding FDR Schema

Event Structure

Each FDR event has:
  • Name: Event identifier (e.g., ProcessRollup2)
  • Description: What the event represents
  • Platform: Operating system (Windows, Linux, Mac)
  • Version: Schema version
  • Fields: Array of field names included in the event

Field Structure

Each field has:
  • Name: Field identifier
  • Description: What the field contains
  • Type: Data type (string, integer, timestamp, etc.)
  • Universal: Whether the field appears across multiple event types
  • Values: Possible enumerated values (for certain fields)

Common Event Types

Common Field Types

SIEM Integration Tips

Field Mapping Strategy
  1. Start with universal fields - they provide consistent context across events
  2. Map timestamp fields for proper event ordering
  3. Include hash fields (SHA256, MD5) for threat intelligence correlation
  4. Map network fields (IPs, domains, ports) for network security analytics
  5. Include user and process context for investigation trails
Requires Falcon Data Replicator: Read permission.FDR subscription is required to stream events to external destinations. Contact CrowdStrike for licensing.
Schema versions may change over time. Regularly validate your field mappings against the current schema using these cmdlets.