1. Resources
  2. Detection rules
  3. PingOne MFA Policy or Sign-On Policy Assignment Changed

PingOne MFA Policy or Sign-On Policy Assignment Changed detection rules

An attacker with PingOne administrator rights weakens MFA settings or an MFA or FIDO policy, or swaps the sign-on policy assigned to an application, so that later sign-ons need fewer or weaker factors.

Platform
Ping Identity
Severity
High
Log source
PingOne audit activities
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft Sentinel
What an attacker needs
A PingOne role that can edit authentication configuration in the environment, such as Environment Admin, or a custom role with the same permissions.
Impact
Accounts in the environment can be taken over with a password alone or with a factor the attacker can intercept, in every application that uses the weaker policy.
Response
Restore the MFA settings and policies from the baseline, assign the application its previous sign-on policy, and suspend the actor that made the change.
Mitigation
Limit the roles that can edit authentication policies, and keep a reviewed baseline of MFA settings and policies to compare after every change event.
Action types
ADMIN_CONFIGURATION.CREATEDADMIN_CONFIGURATION.UPDATEDDEVICE_AUTHENTICATION_POLICY.CREATEDFIDO_POLICY.CREATEDMFA_SETTINGS.UPDATEDDEVICE_AUTHENTICATION_POLICY.UPDATEDDEVICE_AUTHENTICATION_POLICY.DELETEDFIDO_POLICY.UPDATEDFIDO_POLICY.DELETEDACTION.CREATEDACTION.UPDATEDACTION.DELETEDand 6 more in the rules below

How the attack works

In PingOne, what a user must prove at sign-on is configuration: MFA settings for the environment, MFA policies (called device authentication policies in the API and audit log) that list the allowed methods, FIDO policies, and the sign-on policy or DaVinci flow policy assigned to each application. An administrator who can edit these can allow a weaker method such as email or SMS, change the environment's MFA settings, or assign an application a policy that has no MFA step. Nothing about any single user changes, so the weakening is easy to miss and applies to everyone who signs in afterwards.

PingOne records these changes as MFA_SETTINGS.UPDATED, DEVICE_AUTHENTICATION_POLICY, FIDO_POLICY, SIGN_ON_POLICY_ASSIGNMENT and FLOW_POLICY_ASSIGNMENT audit activities. Ping's event reference does not list a separate event type for editing the steps inside a sign-on policy (it lists Action events and titles the Policy events as password policy events), so the rules here cover MFA configuration and which policy an application uses. Review the Action and Policy event types by hand when you investigate. Two further rules read the ADMIN_CONFIGURATION activities, which by their name belong to the Administrator Security settings (the authentication source and the allowed MFA methods for administrator sign-on), and DEVICE_AUTHENTICATION_POLICY.CREATED and FIDO_POLICY.CREATED. A new policy changes nothing until a flow, an assignment or the environment default refers to it, so it is the preparation step. One more rule reads the Action activities (ACTION.CREATED, ACTION.UPDATED and ACTION.DELETED) on their name alone, because sign-on policy actions are the only resource that Ping's API reference calls an action. It reports that an action changed, not which policy it belongs to or whether an MFA step was removed.

Log source: the rules read PingOne audit activities. Include these event types in the PingOne webhook that feeds the SIEM, or poll the Audit Activities API, for every environment.

What an attacker needs

  • A PingOne role that can edit authentication configuration in the environment, such as Environment Admin, or a custom role with the same permissions.

Impact

Accounts in the environment can be taken over with a password alone or with a factor the attacker can intercept, and the attacker's own sign-ons stop triggering MFA prompts. Because applications trust PingOne's decision, the weaker policy applies to every application that uses it.

Detection rules

PingOne Administrator Security Configuration Created or Updated

Detects the audit activities ADMIN_CONFIGURATION.CREATED and ADMIN_CONFIGURATION.UPDATED, which Ping's event list describes as Admin Configuration Created and Updated. By its name the activity belongs to the Administrator Security settings of an environment (the adminConfig resource of the API, changed with the admin:update:config permission); Ping's event list does not state the link, so confirm it with one test change. Those settings decide how administrators sign on: with PingOne and its required MFA, with an external identity provider, or with both, which MFA methods are allowed (email, authenticator app, FIDO2) and whether account recovery by email is allowed. Moving the authentication source to an external identity provider, or allowing a weaker method, changes what an attacker needs to sign on as an administrator. The activity does not say which setting changed.

