We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Ok, so if I run the following with no pipelines:
sigma convert -t eql --without-pipeline sigma/rules/windows/powershell/powershell_module/posh_pm_get_clipboard.yml Parsing Sigma rules [####################################] 100% any where Payload:"*Get-Clipboard*"
Then, I add the windows-logsources pipeline:
windows-logsources
sigma convert -t eql -p windows-logsources sigma/rules/windows/powershell/powershell_module/posh_pm_get_clipboard.yml Parsing Sigma rules [####################################] 100% any where (Channel like~ ("Microsoft-Windows-PowerShell/Operational", "PowerShellCore/Operational")) and (EventID:4103 and Payload:"*Get-Clipboard*")
Finally, I add the ecs_windows pipeline:
ecs_windows
sigma convert -t eql -p ecs_windows -p windows-logsources sigma/rules/windows/powershell/powershell_module/posh_pm_get_clipboard.yml Parsing Sigma rules [####################################] 100% any where (winlog.channel like~ ("Microsoft-Windows-PowerShell/Operational", "PowerShellCore/Operational")) and ((winlog.channel like~ ("Microsoft-Windows-PowerShell/Operational", "PowerShellCore/Operational")) and (event.code:4103 and winlog.event_data.Payload:"*Get-Clipboard*"))
In that last one, is it expected that there is a duplicate search for winlog.channel?
The text was updated successfully, but these errors were encountered:
@thomaspatzke Do you have an idea how to solve this?
Sorry, something went wrong.
No branches or pull requests
Ok, so if I run the following with no pipelines:
Then, I add the
windows-logsources
pipeline:Finally, I add the
ecs_windows
pipeline:In that last one, is it expected that there is a duplicate search for winlog.channel?
The text was updated successfully, but these errors were encountered: