
CrowdStrike EDR (for CTEM)
Outline
About this document
This guide shows you how to connect CrowdStrike EDR to SAFE to bring in the assets with the security alerts Falcon raised on them.
Introduction
CrowdStrike Falcon protects computers and servers. A small program called the Falcon sensor runs on each one, detects threats, and raises an alert when it sees something suspicious.
The CrowdStrike EDR integration brings two things into SAFE:
Hosts: the computers and servers that run the Falcon sensor.
Alerts: each open Falcon alert becomes one EDR finding in SAFE, shown on the host where it happened.
This integration does not bring in vulnerabilities or installed software. For those, use the CrowdStrike Exposure Management integration.
What SAFE pulls from CrowdStrike EDR
| What | Details |
|---|---|
| Assets | Computers and servers that run the Falcon sensor and that Falcon has seen within the Asset last seen days filter (30 by default). |
| Host details | Host name, IP address, external IP address, MAC address, serial number, operating system and version, manufacturer and model, BIOS vendor and version, Falcon sensor version, domain, status, first and last seen time, last logged-in user, and tags. |
| Findings | One EDR finding for each open Falcon alert, with its name, description and severity. |
| Not Supported | Vulnerabilities and installed software (use the CrowdStrike Exposure Management Integration to ingest these) |
Prerequisites and Permissions
You need:
A CrowdStrike Falcon account with the Falcon sensor installed on your hosts.
A Falcon user who can create API clients.
A SAFE account with admin access.
SAFE connects to CrowdStrike over the internet (HTTPS). You do not need to install anything or open any connection into SAFE.
The API client you create needs these permissions. Read access is enough.
- Hosts: Read - To bring in your hosts. Without it, Test Connection and the sync fail.
- Alerts: Read - To bring in the alerts. Without it, Test Connection and the sync fail.
- Host groups: Read - To add the Falcon host group name to each host as a tag. Without it, everything else still works.
Get your CrowdStrike connection details
You need three details from Falcon: the Base URL, the Client ID and the Client Secret.
- Log in to the CrowdStrike Falcon console.
- Open the menu and go to Support and resources > Resources and tools > Client Management.
- On the API clients tab, note the Base URL shown at the top of the page. Then click Create API client.
- Enter a name (for example SAFE EDR) and a short description.
- Mark Read for Alerts, Hosts and Host groups. You can type in the search box above the list to find each one. Leave everything else unticked.
- Click Create.
- Falcon shows the Client ID and Client Secret. Copy both and keep them safe. Copy the Client Secret now: Falcon shows it only once.
If you already have a CrowdStrike API client with Hosts: Read and Alerts: Read, you can use it instead of creating a new one.
Configure in SAFE
From the left menu, open Knowledge Graph, select First-party, then Integrations. Click the + button.
Search for CrowdStrike EDR and click the card.
Enter an Integration Name.
Enter the CrowdStrike Base URL, Client ID and Client Secret.
[Optional] Enter the API Filter. Limits which hosts are brought in, for example only hosts with a certain tag. See "Using the API Filter" below.
Enter the no of days in Asset last seen days filter field. Only hosts that Falcon has seen in the last number of days defined will be ingested.
[Optional] If required, mark the checkbox to Ingest Informational Alerts.
Click Test Connection.
Once verified, Click Save.
Click Sync Now to bring in your data in SAFE.
Using the API Filter
The API Filter lets you bring in only some hosts. You write it in CrowdStrike's filter language, called FQL. Only alerts on the hosts you bring in are shown in SAFE.
Examples:
| Filter | Brings in |
|---|---|
tags:'FalconGroupingTags/Prod' |
Hosts with the Falcon tag "Prod" |
tags:'FalconGroupingTags/Prod',tags:'FalconGroupingTags/DMZ' |
Hosts with the tag "Prod" or the tag "DMZ" |
platform_name:'Windows' |
Windows hosts only |
product_type_desc:'Server' |
Servers only |
platform_name:'Windows'+product_type_desc:'Server' |
Windows servers only |
platform_name:!'Mac' |
All hosts except Mac |
hostname:'prod-*' |
Hosts whose name starts with "prod-" |
machine_domain:'corp.example.com' |
Hosts in that Active Directory domain |
Notes:
- In a filter,
+means AND,,means OR,!means NOT, and*matches any text. Type values exactly as they appear in Falcon, including capital letters. - Test Connection checks that your filter works, but it does not apply the Asset last seen days filter. If your filter only matches hosts that Falcon has not seen in the last N days, Test Connection succeeds but the sync brings in nothing. If that happens, check the filter or increase the Asset last seen days filter.
What you will see in SAFE
Open the CrowdStrike EDR integration from Knowledge Graph > First-party > Integrations. It has two tabs: Finding View and Asset View.
Findings
One finding per alert. Each open Falcon alert becomes one EDR finding on its host. If the same threat is detected several times, you see one finding for each alert, as in Falcon.
Closed alerts are not shown. When an alert is closed in Falcon, its finding disappears from SAFE after the next sync.
Severity is the severity Falcon gave the alert: Critical, High, Medium or Low. If you tick Ingest Informational Alerts, those alerts show with severity None.
Open a finding to see its name, description, severity, status, first and last seen dates, and the host. The Sources tab shows that it came from CrowdStrike EDR.
Hosts
Only hosts that Falcon has seen in the last N days (Asset last seen days filter), and that match your API Filter if you set one, are brought in.
A host reported by CrowdStrike and by your other tools appears once in SAFE, matched by host name.
Each host gets these tags, which you can use in filters and smart groups:
- The tags the host has in Falcon
-
crowdstrike_group: <group name>(needs Host groups: Read) -
AD_DOMAIN: <domain>,SITE_NAME: <site>,ORGANIZATIONAL_UNIT: <ou> -
Crowdstrike-Policy-Prevention,Crowdstrike-Policy-Firewall,Crowdstrike-Policy-Remote-Response: whether each Falcon policy is applied -
Crowdstrike-Reduced-Functionality-Mode,Crowdstrike-RTR-State,Crowdstrike-Provision-Status: the state of the Falcon sensor
Important Notes
When you click Test Connection
If the test works, SAFE shows Test connection success. If it fails, you see one of these messages:
| Message | What it means and what to do |
|---|---|
| Missing base_url, client_id, or client_secret | The Base URL, Client ID or Client Secret is empty. Fill it in. |
| base_url must use https | The Base URL must start with https://. |
| CrowdStrike auth failed (<number>) | CrowdStrike did not accept the details. Check the Base URL, Client ID and Client Secret. |
| Failed to obtain CrowdStrike access token | CrowdStrike did not let SAFE log in. Check the Client ID and Client Secret. |
| CrowdStrike API client is missing the Hosts: Read scope | Give the API client Hosts: Read in Falcon. |
| CrowdStrike API client is missing the Alerts: Read scope | Give the API client Alerts: Read in Falcon. |
| API Filter rejected by CrowdStrike: <reason> | The API Filter is written incorrectly. Fix it using the examples in section 5. |
| API Filter matched no hosts in CrowdStrike | The filter is written correctly but no host matches it. Check the values in Falcon, including capital letters. |
| CrowdStrike API returned <number> | CrowdStrike returned an error. Try again later. |
When a sync fails
If CrowdStrike refuses a request or does not return all the data, the sync stops and shows one of these messages:
| Message | What it means and what to do |
|---|---|
| The integration API refused a request (HTTP <number>). Check that the API credentials can read all the data this integration syncs. | CrowdStrike refused the request. The API client has probably lost Hosts: Read or Alerts: Read. Check its permissions in Falcon. |
| Failed to retrieve data from the integration source. | CrowdStrike did not return all the data. If you use an API Filter, click Test Connection to check it. |
| API rate limit exceeded. Please try again later. | CrowdStrike received too many requests. SAFE already retried. Try again later. |
| The integration API returned a server error. Please try again later. | CrowdStrike had a problem on its side. SAFE already retried. Try again later. |
Frequently asked questions
Q: How often does SAFE sync?
A: Every day by default. You can change this with Auto Sync, or click Sync Now at any time.
Q: Does SAFE change anything in CrowdStrike?
A: No. SAFE only reads data.
Q: Hosts came in, but there are no EDR findings.
A: Check that the hosts have open alerts in Falcon. Closed alerts are not shown. If all the alerts are Informational, tick Ingest Informational Alerts.
Q: SAFE shows fewer findings than Falcon shows alerts.
A: SAFE does not show closed alerts, alerts from other CrowdStrike products such as identity or cloud, or Informational alerts unless you tick the setting. It also does not show alerts on hosts outside your Asset last seen days filter or API Filter.
Q: The same alert appears several times on one host.
A: Each Falcon alert is its own finding. If Falcon detected the same threat several times, it raised several alerts, so you see several findings.
Q: Hosts have no host group tags.
A: Give the API client Host groups: Read in Falcon, then sync again.
Q: Can I use the same API client as the CrowdStrike Exposure Management card?
A: Yes, as long as it has Hosts: Read and Alerts: Read.
Q: Does SAFE bring in old alerts?
A: Yes. Every open alert on your hosts is brought in on every sync, however old it is.
Did this article help?
Let us know by leaving a star rating at the top of this article.
