Nailing the Security Audit with RRCU

ConductorOne docs

Set up a Cortex XSOAR connector

ConductorOne provides identity governance and just-in-time provisioning for Cortex XSOAR. Integrate your XSOAR instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

  • Sync user identities from Cortex XSOAR to ConductorOne

  • Resources supported:

    • Roles

Add a new XSOAR connector

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

  1. In ConductorOne, click Connectors > Add connector.

  2. Search for Xsoar and click Add.

  3. Choose how to set up the new XSOAR 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 XSOAR using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged XSOAR 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.

    An XSOAR connector owner must have the following permissions:

    • Connector Administrator or Super Administrator role in ConductorOne
    • Admin role or a custom role with the ability to generate API tokens in XSOAR
  1. Click Next.

Next steps

  • If you are the connector owner, proceed to Configure your XSOAR connector for instructions on integrating Cortex XSOAR 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 XSOAR connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and Admin role or a custom role with the ability to generate API tokens in XSOAR must perform this task.

Step 1: Generate an API key

  1. Log into Cortex XSOAR and navigate to Settings & Info > Settings > Integrations > API Keys.

  2. Click New Key.

  3. Choose the Standard API key.

  4. If desired, set an expiration for the API key and add a comment describing the key’s purpose.

  5. Give the API key the Admin role or a custom role with the permission to read user and role data.

  6. Click Save to generate the new API key.

  7. Carefully copy and save the API key. We’ll use it in Step 3.

Step 2: Find your API URL

  1. In the table of API keys, right-click your newly generated API key and select View Examples.

  2. Copy the CURL Example URL. The example contains your FQDN, which forms part of your unique API URL. The API URL is in this form: https://api-{fqdn}/xsoar/.

Step 3: Add your XSOAR credentials to ConductorOne

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

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

    • Navigate to Connectors > Xsoar (if there is more than one Xsoar 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. Enter the API URL of the Cortex XSOAR instance that you looked up in Step 2 in the API URL field.

  4. Paste the API key you generated in Step 1 into the Token field.

  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 XSOAR connector is now pulling access data into ConductorOne.

Configure the XSOAR integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between XSOAR and ConductorOne.

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