Query: Sigma YAML for windows / ps_script
Matching passage: Sigma rule: Detects calls to "get-process" where the output is piped to a "where-object" filter to search for security solution proc. Logsource: windows / ps_script. Rule: title: Security Software Discovery Via Powershell Script id: 904e8e61-8edf-4350-b59c-b905fc8e810c status: test description: 'Detects calls to "get-process" where the output is piped to a "where-object" filter to search for security solution processes. Adversaries may attempt to get a listing of security software, configurations, defensive tools, and sensors that are installed on a system or in a cloud environment. This may include things such as firewall rules and anti-virus ' references: - https://github.com/redcanaryco/atomic-red-team/blob/f339e7da7d05f6057fdfcdd3742bfcf365fee2a9/atomics/T1518.001/T1518.001.md#atomic-test-2---security-software-discovery---powershell author: frack113, Anish Bogati, Nasreddine Bencherchali (Nextron Systems) date: 2021-12-16 modified: 2023-10-24 tags: - attack.discovery - attack.t1518.001 logsource: product: windows category: ps_script definition: 'Requirements: Script Block Logging must be enabled' detection: selection_cmdlet: ScriptBlockText|contains: - get-process | \? - get-process | where - gps | \? - gps | where selection_field: ScriptBlockText|contains: - Company -like - Description -like - Name -like - Path -like - Product -like selection_keywords: ScriptBlockText|contains: - \*avira\* - \*carbonblack\* - \*cylance\* - \*defender\* - \*kaspersky\* - \*malware\* - \*sentinel\* - \*symantec\* - \*virus\* condition: all of selection_* falsepositives: - False positives might occur due to the nature of the ScriptBlock being ingested as a big blob. Initial tuning is required. - As the "selection_cmdlet" is common in scripts the matching engine might slow down the search. Change into regex or a more accurate string to avoid heavy resource consumption if experienced level: medium
Near-miss passage: Sigma rule: Detects events generated by user-mode applications when they call the CveEventWrite API when a known vulnerability is tr. Logsource: windows / application. Rule: title: Audit CVE Event id: 48d91a3a-2363-43ba-a456-ca71ac3da5c2 status: test description: 'Detects events generated by user-mode applications when they call the CveEventWrite API when a known vulnerability is trying to be exploited. MS started using this log in Jan. 2020 with CVE-2020-0601 (a Windows CryptoAPI vulnerability. Unfortunately, that is about the only instance of CVEs being written to this log. ' references: - https://twitter.com/VM_vivisector/status/1217190929330655232 - https://twitter.com/DidierStevens/status/1217533958096924676 - https://twitter.com/FlemmingRiis/status/1217147415482060800 - https://www.youtube.com/watch?v=ebmW42YYveI - https://nullsec.us/windows-event-log-audit-cve/ author: Florian Roth (Nextron Systems), Zach Mathis date: 2020-01-15 modified: 2022-10-22 tags: - attack.execution - attack.stealth - attack.t1203 - attack.privilege-escalation - attack.t1068 - attack.t1211 - attack.credential-access - attack.t1212 - attack.lateral-movement - attack.t1210 - attack.impact - attack.t1499.004 logsource: product: windows service: application detection: selection: Provider_Name: - Microsoft-Windows-Audit-CVE - Audit-CVE EventID: 1 condition: selection falsepositives: - Unknown level: critical