-
Notifications
You must be signed in to change notification settings - Fork 210
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
Extract fields from PwSh classic logs #1201
Comments
Thank you so much for mation :) Yes, I would love to implement it!💪 Please let me confirm one thing! |
@fukusuket Whoops! Sorry my English is bad so I misread that part. (焦)ww |
I agree, I think it would be better if the user could choose! |
Sounds good! Let's talk about it at Thurs meeting. |
memo: About field localization
Elastic Winlogbeat impl |
@YamatoSecurity @hitenkoku Processing process
The logic above is the same as the logic below. Processing timing Output image {
"Timestamp": "2023-10-12 16:29:06.591 +09:00",
"Computer": "MyComputer",
"Channel": "PwShClassic",
"EventID": 400,
"Level": "info",
"RecordID": 7,
"RuleTitle": "PwShClassic",
"Details": {
},
"ExtraFieldInfo": {
"Data": "Available",
"Data": "NewEngineState=Available\\r\\n\\tPreviousEngineState=None\\r\\n\\r\\n\\tSequenceNumber=13\\r\\n\\r\\n\\tHostName=ConsoleHost\\r\\n\\tHostVersion=5.1.22621.1778\\r\\n\\tHostId=bafb59f7-0327-4c95-9b52-e515e2c033ff\\r\\n\\tHostApplication=powershell -ExecutionPolicy Bypass -windowstyle hidden -command C:\\mcj\\tool\\win10\\ssd_fw_update\\ssd_fw_update.ps1\\r\\n\\tEngineVersion=5.1.22621.1778\\r\\n\\tRunspaceId=8d3b7b41-5bb3-4bb3-abe4-2c75c231a021\\r\\n\\tPipelineId=\\r\\n\\tCommandName=\\r\\n\\tCommandType=\\r\\n\\tScriptName=\\r\\n\\tCommandPath=\\r\\n\\tCommandLine=",
"Data": "None"
}
} after: {
"Timestamp": "2023-10-12 16:29:06.591 +09:00",
"Computer": "MyComputer",
"Channel": "PwShClassic",
"EventID": 400,
"Level": "info",
"RecordID": 7,
"RuleTitle": "PwShClassic",
"Details": {
},
"ExtraFieldInfo": {
"Data": "Available",
"NewEngineState": "Available",
"PreviousEngineState": "None",
"SequenceNumber": "13",
"HostName": "ConsoleHost",
"HostVersion": "5.1.22621.1778",
"HostId": "bafb59f7-0327-4c95-9b52-e515e2c033ff"
"HostApplication": "powershell -ExecutionPolicy Bypass -windowstyle hidden -command C:\\mcj\\tool\\win10\\ssd_fw_update\\ssd_fw_update.ps1",
"EngineVersion": "5.1.22621.1778",
"RunspaceId": "8d3b7b41-5bb3-4bb3-abe4-2c75c231a021",
"PipelineId": "",
"CommandName": "",
"CommandType": "",
"ScriptName": "",
"CommandPath": "",
"CommandLine": "",
"Data": "None"
}
} Output CSV in the same way as above. Option Should I create a dedicated yml file?
Other notes
If the above is the case, we will not release this feature. |
@fukusuket Sounds good to me! |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry for changing the specifications so many times... In the end, I created it with specifications #1201 (comment). |
As per these discussions: SigmaHQ/sigma#4510 and Yamato-Security/hayabusa-rules#514
It seems best to extract out fields from the
Data
field in PwSh classic logs to get the sigma rules to work internally in Hayabusa.@fukusuket Are you interested in this?
The text was updated successfully, but these errors were encountered: