> 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-secure-access-data-integration.md).

# Cisco Secure Access Data Integration

## Overview

Identity Intelligence integrates with Cisco Secure Access to ingest and display data associated with Application and User and Entity Behavior Analytics events (UEBA).\
\
For information on configuring Secure Access to consume Trust Level data from Identity Intelligence via Security Cloud Control (SCC), please refer to the [Secure Access documentation](https://securitydocs.cisco.com/docs/csa/olh/136576.dita) guide, which contains information about connecting both an existing or new Identity Intelligence tenant to your Secure Access organization. If you already have an Identity Intelligence tenant via Duo, **please** follow the "Existing Tenant" set up steps.&#x20;

### Configuration Steps&#x20;

Follow the instructions below in the order written

#### Generate an API Key in Secure Access

You will first need to generate an API key with the necessary permissions within Secure Access. To do so:

1. Log in to your Secure Access org with a **Full Admin** or **Security Administrator** role
2. Navigate to the **Admin** menu item and select **API Keys**

<figure><img src="/files/mIX38ZZdhngCg8F17YeM" alt="" width="375"><figcaption></figcaption></figure>

3. Select **Add**, then enter a easily recognizable name and a description for the key
4. Assign the key the required scopes by selecting the respective check boxes:

   1. Deployments (Identities and Networks)&#x20;
   2. Reports &#x20;

   <figure><img src="/files/oELjBdm1FEGBGeNopNqk" alt=""><figcaption></figcaption></figure>
5. Select `Read-Only` for each selected scope and resource
6. For **Expiry Date** choose an expiration date or select **Never Expire.** Do NOT enter any information in the Network Restrictions area
7. Select **Create Key.** Then copy and save your API Key and Key Secret in a secure location, as you will need this information to complete the integration steps within Identity Intelligence
8. Select **Accept and Close**

#### Identity Intelligence Configuration Steps

1. Sign in to Identity Intelligence with an Administrator role
2. Navigate to **Integrations** and select **Add Integration** from the Secure Access tile
3. Enter a **name** for the integration. This name will be reused through Identity Intelligence to identify the source
4. Paste the **API Key** and **Key Secret** generated in Secure Access into their respective fields in the form

<figure><img src="/files/nQb8dw0v9szKOraku4Ey" alt=""><figcaption></figcaption></figure>

5. Select **Save** to finish setting up the integration
6. Your integration has been created! Identity Intelligence will test the connectivity automatically, and if there are no errors, will begin the data ingestion process&#x20;


---

# 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.oort.io/integrations/cisco-secure-access-data-integration.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.
