> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/siem-integrations/endpoint-protection/crowdstrike.md).

# CrowdStrike Falcon

Connect CrowdStrike Falcon to ThreatDefence so our SOC can monitor your endpoint detections around the clock, contain compromised hosts on your behalf, and investigate incidents with full context.

The integration uses Falcon's OAuth2 API. You create one API client for ThreatDefence and grant it the permissions listed in Step 2. That one client covers:

| Capability                          | What it enables                                                                                                    | Needed?               |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------ | --------------------- |
| Monitoring                          | Detections, audit activity, asset and vulnerability context flow into ThreatDefence for 24×7 monitoring            | Required              |
| Containment                         | Our analysts can network-contain a compromised host, and lift containment, from the ThreatDefence platform         | Required              |
| Investigation                       | Our analysts can investigate incidents in depth: process trees, telemetry search, threat intelligence              | Required              |
| Live triage and evidence collection | Our analysts can run read-only commands on an affected host and collect evidence from it during an active incident | Optional, recommended |

Keeping these as separate API clients means you can revoke response or investigation access at any time without interrupting monitoring.

{% hint style="info" %}
**Before you begin:**

* Sign in to the Falcon console with an account that holds the **Falcon Administrator** role. Only that role can create API clients.
* Decide which of the API clients above you want to create.
* Note your Falcon cloud (Step 1).
  {% endhint %}

***

### Step 1: Identify your Falcon cloud region

Find the cloud in your Falcon console URL, or under **Support and resources → API clients and keys**, where the base URL is shown above the client list.

| Falcon cloud | API Base URL                             |
| ------------ | ---------------------------------------- |
| US-1         | `https://api.crowdstrike.com`            |
| US-2         | `https://api.us-2.crowdstrike.com`       |
| EU-1         | `https://api.eu-1.crowdstrike.com`       |
| US-GOV-1     | `https://api.laggar.gcw.crowdstrike.com` |

{% hint style="info" %}
**Note:** Always use the base URL your own console shows. Credentials created in one cloud don't work against another.

