Validate Source IP "LOCAL" or "Unknown" in Windows Security Logs#34295
Validate Source IP "LOCAL" or "Unknown" in Windows Security Logs#34295efd6 merged 3 commits intoelastic:mainfrom
Conversation
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
|
/test |
efd6
left a comment
There was a problem hiding this comment.
Thanks.
Are you able to provide events to exercise this in tests?
|
I unfortunately cannot provide EVTX files for this one, as the only record of this happening so far is from servers, and I do not have access to log into those servers. Since I have already made the changes to our Ingest Pipeline, I could provide the JSON of some of these documents in Elasticsearch for these events. |
|
Scratch that. I was able to find a client with some of these. As with the other PR, these events do contain sensitive information. Please let me know how/where I can send them to you, and I will do that. |
|
Attaching five scrubbed events of each where the source IP is either "LOCAL" or "Unknown". |
|
Can we back-port this? |
Tests cases mechanically derived from user-provided XML scrubbed event data.
|
I've added the tests temporarily in the collection testdata. I want to flesh this out with a way to just drop XML files into inputs, but this is a bigger change, so I will do that separately. |
|
/test |
|
/test |
) Tests cases mechanically derived from user-provided XML scrubbed event data. Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co> (cherry picked from commit 4a1e56f) # Conflicts: # x-pack/winlogbeat/module/security/ingest/security.yml # x-pack/winlogbeat/module/security/test/testdata/4778.evtx.golden.json # x-pack/winlogbeat/module/security/test/testdata/4778.golden.json # x-pack/winlogbeat/module/security/test/testdata/4779.evtx.golden.json # x-pack/winlogbeat/module/security/test/testdata/4779.golden.json
) Tests cases mechanically derived from user-provided XML scrubbed event data. Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co> (cherry picked from commit 4a1e56f)
What does this PR do?
Some security events contain a source IP address of "LOCAL" or "Unknown" which are not valid IP addresses. This PR will correct the processing of events containing one of those values.
Why is it important?
This bug causes mapping exceptions and prevents these events from being ingested.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues
-fixes #34263