add SuspDCSyncTraffic from MS Defender #5040
Merged
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cover MS Defender alert
Behavior:Win32/SuspDCSyncTraffic
.Cover MS Defender alert
Behavior:Win32/SuspDCSyncTraffic
with stringDCSync
. It's kind of something different than all the other strings with malware names or categories, but it shows up in the same logs and is as critical, so why not just put it in here.The screenshot is from pentesting with a Kali VM on a Windows host with MS Defender installed. It blamed vmnat.exe for the traffic coming out of the VM:
update: Antivirus Password Dumper Detection - add DCSync for MS Defender traffic detection
Fixed Issues
SigmaHQ Rule Creation Conventions