-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix related.ip field #24892
Fix related.ip field #24892
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
@@ -2005,7 +2005,7 @@ var security = (function () { | |||
{from: "winlog.event_data.ProcessId", to: "process.pid", type: "long"}, | |||
{from: "winlog.event_data.ProcessName", to: "process.executable"}, | |||
{from: "winlog.event_data.IpAddress", to: "source.ip", type: "ip"}, | |||
{from: "winlog.event_data.ClientAddress", to: "related.ip", type: "ip"}, | |||
{from: "winlog.event_data.IpAddress", to: "related.ip", type: "ip"}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the earlier line that renames winlog.event_data.IpAddress
to source.ip
cause a problem for this? I wonder if a more generic copy from source.ip
/destination.ip
to related.ip
that gets applied to all events would be better (not sure if there's already something like this in the pipeline).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @andrewkroh, I agree with you.
I'll populate the related.ip from the generic fields, I'll test it and commit the modifications
This pull request is now in conflicts. Could you fix it? 🙏
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I made 2 changes
- updated golden files
- replaced () with {} in asciidoc
removing "needs_integration_sync" label because the switch to ingest node pipeline already has this fix. |
- [Winlogbeat] fix related.ip field in renameCommonAuthFields function Co-authored-by: Lee E. Hinman <[email protected]> (cherry picked from commit d0887fd)
- [Winlogbeat] fix related.ip field in renameCommonAuthFields function Co-authored-by: Lee E. Hinman <[email protected]> (cherry picked from commit d0887fd) Co-authored-by: Anabella Cristaldi <[email protected]>
What does this PR do?
Fix a bug found when populating related.ip field information in the renameCommonAuthFields
The wrong field winlog.event_data.ClientAddress was copied into related.ip instead of winlog.event_data.IpAddress which is the proper one.
Why is it important?
The related.ip information was not populated correctly in some events. For example: 4624,4648,4625
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues