1. Resources
  2. Detection rules
  3. Safe, Account, Vault User or Group Deleted in Idira (formerly CyberArk)

Safe, Account, Vault User or Group Deleted in Idira (formerly CyberArk) detection rules

An attacker with delete rights removes accounts and Safes, or the Vault users, groups and Safe owners that could respond. The organization loses stored credentials or the people who can reach them, often as the last step of an intrusion.

Platform
Idira (formerly CyberArk)
Severity
High
Log source
Idira (formerly CyberArk) Vault audit log
Last updated
Tactic
Impact
Rule formats
Sigmaand queries for: SplunkMicrosoft Sentinel
What an attacker needs
The Delete accounts or Manage Safe permission for accounts and Safes, the Add/Update Users authorization for users and groups, or Manage Safe Members for owners.
Impact
Accounts, Safes, users or Safe owners are gone from the Vault, which removes stored credentials or the access of the people who would respond.
Response
Suspend the issuer, undelete the accounts while the retention period lasts and restore deleted users, groups and Safe members from the approved list.
Mitigation
Keep delete rights with few named administrators and keep the retention period of Safes long enough to notice a deletion and undelete the accounts.
Vault event codes
52183266273184270276277

How the attack works

For an account whose password the Central Policy Manager changes, the Vault holds the only current value. An attacker who wants to cause damage instead of stealing deletes those accounts, or removes the people who could respond: the Vault users and groups of the PAM team and the owners of the Safes. Each step needs its own right. Deleting an account needs the Delete accounts permission in its Safe, deleting a Safe needs Manage Safe, deleting a user or a group through the REST API needs the Add/Update Users authorization, and removing a member from a Safe needs Manage Safe Members.

CyberArk limits the damage with retention. A deleted account can be undeleted during the file retention period of its Safe. A Safe can only be deleted when it is empty and the retention period of all its accounts and files has ended, and a deleted Safe cannot be recovered. The Vault records each deletion: code 52 (Delete File) for an account or file, 183 (Delete Safe), 184 (Delete User), 270 (Delete Group), 276 and 277 (Delete External User, Delete External Group), 273 (Remove Owner) for a member removed from a Safe and 266 (Remove Group Member). Members removed by the LDAP synchronization have their own code, 287, which the rules do not match.

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 deletion. SyslogMessageCodeFilter must not exclude codes 52, 183, 184, 266, 270, 273, 276 and 277. By default all codes are sent.

What an attacker needs

  • For accounts: a Safe member with the Delete accounts permission.
  • For a Safe: the Manage Safe permission, and a Safe that is empty and whose retention period has ended.
  • For Vault users and groups: the Add/Update Users authorization.
  • For Safe members: the Manage Safe Members permission. CyberArk states that a member can only remove members with the same or fewer permissions.

Impact

Deleted accounts can no longer be retrieved, used for sessions or managed, and once the retention period has passed their passwords are gone from the Vault. Deleted users and groups, and removed Safe owners, take away the access of the people who run the Vault and of everyone who works through it. A deleted Safe cannot be recovered. During an intrusion this slows the response at the moment privileged accounts have to be changed.

Detection rules

Many Accounts or Files Deleted From the CyberArk Vault by One User

Counts, per issuer, the accounts and files deleted from Safes of the CyberArk Digital Vault (audit action code 52, Delete File). In the Vault an account is a file in a Safe, and deleting one needs the Delete accounts permission. One user who deletes 20 or more within 15 minutes is either a planned clean-up or migration, or someone who destroys the stored credentials of the Safes that user can reach. CyberArk documents that a deleted account can be undeleted only during the file retention period of its Safe, so the alert matters while that period lasts. The code table gives the file name in Info1. The rule counts audit records and not distinct accounts, because the key that carries the file name differs between translator files. The count and the window are starting points to tune. 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 20 matching events within 15 minutes.

Threshold ruleLevelHighStatusExperimentalLog sourceIdira (formerly CyberArk) Vault audit log
title: CyberArk Account or File Deleted From a Safe (Bulk Deletion Base Event)
id: d24a7245-f61b-4f87-8797-7e14d703039b
name: cyberark_account_or_file_deleted
status: experimental
description: >-
  Base event of the threshold rule in this file. An account or file deleted
  from a Safe of the CyberArk Digital Vault (audit action code 52, Delete
  File).