LevelMediumStatusExperimentalLog sourcePingOne audit activities
title: PingOne Administrator Security Configuration Created or Updated
id: 864bb1b5-2211-44c2-800d-0251b99e598f
status: experimental
description: >-
  Detects the audit activities ADMIN_CONFIGURATION.CREATED and
  ADMIN_CONFIGURATION.UPDATED, which Ping's event list describes as Admin
  Configuration Created and Updated. By its name the activity belongs to the
  Administrator Security settings of an environment (the adminConfig resource
  of the API, changed with the admin:update:config permission); Ping's event
  list does not state the link, so confirm it with one test change. Those
  settings decide how administrators sign on: with PingOne and its required
  MFA, with an external identity provider, or with both, which MFA methods
  are allowed (email, authenticator app, FIDO2) and whether account recovery
  by email is allowed. Moving the authentication source to an external
  identity provider, or allowing a weaker method, changes what an attacker
  needs to sign on as an administrator. The activity does not say which
  setting changed.
references:
  - https://attack.mitre.org/techniques/T1556/006/
  - https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
  - https://developer.pingidentity.com/pingone-api/platform/administrator-security/
  - https://docs.pingidentity.com/pingone/settings/p1_configure_administrator_security.html
author: Forestall
date: 2026-11-18
tags:
  - attack.defense-impairment
  - attack.persistence
  - attack.credential-access
  - attack.t1556.006
logsource:
  product: pingone
  service: audit
detection:
  selection:
    action.type:
      - ADMIN_CONFIGURATION.CREATED
      - ADMIN_CONFIGURATION.UPDATED
  condition: selection
falsepositives:
  - A planned change to how administrators sign on, for example a move to an external identity provider or to FIDO2. These settings change rarely, so confirm each activity with the change record and read the settings afterwards.
level: medium

False positives

  • A planned change to how administrators sign on, for example a move to an external identity provider or to FIDO2. These settings change rarely, so confirm each activity with the change record and read the settings afterwards.

PingOne MFA Policy or FIDO Policy Created

