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
Inactive Support Threads
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
Hard_Configurator - Windows Hardening Configurator
Message
<blockquote data-quote="Andy Ful" data-source="post: 944303" data-attributes="member: 32260"><p>I tried to find the difference between using the enforcement for 'All users" and the default H_C enforcement (All users except Administrators). I examined the tests on MH made by [USER=64646]@askalan[/USER]. The tests were made with the H_C Strict_Recommended_Settings (<strong>with</strong> <strong>antivirus disabled</strong>), but the results would be the same in the Real-World Scenario with the H_C Basic_Recommended_Settings + SmartScreen (although they could be different for malware from USB drives).</p><p>After several months of testing, there was only one malware that could infect the system. <strong>This malware did not bypass directly the SRP restrictions, but it could infect the system when the user was tricked to install the malware as an application (malware had the ability to bypass SmartScreen <strong>and the user had to allow the malware elevation via UAC prompt)</strong>.</strong></p><p>[URL unfurl="true"]https://malwaretips.com/threads/buhtrap-ransomware-signed-07-02-2019.90379/post-797052[/URL]</p><p></p><p>The infection chain could be broken with <strong>'All users' enforcement</strong> because the malware dropped/executed a script that would be blocked by SRP with this enforcement even when malware used high privileges. In the test with the default H_C enforcement, the malware was allowed to run with high privileges so SRP restrictions for Windows Script Host did not apply.</p><p></p><p>I suspect that this difference would be only theoretical, because most users would think that the file allowed by SmartScreen is most probably clean. Furthermore, such malware is used mostly in targeted attacks on enterprises, organizations, etc. Rarely, the targets can be the home users as in the case of IOBit malware (this one was blocked via anti-DLL-hijacking protection when InstallBySmartScreen or RunBySmartScreen was used).</p><p>Sometimes such malware can be<strong> reused</strong> in widespread attacks, but then most AVs will detect it as malware.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 944303, member: 32260"] I tried to find the difference between using the enforcement for 'All users" and the default H_C enforcement (All users except Administrators). I examined the tests on MH made by [USER=64646]@askalan[/USER]. The tests were made with the H_C Strict_Recommended_Settings ([B]with[/B] [B]antivirus disabled[/B]), but the results would be the same in the Real-World Scenario with the H_C Basic_Recommended_Settings + SmartScreen (although they could be different for malware from USB drives). After several months of testing, there was only one malware that could infect the system. [B]This malware did not bypass directly the SRP restrictions, but it could infect the system when the user was tricked to install the malware as an application (malware had the ability to bypass SmartScreen [B]and the user had to allow the malware elevation via UAC prompt)[/B].[/B] [URL unfurl="true"]https://malwaretips.com/threads/buhtrap-ransomware-signed-07-02-2019.90379/post-797052[/URL] The infection chain could be broken with [B]'All users' enforcement[/B] because the malware dropped/executed a script that would be blocked by SRP with this enforcement even when malware used high privileges. In the test with the default H_C enforcement, the malware was allowed to run with high privileges so SRP restrictions for Windows Script Host did not apply. I suspect that this difference would be only theoretical, because most users would think that the file allowed by SmartScreen is most probably clean. Furthermore, such malware is used mostly in targeted attacks on enterprises, organizations, etc. Rarely, the targets can be the home users as in the case of IOBit malware (this one was blocked via anti-DLL-hijacking protection when InstallBySmartScreen or RunBySmartScreen was used). Sometimes such malware can be[B] reused[/B] in widespread attacks, but then most AVs will detect it as malware. [/QUOTE]
Insert quotes…
Verification
Post reply
Top