Set up a Arctic Wolf connector

C1 provides identity governance and just-in-time provisioning for Arctic Wolf. Integrate your Arctic Wolf instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

Capabilities

The Arctic Wolf connector syncs the following resources:

Resource	Sync	Provision
Accounts
Roles
Zones

Account provisioning creates console users only. The Aurora API has no set-password endpoint, so no password is set and none is returned. Console role and per-zone role (Zone Manager / User) assignments are provisionable. The “Zone Manager” console role is derived (set a user’s console role to User and assign a zone with the Zone Manager role), so it is synced but not directly grantable.

Gather Arctic Wolf credentials

To configure the Arctic Wolf connector, you need administrator permissions in the Aurora Endpoint Defense console.

1. In the Aurora console, go to Settings > Integrations and add a new application (integration) for C1.

2. Grant the application these scopes/privileges: user:list, user:read, user:create, user:update, and zone:list.

3. Copy the Application ID, Application Secret, and Tenant ID from the Integrations page and save them securely. Also note your console’s region/data center (for example, North America, Europe, or Asia-Pacific).

Configure the Arctic Wolf connector

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 Arctic Wolf and click Add.

3. Choose how to set up the new Arctic Wolf connector:

   • Add the connector to a currently unmanaged app
   • Add the connector to a managed app
   • Create a new managed app
4. Set the owner for this connector.

5. Click Next.

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

7. Enter the required configuration:

   • region (required): Aurora API region/data center — one of us, eu, apne, au, sa, usgov
   • app-id (required): Aurora API Application ID (used as the JWT subject)
   • app-secret (required): Aurora API Application Secret (used to sign the JWT)
   • tenant-id (required): Aurora API Tenant ID
8. Click Save.

9. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Arctic Wolf connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Arctic Wolf 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.

Resources

• Official download center: For stable binaries (Windows/Linux/macOS) and container images.

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

Step 1: Set up a new Arctic Wolf 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 Arctic Wolf connector:

   • Add the connector to a currently unmanaged app
   • Add the connector to a managed app
   • Create a new managed app
4. Set the owner for this connector.

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.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Arctic Wolf connector deployment:

Secrets configuration

# baton-arctic-wolf-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-arctic-wolf-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Arctic Wolf (Aurora Endpoint Defense) credentials
  BATON_REGION: <us|eu|apne|au|sa|usgov>
  BATON_APP_ID: <Aurora Application ID>
  BATON_APP_SECRET: <Aurora Application Secret>
  BATON_TENANT_ID: <Aurora Tenant ID>

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

Deployment configuration

# baton-arctic-wolf.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-arctic-wolf
  labels:
    app: baton-arctic-wolf
spec:
  selector:
    matchLabels:
      app: baton-arctic-wolf
  template:
    metadata:
      labels:
        app: baton-arctic-wolf
        baton: "true"
        baton-app: arctic-wolf
    spec:
      containers:
      - name: baton-arctic-wolf
        image: public.ecr.aws/conductorone/baton-arctic-wolf:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-arctic-wolf
        envFrom:
        - secretRef:
            name: baton-arctic-wolf-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 Applications. On the Managed apps tab, locate and click the name of the application you added the Arctic Wolf connector to. Arctic Wolf data should be found on the Entitlements and Accounts tabs.

Done. Your Arctic Wolf connector is now pulling access data into C1.

---

All versions of this connector are available at dist.conductorone.com.