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
Security
Video Reviews - Security and Privacy
A quick Malwarebytes 3.0 test
Message
<blockquote data-quote="509322" data-source="post: 576856"><p>I am going to chime-in here since you are asking about an AppGuard - COMODO FIrewall combo.</p><p></p><p>Supplementing COMODO Firewall with AppGuard really isn't necessary. In fact, it makes no sense. CFW will intercept a file in User Space before AppGuard. If the file is unknown to COMODO, then CFW will attempt to auto-sandbox the file. However, even if you want the file to run sandboxed, then AppGuard is going to block its execution and thereby prevent auto-sandboxing. To not interfere with auto-sandboxing, you have to lower AppGuard's protections to "Allow Installs" or "OFF." Only then can you run files inside COMODO's sandbox or Virtual Desktop. The same applies to combining CFW with NVT ERP - but you have the option to "Allow" in the ERP alert while running it in Alert mode. In ERP Locked Down mode, the same procedure as for AppGuard will be required.</p><p></p><p>I am of the opinion that these sorts of security software combinations are nothing but a needless usability hassle created by the user. How much of hassle it will be depends - mostly - upon how often the user introduces executable files to their system. If the system is essentially static, software kept up-to-date, then CFW and AppGuard will rarely block anything - if ever - since there is nothing that has been introduced <em><strong>by the user</strong></em> to the system that needs to be blocked. If the user constantly changes the system - continually introducing executable files to it - then that user will quickly tire of a CFW - AppGuard combo. Like nearly all things IT, the most influential variable is user computing habits. The user makes it much more complicated than what is required to <em>sensibly</em> protect the system. It makes a big difference in the overall usability index.</p><p></p><p>In CFW you can configure it to be complete default-deny (blocking both file execution & network access) if you so wish. If you configure it this way, then you might have to create some Allow exclusions - and that will depend upon what is installed on your system and whether or not all the safe\legitimate files are known to COMODO. If you configure CFW for absolute-blocking then, once again, AppGuard is pointless.</p><p></p><p>Between AppGuard and COMODO Firewall, you would be better off choosing one product or the other - and learning to use that product knowledgeably.</p></blockquote><p></p>
[QUOTE="509322, post: 576856"] I am going to chime-in here since you are asking about an AppGuard - COMODO FIrewall combo. Supplementing COMODO Firewall with AppGuard really isn't necessary. In fact, it makes no sense. CFW will intercept a file in User Space before AppGuard. If the file is unknown to COMODO, then CFW will attempt to auto-sandbox the file. However, even if you want the file to run sandboxed, then AppGuard is going to block its execution and thereby prevent auto-sandboxing. To not interfere with auto-sandboxing, you have to lower AppGuard's protections to "Allow Installs" or "OFF." Only then can you run files inside COMODO's sandbox or Virtual Desktop. The same applies to combining CFW with NVT ERP - but you have the option to "Allow" in the ERP alert while running it in Alert mode. In ERP Locked Down mode, the same procedure as for AppGuard will be required. I am of the opinion that these sorts of security software combinations are nothing but a needless usability hassle created by the user. How much of hassle it will be depends - mostly - upon how often the user introduces executable files to their system. If the system is essentially static, software kept up-to-date, then CFW and AppGuard will rarely block anything - if ever - since there is nothing that has been introduced [I][B]by the user[/B][/I] to the system that needs to be blocked. If the user constantly changes the system - continually introducing executable files to it - then that user will quickly tire of a CFW - AppGuard combo. Like nearly all things IT, the most influential variable is user computing habits. The user makes it much more complicated than what is required to [I]sensibly[/I] protect the system. It makes a big difference in the overall usability index. In CFW you can configure it to be complete default-deny (blocking both file execution & network access) if you so wish. If you configure it this way, then you might have to create some Allow exclusions - and that will depend upon what is installed on your system and whether or not all the safe\legitimate files are known to COMODO. If you configure CFW for absolute-blocking then, once again, AppGuard is pointless. Between AppGuard and COMODO Firewall, you would be better off choosing one product or the other - and learning to use that product knowledgeably. [/QUOTE]
Insert quotes…
Verification
Post reply
Top