Suspicious Process Discovery With Get-Process
Get the processes that are running on the local computer.
Sigma rule (View on GitHub)
1title: Suspicious Process Discovery With Get-Process
2id: af4c87ce-bdda-4215-b998-15220772e993
3status: test
4description: Get the processes that are running on the local computer.
5references:
6 - https://github.com/redcanaryco/atomic-red-team/blob/f339e7da7d05f6057fdfcdd3742bfcf365fee2a9/atomics/T1057/T1057.md#atomic-test-3---process-discovery---get-process
7 - https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/get-process?view=powershell-7.4
8author: frack113
9date: 2022-03-17
10tags:
11 - attack.discovery
12 - attack.t1057
13logsource:
14 product: windows
15 category: ps_script
16 definition: 'Requirements: Script Block Logging must be enabled'
17detection:
18 selection:
19 ScriptBlockText|contains: Get-Process
20 condition: selection
21falsepositives:
22 - Legitimate PowerShell scripts
23level: low
References
-
Small and highly portable detection tests based on MITRE's ATT&CK. - redcanaryco/atomic-red-team
Read More -
The Get-Process cmdlet gets the processes on a local computer. Without parameters, this cmdlet gets all of the processes on the local computer. You can also specify a particular process by process name or process ID (PID) or pass a process object through the pipeline to this cmdlet. By default, this cmdlet returns a process object that has detailed information about the process and supports methods that let you start and stop the process. You can also use the parameters of the Get-Process cmdlet to get file version information for the program that runs in the process and to get the modules that the process loaded.
Read More
Related rules
- Cisco Discovery
- HackTool - PCHunter Execution
- Process Discovery
- Recon Command Output Piped To Findstr.EXE
- List remote processes using tasklist