1. Resources
  2. Detection rules
  3. PingOne Application Created or Its Resource Access Changed

PingOne Application Created or Its Resource Access Changed detection rules

An attacker with PingOne administrator rights creates an application of their own, or edits an existing one and widens its resource grants, to obtain tokens from PingOne without any user's password.

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 create or edit applications in the environment, such as Client Application Developer.
Impact
The attacker holds a client that PingOne issues tokens to, which for a worker application with roles is durable access to the environment.
Response
Disable the unowned application or restore the changed settings from the inventory, replace the client secret and remove role assignments.
Mitigation
Limit the roles that can edit applications, and create worker applications with assignActorRoles set to false.
Action types
APPLICATION.CREATEDGRANT.CREATEDGRANT.UPDATEDAPPLICATION.UPDATED

How the attack works

An application in PingOne is an OAuth or SAML client: it has a client ID, a way to authenticate, a set of allowed grant types and redirect URIs, and resource access grants that name the resources and scopes it can request tokens for. Each of these is a way in for someone who can edit applications. A new worker application is the plainest one. It signs on with client credentials, without a user and without MFA, and Ping documents that by default the application is assigned the roles of the actor who creates it (assignActorRoles, which defaults to true and which Ping recommends setting to false for worker applications). An administrator account that is held for an hour can leave behind a client that keeps its roles.

Edits to an existing application are quieter. Adding a redirect URI sends authorization codes and tokens of real users to another address, enabling the client_credentials grant type lets the client act by itself, and a wider resource access grant lets it ask for scopes it never had. PingOne records these operations as APPLICATION.CREATED, APPLICATION.UPDATED, GRANT.CREATED and GRANT.UPDATED audit activities. The activities name the application, not the property that changed. The page follows Ping's documentation of applications and grants: no public incident report describes these steps for PingOne at the audit event level.

Log source: the rules read PingOne audit activities. Include the Application and Grant event types in the PingOne webhook that feeds the SIEM, or poll the Audit Activities API, for every environment. In environments where developers register applications daily the rules are for review, and they earn their place as context for role assignments and secret reads.

What an attacker needs

  • A PingOne role that can create or edit applications in the environment. Ping names the Client Application Developer role for operations on application resources.
  • For a worker application that is useful by itself, roles to pass on: either the creator's own roles through the default assignment, or a separate role assignment afterwards.

Impact

The attacker holds a client that PingOne issues tokens to. A worker application with administrator roles is durable access to the environment that survives the password reset of the account that created it. A changed redirect URI or grant on an existing application turns the sign-ons of its real users, or the application's own identity, into tokens for the attacker.

Detection rules

PingOne Application Created

Detects a new application in a PingOne environment (audit activity APPLICATION.CREATED, described by Ping as Application Created). An application is a client that PingOne issues tokens to. The type that matters most is the worker application, which signs on with client credentials and no user. Ping documents that a new application is assigned the roles of the actor who creates it unless assignActorRoles is set to false, and recommends false for worker applications. The activity does not carry the application type in a documented attribute, so the rule fires on every new application: read the type, the grant types and the role assignments of the application during triage.

LevelLowStatusExperimentalLog sourcePingOne audit activities
title: PingOne Application Created
id: fa5db04d-ca23-4355-ae56-b9924709355a
status: experimental
description: >-
  Detects a new application in a PingOne environment (audit activity
  APPLICATION.CREATED, described by Ping as Application Created). An
  application is a client that PingOne issues tokens to. The type that
  matters most is the worker application, which signs on with client
  credentials and no user. Ping documents that a new application is assigned
  the roles of the actor who creates it unless assignActorRoles is set to
  false, and recommends false for worker applications. The activity does not
  carry the application type in a documented attribute, so the rule fires on
  every new application: read the type, the grant types and the role
  assignments of the application during triage.
references:
  - https://attack.mitre.org/techniques/T1136/003/
  - https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
  - https://developer.pingidentity.com/pingone-api/platform/applications/applications-1/index.html
author: Forestall
date: 2026-11-18
tags:
  - attack.persistence
  - attack.t1136.003
logsource:
  product: pingone
  service: audit
detection:
  selection:
    action.type: APPLICATION.CREATED
  condition: selection
falsepositives:
  - Developers and administrators who register applications, and deployment pipelines that create them through the API. Add a filter on actors.client.name or actors.user.name for the identities that do this, after you have reviewed them, or alert only in production environments.
