-
Notifications
You must be signed in to change notification settings - Fork 7
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 RDP logon/logoff information to timeline-logon
command
#209
Comments
@YamatoSecurity |
@fukusuket I think that it depends on the analyst and situation. I think by default we should put things in single events to minimize the events to make things easier to read (I don't think we can add reconnect logs here though) but I was thinking about adding an option to display each event as single events. Since we were only looking at a handful of Security events, I figured that people could just easily filter on those event IDs in Timeline explorer, etc.. to get the singe event logon timeline but if we are adding information and RDP logs, then we might want to have an option to extract out those logon events and put in a timeline but not consolidate them into single events. What do you think? |
@YamatoSecurity Let me confirm one thing! |
I was thinking consolidating 4624 logon events with logoff events like we do now, and consolidating RDP logon and logoff events in one event (and calculate the logon time based on that). I haven't thought about consolidating RDP events and Sec 4624 events together. I would have to look into that so for now, I think we should separate Security events and RDP log events. There may be source IP address info. etc.. inside RDP reconnect logs so I would like to use that information inside the consolidated RDP event if it is not already there. |
I understood! I forgot that the Security logoff events for 4634 were consolidated😅 Yes, it's better to separate Security and RDP log! |
Add RDP logon/logoff information to
timeline-logon
command.There are also RDP reconnect logs that contain source IP address info that should be added. Will have to think about how best to correlate the multiple logs into single events though..
The text was updated successfully, but these errors were encountered: