Falcon data source
Falcon (by CrowdStrike) is an endpoint detection and response (EDR) platform that monitors devices for malicious activity and helps respond to threats.
The Falcon data source uses an API connection to bring Falcon data into Data Manager.
This task requires Data Manager & Adapters admin permissions to complete. See how permissions and roles work in Data Manager.
How to connect Falcon to Data Manager
Gather all of the Data Manager type information, including the data source name, short display name, and the data source type.
Gather the Falcon fields – this may require consultation with the Falcon subject matter expert (SME).
In Data Manager, add a new data source by selecting the tool you which to connect and configure with all the gathered information.
Each time this data source is fetched the data becomes raw data.
Data Manager fields
You need to specify the following information from Data Manager:
Data source name – the name of the data source used to run, transform, map, cleanse, and import the data.
Short display name – a unique name as a data source label.
Data source type – what type of data the tool is providing. For example, Assets, CMDB, user location.
Falcon fields
API URL – base API URL for your CrowdStrike instance.
Client ID – created when the API client is set up.
Client secret – secret string created with the API client.
API limit – sets the page size of API results (number of records per call).
Default:
5000Recommended:
1000for heavily populated sourcesRange:
1–5000
Authentication and authorization
Create API clients to grant API access.
From API Clients and Keys, select Add new API client.
Provide:
Client name (required)
Description (optional)
API scopes
Click Add to generate Client ID and secret.
API calls
Retrieve device IDs:
API:
{api-url}/devices/queries/devices-scroll/v1?limit={apiLimit}Method:
GETResponse:
meta(query_time, pagination, powered_by, trace_id)resources(list of IDs)errors
Retrieve device details for those IDs:
API:
{api-url}/devices/entities/devices/v2Method:
POSTResponse: fields below.
The following fields are retrieved:
DeviceId
Cid
AgentLoadFlags
AgentLocalTime
AgentVersion
BiosManufacturer
BiosVersion
ConfigIdBase
ConfigIdBuild
ConfigIdPlatform
CpuSignature
ExternalIp
MacAddress
InstanceId
ServiceProvider
ServiceProviderAccountId
Hostname
FirstSeen
LastSeen
LocalIp
MajorVersion
MinorVersion
OsVersion
PlatformId
PlatformName
ReducedFunctionalityMode
PreventionPolicyId
PreventionApplied
PreventionSettingsHash
PreventionAssignedDate
PreventionAppliedDate
SensorUpdatePolicyId
SensorUpdateApplied
SensorUpdateSettingsHash
SensorUpdateAssignedDate
SensorUpdateAppliedDat
SensorUpdateUninstallProtection
DeviceControlPolicyId
DeviceControlApplied
DeviceControlAssignedDat
DeviceControlAppliedDate
GlobalConfigPolicyId
GlobalConfigApplied
GlobalConfigSettingsHash
GlobalConfigAssignedDate
GlobalConfigAppliedDat
RemoteResponsePolicyId
RemoteResponseApplied
RemoteResponseSettingsHash
RemoteResponseAssignedDate
RemoteResponseAppliedDate
AirlockPolicyId
AirlockApplie
AirlockSettingsHash
AirlockAssignedDate
AirlockAppliedDate
AirlockVersion
FirewallPolicyId
FirewallApplied
FirewallAssignedDate
FirewallAppliedDate
FirewallRuleSetId
Groups
GroupHash
ProductTypeDesc
SerialNumber
Status
SystemManufacturer
SystemProductName
Tags
ModifiedTimestamp
QueryTim
PoweredBy
TraceId
Version
VersionString
ZoneGroup
KernelVersion
ChassisType
ChassisTypeDesc
ConnectionIp
DefaultGatewayIp
ConnectionMacAddress
LinuxSensorMode
DeploymentType
ProvisionStatus
BuildNumber
OsBuild
Ous
ManagedAppsAirlockPolicyId
ManagedAppsAirlockApplied
ManagedAppsAirlockSettingsHash
ManagedAppsAirlockAssignedDate
ManagedAppsAirlockAppliedDate
ManagedAppsAirlockVersion
ProductType
ServicePackMinor
PointerSize
SiteName
OsProductName
LastReboot
MachineDomain
ServicePackMajor
DetectionSuppressionStatusAtlassian vendor mappings
When you connect a CrowdStrike Falcon data source, Data Manager applies the following Atlassian vendor mappings. These source attributes are mapped to a destination attribute automatically; you can review or override any of them on the Attribute Mapping screen.
Source attribute | Destination attribute | Type | Primary key |
|---|---|---|---|
AgentVersion | AgentVersion | String | No |
BiosManufacturer | BiosManufacturer | String | No |
ExternalIp | IPAddress | String | No |
HostName | Name | String | Yes |
OsVersion | OperatingSystem | String | No |
ProvisionStatus | ProvisionStatus | String | No |
SerialNumber | SerialNumber | String | No |
Status | Status | String | No |
Was this helpful?