Repository navigation
fix: inject nvm_version into all structured event payloads - #29
Merged
Merged
Conversation
SIEM collectors need a stable product-version field on every Advanced Logging Payload. Enrich structured maps/JSON in common/eventlog when ProductVersion is set at process start. Signed-off-by: Corey Butler <770982+coreybutler@users.noreply.github.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
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.
What
Enrich every structured Event Log payload with
nvm_versionwheneventlog.ProductVersionis set at process start.Why
SIEM pipelines need a stable field to filter Advanced Logging events by the NVM for Windows version that wrote them.
Testing
go test ./...incommon/eventlogeventlog.ProductVersion(cli/sync PRs)Risk
Low — additive JSON field; callers that already set
nvm_versionare preserved.