1. Resources
  2. Detection rules
  3. Vault User Created or Added to a Vault Group in Idira (formerly CyberArk)

Vault User Created or Added to a Vault Group in Idira (formerly CyberArk) detection rules

An attacker with the Add/Update Users authorization creates a Vault user or adds one to a group such as Vault Admins, and keeps administrative access to the Digital Vault after the first foothold is closed.

Platform
Idira (formerly CyberArk)
Severity
High
Log source
Idira (formerly CyberArk) Vault audit log
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft Sentinel
What an attacker needs
A Vault user with the Add/Update Users authorization, at the same level or higher in the Vault hierarchy than the user or group it changes.
Impact
A second identity with administrative or Safe access that survives a password reset of the first one, up to control of the Vault's configuration through Vault Admins.
Response
Remove the member from the group and disable the new user, and suspend the issuer until the change is explained.
Mitigation
Give Add/Update Users to as few named administrators as possible, and keep Vault Admins small with native accounts protected by multi-factor authentication.
Vault event codes
61318265180331182211

How the attack works

Vault groups carry rights. The predefined Vault Admins group is added automatically to the System Safe and to the Safes that hold the configuration and internal accounts of the Central Policy Manager, Password Vault Web Access and Privileged Session Manager, and only its members can open the Master Policy page. Other groups are members of the Safes that hold privileged accounts. Adding a member to a Vault group through the REST API needs only the Add/Update Users authorization, the same authorization that lets its holder create users at the same level or lower in the Vault hierarchy.

An attacker who controls an account with that authorization can create a new native user, or pick a dormant one, and add it to Vault Admins or to a group with access to sensitive Safes. CyberArk advises that Vault administrators are native accounts rather than directory accounts, so new native users and new group members should be few and explainable. Two further rules read changes to an existing user: codes 182 and 211 (Update User, Update User Detailed Information), and codes 61 and 318 (Update Trusted Network Areas, Activate/Deactivate Trusted Network Areas), which change the locations on the network from which a user can log on to the Vault. Which authorization or area changed is in the detail text of the record, not in a field the rules can filter on.

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: 180 is Add User, 331 is Add User By Template and 265 is Add Group Member. Users created from an LDAP directory at first logon (code 2, Add External User) and members added by LDAP synchronization (code 286) have their own codes and are not matched. SyslogMessageCodeFilter must not exclude these codes.

What an attacker needs

  • A Vault user with the Add/Update Users authorization, at the same level or higher in the Vault hierarchy than the user or group it changes.

Impact

A second identity with administrative or Safe access that survives a password reset of the first one. Membership of Vault Admins gives control of the Vault's configuration, and membership of a group that is a member of Tier 0 Safes gives the accounts in them.

Detection rules

CyberArk Trusted Network Areas of a Vault User Changed

Detects a change to the Trusted Network Areas of a user in the CyberArk Digital Vault (audit action codes 61, Update Trusted Network Areas, and 318, Activate/Deactivate Trusted Network Areas). CyberArk describes Trusted Network Areas as the locations on the network from which a user can access the Vault. An update can add a location the user could not log on from before. An activation also releases a user whose area the Vault deactivated after too many violations, such as logons with an incorrect password, so it can follow a guessing attempt and gives it a new series of tries. Code 318 is written for activation and deactivation alike. 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 Trusted Network Areas of a Vault User Changed
id: 05ebb53a-8c83-48ac-abfd-e993303e5b05
status: experimental
description: >-
  Detects a change to the Trusted Network Areas of a user in the CyberArk
  Digital Vault (audit action codes 61, Update Trusted Network Areas, and 318,
  Activate/Deactivate Trusted Network Areas). CyberArk describes Trusted
  Network Areas as the locations on the network from which a user can access
  the Vault. An update can add a location the user could not log on from
  before. An activation also releases a user whose area the Vault deactivated
  after too many violations, such as logons with an incorrect password, so it
  can follow a guessing attempt and gives it a new series of tries. Code 318
  is written for activation and deactivation alike. 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/trusted-network-areas.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:
      - '61'
      - '318'
  condition: selection
