Set up a SentinelOne connector

C1 provides identity governance for SentinelOne. Integrate your SentinelOne instance with C1 for unified visibility and governance over user access.

Capabilities

Resource	Sync	Provision
Accounts
Roles
Sites

Gather SentinelOne credentials

Configuring the connector 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.

Done. Next, move on to the connector configuration instructions.

Configure the SentinelOne connector

To complete this task, you’ll need:

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

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Integrations > Connectors and click 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 C1)

   • 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 C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 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.

Done. Your SentinelOne connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the SentinelOne connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

• GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new SentinelOne connector

1. In C1, navigate to Integrations > 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 C1)

   • 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 C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 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:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 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: public.ecr.aws/conductorone/baton-sentinel-one:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-sentinel-one
        envFrom:
        - secretRef:
            name: baton-sentinel-one-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In C1, click Apps. 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.

Done. Your SentinelOne connector is now pulling access data into C1.