Nailing the Security Audit with RRCU

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

  • Sync user identities from CrowdStrike to ConductorOne

  • Resources supported:

    • Roles

Add a new CrowdStrike connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

  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

    Do you SSO into CrowdStrike using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged CrowdStrike app that was created automatically when you integrated your provider with ConductorOne, rather than creating a new managed app.

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

    A CrowdStrike connector owner must have the following permissions:

    • Connector Administrator or Super Administrator role in ConductorOne
    • Falcon Administrator role in CrowdStrike
  1. Click Next.

Next steps

  • If you are the connector owner, proceed to Configure your CrowdStrike connector for instructions on integrating CrowdStrike with ConductorOne.

  • If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your CrowdStrike connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and Falcon Administrator role in CrowdStrike must perform this task.

Step 1: 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. We’ll use them in Step 2.

Step 2: Add your CrowdStrike credentials to ConductorOne

  1. In ConductorOne, navigate to the CrowdStrike connector by either:

    • Clicking the Set up connector link in the email you received about configuring the connector.

    • Navigate to Connectors > CrowdStrike (if there is more than one CrowdStrike listed, click the one with your name listed as owner and the status Not connected).

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

  3. In the Client ID and Client secret fields, enter the CrowdStrike credentials you generated in Step 1.

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

  5. Click Save.

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

Configure the CrowdStrike integration using Terraform

As an alternative to the integration 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.