# SailPoint CrowdStrike Connector Documentation

> CrowdStrike Connector Documentation

# Documentation

# Connecting SailPoint and CrowdStrike

To connect SailPoint with CrowdStrike, perform the following tasks:

## Adding the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

1. Sign in to SailPoint.
2. Go to **Admin \> Connections \> Sources**.
3. Select **Create New**.
4. Search for the connector by entering the name in the search box, and then select **Actions**.
5. In the **Actions** dropdown list, select the setup method:

   - [**Express Setup**](<#configuring-a-source-using-express-setup>) - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     > **Note**
     >
     > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Configuring a Source Using Express Setup

Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data.

1. Review the directions and select **Start Express Setup**.
2. Review the pre-populated **Source Name**, **Source Owner**, and **Description**. To update, select **Edit**.

   > **Note**
   >
   > The source name must be unique. You can change these settings later in the source configuration.
3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section.
5. Select **Finish**.

   After a successful test connection, the system creates your source and prompts you to run an aggregation.

   - If you want to aggregate now, select **Aggregate**.

     - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**.
     - To see the list of aggregated source accounts, go to **Account Management \> Accounts**.
   - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet.

### Configuring a Source Using Standard Setup

Use Standard Setup to configure the connector for full feature support.

1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
4. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there.

## Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a unique name and description for the source.
2. In the **Source Owner** dropdown list, select the identity that owns this source.

   - To find a source owner, begin entering their name.
3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information.
5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
6. (Optional) Select **Create Manual Work Items** to allow the connector to create manual work items for certain operations. You can also enable this option so the source supports additional source management features such as creating accounts and access profile management.

   > **Important**
   >
   > Once you enable this feature, you cannot disable it.

   For more information on manual work items in SailPoint, refer to [Work Items](<https://developer.sailpoint.com/docs/api/work-items>). For more information on SailPoint features, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).
7. Select **Save**.

## Connection Settings

The following information is required to connect and interact with CrowdStrike.

> [!NOTE]
>
> **Screenshot**
>
> [![Connection Settings](<https://documentation.sailpoint.com/connectors/crowdstrike/saas/help/img/connection_settings.png>)](<https://documentation.sailpoint.com/connectors/crowdstrike/saas/help/img/connection_settings.png>)

1. Enter the **Base URL** for the CrowdStrike source. To find the **Base URL**, refer to your CrowdStrike Cloud Environment URL. For example, `https://api.us-2.crowdstrike.com` or `https://api.eu-1.crowdstrike.com`
2. In the **Client ID** and **Client Secret** fields, enter the client identifier and accompanying secret that you previously generated in your CrowdStrike system. For more information on generating the client ID and client secret, refer to the [CrowdStrike OAuth](<https://developer.crowdstrike.com/>) documentation.
3. Select **Save**.

## Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to **Review and Test**.
2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.
3. Select **Test Connection**.

## SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface.

For more information, refer to [Application Onboarding](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# Dataset Management

The CrowdStrike SaaS connector includes Dataset 2.0 datasets for the Entro integration. Both datasets are **push** datasets: Entro discovers the objects from CrowdStrike EDR endpoint telemetry and pushes them into SailPoint. The connector does not call CrowdStrike for these objects, so there is no aggregation schedule. All attributes are new.

Use **Dataset Management** to review the datasets and resources that Entro pushes into SailPoint.

For more information, refer to [Dataset Management](<https://documentation.sailpoint.com/saas/help/sources/datasets.html>).

> [!IMPORTANT]
>
> The connector determines how resources are grouped into datasets. You can view the resources inside each dataset, but you cannot create, delete, or rearrange datasets, or move resources between datasets.

## Resources

A **Resource** defines an object type that Entro pushes from CrowdStrike EDR endpoint telemetry. It specifies the kind of object, the attributes collected for that object, and how SailPoint identifies and displays each object.

For more information, refer to [Managing Resources](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#managing-resources>).

## Datasets

A **Dataset** is a named group of one or more related resources. For these push datasets, Entro discovers the objects and pushes them into SailPoint. The connector does not aggregate these objects from CrowdStrike, so there is no aggregation schedule.

> [!NOTE]
>
> Each resource belongs to exactly one dataset for that source. The source defines dataset membership. You can review associated resources, but you cannot create or delete datasets or move resources between them.

## Supported Datasets

Go to **Admin** \> **Connections** \> **Sources**, open your **CrowdStrike** source, and select **Dataset Management** \> **Datasets** to view the datasets that Entro pushes into SailPoint. Select a dataset to review its associated resources.

> [!NOTE]
>
> These are push datasets. Entro discovers the objects from CrowdStrike EDR endpoint telemetry and pushes them into SailPoint. The connector does not call CrowdStrike for these objects, so there is no aggregation schedule.

| Dataset Name | Associated Resources | Dataset ID | Required Licenses | Schedule |
| --- | --- | --- | --- | --- |
| CrowdStrike EDR Process Agent | CrowdStrike EDR Process Agent | `endpoint:edr-process` | `entro:base` | N/A - pushed by Entro |
| CrowdStrike EDR MCP Config Agent | CrowdStrike EDR MCP Config Agent | `endpoint:edr-mcp` | `entro:base` | N/A - pushed by Entro |

### CrowdStrike EDR Process Agent

AI client processes discovered by Entro from CrowdStrike EDR endpoint telemetry.

### CrowdStrike EDR MCP Config Agent

MCP server configurations discovered by Entro from CrowdStrike EDR endpoint telemetry.

## Supported Resources

A resource represents an object type that Entro pushes from CrowdStrike EDR endpoint telemetry, such as AI client processes or MCP server configurations. Each resource defines the attributes collected for that object type and how SailPoint displays each object.

For more information, refer to [Managing Resources](<https://documentation.sailpoint.com/saas/help/sources/datasets.html#managing-resources>).

> [!NOTE]
>
> These resources belong to push datasets. Entro discovers the objects and pushes them into SailPoint. The connector does not call CrowdStrike for these objects, so there is no aggregation schedule.

On your CrowdStrike source, go to **Dataset Management** \> **Resources** to view each object type. Select a resource to review its schema on the **Schema** tab.

| Resource Name | Resource Type | Resource ID |
| --- | --- | --- |
| CrowdStrike EDR Process Agent | `std:agent` | `endpoint:edr-process` |
| CrowdStrike EDR MCP Config Agent | `std:agent` | `endpoint:edr-mcp` |

**To inspect attribute names and descriptions after the source exists:**

1. Go to **Admin** \> **Connections** \> **Sources**.
2. Open your **CrowdStrike** source.
3. Select **Dataset Management** \> **Resources**.
4. Select a resource.
5. Open the **Schema** tab. Attribute names, descriptions, and types are connector-defined and read-only on this page.

## CrowdStrike EDR Process Agent Attributes

The following table lists schema properties for the **CrowdStrike EDR Process Agent** resource (`endpoint:edr-process`).

| Property | Value |
| --- | --- |
| Resource ID | `endpoint:edr-process` |
| Resource type | `std:agent` |
| Identity attribute | `id` |
| Display attribute | `name` |

### Attributes

| Attribute | Type | Description |
| --- | --- | --- |
| `id` | string | Stable agent identity from Entro (for example, `<uuid>-Claude`). |
| `name` | string | Normalized AI client name (for example, `claude`, `gemini`). |
| `rawName` | string | Original name from the source system (for example, `Claude`, `GEMINI`). |
| `agentType` | string | Endpoint agent discriminator from Entro (`Endpoint Agent: Process`). |
| `classification` | string | Classification enum (for example, `Endpoint`). |
| `detectionMethod` | string | Detection method used by Entro; might be null. |
| `riskBand` | string | Severity band (`BENIGN`, `LOW`, `MEDIUM`, `HIGH`, `CRITICAL`, `UNKNOWN`). |
| `sourceAccount` | string | Source account display name, typically the endpoint hostname. |
| `integrationType` | string | Integration type reported by Entro (for example, `CROWDSTRIKE`). |
| `sourceUrl` | string | Deep link to the source; might be null. |
| `environment` | string | Environment name from the source account. |
| `tags` | array | Tags from the source account. |
| `insights` | array | Insight descriptions from Entro policies. |
| `ownerEmail` | string | Flattened `owner.email`, used for identity correlation. |
| `owner.email` | string | Primary identity-correlation key. |
| `owner.name` | string | Owner display name. |
| `owner.title` | string | Owner job title; might be null. |
| `owner.department` | string | Owner department; might be null. |
| `owner.uid` | string | Entro owner uid; fallback correlation key when email is missing. |
| `lastSeen` | string | ISO-8601 timestamp of the most recent usage or update signal. |
| `device.hostname` | string | Endpoint hostname. |
| `device.computerName` | string | Computer name reported by the endpoint. |
| `device.lastLoginUser` | string | Last login user observed on the device. |
| `device.osVersion` | string | OS version (for example, `Sequoia (15)`). |
| `device.externalIp` | string | External IP observed for the device. |
| `firstSeen` | string | ISO-8601 timestamp when the agent activity was first observed. |
| `dnsHitCount` | number | DNS hits attributed to the agent. |
| `isKnownAiClient` | boolean | Whether Entro recognizes this as a known AI client. |
| `rollupCount` | number | Number of rolled-up activity events. |
| `firstRollup` | string | ISO-8601 timestamp of the first rolled-up event. |
| `lastRollup` | string | ISO-8601 timestamp of the most recent rolled-up event. |
| `contactedEndpoints[].name` | string | Canonical contacted endpoint name (for example, `mcp.entro.security`). |
| `contactedEndpoints[].rawName` | string | Raw contacted endpoint name from the source. |

## CrowdStrike EDR MCP Config Agent Attributes

The following table lists schema properties for the **CrowdStrike EDR MCP Config Agent** resource (`endpoint:edr-mcp`).

| Property | Value |
| --- | --- |
| Resource ID | `endpoint:edr-mcp` |
| Resource type | `std:agent` |
| Identity attribute | `id` |
| Display attribute | `name` |

### Attributes

| Attribute | Type | Description |
| --- | --- | --- |
| `id` | string | Stable agent identity from Entro (for example, `<uuid>-Claude`). |
| `name` | string | Normalized AI client name (for example, `claude`, `gemini`). |
| `rawName` | string | Original name from the source system (for example, `Claude`, `GEMINI`). |
| `agentType` | string | Endpoint agent discriminator from Entro (`Endpoint Agent: MCP Config`). |
| `classification` | string | Classification enum (for example, `Endpoint`). |
| `detectionMethod` | string | Detection method used by Entro; might be null. |
| `riskBand` | string | Severity band (`BENIGN`, `LOW`, `MEDIUM`, `HIGH`, `CRITICAL`, `UNKNOWN`). |
| `sourceAccount` | string | Source account display name, typically the endpoint hostname. |
| `integrationType` | string | Integration type reported by Entro (for example, `CROWDSTRIKE`). |
| `sourceUrl` | string | Deep link to the source; might be null. |
| `environment` | string | Environment name from the source account. |
| `tags` | array | Tags from the source account. |
| `insights` | array | Insight descriptions from Entro policies. |
| `ownerEmail` | string | Flattened `owner.email`, used for identity correlation. |
| `owner.email` | string | Primary identity-correlation key. |
| `owner.name` | string | Owner display name. |
| `owner.title` | string | Owner job title; might be null. |
| `owner.department` | string | Owner department; might be null. |
| `owner.uid` | string | Entro owner uid; fallback correlation key when email is missing. |
| `lastSeen` | string | ISO-8601 timestamp of the most recent usage or update signal. |
| `device.hostname` | string | Endpoint hostname. |
| `device.computerName` | string | Computer name reported by the endpoint. |
| `device.lastLoginUser` | string | Last login user observed on the device. |
| `device.osVersion` | string | OS version (for example, `Sequoia (15)`). |
| `device.externalIp` | string | External IP observed for the device. |
| `filePath` | string | Path to the MCP configuration file. |
| `configuredServers[].name` | string | Canonical MCP server name (for example, `github`). |
| `configuredServers[].rawName` | string | Raw MCP server name from the source. |
| `configuredServers[].serverType` | string | MCP server type; might be null. |
| `configuredServers[].url` | string | MCP server URL; might be null. |
| `correlatedTokens[].tokenId` | string | Correlated token identifier; might be partially redacted. |
| `correlatedTokens[].username` | string | Username associated with the token; might be null. |
| `correlatedTokens[].accessMethod` | string | Access method for the token (for example, `GITHUB_API_TOKEN`). |
| `correlatedTokens[].isAdmin` | boolean | Whether the token holds administrative privileges. |
| `correlatedTokens[].isOriginToken` | boolean | Whether this token is the origin token. |

# Integrating SailPoint with CrowdStrike

CrowdStrike is a SaaS connector that aggregates Risk information for identities from your CrowdStrike module.

This document is designed to give specific information about the requirements and fields needed to successfully configure an instance of the CrowdStrike connector.

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The CrowdStrike connector supports the following features:

- Aggregation of Accounts
- Single Account Aggregation
- Identity Protection - Risky User Alert Feature

  - Assess compromised account risk from CrowdStrike security reports. The connector aggregates `riskScore`, `riskScoreSeverity`, and `riskFactors`.
- Device Enrichment and NHI Mapping

  - Map non-human identities to endpoints using hostname, computer name, last login user, OS version, and external IP.
- Inventorying MCPs and AI Agents

  - Discover AI client processes and MCP server configurations from endpoint telemetry.
- Active Directory Users (NHIs) Management

  - Aggregate Active Directory non-human identities from Identity Protection. Identify programmatic accounts with `isHuman` and `isProgrammatic`.
- Real-Time Response and Incident Data Ingestion

  - Ingest real-time response and incident data to support AI agent discovery and security analysis.

### Non-Human Identity Discovery

- Aggregate CrowdStrike EDR process agents
- Aggregate CrowdStrike EDR MCP config agents

Refer to Dataset Management for more information.

Refer to [Discovering Potential Non-Human Accounts](<https://documentation.sailpoint.com/saas/help/agentic_fabric/nhi/non_human_accounts.html#discovering-potential-non-human-accounts>) for more information.

## Prerequisites

The following prerequisites are required:

- An API Client must be configured in CrowdStrike. This API client must be configured with specific Identity Scopes outlined in [Required Permissions](<#required-permissions>).
- You need the CrowdStrike Cloud Environment URL of the CrowdStrike service.
- To connect with the CrowdStrike API you will need to get an **OAuth Client ID** and **Client Secret**. These will be used to identify and authenticate your application. For more information on generating the client ID and client secret, refer to the [CrowdStrike OAuth](<https://developer.crowdstrike.com/>) documentation (the CrowdStrike documentation requires an active login).

## Required Permissions

The following scopes need to be applied to the API client created in CrowdStrike:

> [!IMPORTANT]
>
> To use any of the Identity Protection API functionality, you must enable the **Identity Protection GraphQL** write scope.

| Scope | Read | Write | Required for |
| --- | --- | --- | --- |
| Hosts | Yes | No | All features |
| Real Time Response | Yes | No | AI agents |
| NGSIEM | Yes | Yes | AI agents |
| Identity Protection Assessment | Yes | No | Identity Protection |
| Identity Protection Automation | Yes | No | Identity Protection |
| Identity Protection Detections | Yes | No | Active Directory NHIs |
| Identity Protection Enforcement | Yes | No | Identity Protection |
| Identity Protection Entities | Yes | No | Active Directory NHIs |
| Identity Protection GraphQL | Yes | Yes | Active Directory NHIs |
| Identity Protection Health | Yes | No | Identity Protection |
| Identity Protection On-premise Enablement | Yes | No | Identity Protection |
| Identity Protection Timeline | Yes | No | Active Directory NHIs |

For example, your permissions may look like the following:

> [!NOTE]
>
> **Screenshot**
>
> [![Permission Scopes](<https://documentation.sailpoint.com/connectors/crowdstrike/saas/help/img/permission_scopes.png>)](<https://documentation.sailpoint.com/connectors/crowdstrike/saas/help/img/permission_scopes.png>)

# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The CrowdStrike connector uses the following default correlation and object configurations.

## Default Correlation Configuration

Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements.

You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities](<https://documentation.sailpoint.com/saas/help/accounts/correlation.html>) for more information.

When you first create the CrowdStrike source, the default correlation mapping is:

| Account Attribute | Operation | Identity Attribute |
| --- | --- | --- |
| entityId | Equals | SailPoint Username (uid) |
| primaryDisplayName | Equals | Display Name (displayName) |
| email | Equals | Work Email |

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account Attributes

The CrowdStrike connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

| Attribute Name | Description |
| --- | --- |
| entityId | The entity's unique identifier. |
| primaryDisplayName | The display name of the account entity. For example, Firstname + Lastname. |
| secondaryDisplayName | The entity type. This also determines the specialized entity subclass that is returned. |
| isHuman | Displays True or False depending on whether this is a human user account. |
| isProgrammatic | Displays True or False depending on whether this user account was created programmatically. |
| email | The email address of the entity. |
| riskScore | A numeric value between 0 and 1 indicating the risk level of an Identity, with 1 being the highest risk. |
| riskScoreSeverity | The entity’s risk score derived from the user's riskScore value. |
| riskFactors | A list of risk factors that contribute to the overall risk of this user entity. For example, `OBJECT_SID_HISTORY_PRIVILEGES_TAKEOVER` |

# Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

- [SailPoint Identity Services Documentation](<https://documentation.sailpoint.com/saas/help/index.html>)
- [SailPoint Support Knowledge Base](<https://support.sailpoint.com/csm?id=kb_view2&amp;kb_id=05ff44289f011200550bf7b6077fcfa3>)
- [SailPoint Developer Community](<https://developer.sailpoint.com/>)

## Debug Logs

For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](<https://documentation.sailpoint.com/saas/help/sources/managing_additional_settings.html>).

## Account Aggregation fails with java.lang.RuntimeException - java.lang.IllegalStateException: \[ConnectorError\] User not found.

**Resolution**: The account aggregation failure is caused by users in the "DECLINED" status. Users who have declined the account invitation are not recognized as members and therefore cannot be retrieved via the Get Users endpoint.

To resolve this issue, please remove the users with "Declined" status from the system and then retry the Full Account Aggregation.