1. Resources
  2. Detection rules
  3. PingOne Audit Webhook Deleted or Changed

PingOne Audit Webhook Deleted or Changed detection rules

An attacker with PingOne administrator rights deletes, redirects or narrows the webhook that streams audit activities to the SIEM, so that the changes that follow are not delivered to defenders.

Platform
Ping Identity
Severity
Medium
Log source
PingOne audit activities
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft Sentinel
What an attacker needs
A PingOne role that can manage webhooks in the environment, such as Environment Admin.
Impact
Detections that depend on the stream stop firing for the environment, and investigators have to pull activities from PingOne by hand.
Response
Recreate or repair the webhook from the reviewed copy and confirm that events reach the SIEM again, then remove the actor's role and reset its credentials.
Mitigation
Restrict the roles that can manage webhooks, and collect audit activities through two independent paths such as a webhook and API polling.
Action types
SUBSCRIPTION.CREATEDSUBSCRIPTION.DELETEDSUBSCRIPTION.UPDATEDSUBSCRIPTION.QUEUE_CLEARED
Threat groups
APT29

How the attack works

PingOne streams audit activities to external tools through webhooks, which the API calls subscriptions. A webhook has a destination URL, optional headers such as the SIEM's collector token, and a list of the event types it sends: an event type that is not selected is not delivered. Ping documents that when the destination is unreachable, PingOne queues and retries events and starts to lose them after 7 days.

An administrator who can edit webhooks can therefore blind the SIEM without touching the audit log itself: delete the webhook, disable it, change its destination, remove event types from its filter, or clear its queue. PingOne records these operations as SUBSCRIPTION.DELETED, SUBSCRIPTION.UPDATED and SUBSCRIPTION.QUEUE_CLEARED audit activities. The activities stay available in the PingOne audit report and the Audit Activities API, which is where to look when the stream stops. A second rule reads SUBSCRIPTION.CREATED: next to a deleted webhook a new one is a replacement whose destination has to be checked, and on its own it sends a copy of the selected activities to a destination that somebody chose.

Log source: the rule reads PingOne audit activities. A deleted webhook may not deliver the activity that records its own deletion, so also poll the Audit Activities API (as the Microsoft Sentinel connector does) or alert in the SIEM when the PingOne source goes silent.

What an attacker needs

  • A PingOne role that can manage webhooks in the environment, such as Environment Admin.

Impact

Detections that depend on the stream stop firing for the environment, and investigators have to pull activities from PingOne by hand. Audit data in PingOne is immediately available for 14 days; older data has to be requested and cannot be requested beyond 2 years.

Detection rules

PingOne Webhook Created

Detects a new PingOne webhook (audit activity SUBSCRIPTION.CREATED; the API calls a webhook a subscription). A webhook sends the event types selected in it to its destination URL. Next to a deleted webhook, a new one is a replacement: check that it points to your SIEM and sends the same event types. On its own, a new webhook sends a copy of the selected audit activities, with user names and source addresses, to a destination that somebody chose. The destination is not in the documented event fields: read it in the webhook's configuration.

LevelMediumStatusExperimentalLog sourcePingOne audit activities
title: PingOne Webhook Created
id: d61e2ccf-ebad-479d-a74d-4cbf7186ad16
status: experimental
description: >-
  Detects a new PingOne webhook (audit activity SUBSCRIPTION.CREATED; the API
  calls a webhook a subscription). A webhook sends the event types selected in
  it to its destination URL. Next to a deleted webhook, a new one is a
  replacement: check that it points to your SIEM and sends the same event
  types. On its own, a new webhook sends a copy of the selected audit
  activities, with user names and source addresses, to a destination that
  somebody chose. The destination is not in the documented event fields: read
  it in the webhook's configuration.
references:
  - https://attack.mitre.org/techniques/T1685/002/
  - https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
  - https://developer.pingidentity.com/pingone-api/platform/subscriptions-webhooks/index.html
author: Forestall
date: 2026-11-18
tags:
  - attack.defense-impairment
  - attack.t1685.002
logsource:
  product: pingone
  service: audit
detection:
  selection:
    action.type: SUBSCRIPTION.CREATED
  condition: selection
falsepositives:
  - Planned onboarding of a new monitoring or SIEM destination, and test webhooks in development environments. Webhooks are created rarely, so confirm each one and its destination with the change record.
level: medium

False positives

  • Planned onboarding of a new monitoring or SIEM destination, and test webhooks in development environments. Webhooks are created rarely, so confirm each one and its destination with the change record.

PingOne Webhook Deleted, Updated or Queue Cleared

Detects a PingOne webhook (subscription) being deleted or updated, or its queue being cleared (audit activities SUBSCRIPTION.DELETED, SUBSCRIPTION.UPDATED and SUBSCRIPTION.QUEUE_CLEARED). Webhooks carry audit activities to the SIEM, so each of these can stop or narrow what defenders receive.

