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: 730206" data-attributes="member: 32260"><p>Ha, ha .<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> So editors who use Office 2007 (unsupported by Microsoft) have to wait until I finish WDDS (Windows Default-Deny Security) which will block active content (macros, OLE, ActiveX, and DDE) in MS Office or use SysHardener. Even without this, Hard_Configurator default-deny settings apply a pretty good protection against malicious documents (including fileless PowerShell attacks). I analyzed many malicious samples, and so far, all of them could be stopped by default-deny setup. That is because all samples used JS or VBS scripts, or PowerShell with advanced functions, or payloads from the Userspace. I do not think that attackers will change soon their attack techniques, which are so successful against most targets.</p><p>Editors who use MS Office 2010+ on Windows 10 FCU have already a decent protection when using Hard_Configurator + Windows Defender ASR.</p><p>It is worth to remember that <span style="color: rgb(184, 49, 47)">without default-deny setup</span>, the users are still vulnerable, even when all active content in Office documents is blocked. This follows from the ability to control MS Office executables programmatically by external programs. That can be used to defeat the anti-ransomware protection.</p><p>Of course, there are many solutions to the Office documents problem (anti-exe, sandboxing, etc.). NVT OSArmor and VoodooShield have very good modules that can protect against malicious documents in MS Office. Also, ReHips are sandboxing by default MS Office executables, and there is also Comodo Firewall with activated sandbox, Excubits drivers, etc.</p><p>I like very much two applications: AppGuard (paid) and Sandboxie (paid), which can also apply a decent protection.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 730206, member: 32260"] Ha, ha .:) So editors who use Office 2007 (unsupported by Microsoft) have to wait until I finish WDDS (Windows Default-Deny Security) which will block active content (macros, OLE, ActiveX, and DDE) in MS Office or use SysHardener. Even without this, Hard_Configurator default-deny settings apply a pretty good protection against malicious documents (including fileless PowerShell attacks). I analyzed many malicious samples, and so far, all of them could be stopped by default-deny setup. That is because all samples used JS or VBS scripts, or PowerShell with advanced functions, or payloads from the Userspace. I do not think that attackers will change soon their attack techniques, which are so successful against most targets. Editors who use MS Office 2010+ on Windows 10 FCU have already a decent protection when using Hard_Configurator + Windows Defender ASR. It is worth to remember that [COLOR=rgb(184, 49, 47)]without default-deny setup[/COLOR], the users are still vulnerable, even when all active content in Office documents is blocked. This follows from the ability to control MS Office executables programmatically by external programs. That can be used to defeat the anti-ransomware protection. Of course, there are many solutions to the Office documents problem (anti-exe, sandboxing, etc.). NVT OSArmor and VoodooShield have very good modules that can protect against malicious documents in MS Office. Also, ReHips are sandboxing by default MS Office executables, and there is also Comodo Firewall with activated sandbox, Excubits drivers, etc. I like very much two applications: AppGuard (paid) and Sandboxie (paid), which can also apply a decent protection. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
