From b6bb18d20c0b0fa513b6eebf0038aca2e5a8040a Mon Sep 17 00:00:00 2001 From: root Date: Thu, 25 Nov 2021 11:55:39 +0000 Subject: [PATCH 1/2] Added detection testing service results inAdd or Set Windows Defender Exclusion --- .../add_or_set_windows_defender_exclusion.yml | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/detections/endpoint/add_or_set_windows_defender_exclusion.yml b/detections/endpoint/add_or_set_windows_defender_exclusion.yml index de9004167a..fc8dd81f3b 100644 --- a/detections/endpoint/add_or_set_windows_defender_exclusion.yml +++ b/detections/endpoint/add_or_set_windows_defender_exclusion.yml @@ -6,19 +6,19 @@ author: Teoderick Contreras, Splunk type: TTP datamodel: - Endpoint -description: This analytic will detect a suspicious process commandline related to windows defender exclusion feature. - This command is abused by adversaries, malware author and red teams to bypassed Windows Defender Anti-Virus product - by excluding folder path, file path, process, extensions and etc. from its real time or schedule scan to execute their malicious code. - This is a good indicator for defense evasion and to look further for events after this behavior. +description: This analytic will detect a suspicious process commandline related to + windows defender exclusion feature. This command is abused by adversaries, malware + author and red teams to bypassed Windows Defender Anti-Virus product by excluding folder + path, file path, process, extensions and etc. from its real time or schedule scan + to execute their malicious code. This is a good indicator for defense evasion and + to look further for events after this behavior. search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) - as lastTime from datamodel=Endpoint.Processes where (Processes.process = "*Add-MpPreference *" OR Processes.process = "*Set-MpPreference *") - AND Processes.process="*-exclusion*" - by Processes.dest Processes.user Processes.parent_process Processes.parent_process_name Processes.process_name Processes.original_file_name - Processes.process Processes.process_id Processes.parent_process_id - | `drop_dm_object_name(Processes)` - | `security_content_ctime(firstTime)` - | `security_content_ctime(lastTime)` - | `add_or_set_windows_defender_exclusion_filter`' + as lastTime from datamodel=Endpoint.Processes where (Processes.process = "*Add-MpPreference + *" OR Processes.process = "*Set-MpPreference *") AND Processes.process="*-exclusion*" + by Processes.dest Processes.user Processes.parent_process Processes.parent_process_name + Processes.process_name Processes.original_file_name Processes.process Processes.process_id + Processes.parent_process_id | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` + | `security_content_ctime(lastTime)` | `add_or_set_windows_defender_exclusion_filter`' how_to_implement: To successfully implement this search you need to be ingesting information on process that include the name of the process responsible for the changes from your endpoints into the `Endpoint` datamodel in the `Registry` node. Also make sure @@ -58,7 +58,6 @@ tags: security_domain: endpoint impact: 80 confidence: 80 - # (impact * confidence)/100 risk_score: 64 context: - Source:Endpoint @@ -72,4 +71,5 @@ tags: - name: dest type: Hostname role: - - Victim \ No newline at end of file + - Victim + automated_detection_testing: passed From 4ed89e21a2004b645a23c7c551121050b5ed7119 Mon Sep 17 00:00:00 2001 From: root Date: Thu, 25 Nov 2021 12:00:54 +0000 Subject: [PATCH 2/2] Added detection testing service results inWindows Defender Exclusion Registry Entry --- ...dows_defender_exclusion_registry_entry.yml | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/detections/endpoint/windows_defender_exclusion_registry_entry.yml b/detections/endpoint/windows_defender_exclusion_registry_entry.yml index b0ce42caef..b9575dea39 100644 --- a/detections/endpoint/windows_defender_exclusion_registry_entry.yml +++ b/detections/endpoint/windows_defender_exclusion_registry_entry.yml @@ -6,16 +6,17 @@ author: Teoderick Contreras, Splunk type: TTP datamodel: - Endpoint -description: This analytic will detect a suspicious process that modify a registry related to windows defender exclusion feature. - This registry is abused by adversaries, malware author and red teams to bypassed Windows Defender Anti-Virus product - by excluding folder path, file path, process, extensions and etc. from its real time or schedule scan to execute their malicious code. - This is a good indicator for a defense evasion and to look further for events after this behavior. +description: This analytic will detect a suspicious process that modify a registry + related to windows defender exclusion feature. This registry is abused by adversaries, + malware author and red teams to bypassed Windows Defender Anti-Virus product by + excluding folder path, file path, process, extensions and etc. from its real time + or schedule scan to execute their malicious code. This is a good indicator for a + defense evasion and to look further for events after this behavior. search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) - as lastTime from datamodel=Endpoint.Registry where Registry.registry_path = "*\\SOFTWARE\\Policies\\Microsoft\\Windows Defender\\Exclusions\\*" - by Registry.dest Registry.user Registry.registry_path Registry.registry_value_name Registry.registry_value_data | `drop_dm_object_name(Registry)` - | `security_content_ctime(lastTime)` - | `security_content_ctime(firstTime)` - | `windows_defender_exclusion_registry_entry_filter`' + as lastTime from datamodel=Endpoint.Registry where Registry.registry_path = "*\\SOFTWARE\\Policies\\Microsoft\\Windows + Defender\\Exclusions\\*" by Registry.dest Registry.user Registry.registry_path Registry.registry_value_name + Registry.registry_value_data | `drop_dm_object_name(Registry)` | `security_content_ctime(lastTime)` + | `security_content_ctime(firstTime)` | `windows_defender_exclusion_registry_entry_filter`' how_to_implement: To successfully implement this search you need to be ingesting information on process that include the name of the process responsible for the changes from your endpoints into the `Endpoint` datamodel in the `Registry` node. Also make sure @@ -50,7 +51,6 @@ tags: security_domain: endpoint impact: 80 confidence: 80 - # (impact * confidence)/100 risk_score: 64 context: - Source:Endpoint @@ -65,4 +65,4 @@ tags: type: Hostname role: - Victim - \ No newline at end of file + automated_detection_testing: passed