Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather SentinelOne credentials

Each setup method requires you to pass in credentials generated in SentinelOne. Gather these credentials before you move on.

A user with access to the SentinelOne management console must perform this task.

Generate a SentinelOne API token

1. In the SentinelOne management console, click your username and select My user.

2. Click Actions > API Token Operations > Generate API Token.

3. The API token is created. Carefully copy and save the token.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a SentinelOne cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of SentinelOne credentials generated by following the instructions above

1. In ConductorOne, click Connectors > Add connector.

2. Search for SentinelOne and click Add.

3. Choose how to set up the new SentinelOne 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 SentinelOne base URL field, enter the base URL of your SentinelOne instance.

   The base URL is in the form https://acmeco.sentinelone.net.

8. Paste the API token into the API token field.

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

Set up a SentinelOne 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 SentinelOne and ConductorOne.

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

Set up a SentinelOne self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of SentinelOne 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 SentinelOne connector

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

2. Search for Baton and click Add.

3. Choose how to set up the new SentinelOne 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 SentinelOne connector deployment:

Secrets configuration

# baton-sentinel-one-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-sentinel-one-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # SentinelOne credentials
  BATON_API_TOKEN: <SentinelOne API token>
  BATON_MANAGEMENT_CONSOLE_URL: <Base URL of your SentinelOne instance in the form https://acmeco.sentinelone.net>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-sentinel-one.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-sentinel-one
  labels:
    app: baton-sentinel-one
spec:
  selector:
    matchLabels:
      app: baton-sentinel-one
  template:
    metadata:
      labels:
        app: baton-sentinel-one
        baton: true
        baton-app: sentinel-one
    spec:
      containers:
      - name: baton-sentinel-one
        image: ghcr.io/conductorone/baton-sentinel-one:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-sentinel-one-secrets

Step 3: Deploy the connector

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

   kubectl create namespace baton-sentinel-one
   

2. Apply the secret configuration:

   kubectl -n baton-sentinel-one apply -f baton-sentinel-one-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-sentinel-one apply -f baton-sentinel-one.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-sentinel-one}
   

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 SentinelOne connector to. SentinelOne data should be found on the Entitlements and Accounts tabs.

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