[system][auth] Populate user.target.name and ECS fields for PAM chauthtok events#19247
[system][auth] Populate user.target.name and ECS fields for PAM chauthtok events#19247nicholasberlin wants to merge 4 commits into
Conversation
…htok events For pam_unix(passwd:chauthtok) password change events, user.name holds the target user (not the actor). This adds user.target.name alongside user.name, indexes it in related.user, and sets event.category=iam, event.type=change, event.outcome=success, event.action=password-changed — fields that were previously absent for this event type. All changes are additive.
|
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
TL;DRThe failing Buildkite step is caused by a changelog version mismatch: Remediation
Investigation detailsRoot Cause
The PR content shows:
This mismatch is what the package lint check rejects. Evidence
Verification
Follow-upAfter adjusting the changelog/version alignment, re-run CI for What is this? | From workflow: PR Buildkite Detective Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. |
💚 Build Succeeded
History
|
Proposed commit message
For pam_unix(passwd:chauthtok) password change events, user.name holds the target user (not the actor). This adds user.target.name alongside user.name, indexes it in related.user, and sets event.category=iam, event.type=change, event.outcome=success, event.action=password-changed — fields that were previously absent for this event type. All changes are additive.
Checklist
changelog.ymlfile.Author's Checklist
Related issues