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
FortiClient vs Scriptors on Windows 10
Message
<blockquote data-quote="hjlbx" data-source="post: 427917"><p>I have been hunting and reporting CIS bugs for quite some time.</p><p></p><p>So from the perspective of experience, let's address the issue of Comodo bugs on a factual, well-measured basis - and some food for thought:</p><p></p><ul> <li data-xf-list-type="ul">A significant portion of CIS bugs, reported or otherwise, are not really bugs. User's that don't fully understand how CIS works frequently interpret unclear and unexpected behavior as a bug. Huge problem in that user frustration gets widely "converted" into CIS bugs. Simple formula: User confusion = bug !</li> </ul><p> The issue of why CIS is difficult to comprehend for so many is an entirely different issue best not covered here... needless to say anyone who delves into the depths of CIS settings is going to be stumped sooner rather than later. Even some seasoned IT professionals balk and begin to sputter when confronted with the CIS Protected COM and Firewall MAC interfaces.</p><p></p><ul> <li data-xf-list-type="ul">In my experience, one need not go very deep into CIS to discover actual bugs. A case in point are the antivirus alerts, scanner and virtual kiosk (not advocating the use of those modules, just using them to make a point - so please, let's steer clear of the CIS AV\HIPS debate). Anyhow, the more modules you use, the more likely one is to find a bug. This is why CFW is less buggy than CIS.</li> </ul><p></p><ul> <li data-xf-list-type="ul">Despite whatever bugs I have discovered, CIS has always provided a means to create a work-around rule and the ability to disable alerts. Alternatively, <em><strong>there is always the option to not use or avoid use of the offending CIS feature or module</strong></em>. I can never understand that some see this as utterly ludicrous security soft heresy. To me, those that adhere to this perspective are way too OCD and have no real, practical understanding of the entire issue. In any case... pardon the micro-rant... I have found no bugs since v 7 that gravely compromise system security.</li> </ul><p></p><ul> <li data-xf-list-type="ul">A significant portion of CIS bugs are system specific; there is a wide variation in CIS behavior dependent upon whether it is installed on an AMD or Intel system, the system's processor type, and installed softs - like OEM crapware and custom drivers.</li> </ul><p></p><ul> <li data-xf-list-type="ul">If one looks at some of the vulnerabilities (which technically are not bugs) reported on the Comodo forum, a significant portion - while actual vulnerabilities - are so arcane and difficult to exploit that no one in their right mind would bother trying to actually exploit them. So it is no surprise that Comodo engineering groups never fix them as it is pointless other than to satisfy some users' OCD security soft fantasies.</li> </ul><p>(A criminal that sets out to exploit CIS vulnerabilities isn't going to be financially successful - not one bit).</p><p></p><p>* * * * *</p><p></p><p>Bottom line...</p><p></p><p>[USER=7463]@cruelsister[/USER] is correct regarding CIS and scriptors.</p><p></p><p>The only viable option is a combination of anti-executable, virtualization and firewall.</p><p></p><p>One can cobble together a highly effective config using separate apps or just use an app that fully integrates AE-V-FW. The only one I have been able to find that works is CIS...</p></blockquote><p></p>
[QUOTE="hjlbx, post: 427917"] I have been hunting and reporting CIS bugs for quite some time. So from the perspective of experience, let's address the issue of Comodo bugs on a factual, well-measured basis - and some food for thought: [LIST] [*]A significant portion of CIS bugs, reported or otherwise, are not really bugs. User's that don't fully understand how CIS works frequently interpret unclear and unexpected behavior as a bug. Huge problem in that user frustration gets widely "converted" into CIS bugs. Simple formula: User confusion = bug ! [/LIST] The issue of why CIS is difficult to comprehend for so many is an entirely different issue best not covered here... needless to say anyone who delves into the depths of CIS settings is going to be stumped sooner rather than later. Even some seasoned IT professionals balk and begin to sputter when confronted with the CIS Protected COM and Firewall MAC interfaces. [LIST] [*]In my experience, one need not go very deep into CIS to discover actual bugs. A case in point are the antivirus alerts, scanner and virtual kiosk (not advocating the use of those modules, just using them to make a point - so please, let's steer clear of the CIS AV\HIPS debate). Anyhow, the more modules you use, the more likely one is to find a bug. This is why CFW is less buggy than CIS. [/LIST] [LIST] [*]Despite whatever bugs I have discovered, CIS has always provided a means to create a work-around rule and the ability to disable alerts. Alternatively, [I][B]there is always the option to not use or avoid use of the offending CIS feature or module[/B][/I]. I can never understand that some see this as utterly ludicrous security soft heresy. To me, those that adhere to this perspective are way too OCD and have no real, practical understanding of the entire issue. In any case... pardon the micro-rant... I have found no bugs since v 7 that gravely compromise system security. [/LIST] [LIST] [*]A significant portion of CIS bugs are system specific; there is a wide variation in CIS behavior dependent upon whether it is installed on an AMD or Intel system, the system's processor type, and installed softs - like OEM crapware and custom drivers. [/LIST] [LIST] [*]If one looks at some of the vulnerabilities (which technically are not bugs) reported on the Comodo forum, a significant portion - while actual vulnerabilities - are so arcane and difficult to exploit that no one in their right mind would bother trying to actually exploit them. So it is no surprise that Comodo engineering groups never fix them as it is pointless other than to satisfy some users' OCD security soft fantasies. [/LIST] (A criminal that sets out to exploit CIS vulnerabilities isn't going to be financially successful - not one bit). * * * * * Bottom line... [USER=7463]@cruelsister[/USER] is correct regarding CIS and scriptors. The only viable option is a combination of anti-executable, virtualization and firewall. One can cobble together a highly effective config using separate apps or just use an app that fully integrates AE-V-FW. The only one I have been able to find that works is CIS... [/QUOTE]
Insert quotes…
Verification
Post reply
Top