NetNTLM Downgrade Attack - Registry
Detects NetNTLM downgrade attack
Sigma rule (View on GitHub)
1title: NetNTLM Downgrade Attack - Registry
2id: d67572a0-e2ec-45d6-b8db-c100d14b8ef2
3status: test
4description: Detects NetNTLM downgrade attack
5references:
6 - https://web.archive.org/web/20171113231705/https://www.optiv.com/blog/post-exploitation-using-netntlm-downgrade-attacks
7 - https://www.ultimatewindowssecurity.com/wiki/page.aspx?spid=NSrpcservers
8author: Florian Roth (Nextron Systems), wagga, Nasreddine Bencherchali (Splunk STRT)
9date: 2018-03-20
10modified: 2024-12-03
11tags:
12 - attack.defense-evasion
13 - attack.t1562.001
14 - attack.t1112
15logsource:
16 product: windows
17 category: registry_event
18detection:
19 selection_regkey:
20 TargetObject|contains|all:
21 - 'SYSTEM\'
22 - 'ControlSet'
23 - '\Control\Lsa'
24 selection_value_lmcompatibilitylevel:
25 TargetObject|endswith: '\lmcompatibilitylevel'
26 Details:
27 - 'DWORD (0x00000000)'
28 - 'DWORD (0x00000001)'
29 - 'DWORD (0x00000002)'
30 selection_value_ntlmminclientsec:
31 TargetObject|endswith: '\NtlmMinClientSec'
32 Details:
33 - 'DWORD (0x00000000)' # No Security
34 - 'DWORD (0x00000010)' # Only Integrity
35 - 'DWORD (0x00000020)' # Only confidentiality
36 - 'DWORD (0x00000030)' # Both Integrity and confidentiality
37 selection_value_restrictsendingntlmtraffic:
38 # Note: The obvious values with issues are 0x00000000 (allow all) and 0x00000001 (audit).
39 # 0x00000002 can be secure but only if "ClientAllowedNTLMServers" is properly configured
40 # Hence all values should be monitored and investigated
41 TargetObject|endswith: '\RestrictSendingNTLMTraffic'
42 condition: selection_regkey and 1 of selection_value_*
43falsepositives:
44 - Services or tools that set the values to more restrictive values
45level: high
References
Related rules
- Disable Security Events Logging Adding Reg Key MiniNt
- NetNTLM Downgrade Attack
- Reg Add Suspicious Paths
- Non-privileged Usage of Reg or Powershell
- HackTool - Stracciatella Execution