-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Sigma FP fixes #4994
Sigma FP fixes #4994
Conversation
I did not edit dates, sorry about that. If that is a requirement for the future I can do it. |
It is a requirements per the Sigma standard and as you're not a fist time contributor you have to do it now not next time :) |
Acknowledged, thanks. |
requires some changes for empty host application based on the data field
Do you need more examples regarding Remote Schtasks Creation - cf349c4b-99af-40fa-a051-823aa2307a84? 4698 - A scheduled task was created. do not contain Source_network_address data. |
I am sorry, my bad on this one. I just noticed that Remote Schtasks Creation has unsupported status. |
Summary of the Pull Request
This PR is meant to resolve noisy FPs found within multiple normal events.
Changelog
update: CodeIntegrity - Unmet Signing Level Requirements By File Under Validation - Add additional filters for third party AV
update: Suspicious Non PowerShell WSMAN COM Provider - Add new filter to cover the edge case where the
HostApplication
field is nullupdate: Renamed Powershell Under Powershell Channel - Add new filter to cover the edge case where the
HostApplication
field is nullExample Log Event
CodeIntegrity - Unmet Signing Level Requirements By File Under Validation
Remote Schtasks Creation
4698 and 4702 do not contain Source Network Address data.
Suspicious Non PowerShell WSMAN COM Provider
Renamed Powershell Under Powershell Channel
Fixed Issues
N/A
SigmaHQ Rule Creation Conventions