1. Resources
  2. Detection rules
  3. Unauthorized Operation Attempts in the Idira (formerly CyberArk) Vault

Unauthorized Operation Attempts in the Idira (formerly CyberArk) Vault detection rules

A Vault user tries operations it has no permission for, such as listing or retrieving accounts, reading other users or changing users, groups and Safe owners. The Vault refuses each one and records it as unauthorized.

Platform
Idira (formerly CyberArk)
Severity
Medium
Log source
Idira (formerly CyberArk) Vault audit log
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft Sentinel
What an attacker needs
A Vault user the attacker can log on with through the web portal, the REST API or the PrivateArk Client, and nothing more than that.
Impact
The refusals show the attacker where the user's permissions end, while the same session performs every operation the user is allowed.
Response
Disable the Vault user and end its sessions until its owner has confirmed the operations, and start a password change for every account it retrieved.
Mitigation
Give each Vault user only the Safes, Safe permissions and Vault authorizations its work needs, and require multi-factor authentication for all users.
Vault event codes
4041424355563063070282930and 27 more in the rules below

How the attack works

An attacker who takes over a Vault user does not know what that user may do, so the first step is to try. They list and search the accounts in Safes, try to retrieve a password, read the details of other users, or try to add a user or make themselves an owner of a Safe. A person doing their job works in the same few Safes and rarely meets a refusal. A user that collects refusals across several kinds of operation is testing where its permissions end.

The Vault refuses these operations and writes an audit record for each one. CyberArk's code table marks such records in its Alert column, which the page explains as an unauthorized operation, for example a task performed without permission. Refused reads include codes 40 and 41 (List Files (Unauthorized)), 42 and 43 (Retrieve File (Unauthorized)), 55 and 56 (Find Files (Unauthorized)), 306 and 307 (Use Password (Unauthorized)) and 178 (Get User's Details (Unauthorized)). Refused changes include 173 (Add User (Unauthorized)), 28 to 30 (Add/Update Owner (Unauthorized)) and 261 (Add Group Member (Unauthorized)). Codes 15 and 18 record a refused impersonation, the mechanism through which a gateway account such as the one of the web portal logs users on to the Vault. The table gives the names of the codes and not the permission that was missing.

What must be collected. The rules read the Vault's audit records forwarded by syslog in CEF format (SIEM integration, configured in DBParm.ini). The CEF header's Device Event Class ID carries the Vault audit action code and the extension key suser carries the issuer, the Vault user who performed the operation. SyslogMessageCodeFilter must not exclude the codes the rules read. By default all codes are sent.

What an attacker needs

  • A Vault user the attacker can log on with, through the web portal, the REST API or the PrivateArk Client.
  • Nothing more. The operations on this page are the ones that user is not allowed to perform.

Impact

A refused operation gives the attacker nothing except the knowledge of where the user's permissions end. The refusals matter because of what surrounds them. The same session also performs the operations that are allowed, such as retrieving the passwords of the Safes the user is a member of, and a user that probes in this way is usually no longer in the hands of its owner.

Detection rules

One CyberArk Vault User Refused Many Times When Listing, Searching or Retrieving Accounts

Counts, per issuer, the attempts to list, find, retrieve or use the files of a Safe that the CyberArk Digital Vault refused: audit action codes 40 and 41 (List Files (Unauthorized)), 42 and 43 (Retrieve File (Unauthorized)), 55 and 56 (Find Files (Unauthorized)) and 306 and 307 (Use Password (Unauthorized)). The code table flags all eight in its Alert column, which CyberArk explains as an unauthorized operation, and gives the file name in Info1. In the Vault an account is a file in a Safe, so these are refused attempts to see or take privileged accounts. One refusal is a permission gap. Ten or more for one user within 10 minutes is a user trying one Safe or account after another. The count and the window are starting points: CyberArk does not document how many of these records ordinary work produces. deviceEventClassId is the CEF header's Device Event Class ID, which CyberArk's syslog translator fills with the Vault audit action code; suser is the issuer, the Vault user who performed the action.

Fires when one suser has at least 10 matching events within 10 minutes.

