1. Expel Support Center
  2. Connect your technology
  3. Endpoint integrations

Cisco AMP setup for Workbench

  • Updated

This article explains how to connect Cisco AMP to Workbench.

In this article

Step 1: Enable console access

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.

This procedure creates a user account for Expel that keeps the Expel activity separate from other activity on the Cisco AMP console.

Note

Expel secures all login information our SOC analysts need about your devices in a 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.

  1. Navigate to Accounts > Users.

  2. Click + New User.

  3. Add the user.

    • For First Name add Expel.

    • For Last Name add SOC.

    • For Login Email add soc+<Your_Organization_Name>@expel.io.

      Tip

      Yes, the "+" sign is part of the email address, and it's important. Click here to find out why.

    • Select Administrator checkbox.

  4. Click Create.

Step 2: Generate API credentials

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.

  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: Configure the technology 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, login to https://workbench.expel.io.

  2. On the console page, navigate to Settings and click Security Devices.

  3. At the upper right of the page, select Add Security Device.

  4. Search for and select Cisco.

  5. For Name type the host name of the Cisco AMP device.

    Screen Shot 2021-07-16 at 4.55.13 PM.png

    • For Location type the geographic location of the device.

    • For API key and Client ID, type the API credentials generated in Step 2.

    • For Username and Password type credentials previously created in the Cisco AMP console.

  6. Click Save.

  7. You can provide console access now or set it up later. Use the instructions below to set it up later.

You can see if the device is healthy on the Security Devices page. It may take a few minutes to see the device listed as healthy.

To check if alerts are coming through, navigate to the Alerts Analysis page. Scroll to the device you want to check and click View alerts. Switch to grid view, then check the list for device alerts. It can take 36 to 72 hours for alerts to appear after setup, as we tune your device.

Step 4: Edit the device to add console access

Expel needs console access to your device to allow our SOC analysts to dig deeper during incident investigations. Additionally, our engineering teams use this access to investigate potential health issues, including proper alert ingestion.

Note

Expel secures all login information our SOC analysts need about your devices in a 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.

  1. Open Workbench. Go to Organization Settings > Security Devices. Next to the device you just connected, click the down arrow and click Edit.

  2. In the Console Login area, type these details:

    • Console URL: type the console URL from the Server address in the Connection Settings area above. At the end of the URL, type /login.

    • Username: type the user name you created above.

    • Password: type 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 engagement manager or to support.

  3. Click Save.

Tip

This article was accurate at the time of writing, but changes happen. If you find the instructions are outdated, leave a description in the comment field below and let us know!

  • Was this article helpful?

  • 0 out of 0 found this helpful

Related articles