-
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
Add Security event ID 4672 #12975
Add Security event ID 4672 #12975
Conversation
var logoff = new processor.Chain() | ||
.Add(convertAuthentication) | ||
.Add(copyTargetUser) |
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.
If anyone tries to run this pipeline on the existing 7.2.0 release you will need to change this line to add .Run
like
.Add(copyTargetUser.Run)
and do the same for .Add(copySubjectUser)
and .Add(renameCommonAuthFields)
b0de866
to
7fe48ff
Compare
Pinging @elastic/secops |
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.
LGTM
7fe48ff
to
cc798b3
Compare
- Add winlog.logon.id field containing all the logon IDs from the event. This makes it possible to find all events related to a logon ID, including when a user changes to a new user. - Copy, rather than move, the TargetUser and SubjectUser fields. This leaves the original fields in event_data. - For failure events decode the status codes to `winlog.logon.failure.status` and `winlog.logon.failure.sub_status`. And decode the FailureReason to `winlog.logon.failure.reason` (e.g. make `%%2313` into a string). - Make the processor chain builder accept other processor chains via the Add() method such that one built chain can be re-used by another.
cc798b3
to
f16df9e
Compare
winlog.logon.failure.status
andwinlog.logon.failure.sub_status
. And decode the FailureReason towinlog.logon.failure.reason
(e.g. make%%2313
into a string).