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: 776637" data-attributes="member: 32260"><p>I was curious how Hard_Configurator can coexist with Comodo Firewall in CS settings.</p><p>Ran Hard_Configurator installation file - it was contained in the sandbox, so I added it to Trusted applications and ran again. Installed without issues.</p><p></p><p>Ran Hard_Configurator executable - it was first contained, but after a file lookup in the Comodo Cloud (very quickly) it was recognized as Trusted.</p><p>The same scenario was for the other executables: SwitchDefaultDeny, ConfigureDefender, and DocumentsAntiExploit. When I checked the details, the 'User' file rating was 'Rate Now' and below 'Comodo Trusted Installer' was Trusted.</p><p></p><p>I tried to execute a custom made program via "Run As SmartScreen" and a surprise, it was not contained - Comodo knew it as Trusted. Repeated the same with "Run By SmartScreen", the RunBySmartScreen executable was treated in the standard way: contained --> file lookup --> Trusted.</p><p></p><p>The Hard_Configurator installer (unpublished yet) and my custom made executable were uploaded to Comodo Cloud and wait for analysis.</p><p></p><p>Conclusion - CF knows H_C executables, except the new unpublished installer.<strong> It may be, that when I manually set the installer to Trusted, then CF can automatically recognize the installed executables as Trusted. </strong></p><p>Yet, I found the problem with blocking PowerShell commands in ConfigureDefender (see the next post).</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 776637, member: 32260"] I was curious how Hard_Configurator can coexist with Comodo Firewall in CS settings. Ran Hard_Configurator installation file - it was contained in the sandbox, so I added it to Trusted applications and ran again. Installed without issues. Ran Hard_Configurator executable - it was first contained, but after a file lookup in the Comodo Cloud (very quickly) it was recognized as Trusted. The same scenario was for the other executables: SwitchDefaultDeny, ConfigureDefender, and DocumentsAntiExploit. When I checked the details, the 'User' file rating was 'Rate Now' and below 'Comodo Trusted Installer' was Trusted. I tried to execute a custom made program via "Run As SmartScreen" and a surprise, it was not contained - Comodo knew it as Trusted. Repeated the same with "Run By SmartScreen", the RunBySmartScreen executable was treated in the standard way: contained --> file lookup --> Trusted. The Hard_Configurator installer (unpublished yet) and my custom made executable were uploaded to Comodo Cloud and wait for analysis. Conclusion - CF knows H_C executables, except the new unpublished installer.[B] It may be, that when I manually set the installer to Trusted, then CF can automatically recognize the installed executables as Trusted. [/B] Yet, I found the problem with blocking PowerShell commands in ConfigureDefender (see the next post). [/QUOTE]
Insert quotes…
Verification
Post reply
Top