Threshold ruleLevelMediumStatusExperimentalLog sourceIdira (formerly CyberArk) Vault audit log
title: CyberArk Vault Refused a Listing, Search, Retrieval or Use of Accounts (Probing Base Event)
id: 46453034-70af-424d-a956-882fa50e8340
name: cyberark_vault_refused_account_listing_or_retrieval
status: experimental
description: >-
  Base event of the threshold rule in this file. An attempt to list, find,
  retrieve or use files in a Safe that the CyberArk Digital Vault refused:
  audit action codes 40 and 41 (List Files (Unauthorized)), 42 and 43
  (Retrieve File (Unauthorized)), 55 and 56 (Find Files (Unauthorized)) and
  306 and 307 (Use Password (Unauthorized)).
logsource:
  product: cyberark
  service: vault
detection:
  selection:
    deviceEventClassId:
      - '40'
      - '41'
      - '42'
      - '43'
      - '55'
      - '56'
      - '306'
      - '307'
  condition: selection
level: low
---
title: One CyberArk Vault User Refused Many Times When Listing, Searching or Retrieving Accounts
id: d6767a52-08e3-4f4f-a57e-35ec6118ea7a
status: experimental
description: >-
  Counts, per issuer, the attempts to list, find, retrieve or use the files of
  a Safe that the CyberArk Digital Vault refused: audit action codes 40 and 41
  (List Files (Unauthorized)), 42 and 43 (Retrieve File (Unauthorized)), 55
  and 56 (Find Files (Unauthorized)) and 306 and 307 (Use Password
  (Unauthorized)). The code table flags all eight in its Alert column, which
  CyberArk explains as an unauthorized operation, and gives the file name in
  Info1. In the Vault an account is a file in a Safe, so these are refused
  attempts to see or take privileged accounts. One refusal is a permission
  gap. Ten or more for one user within 10 minutes is a user trying one Safe
  or account after another. The count and the window are starting points:
  CyberArk does not document how many of these records ordinary work
  produces. deviceEventClassId is the CEF header's Device Event Class ID,
  which CyberArk's syslog translator fills with the Vault audit action code;
  suser is the issuer, the Vault user who performed the action.
references:
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasref/vault%20audit%20action%20codes.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/create-custom-xsl-translator-file.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/safes-add-a-safe-member.htm
  - https://attack.mitre.org/techniques/T1087/
author: Forestall
date: 2026-11-18
tags:
  - attack.discovery
  - attack.t1087
correlation:
  type: event_count
  rules:
    - cyberark_vault_refused_account_listing_or_retrieval
  group-by:
    - suser
  timespan: 10m
  condition:
    gte: 10
falsepositives:
  - A script, integration or report job that runs with too few Safe permissions and repeats the same refused request. Regular refusals at fixed intervals for the same file point to this. Fix the permissions or the job instead of excluding the user.
  - A user whose Safe membership was removed or reduced and who keeps working from bookmarks or saved searches.
  - The values of 10 refusals and 10 minutes are starting points, not tested limits. Measure the refusals of a normal week in your own audit and adjust both.
level: medium

False positives

  • A script, integration or report job that runs with too few Safe permissions and repeats the same refused request. Regular refusals at fixed intervals for the same file point to this. Fix the permissions or the job instead of excluding the user.
  • A user whose Safe membership was removed or reduced and who keeps working from bookmarks or saved searches.
  • The values of 10 refusals and 10 minutes are starting points, not tested limits. Measure the refusals of a normal week in your own audit and adjust both.

CyberArk Vault Refused a Change to Users, Groups, Safe Owners or Directory Maps

Detects an attempt to change who has access to the CyberArk Digital Vault that the Vault refused because the issuer had no permission for it. Safe owners: audit action codes 28, 29 and 30 (Add/Update Owner (Unauthorized)) and 196 and 197 (Update Owners (Unauthorized)). Users: 173 (Add User), 174 (Update User), 175 (Update Your User), 176 (Delete User), 177 (Delete Your User) and 63 and 65 (Rename User), each with (Unauthorized) in its name. Groups: 260 (Add/Update Group), 261 (Add Group Member), 262 (Delete Group Member), 263 (Update Group) and 269 (Delete Group), each (Unauthorized). Directory maps: 0 (Delete), 253 (Update), 255 (Add) and 214, 215 and 216 (Add, Update and Delete Directory Map LDAP Branch), each (Unauthorized). The code table flags all of them in its Alert column, which CyberArk explains as an unauthorized operation. Nothing changed, but someone tried to create a user, widen a group or make a user an owner of a Safe with an account that may not do so. Look for the same change succeeding later with another issuer. deviceEventClassId is the CEF header's Device Event Class ID, which CyberArk's syslog translator fills with the Vault audit action code.

