Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Hard_Configurator Tools
ConfigureDefender utility for Windows 10
Message
<blockquote data-quote="Andy Ful" data-source="post: 738031" data-attributes="member: 32260"><p>It would be interesting to test against the real malware the ASR rule:</p><p>"<span style="color: rgb(65, 168, 95)"><strong>Block executable files from running unless they meet a prevalence, age, or trusted list criteria</strong></span>".</p><p>The above rule is a kind of reputation rule based on <span style="color: rgb(65, 168, 95)"><strong>a prevalence, age, or trusted list criteria.</strong></span></p><p>That would be the cover for SmartScreen, because the EXE or DLL malware files downloaded and ran by scripts are usually ignored by SmartScreen. If the user activated Defender Network Protection, then a connection to the malicious website can be blocked (if the website is known as malicious).</p><p>In theory, this rule can be also useful in Defender + Hard_Configurator set to allow EXE & DLL files. That would be a similar idea as Avast Hardened Aggressive mode with blocked/restricted scripts or Comodo Firewall with Sandbox set to block.</p><p>The rule is supposed to block also PowerShell and WSH scripts, but I prepared a simple trojan downloader that bypassed all ASR rules (script downloaded and ran the EXE payload). So, blocking scripts by this rule is not so strong. Anyway, if the payload was malicious then it should be stopped by "<span style="color: rgb(65, 168, 95)"><strong>Block executable files from running unless they meet a prevalence, age, or trusted list criteria</strong></span>".</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 738031, member: 32260"] It would be interesting to test against the real malware the ASR rule: "[COLOR=rgb(65, 168, 95)][B]Block executable files from running unless they meet a prevalence, age, or trusted list criteria[/B][/COLOR]". The above rule is a kind of reputation rule based on [COLOR=rgb(65, 168, 95)][B]a prevalence, age, or trusted list criteria.[/B][/COLOR] That would be the cover for SmartScreen, because the EXE or DLL malware files downloaded and ran by scripts are usually ignored by SmartScreen. If the user activated Defender Network Protection, then a connection to the malicious website can be blocked (if the website is known as malicious). In theory, this rule can be also useful in Defender + Hard_Configurator set to allow EXE & DLL files. That would be a similar idea as Avast Hardened Aggressive mode with blocked/restricted scripts or Comodo Firewall with Sandbox set to block. The rule is supposed to block also PowerShell and WSH scripts, but I prepared a simple trojan downloader that bypassed all ASR rules (script downloaded and ran the EXE payload). So, blocking scripts by this rule is not so strong. Anyway, if the payload was malicious then it should be stopped by "[COLOR=rgb(65, 168, 95)][B]Block executable files from running unless they meet a prevalence, age, or trusted list criteria[/B][/COLOR]". [/QUOTE]
Insert quotes…
Verification
Post reply
Top