> 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/cyberark/cyberark.md).

# CyberArk

Use CyberArk data with Cortex XSIAM.

{% hint style="warning" %}
**Important**

This connector is only available for tenants that onboarded after July 26, 2026. For tenants that onboarded before this date, use Marketplace to access the standalone integration. For more information, see [Marketplace](/cortex-xsiam/configure-cortex-xsiam/marketplace.md).
{% endhint %}

CyberArk secures human and machine identities across hybrid and multi-cloud environments. This connector collects audit and authentication events from the CyberArk Identity Security Platform, CyberArk Identity, and CyberArk Endpoint Privilege Manager (EPM), activates and deactivates EPM risk plans for endpoints as a SOC response, and retrieves certificate information from CyberArk Certificate Manager.

This connector includes the following sub-capabilities (Marketplace integrations link to PAN DEV for more information):

* [CyberArk Identity Event Collector](https://xsoar.pan.dev/docs/reference/integrations/cyber-ark-identity-event-collector): This integration collects events from the Idaptive Next-Gen Access (INGA) using REST APIs. This sub-capability is available with any active Cortex XSIAM license.
* [CyberArkEPMEventCollector](https://xsoar.pan.dev/docs/reference/integrations/cyber-ark-epm-event-collector): CyberArk EPM Event Collector fetches events. This sub-capability is available with any active Cortex XSIAM, Cortex Cloud, Cortex Cloud Runtime Security, or Cortex XDR license.
* [CyberArkEPMSOCResponse](https://xsoar.pan.dev/docs/reference/integrations/cyber-ark-epmsoc-response): Use the CyberArk EPM integration to activate and deactivate CyberArk EPM risk plans for specific endpoints. This sub-capability is available with any active Cortex XSIAM, Cortex XDR, or Cortex AgentiX license.
* [CyberArkISP](https://xsoar.pan.dev/docs/reference/integrations/cyber-ark-isp): CyberArk Identity Security Platform secures human and machine identities across hybrid/multi-cloud environments with intelligent privilege controls, AI-driven threat detection, and Zero Trust enforcement. This sub-capability is available with any active Cortex XSIAM license.
* [VenafiTLSProtect](https://xsoar.pan.dev/docs/reference/integrations/venafi-tls-protect): This sub-capability is available with any active Cortex XSIAM or Cortex AgentiX license.

To configure this connector, follow the steps outlined in the configuration wizard.


---

# 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/cyberark/cyberark.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.