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
Comodo Firewall vs a test Keylogger
Message
<blockquote data-quote="hjlbx" data-source="post: 423591"><p>Comodo engineers put block setting options (HIPS, sandbox and firewall) into CIS so that it will function as a "complete" anti-executable... the protection model is premised upon a complete system lock-down while at the same time providing the user with the option to run any Unrecognized files virtually or with user-defined restrictions contained within sandbox (right-click "Run in Comodo sandbox.")</p><p></p><p>So, in essence, CIS sandbox is multi-functional in that different sandbox policies are applied to any Unrecognized file - dependent upon how the file is executed. In other words, a CIS user can define two sets of rules for the sandbox. The first being for the auto-sandbox and the other for Right-Click "Run in Comodo sandbox"; executed from the desktop or from within a browser = Block by auto-sandbox, while Right-Click "Run in Comodo sandbox" = will run virtually or Limited, Untrusted, etc dependent upon user settings for the sandbox.</p><p></p><p>This CIS feature isn't explained in the CIS manual... and most users wouldn't know that it exists unless they stumbled upon it...</p><p></p><p>On top of that, the modules are designed to block any Unrecognized files in cascade fashion should any single module fail: auto-sandbox > HIPS > firewall.</p><p></p><p>Comodo performed quite a feat of software engineering on that one... perfect trifecta = anti-executable + virtualization + outbound network notifications or Block ... and it is the primary reason I use CIS; everything to lock-down system is included in one complete package</p></blockquote><p></p>
[QUOTE="hjlbx, post: 423591"] Comodo engineers put block setting options (HIPS, sandbox and firewall) into CIS so that it will function as a "complete" anti-executable... the protection model is premised upon a complete system lock-down while at the same time providing the user with the option to run any Unrecognized files virtually or with user-defined restrictions contained within sandbox (right-click "Run in Comodo sandbox.") So, in essence, CIS sandbox is multi-functional in that different sandbox policies are applied to any Unrecognized file - dependent upon how the file is executed. In other words, a CIS user can define two sets of rules for the sandbox. The first being for the auto-sandbox and the other for Right-Click "Run in Comodo sandbox"; executed from the desktop or from within a browser = Block by auto-sandbox, while Right-Click "Run in Comodo sandbox" = will run virtually or Limited, Untrusted, etc dependent upon user settings for the sandbox. This CIS feature isn't explained in the CIS manual... and most users wouldn't know that it exists unless they stumbled upon it... On top of that, the modules are designed to block any Unrecognized files in cascade fashion should any single module fail: auto-sandbox > HIPS > firewall. Comodo performed quite a feat of software engineering on that one... perfect trifecta = anti-executable + virtualization + outbound network notifications or Block ... and it is the primary reason I use CIS; everything to lock-down system is included in one complete package [/QUOTE]
Insert quotes…
Verification
Post reply
Top