ConductorOne docs

Set up a CrowdStrike connector

ConductorOne provides identity governance for CrowdStrike. Integrate your CrowdStrike instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

Capabilities

Resource	Sync	Provision
Accounts	✅
Roles	✅	✅

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 “ConductorOne 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.

That’s it! 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 ConductorOne
Access to the set of Crowdstrike credentials generated by following the instructions above

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

In ConductorOne, navigate to Admin > 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 ConductorOne)
- 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 ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne 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.

That’s it! Your Crowdstrike connector is now pulling access data into ConductorOne.

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 ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Set up a new Crowdstrike connector

In ConductorOne, navigate to 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 ConductorOne)
- 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 ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
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:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne 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'>

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: ghcr.io/conductorone/baton-crowdstrike:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-crowdstrike-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In ConductorOne, click Applications. 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.

That’s it! Your Crowdstrike connector is now pulling access data into ConductorOne.