Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Crowdstrike credentials

Each setup method 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

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

2. Click + Add new API client.

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

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

   • Read and Write if you want to use ConductorOne to provision CrowdStrike roles
   • Read if you do not want to use ConductorOne for provisioning

5. Click ADD.

6. 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 instructions for your chosen setup method.

Set up a Crowdstrike cloud-hosted 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

1. In ConductorOne, click Connectors > Add connector.

2. Search for Crowdstrike and click Add.

3. 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

4. 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.

5. Click Next.

6. Find the Settings area of the page and click Edit.

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

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

9. Click Save.

10. 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.

Set up a CrowdStrike cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between CrowdStrike and ConductorOne.

See the ConductorOne CrowdStrike integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a Crowdstrike self-hosted 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

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.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the Crowdstrike connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. 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

4. 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.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. 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
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-crowdstrike-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-crowdstrike
   

2. Apply the secret configuration:

   kubectl -n baton-crowdstrike apply -f baton-crowdstrike-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-crowdstrike apply -f baton-crowdstrike.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-crowdstrike}
   

3. 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.