> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/ping-identity/pingone/ping-identity.md).

# Ping Identity

Use the Ping Identity data in Cortex XSIAM.

The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.

This connector includes the following capabilities and sub-capabilities (if applicable):

* Security Posture: Detect, monitor and alert on settings of your SaaS application.
  * saas-posture-config-remediation: Help remediate the misconfigured security settings of your SaaS application.

### How to configure the Ping Identity connector

To access Ping Identity, Cortex XSIAM requires the following information, which you will specify during the connection process.

* **Client ID** and **Client Secret**
* **Environment ID** and **Region** 

#### Task 1: Connect to the Ping Identity API

1. Log in to Ping Identity as an administrator assigned to either the Organization Admin or Environment Admin role.
2. Create a Ping Identity worker application, which will inherit your role assignments and enable access to the API. Copy the application's Client ID and Client Secret.
3. Copy your Environment ID and Region, which are shown on your environment page in Ping Identity.
4. During onboarding, provide the following information:
   * The Client ID and Client Secret of the worker application
   * Your Environment ID and Region

#### Task 2: Connect **Ping Identity** to Cortex XSIAM

1. In Cortex XSIAM, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Sources or Integrations** page, search for Ping Identity.
4. Under **Recommended**, hover over the new Ping Identity integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, Enter a Name for your application.
6. Select Security Posture under **Default Capabilities**. Click **Next**.
7. Under **Connection**, provide the following:
   * **Environment ID**: Your Ping Identity Environment ID.
   * **Region**: Your Ping Identity region.
   * **Client Secret**: The Client Secret of the worker application.
   * **Client ID**: The Client ID of the worker application.
8. Click **Next**.
9. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments. Click **Next**.
10. A confirmation message indicates that Ping Identity is successfully connected. Confirm the Summary details and click **Save instance**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/ping-identity/pingone/ping-identity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.