Skip to content

[system][auth] Populate user.target.name and ECS fields for PAM chauthtok events#19247

Open
nicholasberlin wants to merge 4 commits into
mainfrom
nberlin/chauthtok
Open

[system][auth] Populate user.target.name and ECS fields for PAM chauthtok events#19247
nicholasberlin wants to merge 4 commits into
mainfrom
nberlin/chauthtok

Conversation

@nicholasberlin
Copy link
Copy Markdown
Contributor

@nicholasberlin nicholasberlin commented May 27, 2026

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

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • Review all changes to golden files are additive.

Related issues

…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.
@nicholasberlin nicholasberlin requested a review from a team as a code owner May 27, 2026 19:41
@nicholasberlin nicholasberlin self-assigned this May 27, 2026
@andrewkroh andrewkroh added Integration:system System Team:Security-Linux Platform Linux Platform Security team [elastic/sec-linux-platform] labels May 27, 2026
@infra-vault-gh-plugin-prod
Copy link
Copy Markdown

Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform)

@nicholasberlin nicholasberlin added the enhancement New feature or request label May 27, 2026
@nicholasberlin nicholasberlin requested review from a team as code owners May 27, 2026 20:06
@github-actions
Copy link
Copy Markdown
Contributor

TL;DR

The failing Buildkite step is caused by a changelog version mismatch: packages/system/manifest.yml is still 2.18.0, but this PR added a new top-level changelog block for 2.19.0, so lint reports that the current manifest version has no matching changelog entry. Update the changelog entry to align with the manifest version.

Remediation

  • Move this PR’s new changelog note under the existing 2.18.0 section in packages/system/changelog.yml (instead of creating a new 2.19.0 section), or bump packages/system/manifest.yml to 2.19.0 if a version bump is intentional.
  • Update the changelog link to the PR/issue that actually tracks this change (currently it points to .../issues/19247, but this change is PR #19247).
Investigation details

Root Cause

elastic-package lint failed with:

current manifest version doesn't have changelog entry

The PR content shows:

  • packages/system/manifest.yml:4version: "2.18.0"
  • packages/system/changelog.yml:2 → new top block - version: "2.19.0"

This mismatch is what the package lint check rejects.

Evidence

Error: checking package failed: linting package failed: found 1 validation error:
   1. current manifest version doesn't have changelog entry
  • Relevant PR file changes include a newly added changelog section:
    • packages/system/changelog.yml adds - version: "2.19.0"

Verification

  • Not run locally (workflow is read-only); diagnosis is based on the Buildkite failure log and PR diff.

Follow-up

After adjusting the changelog/version alignment, re-run CI for Check integrations system.


What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

History

cc @nicholasberlin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request Integration:system System Team:Security-Linux Platform Linux Platform Security team [elastic/sec-linux-platform]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[System]: Pipeline failed to extract user.target.name from the log messages for password change event

3 participants