Detects a new MFA policy or FIDO policy in a PingOne environment (audit activities DEVICE_AUTHENTICATION_POLICY.CREATED and FIDO_POLICY.CREATED; Ping's event list describes the first as Auth Method Policy Created). A new policy changes nothing by itself: Ping documents that after an MFA policy is created it can be referred to in any authentication or registration flow. A policy that allows weaker methods is therefore the preparation, and the change that puts it to use is a later activity, such as a policy assignment or a change of the default policy. Use the rule for review and to give context to those later activities.

LevelLowStatusExperimentalLog sourcePingOne audit activities
title: PingOne MFA Policy or FIDO Policy Created
id: c6b973d5-36d4-4e5a-a32f-4f5900a4c359
status: experimental
description: >-
  Detects a new MFA policy or FIDO policy in a PingOne environment (audit
  activities DEVICE_AUTHENTICATION_POLICY.CREATED and FIDO_POLICY.CREATED;
  Ping's event list describes the first as Auth Method Policy Created). A new
  policy changes nothing by itself: Ping documents that after an MFA policy is
  created it can be referred to in any authentication or registration flow. A
  policy that allows weaker methods is therefore the preparation, and the
  change that puts it to use is a later activity, such as a policy assignment
  or a change of the default policy. Use the rule for review and to give
  context to those later activities.
references:
  - https://attack.mitre.org/techniques/T1556/006/
  - https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
  - https://docs.pingidentity.com/pingone/authentication/p1_mfa_policies.html
author: Forestall
date: 2026-11-18
tags:
  - attack.defense-impairment
  - attack.persistence
  - attack.credential-access
  - attack.t1556.006
logsource:
  product: pingone
  service: audit
detection:
  selection:
    action.type:
      - DEVICE_AUTHENTICATION_POLICY.CREATED
      - FIDO_POLICY.CREATED
  condition: selection
falsepositives:
  - Policy design by the team that owns authentication, for example a separate MFA policy for one application or a first FIDO2 policy. Compare the methods the new policy allows with your baseline.
level: low

False positives

  • Policy design by the team that owns authentication, for example a separate MFA policy for one application or a first FIDO2 policy. Compare the methods the new policy allows with your baseline.

PingOne MFA Settings, MFA Policy or FIDO Policy Changed

Detects a change to the MFA configuration of a PingOne environment: MFA settings updated, or an MFA policy (DEVICE_AUTHENTICATION_POLICY in the audit log) or FIDO policy updated or deleted. The event does not say whether the change weakens or strengthens the policy: compare with the baseline.

LevelMediumStatusExperimentalLog sourcePingOne audit activities
title: PingOne MFA Settings, MFA Policy or FIDO Policy Changed
id: f752b400-974e-4a2e-bae1-a3fe55d197f9
status: experimental
description: >-
  Detects a change to the MFA configuration of a PingOne environment: MFA
  settings updated, or an MFA policy (DEVICE_AUTHENTICATION_POLICY in the audit
  log) or FIDO policy updated or deleted. The event does not say whether the
  change weakens or strengthens the policy: compare with the baseline.
references:
  - https://attack.mitre.org/techniques/T1556/006/
  - https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
author: Forestall
date: 2026-11-11
tags:
  - attack.defense-impairment
  - attack.persistence
  - attack.credential-access
  - attack.t1556.006
logsource:
  product: pingone
  service: audit
detection:
  selection:
    action.type:
      - MFA_SETTINGS.UPDATED
      - DEVICE_AUTHENTICATION_POLICY.UPDATED
      - DEVICE_AUTHENTICATION_POLICY.DELETED
      - FIDO_POLICY.UPDATED
      - FIDO_POLICY.DELETED
  condition: selection
falsepositives:
  - Planned changes to MFA methods, for example a move from FIDO to FIDO2 policies. Confirm with the change record.
level: medium

False positives

  • Planned changes to MFA methods, for example a move from FIDO to FIDO2 policies. Confirm with the change record.

PingOne Sign-On Policy Action Created, Updated or Deleted

Detects the audit activities ACTION.CREATED, ACTION.UPDATED and ACTION.DELETED, which Ping's event list describes as Action Created, Action Updated and Action Deleted. The rule matches on the name of the activity alone. Ping's event list does not say which resource these activities belong to, and the link to sign-on policies rests on the API reference, where sign-on policy actions are the only resource that is called an action. Confirm it with one test change before you rely on the rule. Ping documents sign-on policy actions as the steps of a sign-on policy, such as LOGIN, MULTI_FACTOR_AUTHENTICATION and IDENTITY_PROVIDER, each with the conditions that decide when it runs. Deleting the MFA action of a policy, or giving it a condition that an attacker's address or population does not meet, removes the second factor for every application that uses the policy, while the policy and its assignments stay unchanged. The activity does not say which policy the action belongs to or what changed, and because the meaning is not documented the level is one step lower than for the other changes of this page.

LevelLowStatusExperimentalLog sourcePingOne audit activities
title: PingOne Sign-On Policy Action Created, Updated or Deleted
id: 78459348-bb3c-4a84-b795-4b72cb0a4640
status: experimental
description: >-
  Detects the audit activities ACTION.CREATED, ACTION.UPDATED and
  ACTION.DELETED, which Ping's event list describes as Action Created, Action
  Updated and Action Deleted. The rule matches on the name of the activity
  alone. Ping's event list does not say which resource these activities
  belong to, and the link to sign-on policies rests on the API reference,
  where sign-on policy actions are the only resource that is called an
  action. Confirm it with one test change before you rely on the rule. Ping
  documents sign-on policy actions as the steps of a sign-on policy, such as
  LOGIN, MULTI_FACTOR_AUTHENTICATION and IDENTITY_PROVIDER, each with the
  conditions that decide when it runs. Deleting the MFA action of a policy,
  or giving it a condition that an attacker's address or population does not
  meet, removes the second factor for every application that uses the policy,
  while the policy and its assignments stay unchanged. The activity does not
  say which policy the action belongs to or what changed, and because the
  meaning is not documented the level is one step lower than for the other
  changes of this page.
references:
  - https://attack.mitre.org/techniques/T1556/009/
  - https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
  - https://developer.pingidentity.com/pingone-api/platform/sign-on-policies/sign-on-policy-actions/index.html
author: Forestall
date: 2026-11-18
tags:
  - attack.defense-impairment
  - attack.persistence
  - attack.credential-access
  - attack.t1556.009
logsource:
  product: pingone
  service: audit
detection:
  selection:
    action.type:
      - ACTION.CREATED
      - ACTION.UPDATED
      - ACTION.DELETED
  condition: selection
falsepositives:
  - Policy design by the team that owns authentication, for example a new sign-on policy with its login and MFA actions, or a changed condition for one group of users. Compare the actions of the policy with your baseline afterwards.
  - Activities of another kind of action, if your environment writes these event types for something other than sign-on policies. Check the resource named in the activity.
level: low

False positives

  • Policy design by the team that owns authentication, for example a new sign-on policy with its login and MFA actions, or a changed condition for one group of users. Compare the actions of the policy with your baseline afterwards.
  • Activities of another kind of action, if your environment writes these event types for something other than sign-on policies. Check the resource named in the activity.

PingOne Application Sign-On Policy or Flow Policy Assignment Changed

Detects a change to which sign-on policy or DaVinci flow policy an application uses in PingOne (audit activities SIGN_ON_POLICY_ASSIGNMENT and FLOW_POLICY_ASSIGNMENT, created, updated or deleted). Moving an application to a policy without an MFA step removes MFA for that application without editing any policy.

LevelMediumStatusExperimentalLog sourcePingOne audit activities
title: PingOne Application Sign-On Policy or Flow Policy Assignment Changed
id: 4fd555a2-7bee-4feb-9ed3-f435606615aa
status: experimental
description: >-
  Detects a change to which sign-on policy or DaVinci flow policy an
  application uses in PingOne (audit activities SIGN_ON_POLICY_ASSIGNMENT and
  FLOW_POLICY_ASSIGNMENT, created, updated or deleted). Moving an application
  to a policy without an MFA step removes MFA for that application without
  editing any policy.
references:
  - https://attack.mitre.org/techniques/T1556/009/
  - https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
  - https://developer.pingidentity.com/pingone-api/platform/applications/application-sign-on-policy-assignments/index.html
author: Forestall
date: 2026-11-11
tags:
  - attack.defense-impairment
  - attack.persistence
  - attack.credential-access
  - attack.t1556.009
logsource:
  product: pingone
  service: audit
detection:
  selection:
    action.type:
      - SIGN_ON_POLICY_ASSIGNMENT.CREATED
      - SIGN_ON_POLICY_ASSIGNMENT.UPDATED
      - SIGN_ON_POLICY_ASSIGNMENT.DELETED
      - FLOW_POLICY_ASSIGNMENT.CREATED
      - FLOW_POLICY_ASSIGNMENT.UPDATED
      - FLOW_POLICY_ASSIGNMENT.DELETED
  condition: selection
falsepositives:
  - New applications, which receive their first policy assignment when they are set up, and planned policy rollouts. Tune by excluding the actors that deploy applications after you have reviewed them.
level: medium

False positives

  • New applications, which receive their first policy assignment when they are set up, and planned policy rollouts. Tune by excluding the actors that deploy applications after you have reviewed them.

Triage

  • Identify the actor (actors.user.name or actors.client.name) and the policy or application named in the activity, and check for an approved change.
  • Compare the current settings with the baseline. Look for newly allowed methods, removed MFA steps, and applications moved to a different policy.
  • Review sign-ons to the affected applications after the change for users who authenticated with fewer factors than before.
  • If unexplained, restore the previous configuration and review what else the actor changed in the same session.

Response

Once the attack is confirmed:

  1. Restore the MFA settings and the MFA or FIDO policy from the baseline, and assign the application its previous sign-on policy or flow policy.
  2. Suspend the administrator or worker application that made the change until it is explained, and remove the role that lets it edit authentication configuration.
  3. End the sessions of accounts that signed on with fewer factors after the change, and reset the credentials of those whose owners cannot confirm the sign-on.
  4. Review the Action and Policy activities of the same actor by hand, because the rule on sign-on policy actions matches the activity by name only and does not say which step of the policy changed.
  5. Compare the policy assigned to every application with the baseline, in every environment that shares users with production.

Mitigation

  • Limit Environment Admin and custom roles that can edit authentication policies, and require a change record for every edit.
  • Keep a reviewed baseline of MFA settings, MFA and FIDO policies and the policy assigned to each application, and compare it after every change event.
  • Prefer FIDO2 and authenticator apps over email, SMS and voice in MFA policies.
  • Alert on these event types in every environment, including test environments that share users with production.

Frequently asked questions

Do the rules notice an MFA step removed from inside a sign-on policy?

Only as a change of an action, not as a removed MFA step. Ping's event reference does not list a separate event type for editing the steps inside a sign-on policy. It lists Action events and titles the Policy events as password policy events. One rule reads the Action events on their name alone and reports that an action was created, updated or deleted. It cannot say which policy the action belongs to or what changed, so compare the actions of your sign-on policies with the baseline after each match.

Does the alert say whether the policy became weaker?

No. The activity reports that MFA settings or a policy were updated or deleted, not whether the result is weaker or stronger. Compare the current configuration with your reviewed baseline and look for newly allowed methods such as email or SMS, removed MFA steps and applications moved to a different policy.

Why does the audit log mention a device authentication policy?

It is the name the API and the audit log use for what the admin console calls an MFA policy. `DEVICE_AUTHENTICATION_POLICY.UPDATED` and `DEVICE_AUTHENTICATION_POLICY.DELETED` are therefore changes to an MFA policy, which lists the allowed authentication methods.

How can MFA disappear for an application when no policy was edited?

Through the assignment. Each application has a sign-on policy or DaVinci flow policy assigned to it, and moving the application to a policy without an MFA step removes MFA for it without editing any policy. The second rule reports these assignment changes. It also fires when a new application receives its first policy, which is the usual benign cause.

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.