logsource:
  product: cyberark
  service: vault
detection:
  selection:
    deviceEventClassId: '52'
  condition: selection
level: low
---
title: Many Accounts or Files Deleted From the CyberArk Vault by One User
id: b48983f1-3efa-4036-bcc5-e970ec74acaa
status: experimental
description: >-
  Counts, per issuer, the accounts and files deleted from Safes of the
  CyberArk Digital Vault (audit action code 52, Delete File). In the Vault an
  account is a file in a Safe, and deleting one needs the Delete accounts
  permission. One user who deletes 20 or more within 15 minutes is either a
  planned clean-up or migration, or someone who destroys the stored
  credentials of the Safes that user can reach. CyberArk documents that a
  deleted account can be undeleted only during the file retention period of
  its Safe, so the alert matters while that period lasts. The code table
  gives the file name in Info1. The rule counts audit records and not
  distinct accounts, because the key that carries the file name differs
  between translator files. The count and the window are starting points to
  tune. 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/safes-add-a-safe-member.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/webservices/delete%20account.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/create-custom-xsl-translator-file.htm
  - https://attack.mitre.org/techniques/T1485/
author: Forestall
date: 2026-11-18
tags:
  - attack.impact
  - attack.t1485
correlation:
  type: event_count
  rules:
    - cyberark_account_or_file_deleted
  group-by:
    - suser
  timespan: 15m
  condition:
    gte: 20
falsepositives:
  - Decommissioning of systems, clean-up after discovery or a migration between Safes, done by an administrator or a script through the REST API. Match the issuer and the time with the change record.
  - Component and integration users, if your audit shows that they delete files as part of their normal work. CyberArk does not document which components write this code. Give such a user its own higher count instead of excluding it.
  - The values of 20 deletions and 15 minutes are starting points, not tested limits. Measure the deletions of a normal week in your own audit and adjust both.
level: high

False positives

  • Decommissioning of systems, clean-up after discovery or a migration between Safes, done by an administrator or a script through the REST API. Match the issuer and the time with the change record.
  • Component and integration users, if your audit shows that they delete files as part of their normal work. CyberArk does not document which components write this code. Give such a user its own higher count instead of excluding it.
  • The values of 20 deletions and 15 minutes are starting points, not tested limits. Measure the deletions of a normal week in your own audit and adjust both.

CyberArk Safe Deleted

Detects a Safe being deleted from the CyberArk Digital Vault (audit action code 183, Delete Safe). CyberArk states that a deleted Safe cannot be recovered, and that a Safe can only be deleted when it is empty and the retention period of all its accounts and files has ended. The record is therefore the last step of a longer sequence in which the accounts of the Safe were deleted first. Deleting a Safe needs the Manage Safe permission. The code table gives no fields for the code, so the rule matches the code alone and the Safe has to be read from the audit record. 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 Safe Deleted
id: 6d13c722-befb-4f33-8461-99a745cf3776
status: experimental
description: >-
  Detects a Safe being deleted from the CyberArk Digital Vault (audit action
  code 183, Delete Safe). CyberArk states that a deleted Safe cannot be
  recovered, and that a Safe can only be deleted when it is empty and the
  retention period of all its accounts and files has ended. The record is
  therefore the last step of a longer sequence in which the accounts of the
  Safe were deleted first. Deleting a Safe needs the Manage Safe permission.
  The code table gives no fields for the code, so the rule matches the code
  alone and the Safe has to be read from the audit record. 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/safes-manage-safes.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/webservices/delete%20safe.htm
  - https://attack.mitre.org/techniques/T1485/
author: Forestall
date: 2026-11-18
tags:
  - attack.impact
  - attack.t1485
logsource:
  product: cyberark
  service: vault
detection:
  selection:
    deviceEventClassId: '183'
  condition: selection
falsepositives:
  - Planned removal of empty or unused Safes, for example after a migration or when a team is dissolved. Match the Safe and the issuer with the change record.
level: medium

False positives

  • Planned removal of empty or unused Safes, for example after a migration or when a team is dissolved. Match the Safe and the issuer with the change record.

CyberArk Safe Member or Vault Group Member Removed

