T1621 PingID: add UPN and multiple-reset regression fixture - #1230
Open
sbaker-gre wants to merge 1 commit into
Open
sbaker-gre wants to merge 1 commit into
sbaker-gre wants to merge 1 commit into
Conversation
Add five synthetic PingID device-pairing events and six Windows 4723/4724 password events for PingID New MFA Method After Credential Reset. Cover UPN-to-bare username matching, multiple resets and nearest-reset selection, exclusion outside the one-hour window, and simultaneous pairings from distinct source IPs. Register both files in the manifest. Use lab identities and reserved documentation IPs. Companion to splunk/security_content#4298. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sbaker-gre
force-pushed
the
pingid-credential-reset-upn-fixture
branch
from
September 29, 2026 19:09
1b08d87 to
65f19f0
Compare
sbaker-gre
added a commit
to sbaker-gre/security_content
that referenced
this pull request
Sep 29, 2026
Normalize UPN and domain-prefixed usernames on both sides of the Windows password-event join while preserving the original PingID user in findings. Consider all matching password events and retain the nearest qualifying reset per complete stats group, preserving source-distinct pairings. Add the synthetic regression fixture from splunk/attack_data#1230 and increment the detection version. Local unit tests return two findings for the original fixture and four for the new fixture. Separate local assertions verify the exact results and nearest qualifying reset; the current CI unit runner only requires nonzero results. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds regression data for PingID New MFA Method After Credential Reset.
The existing
pingid.log/windows_pw_reset.logpair uses the bare namevictim_useronboth sides. That hides two problems in the detection: PingID reports the IdP username
(typically a UPN), while Windows 4723/4724 carry the bare account name; and the join keeps
only one password event per user.
New files in
datasets/attack_techniques/T1621/pingid/, dated 2023-10-16, synthetic:pingid_upn_multi_reset.log: 5 PingID device pairings (_json,source=PINGID)windows_pw_reset_upn_multi_reset.log: 6 Security 4723/4724 events (XmlWinEventLog)victim_user2@attack_range.lanpairs 10 and 5 minutes after two resetsvictim_user3: one reset after the pairing, one 10 minutes beforevictim_user4@attack_range.lan: only reset is 90 minutes earliervictim_user5@attack_range.lanpairs the same device in the same second from two source IPspingid.ymllists both files. The companion security_content PR adds a second unit testthat uses them; the current detection returns 0 on this fixture, the fixed one returns 4.
🤖 Generated with Claude Code