LevelMediumStatusExperimentalLog sourcePingOne audit activities
title: PingOne Webhook Deleted, Updated or Queue Cleared
id: 8b400df2-9608-4257-838d-1e5921146786
status: experimental
description: >-
  Detects a PingOne webhook (subscription) being deleted or updated, or its
  queue being cleared (audit activities SUBSCRIPTION.DELETED,
  SUBSCRIPTION.UPDATED and SUBSCRIPTION.QUEUE_CLEARED). Webhooks carry audit
  activities to the SIEM, so each of these can stop or narrow what defenders
  receive.
references:
  - https://attack.mitre.org/techniques/T1685/002/
  - https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
  - https://developer.pingidentity.com/pingone-api/platform/subscriptions-webhooks/index.html
author: Forestall
date: 2026-11-11
tags:
  - attack.defense-impairment
  - attack.t1685.002
logsource:
  product: pingone
  service: audit
detection:
  selection:
    action.type:
      - SUBSCRIPTION.DELETED
      - SUBSCRIPTION.UPDATED
      - SUBSCRIPTION.QUEUE_CLEARED
  condition: selection
falsepositives:
  - Planned changes to the event types a webhook sends, token rotation on the destination header, and removal of test webhooks.
level: medium

False positives

  • Planned changes to the event types a webhook sends, token rotation on the destination header, and removal of test webhooks.

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.

PingOne activities stop arriving from an environment that normally sends them

Detection hypothesisNeeds a baselineJoins two logs

A deleted or narrowed webhook may not deliver the activity that records the change, so the rules on this page can miss the very event they look for. What the SIEM can always see is the silence that follows. An environment that normally delivers activities every hour and then delivers none, or whose webhook delivers fewer activities than the Audit Activities API holds for the same period, has lost its stream.

  1. Count the PingOne activities that reach the SIEM per environment (resources.environment.id) and per hour, and learn the usual count for each hour of the week over the last 30 days.
  2. Alert when an environment whose usual count is well above zero delivers nothing for two consecutive hours.
  3. Where a second path exists, such as API polling next to the webhook, compare the two per hour on the activity id. Activities present only in the polled copy, above all SUBSCRIPTION.UPDATED, SUBSCRIPTION.DELETED and SUBSCRIPTION.QUEUE_CLEARED, show which change silenced the stream.

EventsSUBSCRIPTION.UPDATEDSUBSCRIPTION.DELETEDSUBSCRIPTION.QUEUE_CLEARED

LimitsCollector outages, expired collector tokens and quiet environments also fall silent, and Ping documents that PingOne queues and retries events for an unreachable destination, so a gap can fill in later. Removing a few event types from the webhook lowers the count without stopping it. The 30 days and two hours are starting points.

Triage

  • Identify the actor (actors.user.name or actors.client.name) and the webhook named in the activity, and check for an approved change.
  • Compare the webhook's destination, enabled state and event type list with the reviewed copy.
  • Pull the audit activities for the period after the change from the PingOne audit report or the Audit Activities API and review role, secret, identity provider, policy and key events in it.
  • Restore the webhook and backfill the SIEM from the API if events were lost.

Response

Once the attack is confirmed:

  1. Recreate or repair the webhook from the reviewed copy, with its destination, headers and full event type list, and confirm that events reach the SIEM again.
  2. If the destination was changed, replace the collector token at the SIEM. A webhook sends its headers with each event, so treat the token as disclosed to the other URL.
  3. Treat the actor as compromised. Remove its role, reset its credentials and end its sessions.
  4. Export the audit activities for the gap while they are within the 14 days that are immediately available, then reverse the role, secret, identity provider, policy and key changes found in them.
  5. Check the webhooks of every other environment for the same change, the Administrators environment first.

Mitigation

  • Restrict Environment Admin and custom roles that can manage webhooks.
  • Collect audit activities through two independent paths, for example a webhook and API polling, at least for the Administrators environment.
  • Alert in the SIEM when no PingOne events arrive for a period that is unusual for the environment.
  • Keep a reviewed copy of each webhook's destination and event type list and compare it after every change event.

Frequently asked questions

Will the SIEM receive the activity that reports the webhook's own deletion?

It may not. A deleted webhook may not deliver the activity that records its own deletion. Collect audit activities through a second path as well, for example by polling the Audit Activities API as the Microsoft Sentinel connector does, or alert in the SIEM when the PingOne source goes silent.

Does deleting the webhook remove audit data from PingOne?

No. The webhook only carries a copy, and the activities stay in the PingOne audit report and the Audit Activities API. Audit data is immediately available for 14 days. Older data has to be requested and cannot be requested beyond 2 years, so pull the gap soon after you notice it.

How can a webhook be silenced without deleting it?

An administrator can disable it, change its destination, remove event types from its filter, or clear its queue. An event type that is not selected is not delivered. PingOne records these edits as `SUBSCRIPTION.UPDATED` and `SUBSCRIPTION.QUEUE_CLEARED`, so compare the webhook with your reviewed copy after every such activity.

What happens to events while the SIEM endpoint cannot be reached?

Ping documents that PingOne queues and retries events when the destination is unreachable, and starts to lose them after 7 days. An outage of the collector can therefore be recovered for a while. A `SUBSCRIPTION.QUEUE_CLEARED` activity during such an outage deserves an explanation, because clearing the queue is one of the ways to blind the SIEM.

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.