LevelMediumStatusExperimentalLog sourceIdira (formerly CyberArk) Vault audit log
title: CyberArk Vault Refused a Change to Users, Groups, Safe Owners or Directory Maps
id: d58c4b0c-463b-4d35-9441-47f1a6328bbf
status: experimental
description: >-
  Detects an attempt to change who has access to the CyberArk Digital Vault
  that the Vault refused because the issuer had no permission for it. Safe
  owners: audit action codes 28, 29 and 30 (Add/Update Owner (Unauthorized))
  and 196 and 197 (Update Owners (Unauthorized)). Users: 173 (Add User), 174
  (Update User), 175 (Update Your User), 176 (Delete User), 177 (Delete Your
  User) and 63 and 65 (Rename User), each with (Unauthorized) in its name.
  Groups: 260 (Add/Update Group), 261 (Add Group Member), 262 (Delete Group
  Member), 263 (Update Group) and 269 (Delete Group), each (Unauthorized).
  Directory maps: 0 (Delete), 253 (Update), 255 (Add) and 214, 215 and 216
  (Add, Update and Delete Directory Map LDAP Branch), each (Unauthorized). The
  code table flags all of them in its Alert column, which CyberArk explains as
  an unauthorized operation. Nothing changed, but someone tried to create a
  user, widen a group or make a user an owner of a Safe with an account that
  may not do so. Look for the same change succeeding later with another
  issuer. deviceEventClassId is the CEF header's Device Event Class ID, which
  CyberArk's syslog translator fills with the Vault audit action code.
references:
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasref/vault%20audit%20action%20codes.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/users-groups-add-users-pa.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/safes-add-a-safe-member.htm
  - https://attack.mitre.org/techniques/T1098/
author: Forestall
date: 2026-11-18
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098
logsource:
  product: cyberark
  service: vault
detection:
  selection:
    deviceEventClassId:
      - '0'
      - '28'
      - '29'
      - '30'
      - '63'
      - '65'
      - '173'
      - '174'
      - '175'
      - '176'
      - '177'
      - '196'
      - '197'
      - '214'
      - '215'
      - '216'
      - '253'
      - '255'
      - '260'
      - '261'
      - '262'
      - '263'
      - '269'
  condition: selection
falsepositives:
  - An administrator whose role was reduced and who tries a task they used to perform, or a help desk user who opens a function outside their delegation. Confirm with the issuer what they were trying to do.
  - Provisioning scripts and identity management integrations that run with a user that lacks the Add/Update Users authorization or the Manage Safe Members permission. Fix the permissions of the integration.
level: medium

False positives

  • An administrator whose role was reduced and who tries a task they used to perform, or a help desk user who opens a function outside their delegation. Confirm with the issuer what they were trying to do.
  • Provisioning scripts and identity management integrations that run with a user that lacks the Add/Update Users authorization or the Manage Safe Members permission. Fix the permissions of the integration.

CyberArk Vault Refused an Impersonation

Detects an impersonation that the CyberArk Digital Vault refused: audit action codes 15 (Impersonation not by an agent) and 18 (Non authorized impersonation). The code table flags both in its Alert column, which CyberArk explains as an unauthorized operation, and gives a user name in Info1 for code 18. CyberArk documents impersonation as what a gateway account does: an application such as the web portal logs a user on to the Vault after the user authenticated elsewhere, or passes a partial impersonation token to another component. A refused impersonation means that an account or host that is not set up as a gateway tried to act for another user. The code table gives no description beyond the two names, so the rule matches the codes alone. deviceEventClassId is the CEF header's Device Event Class ID, which CyberArk's syslog translator fills with the Vault audit action code.

LevelMediumStatusExperimentalLog sourceIdira (formerly CyberArk) Vault audit log
title: CyberArk Vault Refused an Impersonation
id: 424df723-5b2c-4c56-8ec4-283784fa7b74
status: experimental
description: >-
  Detects an impersonation that the CyberArk Digital Vault refused: audit
  action codes 15 (Impersonation not by an agent) and 18 (Non authorized
  impersonation). The code table flags both in its Alert column, which
  CyberArk explains as an unauthorized operation, and gives a user name in
  Info1 for code 18. CyberArk documents impersonation as what a gateway
  account does: an application such as the web portal logs a user on to the
  Vault after the user authenticated elsewhere, or passes a partial
  impersonation token to another component. A refused impersonation means
  that an account or host that is not set up as a gateway tried to act for
  another user. The code table gives no description beyond the two names, so
  the rule matches the codes alone. deviceEventClassId is the CEF header's
  Device Event Class ID, which CyberArk's syslog translator fills with the
  Vault audit action code.