Detects a member being removed from a Safe or from a group of the CyberArk Digital Vault: audit action codes 273 (Remove Owner) and 266 (Remove Group Member). The audit calls the members of a Safe owners. Removing one needs the Manage Safe Members permission, and CyberArk states that a member can only remove members with the same or fewer permissions. The removal takes away a person's access to the accounts of the Safe, or to everything a group such as Vault Admins grants. In an attack it is used against the people who could change the stolen passwords. The code table gives the user name in Info1 of code 273 and the group and the user in Info1 and Info2 of code 266. Members removed by the LDAP synchronization have their own code, 287, 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 Safe Member or Vault Group Member Removed
id: f87292a7-add8-47d4-9747-3c534775e238
status: experimental
description: >-
  Detects a member being removed from a Safe or from a group of the CyberArk
  Digital Vault: audit action codes 273 (Remove Owner) and 266 (Remove Group
  Member). The audit calls the members of a Safe owners. Removing one needs
  the Manage Safe Members permission, and CyberArk states that a member can
  only remove members with the same or fewer permissions. The removal takes
  away a person's access to the accounts of the Safe, or to everything a
  group such as Vault Admins grants. In an attack it is used against the
  people who could change the stolen passwords. The code table gives the
  user name in Info1 of code 273 and the group and the user in Info1 and
  Info2 of code 266. Members removed by the LDAP synchronization have their
  own code, 287, 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/safes-manage-safe-members.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/webservices/removeuserfromgroup.htm
  - https://attack.mitre.org/techniques/T1531/
author: Forestall
date: 2026-11-18
tags:
  - attack.impact
  - attack.t1531
logsource:
  product: cyberark
  service: vault
detection:
  selection:
    deviceEventClassId:
      - '266'
      - '273'
  condition: selection
falsepositives:
  - Access reviews, role changes and offboarding, which remove members from Safes and groups all the time. Scope the alert to Vault Admins and to the Safes that hold Tier 0 accounts, or alert only when one issuer removes several members in a short time.
level: low

False positives

  • Access reviews, role changes and offboarding, which remove members from Safes and groups all the time. Scope the alert to Vault Admins and to the Safes that hold Tier 0 accounts, or alert only when one issuer removes several members in a short time.

CyberArk Vault User or Group Deleted

Detects a user or a group being deleted from the CyberArk Digital Vault: audit action codes 184 (Delete User), 270 (Delete Group), 276 (Delete External User) and 277 (Delete External Group). Deleting a user or a group through the REST API needs the Add/Update Users authorization. A deleted user can no longer log on, and a deleted group takes the Safe access of all its members with it. An attacker uses this to lock out the administrators who would respond, or to remove a user that was created for the attack. CyberArk notes that a deleted external user is created again at its next logon unless it is also deleted from the external directory. The code table gives the user or group name in Info1. 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 or Group Deleted
id: 7d4fd67e-5796-48de-9de1-4da4584b7414
status: experimental
description: >-
  Detects a user or a group being deleted from the CyberArk Digital Vault:
  audit action codes 184 (Delete User), 270 (Delete Group), 276 (Delete
  External User) and 277 (Delete External Group). Deleting a user or a group
  through the REST API needs the Add/Update Users authorization. A deleted
  user can no longer log on, and a deleted group takes the Safe access of all
  its members with it. An attacker uses this to lock out the administrators
  who would respond, or to remove a user that was created for the attack.
  CyberArk notes that a deleted external user is created again at its next
  logon unless it is also deleted from the external directory. The code
  table gives the user or group name in Info1. 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/sdk/users%20web%20services%20-%20delete%20user.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/sdk/users%20web%20services%20-%20delete%20user%20group.htm
  - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/users-groups-add-users-pa.htm
  - https://attack.mitre.org/techniques/T1531/
author: Forestall
date: 2026-11-18
tags:
  - attack.impact
  - attack.t1531
logsource:
  product: cyberark
  service: vault
detection:
  selection:
    deviceEventClassId:
      - '184'
      - '270'
      - '276'
      - '277'
  condition: selection
falsepositives:
  - Offboarding of people who left, and removal of users that are no longer used, which CyberArk's documentation advises. Match the deleted user with the offboarding record.
  - Removal of component users when a component server is retired.
level: medium

False positives

  • Offboarding of people who left, and removal of users that are no longer used, which CyberArk's documentation advises. Match the deleted user with the offboarding record.
  • Removal of component users when a component server is retired.

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.

Safe updated, emptied and deleted by the same issuer

