> 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/q-z-integrations/trellix-endpoint-security-hx-formerly-fireeye-hx-setup-for-workbench.md). # Trellix Endpoint Security (HX) (formerly FireEye HX) Setup for Workbench This article explains how to connect Trellix Endpoint Security (HX) to Workbench. ## Prerequisites * If you are connecting an on-prem device, you must first [add an Expel Assembler](/connect-your-technology/expel-assembler/add-a-new-assembler.md) (assemblers are not required for cloud devices). ### Step 1: Enable Console Access This step creates a user account for Expel that keeps the Expel activity separate from other activity on the Endpoint Security (HX) console. You will use these credentials when you set up console access in Workbench. {% hint style="info" %} Having read-only access to the interface of your technology allows Expel to dig deeper during incident investigations. Our device health team uses this access to investigate potential health issues with your tech. For more information, see [Why Expel Asks for Console Access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md). {% endhint %} 1. Navigate to **Admin > Appliance Settings**. 2. Select **User Accounts** on the left. 3. For **Username**, enter "Expel". 4. Ensure the **Role** is set to `Admin`. 5. Enter a **Password**. 6. Select **Add User**. ### Step 2: Generate API Credentials This step creates an authentication token that allows the assembler to access the Endpoint Security (HX) API. You will use these credentials when you set up the security device in Workbench. 1. Go to the **User Accounts** section. 2. For Username, enter "expelapi". 3. Make sure the **Role** is set to `API Admin`. 4. Enter a **Password**. 5. Select **Add User**. ### Step 3: Add Trellix Endpoint Security (HX) 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. [Log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F). 2. In the side menu, navigate to **Organization Settings > Security Devices**. If you have multiple organizations, you must select the appropriate organization name from the list. 3. Select **Add Security Device**. 4. In the search box, enter “Trellix” and then select the Trellix Endpoint Security (HX) integration. 5. Complete the fields as follows: * **Assembler (On-prem only)** - select your [assembler](#prerequisites) from the list. * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Trellix”; this name will display in Workbench under the Name column, and is a text string that you can filter on. * **Location** - enter the location of your integration, for example “cloud;” this is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations. * **Server address** - enter the Endpoint Security (HX) device IP and communications port in the following format: `https://:3000`. Find the Device IP in the Endpoint Security (HX) console > Admin > Appliance Settings > Network. * **API username** - enter the API admin credentials from Step 2. * **API password** - enter the API admin credentials from Step 2. 6. Select **Save**. 7. On the console access screen, select **Set up now (recommended)** from the dropdown and provide your console URL and the user credentials from Step 1. 8. 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/q-z-integrations/trellix-endpoint-security-hx-formerly-fireeye-hx-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.