-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Update proc_creation_win_reg_windows_defender_tamper.yml #5148
base: master
Are you sure you want to change the base?
Conversation
- 'DisableCloudProtection' | ||
- 'DisableNetworkProtection' | ||
- 'DisableAntiVirusSignatures' | ||
- 'DisableAccess' | ||
- 'DisableSecurityCenter' |
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.
Doing a quick search on the interwebs, I dont seem to find these locations. Perhaps they are internal values? If so, I will need additional proof or this will have to wait so that i do some additional research to prove this.
A single tria.ge sample is not sufficient for now.
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.
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.
Please read my comment again :)
I said, to provide proof more than a triage execution. External references or internal research explaining these values.
The author of the PR did not provide enough data for an approval yet.
Summary of the Pull Request
Add new values which used by the attacker to disable windows defender
Changelog
update: Suspicious Windows Defender Registry Key Tampering Via Reg.EXE
Example Log Event
Fixed Issues
SigmaHQ Rule Creation Conventions