references:
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasref/vault%20audit%20action%20codes.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/accessing-the-vault-through-a-gateway-account.htm
  - https://attack.mitre.org/techniques/T1098/
author: Forestall
date: 2026-11-18
tags:
  - attack.privilege-escalation
  - attack.t1098
logsource:
  product: cyberark
  service: vault
detection:
  selection:
    deviceEventClassId:
      - '15'
      - '18'
  condition: selection
falsepositives:
  - A web portal or session manager that was installed or reconfigured with a user that is not defined as a gateway account, or a Safe that is not shared with the gateway account. These produce the record repeatedly from the address of the component, so fix the configuration.
level: medium

False positives

  • A web portal or session manager that was installed or reconfigured with a user that is not defined as a gateway account, or a Safe that is not shared with the gateway account. These produce the record repeatedly from the address of the component, so fix the configuration.

CyberArk Vault Refused a Lookup of Users, Group Members or the LDAP Configuration

Detects an attempt to read who exists in the CyberArk Digital Vault that the Vault refused: audit action codes 178 (Get User's Details (Unauthorized)), 179 (Get Your User's Details (Unauthorized)), 186 (Get UserDetails By Identifier (Unauthorized User)), 271 (List Group Members (Unauthorized)), 222 (List Directory Map LDAP Branches (Unauthorized)) and 3 (Get LDAP configuration data (Unauthorized)). The code table flags all six in its Alert column, which CyberArk explains as an unauthorized operation. Reading users, the members of groups such as Vault Admins and the directory integration is how someone with a foothold finds the accounts worth taking next. The Audit Users authorization is what lets a user track other users in the Vault, and the REST method that returns a user's details requires it. The code table gives the user, group or map name in Info1 for four of these codes and no fields for codes 3 and 186, so the rule matches the codes alone. deviceEventClassId is the CEF header's Device Event Class ID, which CyberArk's syslog translator fills with the Vault audit action code.

