> 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/l-p-integrations/pingone-platform-via-collector-setup-for-workbench.md).

# PingOne Platform (via Collector) Setup for Workbench

## Prerequisites

1. You must have a **Splunk or Exabeam Fusion New-Scale SIEM Collector** available as a Security Device in Expel Workbench before onboarding PingOne Platform.

## Add PingOne Platform as a Security Device in Workbench

Please ensure you have met the [prerequisites](#prerequisites) before proceeding with this step.

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 “Ping” and then select the **PingOne Platform (via Collector)** integration.
5. A configuration pane displays. Complete the fields as follows:<br>

   <div align="left"><figure><img src="/files/3nFm2WY7xJ3XwLcJLvzL" alt="PingOne Platform (via Collector) Add a Security Device screen in Workbench." width="384"><figcaption></figcaption></figure></div>

   * **SIEM** - select an onboarded collector from the dropdown.
   * **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName PingOne Platform”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
   * **Location** - enter the location of your integration, for example “cloud.” This is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.
   * **Collector query** - this value will depend on the SIEM you are using:

{% tabs %}
{% tab title="Splunk" %}
Enter the following string, replacing **\<ping ID index>** with the value defined in your SIEM:

```
index=<ping ID index> status IN ("success","failure") event="AUTHN_ATTEMPT" | table *
```

{% endtab %}

{% tab title="Exabeam Fusion New-Scale SIEM" %}
Enter the following string:

```
vendor:"Ping Identity" AND ((product:"PingOne" AND activity:"authentication") OR (product:"Ping Identity" AND event_name:"AUTHN_ATTEMPT")) AND outcome:("success","fail") AND NOT user: null
```

{% endtab %}
{% endtabs %}

6. Select **Save**.
7. 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 receiving data.
   * To check on the status, click on the downward arrow for your device in the first column and choose **View details**. You can then scroll to the **Connection** section to see if your device is fully connected.
   * Polling will happen first; data will be received after that. **You must refresh the page to see updates.**&#x20;
   * If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team](/support/how-to-reach-us.md) for help.


---

# 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/l-p-integrations/pingone-platform-via-collector-setup-for-workbench.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.