level: low

False positives

  • Developers and administrators who register applications, and deployment pipelines that create them through the API. Add a filter on actors.client.name or actors.user.name for the identities that do this, after you have reviewed them, or alert only in production environments.

PingOne Resource Access Grant Created or Updated

Detects the audit activities GRANT.CREATED and GRANT.UPDATED, which Ping's event list describes as Grant Created and Grant Updated. By its name the activity belongs to the resource access grants of an application (the grants endpoint under an application in the API). Ping's event list does not state the link, so confirm it with one test change. Ping documents a resource access grant as naming the resource associated with the application and the scopes of that grant, and scopes as defining the permissions an access token carries. A new grant, or a grant with more scopes, widens what tokens issued to the application can do, for example by adding scopes of the PingOne API. The activity does not carry the scopes in a documented attribute: read the grants of the application and compare them with your inventory.

LevelLowStatusExperimentalLog sourcePingOne audit activities
title: PingOne Resource Access Grant Created or Updated
id: 5162412f-3ba1-4510-8cb9-aada3f0ee151
status: experimental
description: >-
  Detects the audit activities GRANT.CREATED and GRANT.UPDATED, which Ping's
  event list describes as Grant Created and Grant Updated. By its name the
  activity belongs to the resource access grants of an application (the
  grants endpoint under an application in the API). Ping's event list does
  not state the link, so confirm it with one test change. Ping documents a
  resource access grant as naming the resource associated with the
  application and the scopes of that grant, and scopes as defining the
  permissions an access token carries. A new grant, or a grant with more
  scopes, widens what tokens issued to the application can do, for example by
  adding scopes of the PingOne API. The activity does not carry the scopes in
  a documented attribute: read the grants of the application and compare them
  with your inventory.
references:
  - https://attack.mitre.org/techniques/T1098/001/
  - https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
  - https://developer.pingidentity.com/pingone-api/platform/applications/application-resource-grants/index.html
  - https://developer.pingidentity.com/pingone-api/platform/resources/resource-scopes/index.html
author: Forestall
date: 2026-11-18
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098.001
logsource:
  product: pingone
  service: audit
detection:
  selection:
    action.type:
      - GRANT.CREATED
      - GRANT.UPDATED
  condition: selection
falsepositives:
  - New applications, which receive their grants when they are set up, and applications that start to use another API. Confirm with the application owner which scopes are needed.
level: low

False positives

  • New applications, which receive their grants when they are set up, and applications that start to use another API. Confirm with the application owner which scopes are needed.

PingOne Application Updated

Detects an application being updated in PingOne (audit activity APPLICATION.UPDATED, described by Ping as Application Updated). The properties of an application decide who can obtain tokens through it: its redirect URIs, to which authorization codes and tokens of users are sent, whether wildcards are allowed in them, its grant types, which include client_credentials, and how it authenticates to the token endpoint. A new redirect URI on a foreign host or a newly enabled grant type turns an existing, trusted application into a way to obtain tokens. The activity does not say which property changed, and edits of a name or an icon use the same activity, so the rule is for review: compare the application with your inventory.

LevelLowStatusExperimentalLog sourcePingOne audit activities
title: PingOne Application Updated
id: 4c470af8-8745-4e0b-a5cc-e67237083ad9
status: experimental
description: >-
  Detects an application being updated in PingOne (audit activity
  APPLICATION.UPDATED, described by Ping as Application Updated). The
  properties of an application decide who can obtain tokens through it: its
  redirect URIs, to which authorization codes and tokens of users are sent,
  whether wildcards are allowed in them, its grant types, which include
  client_credentials, and how it authenticates to the token endpoint. A new
  redirect URI on a foreign host or a newly enabled grant type turns an
  existing, trusted application into a way to obtain tokens. The activity
  does not say which property changed, and edits of a name or an icon use the
  same activity, so the rule is for review: compare the application with your
  inventory.
references:
  - https://attack.mitre.org/techniques/T1098/001/
  - https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
  - https://developer.pingidentity.com/pingone-api/platform/applications/applications-1/index.html
author: Forestall
date: 2026-11-18
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098.001
logsource:
  product: pingone
  service: audit
detection:
  selection:
    action.type: APPLICATION.UPDATED
  condition: selection
