Detectionhightest
Suspicious PsExec Execution
detects execution of psexec or paexec with renamed service name, this rule helps to filter out the noise if psexec is used for legit purposes or if attacker uses a different psexec client other than sysinternal one
Convert In Phoenix Studio
Open this Sigma rule in the converter with the YAML preloaded and ready for backend selection.
Launch
Log Source
Windowssecurity
ProductWindows← raw: windows
Servicesecurity← raw: security
Definition
The advanced audit policy setting "Object Access > Audit Detailed File Share" must be configured for Success/Failure
Detection Logic
Detection Logic2 selectors
detection:
selection1:
EventID: 5145
ShareName: '\\\\\*\\IPC$' # looking for the string \\*\IPC$
RelativeTargetName|endswith:
- '-stdin'
- '-stdout'
- '-stderr'
filter:
RelativeTargetName|startswith: 'PSEXESVC'
condition: selection1 and not filterFalse Positives
Unknown
False positive likelihood has not been assessed. Additional context may be needed during triage.
References
MITRE ATT&CK
Tactics
Sub-techniques
Rule Metadata
Rule ID
c462f537-a1e3-41a6-b5fc-b2c2cef9bf82
Status
test
Level
high
Type
Detection
Created
Wed Apr 03
Modified
Thu Aug 11
Author
Path
rules/windows/builtin/security/win_security_susp_psexec.yml
Raw Tags
attack.lateral-movementattack.t1021.002