> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/d-j-integrations/darktrace-setup-for-workbench.md). # Darktrace Setup for Workbench Darktrace is an Intrusion Detection Device (IDS) that leverages machine learning to detect emerging threats, including insider threats, low-and-slow attacks, and automated viruses. {% hint style="warning" %} If you are setting up an **on-prem** device, you must [add an assembler](/connect-your-technology/expel-assembler/add-a-new-assembler.md) *before* completing this guide. Cloud devices do not require assemblers. {% endhint %} ## Step 1: Enable Access for Expel Expel requires a Darktrace user account to review alerts and models within the console. For more information, see [Why Expel Asks for Console Access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md). 1. From the menu located at the top left, select **Add New User**. 2. **Username** - enter "Expel". 3. **Password** - set a temporary password (this is changed on initial login). 4. **Account Permissions** - select all available permissions, *except* User Admin or Group Admin. These can be left cleared. 5. Select **OK**. ## Step 2: Generate API credentials To integrate the technology with Workbench, we need to create secure credentials to the API. {% hint style="info" %} Expel secures all login information our SOC analysts need about your devices in an MFA password product. Access to this login information is protected using our internal MFA processes. To learn more about the IP addresses all Expel traffic [comes from, go here.](/workbench-setup/configure-an-ip-allow-list.md) {% endhint %} 1. Log into the Darktrace console. 2. Navigate to **Admin > System Config**. 3. Near the bottom of the page, under **API Token**, select **New**. 4. The Darktrace system generates a **Token** and a **Private Token**. The Private Token can only be seen once, after the token pair is initially generated. Make note of the tokens for onboarding in Workbench. {% hint style="warning" %} The system can only have 1 token pair, so if one already exists and you do not have a record of this, you must generate another token pair. If a replacement Token pair is generated, other clients using the API must be reconfigured with the new credentials. {% endhint %} ## Step 3: Add Darktrace as a Security Device in Workbench Now that we have the correct access configured and noted the credentials, we can integrate your tech with Workbench. 1. In a new browser tab, log in to [https://workbench.expel.io](https://workbench.expel.io/). 2. Navigate to **Organization Settings > Security Devices**. 3. Select **Add Security Device**. 4. Search for and select your technology. 5. Choose the location of your device. 6. For on-prem devices, select the assembler you created before beginning this setup guide. 7. Enter the name and location. 8. For Server address, enter the server address of the vendor’s server and make sure to include the port. Example: `https://127.0.0.1:443 or myvendordevice.acme.com:443` 9. For Public key, enter the API token used to authenticate to the device from [Step 2](#step-2-generate-api-credentials). 10. For Private key, type the private token used to authenticate to the device from [Step 2](#step-2-generate-api-credentials). 11. Select **Save**. 12. Select **No thanks, I will not provide console access** from the console access dropdown (we will access the console via the user account created in [Step 1](#step-1-enable-access-for-expel)). 13. Select **Save**. Your device should be created successfully within a few seconds. A few reminders: * After your connection is healthy, it will take some time for your device to begin polling and receiving data. * To check on the status, select the downward arrow for your device in the first column and choose **View details**. * Polling will happen first; data will be received after that. **You must refresh the page to see updates.** * If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team for help](/support/how-to-reach-us.md). * To check if alerts are coming through, navigate to **Dashboards > Alert Analysis**. Scroll to the device you want to check, and select the **Expel Alerts** tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we [tune your device](/workbench-reference/alerts/how-expel-alerts-work.md#device-tuning). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.expel.io/connect-your-technology/d-j-integrations/darktrace-setup-for-workbench.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.