Detection hypothesisSequence of eventsNeeds your own lists

A Safe can only be deleted when it is empty and the retention of its accounts has ended. Someone who wants a Safe gone for good therefore updates the Safe, deletes its accounts and deletes the Safe. Each record is ordinary housekeeping. All three on one Safe by one issuer is the destruction of a Safe.

  1. A Safe is updated: code 181 (Update Safe). Keep the issuer (suser) and the Safe field of the audit record.
  2. Accounts or files in that Safe are deleted: code 52 (Delete File), with the file name in Info1 according to the code table, by the same issuer.
  3. The Safe is deleted: code 183 (Delete Safe), by the same issuer, within 30 days of the first record.
  4. Compare the Safe with your list of Safes that hold Tier 0 accounts, and the sequence with a decommissioning record.

Events18152183

LimitsThe code table gives no detail field for code 181, so the record does not say that the retention was the property that changed. A planned clean-up of an unused Safe produces the same sequence. The Safe reaches the SIEM under a key that depends on the translator file. The 30 days are a starting point.

Triage

  • Read the issuer (suser) and the station of the audit record, and what was deleted. The code table gives the file name in Info1 of code 52, the user or group name in Info1 of codes 184, 270, 273, 276 and 277, and the group and the user in Info1 and Info2 of code 266.
  • For accounts, count the deletions by that issuer, list the Safes they are in and check whether those Safes hold Tier 0 accounts. Compare with a decommissioning or migration record.
  • For a deleted Safe, find when and by whom it was emptied, and whether its properties were updated before (code 181).
  • For users, groups and members, check whether the deleted or removed identity belongs to the PAM team or to Vault Admins, and whether an offboarding ticket exists.
  • Check which owners a Safe has left after a removal, and whether the issuer is one of them.
  • Review what the issuer did before the deletions, above all retrievals (codes 295 and 428) and changes to Safe members.

Response

Once the attack is confirmed:

  1. Suspend the issuer and end its sessions before more is deleted.
  2. Undelete the deleted accounts while the retention period lasts. CyberArk documents the Undelete button for members with the Update account content permission.
  3. Create the deleted users and groups again and restore Safe members from your last approved list. Use the Master user if no administrator is left with access.
  4. Restore deleted Safes from the Vault backup, and for accounts that cannot be brought back, set new passwords on the target systems and onboard them again.
  5. Start a password change for the accounts the issuer retrieved before the deletions, because deletion often follows theft.

Mitigation

  • Give the Delete accounts and Manage Safe permissions to as few Safe members as possible, and the Add/Update Users authorization to as few named administrators as possible.
  • Keep the retention period of objects in Safes long enough to notice a deletion and undelete the accounts. The default for Safes created in the web portal is 30 days, and 7 days where the portal was upgraded from an earlier version.
  • Back up the Vault and test the restore, as CyberArk's security fundamentals ask in the disaster recovery plan, so that deleted Safes, users and members can be brought back.
  • Keep the Master user's keys available and tested. CyberArk states that the Master user cannot be removed from any Safe and is used to manage a full recovery.
  • Forward the Vault audit to your SIEM and alert on deleted Safes, users and groups and on one user deleting many accounts.

Frequently asked questions

Can a deleted account be brought back?

Yes, for a limited time. CyberArk documents that members with the Update account content permission can undelete an account with the Undelete button on the page of the deleted account, and that this is only relevant during the file retention period. Safes created in the web portal keep objects for 30 days by default before they can be deleted for good, or 7 days where the portal was upgraded from an earlier version.

Can a Safe that still holds accounts be deleted?

No. CyberArk states that only empty Safes can be deleted and that all accounts and files must be permanently deleted first, which means their retention period has ended. A deleted Safe cannot be recovered. A Safe deletion is therefore the end of a longer sequence, and the earlier steps are in the audit.

Who can still get in when the administrators' Vault users were deleted?

The Master user. CyberArk describes it as the user that manages a full recovery, states that it cannot be removed from any Safe and that it can only log on with the Master CD, which holds the private recovery key. Keep that key where the security fundamentals say, in a physical safe that needs more than one person to open.

Is there a public incident report that describes deletions in the Vault?

No public incident report describes this at the audit event level. The page rests on what CyberArk documents about the delete permissions, the retention periods and the audit codes the Vault writes for each deletion.

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.