How the attack works
In environments that use PingOne DaVinci, the sign-on experience is a flow: Ping describes flows as constructed, logical paths that specify the workflow for the user's authorization and authentication experiences, made of nodes that each perform one task. A flow has a saved version and a deployed version, and a flow policy is the entity that points an application to one or more flows or versions of flows. Whoever can edit these decides what every user of the application has to prove and what happens to what they type. Removing the MFA node, adding a branch that lets one account through, reverting to an older version without a check, or pointing the flow policy at another flow all change authentication without touching a user, a password policy or an MFA policy. Custom JavaScript added to a flow or to a connector runs as part of the sign-on and is in a position to read what the page handles.
Ping documents 37 DaVinci administrative audit events that appear alongside the other PingOne audit events. The ones that mark a change going live are the deployment of a flow, the revert of a flow version and the update or deletion of a flow policy, and custom JavaScript has its own events. Two Ping pages write the event types differently: the API event reference lists DAVINCI_FLOW.DEPLOYED, the administration guide DAVINCI.FLOW.DEPLOYED. The rules here match both forms. The page follows Ping's documentation: no public incident report describes tampering with a DaVinci flow.
Log source: the rules read PingOne audit activities. Include the DaVinci event types in the PingOne webhook that feeds the SIEM, or poll the Audit Activities API, for every environment that runs DaVinci flows. Which flow policy an application uses is a separate activity (FLOW_POLICY_ASSIGNMENT), covered by the library's page on MFA settings and sign-on policy assignments.
What an attacker needs
- A PingOne role that can edit and deploy DaVinci flows, connectors or flow policies in the environment.
- An application whose sign-on runs through the changed flow or flow policy.
Impact
Every sign-on through the changed flow follows the attacker's logic. Accounts can be entered with fewer factors or through a branch made for the attacker, and custom script in the flow can capture the credentials of everyone who signs on. Because applications trust the result of the flow, the effect reaches every application that the flow policy serves.
Detection rules
PingOne DaVinci Custom JavaScript Added or Updated
Detects custom JavaScript being added to or updated in a DaVinci flow or a DaVinci connector configuration. Ping's administration guide documents the events with example descriptions: custom JavaScript added during flow creation, cloning or import, custom JavaScript updated in a flow, and custom JavaScript added or updated in a connector's configuration. Script that runs as part of the sign-on experience is in a position to read what the user enters there and to send it elsewhere, which makes an unreviewed change the identity provider's form of web portal capture. Each event type is listed in the spelling of both Ping pages: the API event reference with underscores, which has separate types for flows and connectors, and the administration guide with dots, where connector events share the flow type and are told apart by the resource type. Ping documents the node IDs that contain the script in _embedded.davinciFlow.targetNodeId. The rule does not read the script: review it in the flow.
title: PingOne DaVinci Custom JavaScript Added or Updated
id: 07b447fc-4cd3-479e-bc9d-2743350be9e0
status: experimental
description: >-
Detects custom JavaScript being added to or updated in a DaVinci flow or a
DaVinci connector configuration. Ping's administration guide documents the
events with example descriptions: custom JavaScript added during flow
creation, cloning or import, custom JavaScript updated in a flow, and
custom JavaScript added or updated in a connector's configuration. Script
that runs as part of the sign-on experience is in a position to read what
the user enters there and to send it elsewhere, which makes an unreviewed
change the identity provider's form of web portal capture. Each event type is listed
in the spelling of both Ping pages: the API event reference with
underscores, which has separate types for flows and connectors, and the
administration guide with dots, where connector events share the flow type
and are told apart by the resource type. Ping documents the node IDs that
contain the script in _embedded.davinciFlow.targetNodeId. The rule does not
read the script: review it in the flow.
references:
- https://attack.mitre.org/techniques/T1056/003/
- https://docs.pingidentity.com/pingone/monitoring/p1_davinci_audit_events.html
- https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
author: Forestall
date: 2026-11-18
tags:
- attack.collection
- attack.credential-access
- attack.t1056.003
logsource:
product: pingone
service: audit
detection:
selection:
action.type:
- DAVINCI_FLOW.CUSTOM_JAVASCRIPT_ADDED
- DAVINCI_FLOW.CUSTOM_JAVASCRIPT_UPDATED
- DAVINCI_CONNECTOR.CUSTOM_JAVASCRIPT_ADDED
- DAVINCI_CONNECTOR.CUSTOM_JAVASCRIPT_UPDATED
- DAVINCI.FLOW.CUSTOM_JAVASCRIPT.ADDED
- DAVINCI.FLOW.CUSTOM_JAVASCRIPT.UPDATED
condition: selection
falsepositives:
- Flow developers who add client-side script for form behavior or branding, and imports or clones of flows that already contain script, which Ping documents as writing the same event. Review the script once and add a filter on the reviewed flows only if the volume requires it.
level: medium
False positives
- Flow developers who add client-side script for form behavior or branding, and imports or clones of flows that already contain script, which Ping documents as writing the same event. Review the script once and add a filter on the reviewed flows only if the volume requires it.
PingOne DaVinci Flow Deployed or Reverted, or Flow Policy Changed
Detects the DaVinci activities that put a change of the sign-on process into effect: a flow deployed, a flow version reverted, and a flow policy updated or deleted. Ping describes DaVinci flows as the paths that specify the workflow for the user's authorization and authentication experiences, and a flow policy as the entity that points an application to one or more flows or versions of flows. The flow model separates the saved version from the currently deployed version, so saved edits (flow updated) are left out and the deployment is what the rule reads. A deployment can remove an MFA node or add a branch for one account, a revert can bring back an older version without a check, and a changed flow policy can run another flow for the application. Each event type is listed twice because two Ping pages write it differently: the API event reference with underscores (DAVINCI_FLOW.DEPLOYED) and the administration guide with dots (DAVINCI.FLOW.DEPLOYED). The rule does not read what changed: compare the deployed flow and the flow policy with your reviewed export.
title: PingOne DaVinci Flow Deployed or Reverted, or Flow Policy Changed
id: 015365ea-5a7a-4ba0-a1b8-e0c9a88314d9
status: experimental
description: >-
Detects the DaVinci activities that put a change of the sign-on process into
effect: a flow deployed, a flow version reverted, and a flow policy updated
or deleted. Ping describes DaVinci flows as the paths that specify the
workflow for the user's authorization and authentication experiences, and a
flow policy as the entity that points an application to one or more flows
or versions of flows. The flow model separates the saved version from the
currently deployed version, so saved edits (flow updated) are left out and
the deployment is what the rule reads. A deployment can remove an MFA node
or add a branch for one account, a revert can bring back an older version
without a check, and a changed flow policy can run another flow for the
application. Each event type is listed twice because two Ping pages write
it differently: the API event reference with underscores
(DAVINCI_FLOW.DEPLOYED) and the administration guide with dots
(DAVINCI.FLOW.DEPLOYED). The rule does not read what changed: compare the
deployed flow and the flow policy with your reviewed export.
references:
- https://attack.mitre.org/techniques/T1556/009/
- https://docs.pingidentity.com/pingone/monitoring/p1_davinci_audit_events.html
- https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
- https://developer.pingidentity.com/pingone-api/davinci/davinci-admin-apis/admin-flows/index.html
- https://developer.pingidentity.com/pingone-api/davinci/davinci-admin-apis/davinci-admin-application-flow-policies/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:
- DAVINCI_FLOW.DEPLOYED
- DAVINCI_FLOW.VERSION_REVERTED
- DAVINCI_FLOW_POLICY.UPDATED
- DAVINCI_FLOW_POLICY.DELETED
- DAVINCI.FLOW.DEPLOYED
- DAVINCI.FLOW.VERSION.REVERTED
- DAVINCI.FLOW_POLICY.UPDATED
- DAVINCI.FLOW_POLICY.DELETED
condition: selection
falsepositives:
- Releases by the team that builds the flows. In an environment under active development deployments are frequent, so add a filter on actors.user.name for the release identities you have reviewed, or alert only in production environments and outside release windows.
level: medium
False positives
- Releases by the team that builds the flows. In an environment under active development deployments are frequent, so add a filter on actors.user.name for the release identities you have reviewed, or alert only in production environments and outside release windows.
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.
Custom JavaScript added to a flow that the same actor deploys soon after
Script that is added to a flow does nothing until the flow is deployed. Custom JavaScript added or updated in a flow, followed by a deployment of that flow by the same actor within a short time and without a change record, is how code that reads credentials would be put in front of users.
- Find the custom JavaScript activities (
DAVINCI_FLOW.CUSTOM_JAVASCRIPT_ADDEDorDAVINCI_FLOW.CUSTOM_JAVASCRIPT_UPDATED, in the administration guideDAVINCI.FLOW.CUSTOM_JAVASCRIPT.ADDEDand.UPDATED) and note the flow inresources.idand the actor inactors.user.id. - Look for a deployment of the same flow (
DAVINCI_FLOW.DEPLOYEDorDAVINCI.FLOW.DEPLOYED) with the sameresources.idwithin the next 24 hours. - Compare the actor of both activities and their
source.ipAddress, and check your change records for the deployment. - Read
_embedded.davinciFlow.targetNodeIdof the JavaScript activity to find the node, and review the script in that node.
EventsDAVINCI_FLOW.CUSTOM_JAVASCRIPT_ADDEDDAVINCI_FLOW.CUSTOM_JAVASCRIPT_UPDATEDDAVINCI_FLOW.DEPLOYED
LimitsFlow developers add script and deploy as part of normal work, so the result is a list to review against change records, not a verdict. Ping documents that importing or cloning a flow that already contains script writes the JavaScript activity too. The window is a starting point.
Triage
- Identify the actor (actors.user.name or actors.client.name), the source address and the flow, connector or flow policy named in the activity's resources, and check for an approved deployment.
- Read
_embedded.davinciFlowin the activity where your SIEM keeps it. Ping documents the flow name, the flow version, the array of attribute paths that an update changed (modifiedAttributes) and, for custom JavaScript, the node IDs that contain it (targetNodeId). - Compare the deployed version of the flow with the last reviewed export. Look for a removed MFA or risk node, a new branch on a user name, group or address, new nodes that call outside services or run script, and changed success nodes.
- For a flow policy, check which flows and versions it points to now and with which weights, and which applications use it.
- Read the added or changed JavaScript itself, and check where it sends data.
- Review sign-ons through the flow since the change, and what else the actor changed in the same session.
Response
Once the attack is confirmed:
- Revert the flow to the last reviewed version and deploy it, or point the flow policy back to the reviewed flow and version.
- Remove custom JavaScript that nobody approved from the flow or connector, and keep a copy for the investigation.
- Treat credentials entered through the flow while unapproved script was deployed as disclosed. Reset those passwords and end the sessions.
- End the sessions of accounts that signed on through a weakened flow, and reset the credentials of those whose owners cannot confirm the sign-on.
- Suspend the administrator or worker application that made the change, remove the role that allows it, and compare every flow and flow policy of the environment with the reviewed exports.
Mitigation
- Limit the roles that can edit and deploy DaVinci flows and flow policies, and separate the people who design flows from the people who deploy them to production.
- Keep exports of the deployed version of every flow and of every flow policy under version control, and compare them after every deployment or policy change.
- Review custom JavaScript in flows and connectors like application code, and keep a list of the flows and connectors that are allowed to carry it.
- Use version aliases and a change record for every deployment, so that an unexplained deployment stands out.
- Alert on these event types in every environment that runs DaVinci flows, including test environments that share users with production.
Frequently asked questions
Which DaVinci audit event means that a flow change is live?
Ping's flow model separates the saved version of a flow from the currently deployed version, and a flow policy points an application to flows or versions of flows. Ping lists a separate event for a flow update, which is an edit. What users meet changes with the deployment of a flow, the revert of a flow version, and the update or deletion of a flow policy. The first rule reads those activities and leaves saved edits out.
Why do the rules list every event type in two spellings?
Ping documents the DaVinci events in two places that do not agree. The API event reference lists them with underscores, for example `DAVINCI_FLOW.DEPLOYED` and `DAVINCI_FLOW.CUSTOM_JAVASCRIPT_ADDED`. The administration guide lists them with dots, for example `DAVINCI.FLOW.DEPLOYED` and `DAVINCI.FLOW.CUSTOM_JAVASCRIPT.ADDED`. The rules match both. Check one activity in your own log and keep the form you see.
Does the audit activity show what changed in a flow?
Partly. Ping documents DaVinci-specific fields under `_embedded.davinciFlow`, among them the flow name and version, the array of attribute paths changed during an update, and for custom JavaScript the IDs of the nodes that contain it. The rules do not read these fields, because the SIEM mappings of this log source do not carry them. Read them during triage and compare the flow with your reviewed export.
Has a DaVinci flow been tampered with in a reported attack?
No public incident report describes it. The page is derived from Ping's documentation of flows, flow versions, flow policies and the DaVinci audit events. Changing the sign-on process of an identity provider and capturing credentials at a sign-on page are established techniques in MITRE ATT&CK, and a flow builder puts both within reach of one administrator role.
References
- MITRE ATT&CK T1556.009: Modify Authentication Process, Conditional Access Policies
- MITRE ATT&CK T1056.003: Input Capture, Web Portal Capture
- PingOne: DaVinci administrative audit events
- PingOne Platform API: Audit reporting events
- PingOne DaVinci API: DaVinci admin flows
- PingOne DaVinci API: DaVinci admin flow versions
- PingOne DaVinci API: DaVinci admin application flow policies