falsepositives:
  - Administrators who reactivate a user after mistyped passwords. Confirm with the user that the failed logons were their own before the area is activated again.
  - Planned changes to where administrators may log on from, for example a new jump host network.
level: medium

False positives

  • Administrators who reactivate a user after mistyped passwords. Confirm with the user that the failed logons were their own before the area is activated again.
  • Planned changes to where administrators may log on from, for example a new jump host network.

CyberArk Vault Group Member Added

Detects a member being added to a group in the CyberArk Digital Vault (audit action code 265, Add Group Member). The group and the member are named in the audit record; treat additions to Vault Admins and to groups that are members of sensitive Safes as high priority. Members added by LDAP synchronization use code 286 and are not matched. 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 Group Member Added
id: c751173b-fdb8-417a-9edd-bf7b583a6f28
status: experimental
description: >-
  Detects a member being added to a group in the CyberArk Digital Vault (audit
  action code 265, Add Group Member). The group and the member are named in
  the audit record; treat additions to Vault Admins and to groups that are
  members of sensitive Safes as high priority. Members added by LDAP
  synchronization use code 286 and are not matched. 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/predefined-users-and-groups.htm
  - https://attack.mitre.org/techniques/T1098/
author: Forestall
date: 2026-11-11
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098
logsource:
  product: cyberark
  service: vault
detection:
  selection:
    deviceEventClassId: '265'
  condition: selection
falsepositives:
  - Planned changes to Vault groups by the PAM team; alert on changes made by any other issuer or outside a change window.
  - Component installation and upgrade, which add component users to their groups.
level: medium

False positives

  • Planned changes to Vault groups by the PAM team; alert on changes made by any other issuer or outside a change window.
  • Component installation and upgrade, which add component users to their groups.

CyberArk Vault User Created

Detects a new user being created in the CyberArk Digital Vault (audit action codes 180, Add User, and 331, Add User By Template). Users created from an LDAP directory at first logon are recorded as code 2 (Add External User) and are not matched. 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 User Created
id: 88cbcba4-9153-44b4-9ef8-33e1cc4beb01
status: experimental
description: >-
  Detects a new user being created in the CyberArk Digital Vault (audit action
  codes 180, Add User, and 331, Add User By Template). Users created from an
  LDAP directory at first logon are recorded as code 2 (Add External User)
  and are not matched. 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://attack.mitre.org/techniques/T1136/
author: Forestall
date: 2026-11-11
tags:
  - attack.persistence
  - attack.t1136
logsource:
  product: cyberark
  service: vault
detection:
  selection:
    deviceEventClassId:
      - '180'
      - '331'
  condition: selection
falsepositives:
  - New administrators and application users created by the PAM team; match each alert to a request.
  - Component installation, which creates the component users.
level: medium

False positives

  • New administrators and application users created by the PAM team; match each alert to a request.
  • Component installation, which creates the component users.

CyberArk Vault User Updated

Detects an existing user being updated in the CyberArk Digital Vault (audit action codes 182, Update User, and 211, Update User Detailed Information). An update can change the user's Vault authorizations, such as Add/Update Users or Manage Directory Mapping, its authentication method, its logon hours and whether it is disabled. The code table gives the user name for code 182 and a free text detail for code 211, so which property changed is in the detail text of the record and not in a field this rule can filter on. Updates of users that come from an LDAP directory use code 256 and are not matched. 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 User Updated
id: 5f7f6dce-4097-4ab1-8867-6d59ac514dd6
status: experimental
description: >-
  Detects an existing user being updated in the CyberArk Digital Vault (audit
  action codes 182, Update User, and 211, Update User Detailed Information).
  An update can change the user's Vault authorizations, such as Add/Update
  Users or Manage Directory Mapping, its authentication method, its logon
  hours and whether it is disabled. The code table gives the user name for
  code 182 and a free text detail for code 211, so which property changed is
  in the detail text of the record and not in a field this rule can filter
  on. Updates of users that come from an LDAP directory use code 256 and are
  not matched. 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://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:
      - '182'
      - '211'
  condition: selection
