Detectionmediumtest
Service Registry Permissions Weakness Check
Adversaries may execute their own malicious payloads by hijacking the Registry entries used by services. Adversaries may use flaws in the permissions for registry to redirect from the originally specified executable to one that they control, in order to launch their own code at Service start. Windows stores local service configuration information in the Registry under HKLM\SYSTEM\CurrentControlSet\Services
Convert In Phoenix Studio
Open this Sigma rule in the converter with the YAML preloaded and ready for backend selection.
Launch
Log Source
WindowsPowerShell Script
ProductWindows← raw: windows
CategoryPowerShell Script← raw: ps_script
Definition
Requirements: Script Block Logging must be enabled
Detection Logic
Detection Logic1 selector
detection:
selection:
ScriptBlockText|contains|all:
- 'get-acl'
- 'REGISTRY::HKLM\SYSTEM\CurrentControlSet\Services\'
condition: selectionFalse Positives
Legitimate administrative script
MITRE ATT&CK
Sub-techniques
Other
stp.2a
Rule Metadata
Rule ID
95afc12e-3cbb-40c3-9340-84a032e596a3
Status
test
Level
medium
Type
Detection
Created
Thu Dec 30
Author
Path
rules/windows/powershell/powershell_script/posh_ps_get_acl_service.yml
Raw Tags
attack.privilege-escalationattack.defense-evasionattack.persistenceattack.t1574.011stp.2a