LevelLowStatusExperimentalLog sourceIdira (formerly CyberArk) Vault audit log
title: CyberArk Vault Refused a Lookup of Users, Group Members or the LDAP Configuration
id: dea86212-1b04-48ae-b1eb-d8354b55151f
status: experimental
description: >-
  Detects an attempt to read who exists in the CyberArk Digital Vault that the
  Vault refused: audit action codes 178 (Get User's Details (Unauthorized)),
  179 (Get Your User's Details (Unauthorized)), 186 (Get UserDetails By
  Identifier (Unauthorized User)), 271 (List Group Members (Unauthorized)),
  222 (List Directory Map LDAP Branches (Unauthorized)) and 3 (Get LDAP
  configuration data (Unauthorized)). The code table flags all six in its
  Alert column, which CyberArk explains as an unauthorized operation. Reading
  users, the members of groups such as Vault Admins and the directory
  integration is how someone with a foothold finds the accounts worth taking
  next. The Audit Users authorization is what lets a user track other users
  in the Vault, and the REST method that returns a user's details requires it.
  The code table gives the user, group or map name in Info1 for four of these
  codes and no fields for codes 3 and 186, so the rule matches the codes
  alone.
  deviceEventClassId is the CEF header's Device Event Class ID, which
  CyberArk's syslog translator fills with the Vault audit action code.
references:
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasref/vault%20audit%20action%20codes.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/users-groups-add-users-pa.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/sdk/get-user-details-v10.htm
  - https://attack.mitre.org/techniques/T1087/
author: Forestall
date: 2026-11-18
tags:
  - attack.discovery
  - attack.t1087
logsource:
  product: cyberark
  service: vault
detection:
  selection:
    deviceEventClassId:
      - '3'
      - '178'
      - '179'
      - '186'
      - '222'
      - '271'
  condition: selection
falsepositives:
  - A user without the Audit Users authorization who opens a user or group page in the web portal or the PrivateArk Client. Several of these from one user in a short time, or together with other refused operations, deserve more attention than one.
  - Integrations and inventory scripts that read users with an account that lacks the authorization. Fix the permissions of the integration.
level: low

False positives

  • A user without the Audit Users authorization who opens a user or group page in the web portal or the PrivateArk Client. Several of these from one user in a short time, or together with other refused operations, deserve more attention than one.
  • Integrations and inventory scripts that read users with an account that lacks the authorization. Fix the permissions of the integration.

Detection logic

Patterns that need more than one event, a baseline or knowledge of your own environment. Each is a hypothesis to build and tune in your SIEM, not a ready rule.

Refused on a Safe, then added to that Safe, then a retrieval from it

Detection hypothesisSequence of events

An attacker who is refused does not stop. If they also hold a user with the Manage Safe Members permission, the refusal is followed by a new Safe member and then by the retrieval that was refused before. The three records together show a permission that was created to get past a refusal.

  1. A user is refused in a Safe: code 40, 41, 42, 43, 306 or 307. Keep the issuer (suser), the Safe field of the audit record and the file the code table gives in Info1.
  2. Within 24 hours a member is added to the same Safe or an existing member is updated: code 32 (Add Owner) or 33 (Update Owner), where the code table gives the member's user name in Info1. Keep the records in which that name is the refused user or a group it belongs to.
  3. After that the refused user retrieves from the same Safe: code 295 (Retrieve password) or 428 (Retrieve SSH Key) with the same suser and Safe.
  4. Compare the issuer of the code 32 or 33 record with the refused user, and check the change against an access request.

Events404142433063073233295428

LimitsA user who asks for access after a refusal and receives it through the normal process produces the same three records, so the result has to be compared with access requests. The Safe field of the audit record reaches the SIEM under a key that depends on the translator file. The 24 hours are a starting point.

Triage

  • Read the issuer (suser), the code and the Station of the audit record, and the Safe, file or user the operation was aimed at.
  • Count the refusals of that user over the last day, and how many different codes and Safes they cover. One refusal in a Safe the user works with is a gap in its permissions. Refusals across many Safes, or in user and group management, are probing.
  • List what the same user did successfully around the refusals, above all retrievals (codes 295 and 428), new Safe members (code 32) and new users (code 180).
  • Find the logon of the session (code 7) and compare its station and time with the user's usual ones.
  • For codes 15 and 18, identify the user and the host that tried to impersonate. Only gateway accounts, such as the one of the web portal, are meant to do this.
  • Ask the owner of the user whether they tried these operations, through a channel other than the Vault.

Response

Once the attack is confirmed:

  1. Disable the Vault user and end its sessions until its owner has confirmed which operations were their own.
  2. Reset the user's password and second factor before it is enabled again.
  3. List everything the user did successfully since its first unusual logon, and start a password change for every account it retrieved or used.
  4. Reverse the changes the user made to Safe members, users, groups and directory maps that nobody approved.
  5. Block the station the session came from if it is not one of the owner's, and look for other Vault users that logged on from it.

Mitigation

  • Give each Vault user only the Safes, Safe permissions and Vault authorizations its work needs, so that a user in the wrong hands meets a refusal early and often.
  • Require multi-factor authentication for all users and administrators of the Vault, as CyberArk's security fundamentals do.
  • Keep gateway accounts few and protect the servers that hold their credentials, because a gateway account logs other users on to the Vault by impersonation.
  • Forward the Vault audit to your SIEM and alert on refused operations per user, not only on successful ones.

Frequently asked questions

What does the Alert column in CyberArk's audit code table mean?

CyberArk's Vault Audit Action Codes page says the column indicates that an unauthorized operation was performed, and gives a task performed without permission and an authentication failure as examples. The rules on this page read codes that carry this flag and whose names say Unauthorized, or name an impersonation that was not authorized. The table does not say which permission was missing.

Does one refused operation mean the Vault user is compromised?

No. A person who opens a Safe they were removed from, or tries an action their role does not include, produces the same record. The pattern that deserves attention is one user with refusals across many Safes or across several kinds of operation in a short time, above all when the logon came from an unusual station.

Why are refused listing and retrieval attempts counted instead of alerted on one by one?

A single refused read is common enough to be noise, and CyberArk does not document how many such records ordinary work in the web portal produces. The threshold rule therefore counts them per user and fires at 10 within 10 minutes. Both values are starting points. Measure a normal week in your own audit before you rely on them.

Is there a public incident report that describes this pattern?

No public incident report describes this at the audit event level. The page rests on what CyberArk documents: the Vault refuses operations a user has no permission for and records them with codes that the vendor flags as unauthorized operations.

References

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.