falsepositives:
  - Routine maintenance of user profiles by the PAM team, such as contact details, logon hours or an expiry date. Read the detail text and alert when authorizations or the authentication method changed.
level: low

False positives

  • Routine maintenance of user profiles by the PAM team, such as contact details, logon hours or an expiry date. Read the detail text and alert when authorizations or the authentication method changed.

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.

User added to Vault Admins and removed again within a few hours

Detection hypothesisSequence of events

Vault Admins controls the Vault's configuration, and a membership that lasts only a few hours is missing from the next membership review. An attacker who holds Add/Update Users can add a user, use the group's rights and remove the member again. An Add Group Member and a Remove Group Member for the same group and user, with actions by that user between them, is that pattern.

  1. The Vault records code 265 (Add Group Member), for which the code table gives the group in Info1 and the user in Info2. Keep the records whose group is Vault Admins or a group that is a member of Safes that hold Tier 0 accounts, and the issuer (suser).
  2. Within 24 hours the Vault records code 266 (Remove Group Member) for the same group and user.
  3. Between the two records, list what that user did: records with the user as suser, such as code 7 (Logon), 385 (a change to the Master Policy), 32 or 33 (a Safe member added or updated) and 295 (Retrieve password).
  4. Compare the issuers of the addition and the removal, and check both against a change record.

Events26526673853233295

LimitsElevation for a maintenance task through an approved change, and component installation or upgrade, add and remove members on purpose. Membership that comes from LDAP synchronization (code 286) is not seen. The group and user reach the SIEM under keys that depend on the translator file. The 24 hours are a starting point.

Triage

  • Read the group and the member named in the audit record, and raise the priority when the group is Vault Admins or a member of Safes that hold Tier 0 accounts.
  • Identify the issuer (suser) and confirm the change with that administrator through a separate channel.
  • For a new user, check its authorizations, authentication method and group memberships, and whether it has logged on.
  • If it was not approved, remove the member or disable the user and review what both accounts did since the change.

Response

Once the attack is confirmed:

  1. Remove the member from the group and disable the new user. If a dormant user was reused, reset its authentication as well.
  2. Suspend the issuer until the change is explained and take away its Add/Update Users authorization.
  3. If the group was Vault Admins, review access to the System Safe and to the Safes that hold the configuration and internal accounts of the Central Policy Manager, Password Vault Web Access and Privileged Session Manager.
  4. Remove what the two accounts set up afterwards, such as further users, Safe members, directory maps and Master Policy changes.
  5. Start a password change for the privileged accounts they retrieved, then confirm the members of Vault Admins and of the groups on Tier 0 Safes against the approved list.

Mitigation

  • Give Add/Update Users to as few named administrators as possible and remove it from service and integration accounts that do not provision users.
  • Keep Vault Admins small, with native accounts protected by multi-factor authentication, as CyberArk recommends.
  • Require approval for group membership changes and review the members of Vault Admins and of groups on Tier 0 Safes on a schedule.
  • Forward the Vault audit to your SIEM and alert on new users and group members.

Frequently asked questions

Does the rule see users that arrive from the LDAP directory?

No. Users created from an LDAP directory at first logon are recorded as code 2, Add External User, and members added by LDAP synchronization as code 286. Neither code is matched. The rules for new users and group members cover code 180, Add User, code 331, Add User By Template, and code 265, Add Group Member.

Why is the Add/Update Users authorization so sensitive?

Adding a member to a Vault group through the REST API needs only the Add/Update Users authorization, the same one that lets its holder create users at the same level or lower in the Vault hierarchy. An account that holds it can create a user, or pick a dormant one, and add it to Vault Admins or to a group with access to sensitive Safes. Give it to as few named administrators as possible.

Why does a component installation or upgrade raise these alerts?

Component installation creates the component users, and installation and upgrade add component users to their groups. Those records look the same as a manual change. Match them to the maintenance window, and alert on changes made by any other issuer or outside a change window.

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.