> 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/detection-strategy-guides/a-c/cyberark/cyberark-identity-detection-strategy.md).

# CyberArk Identity Detection Strategy

## Product Overview <a href="#h_01k0wc4k0hnhxhj6mmpc3mmvnz" id="h_01k0wc4k0hnhxhj6mmpc3mmvnz"></a>

CyberArk Identity is an Identity and Access Management (IAM) solution that delivers secure access to applications and resources for any user, from any device, anywhere. It provides a comprehensive set of capabilities including Single Sign-On (SSO), adaptive Multi-Factor Authentication (MFA), and user lifecycle management to enforce intelligent, context-aware access policies and protect against identity-based threats. The platform is built on the principles of Zero Trust, verifying every access request to ensure that only authorized users can access sensitive data. By integrating with a wide range of applications, both in the cloud and on-premises, CyberArk Identity helps organizations reduce password-related risks, streamline compliance and auditing, and provide a seamless and secure user experience.

## What We Support for CyberArk Identity <a href="#h_01jxzrm2r6th1sjj5hwce4qc2f" id="h_01jxzrm2r6th1sjj5hwce4qc2f"></a>

To see a comprehensive list of the most up-to-date Expel detection rules, vendor detection rules, opt-in detections, and available DUETs (**d**id yo**u** **e**xpect **t**his) that we support for CyberArk Identity, you can visit the [Detections page](https://workbench.expel.io/tools/detections/all?filter=%7B%22supportedTech%22%3A%7B%22is%22%3A%5B%22cyberark_identity%3A1.0.0%22%5D%7D%7D) in Workbench or ask your Sales or Support rep for the most recent download.

| **Supported versions**                        | <ul><li>21.11.133+</li></ul>                                                                                                                                                                                                                                                                       |
| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supported event log sources**               | <ul><li>Expel collects all CyberArk Identity event types from the Events (RedRock) API. Detection coverage prioritizes authentication, MFA, credential-change, and administrative or privilege event types, while all event types remain available for both detection and investigation.</li></ul> |
| **CyberArk Identity detection rules support** | No.                                                                                                                                                                                                                                                                                                |
| **Detection rules written by Expel**          | Yes.                                                                                                                                                                                                                                                                                               |
| **Auto remediations**                         | No.                                                                                                                                                                                                                                                                                                |
| **Investigative support through Workbench**   | <p>Yes. We are able to take the following investigative actions to gather data for triage and investigation of events:</p><ul><li>Query User</li><li>Query IP Address</li><li>Query Logs</li><li>Query Raw Logs</li></ul>                                                                          |
| **Hunting support**                           | <p>No. Hunting is not currently available for this<br>integration.</p>                                                                                                                                                                                                                             |

## Additional Details and Common Questions <a href="#h_01jx38a4wqthksj31zbt76vt7s" id="h_01jx38a4wqthksj31zbt76vt7s"></a>

#### Console Access <a href="#h_01jx38ambp5pyrrbe1cmr3vmg9" id="h_01jx38ambp5pyrrbe1cmr3vmg9"></a>

A vendor alert does not typically include all of the contextual timeline activity surrounding the event of interest. Because this integration does not allow us to get all necessary data via the API, we will ask you for a certain level of console access during onboarding.

The level of access that we require is meant to support essential triage and research activities, and to help us determine the vector and extent of attacker activity for an identified threat. At minimum, we will ask for visibility into alert data, timeline events recorded, and live response/real time response shell (if applicable).

#### DUET <a href="#id-01jx38b7g0r611et51ks5eq8ba" id="id-01jx38b7g0r611et51ks5eq8ba"></a>

A DUET (**d**id yo**u** **e**xpect **t**his) rule flags certain events as needing an immediate verification or notification, and bypasses the normal internal event triage process. The events subject to DUET rules contain behaviors that are not typically indicative of true security incidents, as they are related to policy violations or potential risk.

There are a number of workflows that a DUET may follow. When enabled, the activity will be flagged for investigation and will be routed to you (rather than to us) to take a specified first action. To see the specific DUET rules currently supported for this integration, visit the [Detections page](https://workbench.expel.io/tools/detections/all) in Workbench.


---

# 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/detection-strategy-guides/a-c/cyberark/cyberark-identity-detection-strategy.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.