[et_pb_section fb_built=”1″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_row _builder_version=”4.7.7″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.7.7″ _module_preset=”default”][et_pb_text _builder_version=”4.7.7″ _module_preset=”default”]<\/p>\n
Following THOR’s approach of showing suspicious elements, it is not feasible to completely avoid false positives. Therefore we always try to provide as much information as possible for an analyst to assess such a suspicious element as quickly as possible.<\/p>\n
Users liked the DeeDive feature in which a string match on a chunk of data does not only include the matching string but also the surrounding strings, which help enormously to evaluate the criticality of a matching YARA signature.\u00a0<\/p>\n
The TechPreview version of THOR 10.6 now introduces this extra information in many other modules.\u00a0<\/p>\n
The following example shows a false positive in which the string ‘ -p 0x53A4C60B’ matched on the process memory of the ‘svchost.exe’ process with the full command line as ‘svchost.exe -k ClipboardSvcGroup -p’.\u00a0 \u00a0<\/p>\n
[\/et_pb_text][et_pb_image src=”https:\/\/www.nextron-systems.com\/wp-content\/uploads\/2021\/01\/Screenshot-2021-01-06-at-16.23.16.png” title_text=”Screenshot 2021-01-06 at 16.23.16″ _builder_version=”4.7.7″ _module_preset=”default”][\/et_pb_image][et_pb_text _builder_version=”4.7.7″ _module_preset=”default”]<\/p>\n
In previous versions THOR you would only see the matching string, but the new versions will also show the 40 bytes before and after the string match. (in the example it has been set to 100 bytes by using `–string-context 100`)<\/p>\n
This helps analysts to assess the match more easily without having a process memory dump. In the example above, analyst can review that data block in which the string match occurred and see that it has been within HTML text that has been copied to memory. It could be an analyst system on which someone handling forensic reports copied sections from one document to another, but it’s certainly not the threat, which the YARA rule tried to detect.\u00a0<\/p>\n
This feature will be available in the upcoming THOR TechPreview 10.6.4.\u00a0<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"
Following THOR’s approach of showing suspicious elements, it is not feasible to completely avoid false positives. Therefore we always try to provide as much information as possible for an analyst to assess such a suspicious element as quickly as possible. Users liked the DeeDive feature in which a string match on a chunk of data does not only include the matching string but also the surrounding strings, which help enormously to evaluate the criticality of a matching YARA signature.\u00a0 The TechPreview version of THOR 10.6 now introduces this extra information in many other modules.\u00a0 The following example shows a false positive in which the string ‘ -p 0x53A4C60B’ matched on the process memory of the ‘svchost.exe’ process with the full command line as ‘svchost.exe -k ClipboardSvcGroup -p’.\u00a0 \u00a0In previous versions THOR you would only see the matching string, but the new versions will also show the 40 bytes before and after the string match. (in the example it has been set to 100 bytes by using `–string-context 100`) This helps analysts to assess the match more easily without having a process memory dump. In the example above, analyst can review that data block in which the string match occurred and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[46,1,32,248],"tags":[],"class_list":["post-9186","post","type-post","status-publish","format-standard","hentry","category-newsletter","category-nextron","category-thor","category-thor-lite"],"yoast_head":"\n