Add rule for Win connection to suspicious WiFi#6005
Conversation
swachchhanda000
left a comment
There was a problem hiding this comment.
Hi @privet-username,
Thanks for this solid PR.
I made a few additional improvements on top of your original rule, including fixing some typos, expanding the detection logic to cover suspicious SSIDs and additional OUIs, and refining the metadata for better description and clarity.
Cheers!
|
Hi @swachchhanda000, Thank you for the review. Your idea to cover suspicious SSIDs is great. However, I think it should be separate because it covers a different type of attack and has a different severity level than Evil Twin AP. I would create a different rule based on your idea using SSIDs and keep my PR separate. |
f648b10 to
643adcd
Compare
I appreciate the effort, but I’ve reverted the changes related to SSIDs to keep this PR focused strictly on BSSID-based detection, as they represent different attack vectors and severity levels. I'll be happy to see the SSID logic as a separate PR. |
Fix event field name Co-authored-by: frack113 <62423083+frack113@users.noreply.github.com>
Summary of the Pull Request
Add new detection rule for Windows Security event that detects successfull connection to suspicious WiFi AP. Based on MAC addresses belong to RaspberryPi and Alfa AP.
Changelog
new: Connection to suspicious WiFi
Example Log Event
Fixed Issues
SigmaHQ Rule Creation Conventions