> For the complete documentation index, see [llms.txt](https://docs.oort.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oort.io/integrations/cisco-identity-services-engine-ise.md).

# Cisco Identity Services Engine (ISE)

## Overview

Cisco Identity Intelligence connects to Cisco Identity Services Engine (ISE) through a secure, on-premises agent to collect identity, device, network session, authentication, and deployment health data from ISE and provide visibility into connected users and devices, ISE infrastructure health, and authentication activity.\
\
The goal of this guide is to help you configure the integration between Identity Intelligence and your organization’s ISE environment, including deploying the agent, configuring pxGrid, verifying the connection, and troubleshooting common issues.

### 1. Set up the ISE Agent

Refer to the [ISE documentation](https://www.cisco.com/c/en/us/td/docs/security/ise/ise-cloud-central-agent/cisco-ise-cloud-central-agent-integration.html) for instructions on how to configure the ISE Agent

### 2. Create the Cisco ISE integration within Identity Intelligence

<img src="https://582105988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqPSBzsjxd7KYg9DNVZ4l%2Fuploads%2FuuEOU8iezbcYhJsYnlQP%2Funknown.png?alt=media&amp;token=34f2e917-96f2-4cfd-8a6d-b62aa924fe67" alt="" height="285" width="609">

1. Using an Admin role in Cisco Identity Intelligence, navigate to **Integrations** and select **Cisco ISE**
2. Enter a name and (optional) description into the form. Be sure to use a name that easily identifies the ISE cluster or location
3. Select **Generate ISE Agent Package.** Identity Intelligence will then provision the agent identity, and display the deployment package and copyable install command
4. Save the deployment material *immediately*. Use **Download ISE Agent Package** or C**opy Command**. <mark style="color:$danger;">Note:</mark> You **must** save these credentials as they **cannot** be displayed again after leaving the setup page; if replacement material is generated and deployed, the running agent credentials are rotated.

<img src="https://582105988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqPSBzsjxd7KYg9DNVZ4l%2Fuploads%2FbRtOHX7uDOZ5rMeegVjn%2Funknown.png?alt=media&amp;token=a2e96fee-f82f-45d6-bc4a-f38fe473a165" alt="" height="264" width="609">
