Set up a CrowdStrike connector

Capabilities

Resource	Sync	Provision
Accounts
Roles
Insights (opt-in)

Connector actions

Action	Description
Update User	Updates a CrowdStrike user’s first and/or last name.

Additional functionality: The CrowdStrike connector supports external insights when your organization has a Falcon Identity Protection license. See Enable risk score ingestion and Surface identity password risk for setup instructions.

Gather CrowdStrike credentials

Configuring the connector requires you to pass in credentials generated in CrowdStrike. Gather these credentials before you move on.

A user with the Falcon Administrator role in CrowdStrike must perform this task.

Create a CrowdStrike API client

Sign into the Falcon console and navigate to Support > API Clients and Keys.

Click + Add new API client.

Give the new API client a name, such as “C1 integration” and add a description.

In the API SCOPES section of the page, select the appropriate User management scopes:

Read and Write to sync access data and provision CrowdStrike roles
Read to sync access data

Click ADD.

The new API client is created, and its client ID and client secret are shown. Carefully copy and save these credentials.

Done. Next, move on to the connector configuration instructions.

Configure the CrowdStrike connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of CrowdStrike credentials generated by following the instructions above

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Integrations > Connectors and click Add connector.

Search for CrowdStrike and click Add.

Choose how to set up the new CrowdStrike connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

Click Next.

Find the Settings area of the page and click Edit.

In the Client ID and Client secret fields, enter the CrowdStrike credentials.

Optional. Enter your CrowdStrike region in the Region field. The default region is US-1.

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your CrowdStrike connector is now pulling access data into C1.

Follow these instructions to use the CrowdStrike connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

Official download center: For stable binaries (Windows/Linux/macOS) and container images.
GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new CrowdStrike connector

In C1, navigate to Integrations > Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new CrowdStrike connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Click Next.

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your CrowdStrike connector deployment:

Secrets configuration

# baton-crowdstrike-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-crowdstrike-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # CrowdStrike credentials
  BATON_CROWDSTRIKE_CLIENT_ID: <Client ID for the CrowdStrike API client>
  BATON_CROWDSTRIKE_CLIENT_SECRET: <Client secret for the CrowdStrike API client>
  BATON_REGION: <CrowdStrike region, options include 'us-1' (default), 'us-2', 'eu-1', and 'us-gov-1'>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-crowdstrike.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-crowdstrike
  labels:
    app: baton-crowdstrike
spec:
  selector:
    matchLabels:
      app: baton-crowdstrike
  template:
    metadata:
      labels:
        app: baton-crowdstrike
        baton: true
        baton-app: crowdstrike
    spec:
      containers:
      - name: baton-crowdstrike
        image: public.ecr.aws/conductorone/baton-crowdstrike:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-crowdstrike
        envFrom:
        - secretRef:
            name: baton-crowdstrike-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the CrowdStrike connector to. CrowdStrike data should be found on the Entitlements and Accounts tabs.

Done. Your CrowdStrike connector is now pulling access data into C1.

Enable risk score ingestion

The CrowdStrike connector can ingest Falcon identity risk scores and surface them in C1 during access reviews and access request approvals. See External insights for an overview of where risk data appears.

Before you begin

Confirm that:

Your organization has a CrowdStrike Falcon Identity Protection license
You have the Falcon Administrator role in CrowdStrike
Your CrowdStrike connector is already set up and syncing in C1

Add required API scopes

The CrowdStrike API client you created during connector setup needs additional scopes to access risk score data.

Sign into the Falcon console and navigate to Support > API Clients and Keys.

Find the API client you created for the C1 integration and click to edit it.

In the API SCOPES section, enable the following scopes:

Identity Protection Entities: Read
Identity Protection GraphQL: Write (This is required by CrowdStrike to fetch the data)

Click Save.

Done. Your CrowdStrike connector will now sync risk score data into C1. See External insights for details on where to see this data in the UI.

Surface identity password risk

Early access. This feature is in early access, which means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve outputs. Contact the C1 Support team if you’d like to try it out or share feedback.

Once risk score ingestion is enabled, you can flag identities with a compromised or weak password from Falcon Identity Protection as risk factors:

EXPOSED_PASSWORD (High) — the identity’s password appears in a known breach or exposed-credential set (a compromised password).
WEAK_PASSWORD (Medium) — the identity’s password is weak.

These are not a separate resource or screen — they appear as risk factors on the identity’s existing risk insight, in the same places as risk scores (see Where external insights appear). A factor is added only when an account has that condition — identities with strong, unexposed passwords carry no password factor.

Before you begin

Confirm that:

Risk score ingestion is set up — see Enable risk score ingestion.
The Identity Risk Score resource capability is turned on for your connector (see Enable or disable external insights). Password risk attaches to that insight, so it won’t appear if the capability is off.
Your CrowdStrike connector is already set up and syncing in C1.

Turn on password risk

Password risk uses the same Identity Protection scopes as risk score ingestion, so no additional CrowdStrike API scopes are required. Enable it in the connector’s settings:

In C1, go to Integrations > Connectors and select your CrowdStrike connector.

On the connector’s Settings, click Edit.

Enable Ingest identity password risk (off by default), then click Save.

Done. On the next sync, identities with a compromised or weak password carry the corresponding risk factor, visible wherever external insights appear.

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a CrowdStrike connector

Capabilities

Connector actions

Gather CrowdStrike credentials

Create a CrowdStrike API client

Configure the CrowdStrike connector

Resources

Step 1: Set up a new CrowdStrike connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Enable risk score ingestion

Before you begin

Add required API scopes

Surface identity password risk

Before you begin

Turn on password risk

​Capabilities

​Connector actions

​Gather CrowdStrike credentials

​Create a CrowdStrike API client

​Configure the CrowdStrike connector

​Resources

​Step 1: Set up a new CrowdStrike connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

​Enable risk score ingestion

​Before you begin

​Add required API scopes

​Surface identity password risk

​Before you begin

​Turn on password risk

Capabilities

Connector actions

Gather CrowdStrike credentials

Create a CrowdStrike API client

Configure the CrowdStrike connector

Resources

Step 1: Set up a new CrowdStrike connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Enable risk score ingestion

Before you begin

Add required API scopes

Surface identity password risk

Before you begin

Turn on password risk