> 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/cisco/cisco-secure-endpoint-formerly-amp-setup-for-workbench.md).
# Cisco Secure Endpoint (Formerly AMP) Setup for Workbench
## Step 1: Enable Console Access
Expel requires console access to allow analysts to perform investigation and triage. Without this additional level of information, alerts cannot be verified by our analysts and an investigation cannot be initiated. [Learn more about why Expel asks for console access](/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md).
This procedure creates a user account for Expel that keeps the Expel activity separate from other activity on the Secure Endpoint console.
1. Navigate to **Accounts > Users**.
2. Click **+ New User**.
3. Configure the user:
* **First Name** - enter add "Expel".
* **Last Name** - enter add "SOC".
* **Login Email** - enter add "soc+\@expel.io".
* For example, if your organization were Acme Corp, the format would be "".
* Select the **Administrator** checkbox.
4. Click **Create**.
## Step 2: Generate API Credentials
1. Navigate to **Accounts > API Credentials**.
2. Click **+New API Credential**.
3. For Application name, enter "**expelapi"**.
4. For Scope, select **Read-Only**.
5. Click **Create**.
6. A new page opens with your **API Key Details**. **Save these items** as they are not easily accessible later in the process and are needed for onboarding in Workbench.
## Step 3: Add Cisco Secure Endpoint as a Security Device in Workbench
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/auth/login?orig=%2F).
2. In the side menu, navigate to **Organization Settings > Security Devices**.
3. Select **Add Security Device**.
4. In the search box, type "Cisco" and then select the **Cisco Secure Endpoint (formerly AMP)** integration.
5. Configure the fields as follows:
* **Name** - enter the host name of the Secure Endpoint device.
* **Location** - enter the geographic location of the device.
* **API key** and **Client ID**- enter the API credentials generated in [Step 2](#uuid-f748a2ce-97ae-2bdf-4521-ebdfd25fccfb_bridgehead-26545).
6. Select **Save**.
7. On the console access screen, select **Set up later**, as Expel will complete console access configuration with the user you created in [Step 1](#uuid-f748a2ce-97ae-2bdf-4521-ebdfd25fccfb_bridgehead-26533).
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/a-c-integrations/cisco/cisco-secure-endpoint-formerly-amp-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.