> 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/a-c-integrations/aurora-endpoint-security-formerly-cylance-protect-av-setup-for-workbench.md).

# Aurora Endpoint Security (formerly Cylance PROTECT AV) Setup for Workbench

## Step 1: Enable Console Access for Expel <a href="#uuid-c0e6298e-b3ae-2cf8-a222-34f54f60f7d3_bridgehead-26487" id="uuid-c0e6298e-b3ae-2cf8-a222-34f54f60f7d3_bridgehead-26487"></a>

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).

1. Log in to the Aurora Endpoint Security Console as an administrator.
2. Click **Settings > Users**.
3. Add a user for Expel with a Read-Only role.

## Step 2: Generate API Credentials <a href="#uuid-c0e6298e-b3ae-2cf8-a222-34f54f60f7d3_bridgehead-26492" id="uuid-c0e6298e-b3ae-2cf8-a222-34f54f60f7d3_bridgehead-26492"></a>

To integrate the technology with Workbench, we need to create secure credentials to the API.

1. Log in to the Aurora Endpoint Security Console **as an administrator**. Only administrators can create an application integration.
2. Select **Settings > Integrations**.
3. Click **Add Application**.
4. Type an **Application Name**. This must be unique within your organization.
5. Select **Threats READ**, **Devices READ**, and **Users READ** privileges.
6. Click **Save**. The application credentials appear.
7. Copy the **Tenant ID** located in the **Integrations** page and save for onboarding in Workbench.
8. Note your Cylance Service Endpoint. This can be found by mapping your CylanceENDPOINT in the table below.

| URL                                 | Service endpoint                       |
| ----------------------------------- | -------------------------------------- |
| <https://protect-apne1.cylance.com> | <https://protectapi-apne1.cylance.com> |
| <https://protect-euc1.cylance.com>  | <https://protectapi-euc1.cylance.com>  |
| <https://protect-au.cylance.com>    | <https://protectapi-au.cylance.com>    |
| <https://protect-sae1.cylance.com>  | <https://protectapi-sae1.cylance.com>  |
| <https://protect.us.cylance.com>    | <https://protectapi.us.cylance.com>    |
| <https://protect.cylance.com>       | <https://protectapi.cylance.com>       |

## Step 3: Add Aurora Endpoint Security as a Security Device in Workbench <a href="#uuid-c0e6298e-b3ae-2cf8-a222-34f54f60f7d3_bridgehead-26516" id="uuid-c0e6298e-b3ae-2cf8-a222-34f54f60f7d3_bridgehead-26516"></a>

Now that you have the correct access configured and noted the credentials, you can integrate your tech with Workbench.

1. [Log in to Workbench](https://workbench.expel.io/).
2. On the console page, navigate to **Settings** and click **Security Devices**.
3. At the top of the page, click **Add Security Device**.
4. Search for and select **Aurora Endpoint Security**.
5. Configure the fields as follows:
   * **Name** - type the hostname of the Aurora Endpoint Security device.
   * **Location** - type the geographic location of the appliance.
   * **Tenant ID** - type the Tenant ID generated in [Step 2](#uuid-c0e6298e-b3ae-2cf8-a222-34f54f60f7d3_bridgehead-26492).
   * **Application ID** - type the Application ID generated in [Step 2](#uuid-c0e6298e-b3ae-2cf8-a222-34f54f60f7d3_bridgehead-26492).
   * **Application secret** - type the application secret generated in [Step 2](#uuid-c0e6298e-b3ae-2cf8-a222-34f54f60f7d3_bridgehead-26492).
   * **Service Endpoint** - type your correct Service Endpoint from the table in [Step 2](#uuid-c0e6298e-b3ae-2cf8-a222-34f54f60f7d3_bridgehead-26492).

<div align="left"><figure><img src="/files/GBk34X9XZnMfnSMjVUmg" alt="Aurora Endpoint Security add security device page in Workbench." width="375"><figcaption></figcaption></figure></div>

6. Click **Save**.
7. On the console access screen, select **Set up now**.
8. Provide these details:
   * **Console URL** - enter the console URL from the **Server address** in the **Connection Settings** area in the Workbench security device configuration window. At the end of the URL, type **/login**.
   * **Username** - enter the user name you created above.
   * **Password** - enter the password you created above.
   * **Two-factor secret key (32-character code)** - depending on how your organization enforces log-ins, this field may not apply to you. In these cases, you can leave it blank. This field is optional and if you have questions or concerns, reach out to your Customer Success Manager or to support.
9. Click **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/a-c-integrations/aurora-endpoint-security-formerly-cylance-protect-av-setup-for-workbench.md?ask=<question>&goal=<endgoal>
```

`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.