falsepositives:
  - Routine maintenance of applications, such as a new redirect URI for a new release or a changed name or logo. Expect regular volume and add a filter on the actors that deploy applications, after you have reviewed them.
level: low

False positives

  • Routine maintenance of applications, such as a new redirect URI for a new release or a changed name or logo. Expect regular volume and add a filter on the actors that deploy applications, after you have reviewed them.

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.

Application created, given an administrator role and its secret read by the same actor

Detection hypothesisSequence of events

A client that is meant as a back door needs three things in a short time: the application, a role and the secret. The three activities by one actor within minutes are how a credential for later use is minted, and together they are far rarer than a developer registering an application.

  1. Find an APPLICATION.CREATED activity and note the actor (actors.user.id, or actors.client.id when no user is the actor) and the application in resources.id.
  2. Look for ROLE_ASSIGNMENT.CREATED by the same actor within the next 15 minutes. Ping documents that a new application is assigned the creator's roles by default, so these can follow without a separate request.
  3. Look for SECRET.READ by the same actor in the same period, and check in the console that the role assignment and the secret belong to the new application.
  4. Check where the application authenticated from afterwards, if your environment records its token requests.

EventsAPPLICATION.CREATEDROLE_ASSIGNMENT.CREATEDSECRET.READ

LimitsSetting up a legitimate integration produces the same three activities, so the result is a short list to confirm with the owners, not a verdict. The documented attributes do not include the role name or the application type, and the window is a starting point.

Triage

  • Identify the actor (actors.user.name or actors.client.name) and the application named in the activity's resources, and check for an approved request or deployment.
  • Read the application through the API or the console. Check its type, its grant types, its redirect URIs, how it authenticates to the token endpoint, and whether it is enabled.
  • For a new application, list its role assignments and check whether its secret was read (SECRET.READ) and by whom.
  • For an updated application or grant, compare the redirect URIs, grant types and granted scopes with the inventory. A new redirect host, a newly enabled client_credentials grant or a PingOne API scope that was not there before is the change to act on.
  • Review what else the actor did in the same session, such as role assignments, sign-on policy assignments and secret reads.

Response

Once the attack is confirmed:

  1. Disable an application that nobody owns, then delete it once the investigation no longer needs it. Remove its role assignments first.
  2. Restore the redirect URIs, grant types and resource grants of a changed application from the inventory, and replace its client secret.
  3. Revoke the sessions and consents of users who signed on to the application while a foreign redirect URI was in place, and reset what the application's own tokens could have changed.
  4. Suspend the administrator or worker application that made the change and remove the role that allows it.
  5. Compare every application of the environment with the inventory, worker applications and their roles first.

Mitigation

  • Limit the Client Application Developer role and custom roles with application permissions, and review who holds them in every environment.
  • Create worker applications with assignActorRoles set to false, as Ping recommends, and assign each one only the roles it needs.
  • Keep an inventory of applications with their type, grant types, redirect URIs and resource grants, and compare it after every change event.
  • Do not allow wildcards in redirect URIs, and remove grant types an application does not use.
  • Review the list of worker applications and their role assignments regularly, and delete those without an owner.

Frequently asked questions

Why does a new worker application deserve more attention than other new applications?

A worker application calls the PingOne API as itself, with client credentials, so no user signs on and no MFA step runs. Ping documents that the application is assigned the roles of the actor who creates it unless `assignActorRoles` is set to false, which Ping recommends for worker applications. A worker application created by an administrator therefore starts with that administrator's roles and keeps them.

Does the audit activity show what was changed in an application?

No. Ping's event list gives `APPLICATION.UPDATED` and the grant activities the common attributes only, such as the actor, the source address and the resource. Whether a redirect URI, a grant type or the name changed is not in a documented attribute. Keep an inventory of application settings and compare the application with it after each alert.

What does a resource access grant give an application?

Ping describes resources as the protected endpoints that applications request access to, and a resource access grant as naming the resource and the scopes associated with the application. Scopes define the permissions an access token carries. A grant that adds scopes of the PingOne API, or of one of your own APIs, widens what tokens issued to that application are allowed to do.

Are these steps known from attacks on PingOne tenants?

No public incident report describes them for PingOne at the audit event level. The page is derived from Ping's documentation of application properties, role assignment at creation and resource grants. The operations are the PingOne form of what MITRE ATT&CK describes as creating a cloud account and adding credentials to one.

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.