Nailing the Security Audit with RRCU

ConductorOne docs

Set up an Elastic connector

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

Capabilities

  • Sync user identities from Elastic to ConductorOne

  • Resources supported:

    • Organizations
    • Deployment users (optional)
    • Deployment roles (optional)
    • Role mappings

  • Provisioning supported:

    • Deployment role assignments

Add a new Elastic connector

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

  1. In ConductorOne, click Connectors > Add connector.

  2. Search for Elastic and click Add.

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

    A Elastic connector owner must have the following permissions:

    • Connector Administrator or Super Administrator role in ConductorOne
    • Organization owner role in Elastic Cloud
  1. Click Next.

Next steps

  • If you are the connector owner, proceed to Configure your Elastic connector.

  • 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 Elastic connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and the Organization owner role in Elastic must perform this task.

Step 1: Generate an Elastic Cloud API key

  1. In the Elasticsearch Service Console, click your avatar in the upper right corner and select Organization.

  2. Navigate to the API keys tab and click Create API key.

  3. Give the new API key a name, such as “ConductorOne integration”.

  4. Select an expiration for the API key.

  5. In the Assign roles area, give the API key the Organization owner role.

  6. Click Create API key.

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

(Optional) Step 2: Generate an Elastic deployment API key and look up the deployment’s endpoint

The credentials generated in this step are required for ConductorOne to sync information on Elastic deployment users and deployment roles, and to provision Elastic deployment role assignments. If you do not want to sync or provision deployment users or deployment roles, skip ahead to Step 3.

  1. Back on the Elasticsearch Service Console homepage, find the Hosted deployments area of the page and click the name of the deployment you want to integrate.

  2. On the deployment’s page, click Manage permissions.

  3. In the sidebar, click API keys > Create API key.

  4. Give the new API key a name, such as “ConductorOne deployment info integration”.

  5. Select the Personal API key option.

  6. Click Create API key.

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

  8. We also need to look up the deployment’s Elasticsearch endpoint. Click the Elastic logo to return to your deployment’s home page.

  9. Click Add integrations.

  10. In the upper right corner of the screen, click Connection details.

  11. Carefully copy and save the Elasticsearch endpoint. We’ll use it in Step 3.

Step 2: Add your Elastic credentials to ConductorOne

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

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

    • Navigate to Connectors > Elastic (if there is more than one Elastic 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. Paste the API key you generated in Step 1 into the API key field.

  4. Optional. If you completed Step 2, paste the credentials you generated into the Deployment API key and Deployment endpoint fields.

  5. Optional. By default, ConductorOne will sync information about all users in all organizations. If you want to limit the sync to a single organization, paste that organization’s ID into the Organization ID field.

  6. Click Save.

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

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

Configure the Elastic integration using Terraform

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

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