Files
hayabusa/rules/sigma/pipe_created/pipe_created_tool_psexec.yml
itiB 83d891b2fa Feature/rm submodule (#312)
* rm: submodule

* Add: rules

* Fix: hayabusa-rules to c9c10a
2021-12-20 21:14:32 +09:00

50 lines
1.4 KiB
YAML

title: PsExec Tool Execution
ruletype: Sigma
author: Thomas Patzke
date: 2017/06/12
description: Detects PsExec service installation and execution events (service and
Sysmon)
detection:
SELECTION_1:
EventID: 17
SELECTION_2:
EventID: 18
SELECTION_3:
PipeName: \PSEXESVC
condition: ((SELECTION_1 or SELECTION_2) and SELECTION_3)
falsepositives:
- unknown
fields:
- EventID
- CommandLine
- ParentCommandLine
- ServiceName
- ServiceFileName
- TargetFilename
- PipeName
id: f3f3a972-f982-40ad-b63c-bca6afdfad7c
level: low
logsource:
category: pipe_created
definition: Note that you have to configure logging for Named Pipe Events in Sysmon
config (Event ID 17 and Event ID 18). The basic configuration is in popular sysmon
configuration (https://github.com/SwiftOnSecurity/sysmon-config), but it is worth
verifying. You can also use other repo, e.g. https://github.com/Neo23x0/sysmon-config,
https://github.com/olafhartong/sysmon-modular. How to test detection? You can
check powershell script from this site https://svch0st.medium.com/guide-to-named-pipes-and-hunting-for-cobalt-strike-pipes-dc46b2c5f575
product: windows
modified: 2021/09/21
references:
- https://www.jpcert.or.jp/english/pub/sr/ir_research.html
- https://jpcertcc.github.io/ToolAnalysisResultSheet
related:
- id: 42c575ea-e41e-41f1-b248-8093c3e82a28
type: derived
status: experimental
tags:
- attack.execution
- attack.t1035
- attack.t1569.002
- attack.s0029