CrowdStrike Falcon host sync
Airgate reads the hosts from the CrowdStrike Falcon Hosts API and writes their state (sensor found, containment status, platform, Zero Trust Assessment score…) to the matching device records. Access policies can then admit only devices with a healthy Falcon sensor and quarantine contained hosts.
How it works
Section titled “How it works”- Airgate lists every host (
/devices/queries/devices-scroll/v1), loads the details in batches (/devices/entities/devices/v2) and, optionally, the Zero Trust Assessment scores, every sync interval (default every hour). - Matching by MAC. Each host is written to the device records of the
MACs the sensor reports: the main MAC (
mac_address) and the connection MAC (connection_mac_address). - With Intune device-ID matching, the Falcon facts of an Intune device (found by its hardware MACs or serial number) are added to EAP-TLS sign-ins even with a private Wi-Fi address.
- Hosts that leave Falcon get
CrowdStrike System Found = false. - The attribute names match the ClearPass CrowdStrike extension.
Before you begin
Section titled “Before you begin”- A Falcon role that can create API clients (Falcon Administrator).
- An Airgate administrator with
admin:write. - Airgate reaches your Falcon API host over HTTPS.
Step 1: Create an API client in Falcon
Section titled “Step 1: Create an API client in Falcon”- In the Falcon console, open Support and resources › API clients and keys › Create API client.
- Give it the scope Hosts: Read. Add Zero Trust Assessment: Read if you want the scores. No write scopes are needed.
- Copy the Client ID and the Secret (shown once), and note the Base URL shown on the page: it tells you your cloud.
Step 2: Connect CrowdStrike in Airgate
Section titled “Step 2: Connect CrowdStrike in Airgate”-
Open Integrations › CrowdStrike Falcon.
-
In Connect CrowdStrike Falcon, enter:
Field Value Cloud US-1 (api.crowdstrike.com), US-2 (api.us-2.crowdstrike.com), EU-1 (api.eu-1.crowdstrike.com) or US-GOV-1 (api.laggar.gcw.crowdstrike.com), matching the Base URL Client ID from Step 1 Client secret from Step 1 (stored encrypted) Fetch Zero Trust Assessment scores on to add the CrowdStrike Assessment …scores (needs the Zero Trust Assessment scope)Sync hosts on, with the interval -
Select Connect, then Test connection. A success shows “Falcon Hosts API reachable (N hosts)”. The first sync starts within a minute.
-
Sync now starts a sync within 30 seconds.
To sync only some hosts, set the key host_filter in the context server’s
config through the API (PUT /api/v1/t/{tenant}/context-servers/{id}).
Its value is a Falcon Query Language filter passed to the hosts query, for
example platform_name:'Windows'.
Step 3: Use CrowdStrike in access policies
Section titled “Step 3: Use CrowdStrike in access policies”Use enforcement conditions on the endpoint attributes, for example:
| When | Then |
|---|---|
CrowdStrike System Found EQUALS true and CrowdStrike Status EQUALS normal |
Allow, corporate role |
CrowdStrike Status EQUALS contained |
Deny or quarantine |
CrowdStrike Assessment Overall LESS_THAN 50 |
Remediation role |
On Access › Access policies, a rule can test CrowdStrike sensor
(Installed (found in CrowdStrike) / Not found, from
CrowdStrike System Found) and CrowdStrike containment (Not contained
(normal) / Network contained, from CrowdStrike Status). Other
attributes, such as the Zero Trust Assessment score, are tested with
conditions on Endpoint:CrowdStrike … added through the API
(/api/v1/t/{tenant}/enforcement-policies); the Access policies page shows
such conditions as they are and keeps them when you save.
Attributes written
Section titled “Attributes written”| Attribute | Value |
|---|---|
CrowdStrike System Found |
true while the host is in Falcon, false once removed |
CrowdStrike Status |
normal, containment_pending, contained, lift_containment_pending |
CrowdStrike Provision Status |
Provisioned, NotProvisioned |
CrowdStrike Reduced Functionality Mode |
no, yes |
CrowdStrike Platform Name, CrowdStrike OS Version, CrowdStrike OS Build |
for example Windows |
CrowdStrike Agent Version, CrowdStrike First Seen, CrowdStrike Last Seen |
sensor |
CrowdStrike Hostname, CrowdStrike Local IP, CrowdStrike External IP, CrowdStrike MAC Address, CrowdStrike Connection MAC Address |
network |
CrowdStrike Serial Number, CrowdStrike System Manufacturer, CrowdStrike System Product Name, CrowdStrike BIOS Manufacturer, CrowdStrike BIOS Version |
hardware |
CrowdStrike Tags, CrowdStrike Groups, CrowdStrike Policies |
comma-separated |
CrowdStrike Device ID, CrowdStrike Cid |
identifiers |
CrowdStrike Assessment Overall, CrowdStrike Assessment OS, CrowdStrike Assessment Sensor Config |
0 to 100, with Zero Trust scores on |
Verify
Section titled “Verify”- The status tiles show Hosts synced, Last sync, Next sync and Connection OK.
- Hosts from CrowdStrike Falcon lists the hosts with Status, Platform, Sensor, ZTA score and Last seen.
- Devices › Devices › a MAC › Attributes: the
CrowdStrike …attributes.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| Connection failed with an OAuth error | Wrong client ID or secret, or the wrong Cloud. | Check the values and pick the cloud of the Base URL. |
The last sync failed: crowdstrike /devices/queries/devices-scroll/v1 HTTP 403: … |
The API client lacks Hosts: Read. | Add the scope in Falcon. |
Sync fails on /zero-trust-assessment/… with HTTP 403 |
Zero Trust scores are on without the scope. | Add Zero Trust Assessment: Read, or turn the scores off. |
| A host is not matched | Its sensor reports a MAC the device does not use on the network (docking station, private Wi-Fi address). | Use Intune device-ID matching, or another rule for these devices. |