Reference: [Crowdstrike API Regional URLs](https://developer.crowdstrike.com/falcon-mcp/getting-started/credentials/#api-region-urls)
{% endhint %}

***

### Step 2: Create the ThreatDefence SIEM API client (required)

1. Go to **Support and resources → API clients and keys** and select **Create API client**.
2. Name it **ThreatDefence** and add a description such as "ThreatDefence 24×7 SOC monitoring and response".
3. Grant the permissions in the tables below. A scope appears on this screen only if your tenant licenses the matching Falcon product, so grant every listed scope your console shows.

**Monitoring**

| API scope                | Permission | What ThreatDefence uses it for                                                                                                   |
| ------------------------ | ---------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Alerts                   | Read       | All Falcon detections (endpoint, identity, cloud, mobile, Next-Gen SIEM, OverWatch) and their status changes                     |
| Event streams            | Read       | Falcon console audit activity: user logins, policy changes, API client and user changes, Real Time Response sessions             |
| Hosts                    | Read       | Host inventory and sensor health: sensor version, last seen, containment status, hidden hosts, user login and IP address history |
| Cases                    | Read       | CrowdStrike cases, which replace the retired Incidents API                                                                       |
| Real time response audit | Read       | A record of every Real Time Response session and command run on your hosts, by any user                                          |

**Context and posture**

| API scope                                    | Permission | Falcon module                         | What ThreatDefence uses it for                                                                                                                        |
| -------------------------------------------- | ---------- | ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| Vulnerabilities                              | Read       | Falcon Spotlight                      | Open vulnerabilities per host, for prioritization and reporting, and whether a vulnerability was the way in                                           |
| Zero Trust Assessment                        | Read       | Falcon Insight / ZTA                  | Per-host posture scores                                                                                                                               |
| Assets                                       | Read       | Falcon Discover / Exposure Management | Installed applications, accounts and logins                                                                                                           |
| Identity Protection Entities                 | Read       | Falcon Identity Protection            | Account and identity risk context                                                                                                                     |
| Identity Protection Timeline                 | Read       | Falcon Identity Protection            | Authentication activity (Kerberos, NTLM, LDAP)                                                                                                        |
| Identity Protection Detections               | Read       | Falcon Identity Protection            | Detection detail for identity-related incidents                                                                                                       |
| Identity Protection GraphQL                  | Write      | Falcon Identity Protection            | Lets the read-only identity queries above run. CrowdStrike labels this scope Write because queries are POST requests; it can't modify identity policy |
| Quarantined files                            | Read       | Falcon Prevent                        | Files Falcon quarantined, and their status                                                                                                            |
| IOC Management                               | Read       | Any                                   | Your custom indicators (blocked hashes, domains, IPs)                                                                                                 |
| Monitoring rules (Falcon Intelligence Recon) | Read       | Falcon Intelligence Recon             | Dark-web and credential-exposure notifications                                                                                                        |
| Firewall Management                          | Read       | Falcon Firewall                       | Host firewall events                                                                                                                                  |
| FileVantage                                  | Read       | Falcon FileVantage                    | File integrity monitoring changes                                                                                                                     |
| On-demand scans (ODS)                        | Read       | Falcon Prevent                        | On-demand scan findings                                                                                                                               |
| Cloud Security API Detections                | Read       | Falcon Cloud Security                 | New cloud misconfigurations                                                                                                                           |
| Falcon Container Image                       | Read       | Falcon Cloud Security                 | Container image detections and vulnerabilities                                                                                                        |
| SaaS Security                                | Read       | Falcon Shield                         | SaaS security alerts                                                                                                                                  |

**Containment**

Every containment action is recorded in ThreatDefence with the analyst's name and the reason, and Falcon also logs it in its own audit trail.

| API scope | Permission | What ThreatDefence uses it for                                                                                                        |
| --------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Hosts     | Write      | Contain a host to stop an attack spreading, and lift containment once it's remediated. ThreatDefence uses only those two host actions |
| Alerts    | Write      | Update a detection's status and add comments, so your Falcon console shows the SOC's progress                                         |

**Investigation**

Together with the scopes above, these give ThreatDefence analysts, and the AI-assisted investigation tools they supervise, the read access needed to investigate an incident end to end.

| API scope                                                                   | Permission | What ThreatDefence uses it for                                                        |
| --------------------------------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------- |
| Threatgraph                                                                 | Read       | Process trees and how a threat moved between hosts                                    |
| IOCs (Indicators of Compromise)                                             | Read       | Where else a file hash or domain was seen in your estate                              |
| NGSIEM                                                                      | Read       | Search raw Falcon telemetry (processes, network, DNS, logons) during an investigation |
| Actors, Reports, Indicators (Falcon Intelligence)                           | Read       | Threat-actor and indicator context, if you license Falcon Intelligence                |
| Prevention policies, Sensor update policies, Response policies, Host groups | Read       | Whether a host was in detect-only mode or missed an update                            |

**Live triage and evidence collection (optional, recommended)**

These let analysts work directly on an affected host. They're used only during an active incident, with an analyst approving each action. Without them, ThreatDefence still monitors, contains hosts and investigates from telemetry, but collecting evidence from a host has to be done by your own team.

| API scope                     | Permission  | What ThreatDefence uses it for                                                                                                          |
| ----------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Real time response            | Read        | Open a session on an affected host and run read-only commands: list processes, files, network connections, registry keys and event logs |
| Real time response            | Write       | Collect evidence from an affected host: retrieve a file, capture memory, stop a malicious process                                       |
| Sample uploads                | Write       | Submit a collected file for analysis                                                                                                    |
| Sandbox (Falcon Intelligence) | Read, Write | Detonate a submitted file and read the report, if you license Falcon Sandbox                                                            |

4. Select **Create**. Copy the **Client ID** and **Client secret** now. Falcon shows the secret only once.

***

### Scopes ThreatDefence never asks for

ThreatDefence never needs, and you should never grant to any ThreatDefence API client:

* **Real time response (admin)**: runs arbitrary scripts with system privileges. If you want ThreatDefence to run remediation scripts, we agree each script with you first and set it up as a Falcon Fusion workflow you control.
* **API clients**, **User management** or **Installation tokens** with Write.
* **Sensor update policies** with Write: it can reveal the sensor uninstall token.
* Write on any prevention, response, device control or firewall policy.

If anyone asks you to grant these on ThreatDefence's behalf, contact us before you do.

***

### Step 3: Add the integration in ThreatDefence

Please follow the [Managing Integrations](https://docs.threatdefence.com/platform-management/managing-integrations.md) instructions and onboard the integration. The credentials saved above are required in this process.

* Client ID
* Client Secret
* Base URL

{% hint style="warning" %}
Don't send API credentials by email or chat. If you can't use the platform form, ask your ThreatDefence contact for a one-time secure upload link.
{% endhint %}

#### Restrict access to ThreatDefence's IP addresses (recommended)

If your Falcon tenant uses **IP allowlisting** for API access (**Support and resources → IP allowlist management**), add the ThreatDefence egress addresses for your region, listed under **Settings → Network** in the ThreatDefence platform.

#### MSSP and Flight Control tenants

If your Falcon tenant is a Flight Control parent with child CIDs, you can create the API clients in the parent and ThreatDefence will reach each child you specify. For the Response and Investigation clients, we recommend creating them in each child CID instead, so each one's access stays limited to that customer.

#### Rotating or revoking credentials

* **Rotate**: in Falcon, open the API client, select **Reset client secret**, then paste the new secret into the ThreatDefence integration. Collection pauses only between the reset and the update.
* **Revoke**: delete the API client in Falcon. Deleting the Response or Investigation client stops those capabilities straight away and leaves monitoring running.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.threatdefence.com/siem-integrations/endpoint-protection/crowdstrike.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
