|
1 | 1 | <!--
|
2 | 2 | sysmon-config | A sysmon configuration focused on default high-quality event tracing and easy customization by the community
|
3 |
| - Master version: 50 | Date: 2017-03-02 |
4 |
| - Master author: @SwiftOnSecurity, with contributors also credited in-line or on Git. |
| 3 | + Master version: 51 | Date: 2017-03-14 |
| 4 | + Master author: @SwiftOnSecurity, other contributors also credited in-line or on Git. |
5 | 5 | Master project: https://github.com/SwiftOnSecurity/sysmon-config
|
6 | 6 | Master license: Creative Commons Attribution 4.0 | You may privatize, fork, edit, teach, publish, or deploy for commercial use - with attribution in the text.
|
7 | 7 |
|
|
197 | 197 | <!-- Often exploited services -->
|
198 | 198 | <Image condition="image">omniinet.exe</Image> <!-- HP Data Protector https://www.cvedetails.com/vulnerability-list/vendor_id-10/product_id-20499/HP-Data-Protector.html | Credit @Cyb3rOps -->
|
199 | 199 | <Image condition="image">hpsmhd.exe</Image> <!-- HP System Management Homepage https://www.cvedetails.com/vulnerability-list/vendor_id-10/product_id-7244/HP-System-Management-Homepage.html | Credit @Cyb3rOps -->
|
| 200 | + <!--Malware related--> |
| 201 | + <Image condition="image">tor.exe</Image> <!--Tor [ https://www.hybrid-analysis.com/sample/800bf028a23440134fc834efc5c1e02cc70f05b2e800bbc285d7c92a4b126b1c?environmentId=100 ] --> |
200 | 202 | <!--Ports: Suspicious-->
|
201 | 203 | <DestinationPort condition="is">22</DestinationPort> <!--SSH protocol-->
|
202 | 204 | <DestinationPort condition="is">23</DestinationPort> <!--Telnet protocol-->
|
203 |
| - <DestinationPort condition="is">25</DestinationPort> <!--SMTP email--> |
| 205 | + <DestinationPort condition="is">25</DestinationPort> <!--SMTP mail protocol--> |
204 | 206 | <DestinationPort condition="is">3389</DestinationPort> <!--Microsoft:Windows:RDP-->
|
205 | 207 | <DestinationPort condition="is">5800</DestinationPort> <!--VNC protocol-->
|
206 | 208 | <DestinationPort condition="is">5900</DestinationPort> <!--VNC protocol-->
|
207 | 209 | <!--Ports: Proxy-->
|
208 | 210 | <DestinationPort condition="is">1080</DestinationPort> <!--Socks proxy port | Credit @ion-storm-->
|
209 |
| - <DestinationPort condition="is">8080</DestinationPort> <!--Socks proxy port | Credit @ion-storm--> |
210 | 211 | <DestinationPort condition="is">3128</DestinationPort> <!--Socks proyx port | Credit @ion-storm-->
|
| 212 | + <DestinationPort condition="is">8080</DestinationPort> <!--Socks proxy port | Credit @ion-storm--> |
211 | 213 | <!--Ports: Tor-->
|
212 | 214 | <DestinationPort condition="is">1723</DestinationPort> <!--Tor protocol | Credit @ion-storm-->
|
213 | 215 | <DestinationPort condition="is">4500</DestinationPort> <!--Tor protocol | Credit @ion-storm-->
|
|
280 | 282 | <!--SYSMON EVENT ID 10 : INTER-PROCESS ACCESS-->
|
281 | 283 | <!--DATA: UtcTime, SourceProcessGuid, SourceProcessId, SourceThreadId, SourceImage, TargetProcessGuid, TargetProcessId, TargetImage, GrantedAccess, CallTrace-->
|
282 | 284 | <ProcessAccess onmatch="include">
|
283 |
| - <!--COMMENT: Monitor for processes accessing other process' memory. This can be valuable, but can cause massive event glut. |
284 |
| - Disabled by default since including even one entry here activates this component. Reward/performance decision. |
285 |
| - Encourage you to experiment with this feature yourself.--> |
286 |
| - <!--FUTURE WORK: Include mimikatz-specific events.--> |
| 285 | + <!--COMMENT: Monitor for processes accessing other process' memory. This can be valuable, but can cause a huge number of events.--> |
287 | 286 | </ProcessAccess>
|
288 | 287 |
|
289 | 288 | <!--SYSMON EVENT ID 11 : FILE CREATED-->
|
|
343 | 342 | <!--NOTE: "contains" works by finding the first letter, then matching the second, etc, so the first letters should be as low-occurance as possible.-->
|
344 | 343 | <!--NOTE: Windows writes hundreds or thousands of registry keys a minute, so just because you're not changing stuff, doesn't mean these rules aren't being run.-->
|
345 | 344 | <!--NOTE: You don't have to spend a lot of time worrying about this, CPUs are fast, but it's something to consider. Every rule and condition type has a cost.-->
|
346 |
| - |
347 | 345 | <!--DATA: EventType, UtcTime, ProcessGuid, ProcessId, Image, TargetObject, Details, NewName-->
|
348 | 346 | <!--TECHNICAL: Possible prefixes are HKLM, HKCR, and HKEY_USERS-->
|
349 | 347 | <!--CRITICAL: Schema version 3.30 and higher use HKLM and HKEY_USERS and HKCR and CurrentControlSet instead of REGISTRY\MACHINE\ and \REGISTRY\USER\ and ControlSet001-->
|
|
427 | 425 | <TargetObject condition="begin with">HKLM\SOFTWARE\Microsoft\Security Center\UpdatesDisableNotify</TargetObject>
|
428 | 426 | <!--Windows Defender tampering | Credit @ion-storm -->
|
429 | 427 | <TargetObject condition="begin with">HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\DisableAntiSpyware</TargetObject>
|
| 428 | + <TargetObject condition="begin with">HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\DisableAntiVirus</TargetObject> |
430 | 429 | <TargetObject condition="begin with">HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\Real-Time Protection\DisableBehaviorMonitoring</TargetObject>
|
431 | 430 | <TargetObject condition="begin with">HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\Real-Time Protection\DisableOnAccessProtection</TargetObject>
|
432 | 431 | <TargetObject condition="begin with">HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\Real-Time Protection\DisableScanOnRealtimeEnable</TargetObject>
|
|
0 commit comments