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
VoodooShield
VoodooShield CyberLock 7.0
Message
<blockquote data-quote="danb" data-source="post: 1081977" data-attributes="member: 62850"><p>You must have been reading my mind or have connections I do not know about <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite110" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" />.</p><p></p><p>Anyway, prior to 7.72, there was a dedicated script list that contained all of the common and many not so common file types. But keep in mind, CyberLock utilizes other modules, such as its anti-exploit and command line modules that are capable of blocking all kinds of things. So there was not a list that was written in stone, and even with 2.72 there still is not a list written in stone.</p><p></p><p>Starting with 7.72, in addition to the dedicated script list, we also have a dedicated BlockedFileType list. The BlockedFileType list in 7.72 is a quick and dirty list that needs to be refined a little. I need to add and remove types, and maybe move a few from the BlockedFileType to the Script list. There is also a dedicated Executable binary list.</p><p></p><p><u>The entire goal is to block each individual attack vector / file type as optimally as possible, and ultimately we will be able to refine the user prompts so they are dead on and super useful to the end user</u>. We actually get a lot of compliments on our user prompt, but I am certain we can do even better.</p><p></p><p>Here is an one example of what I mean by an optimal block for a specific file type…</p><p></p><p>Just for the fun of it, I included .rtf in the BlockedFileType list for 7.72. The .rtf file type is best suited to be blocked by our Anti-Exploit module, and that way CyberLock only has to block a specific file if it is being utilized in an exploit. I have been reading a lot about .rtf file malware, so if we wanted to be even safer, we could keep it on the BlockedFileType, and that way each .rtf file has to be manually allowed. Sure, it might be slightly safer to block it this way, but it might interrupt end-users workflow too much.</p><p></p><p>So essentially, we need to take hard look at each file type and decide which module in CyberLock would be optimal to perform the block. Cybersecurity is all about striking the right balance between robust security and convenience, and each attack vector / file type is a little different, and should be handled optimally.</p></blockquote><p></p>
[QUOTE="danb, post: 1081977, member: 62850"] You must have been reading my mind or have connections I do not know about ;). Anyway, prior to 7.72, there was a dedicated script list that contained all of the common and many not so common file types. But keep in mind, CyberLock utilizes other modules, such as its anti-exploit and command line modules that are capable of blocking all kinds of things. So there was not a list that was written in stone, and even with 2.72 there still is not a list written in stone. Starting with 7.72, in addition to the dedicated script list, we also have a dedicated BlockedFileType list. The BlockedFileType list in 7.72 is a quick and dirty list that needs to be refined a little. I need to add and remove types, and maybe move a few from the BlockedFileType to the Script list. There is also a dedicated Executable binary list. [U]The entire goal is to block each individual attack vector / file type as optimally as possible, and ultimately we will be able to refine the user prompts so they are dead on and super useful to the end user[/U]. We actually get a lot of compliments on our user prompt, but I am certain we can do even better. Here is an one example of what I mean by an optimal block for a specific file type… Just for the fun of it, I included .rtf in the BlockedFileType list for 7.72. The .rtf file type is best suited to be blocked by our Anti-Exploit module, and that way CyberLock only has to block a specific file if it is being utilized in an exploit. I have been reading a lot about .rtf file malware, so if we wanted to be even safer, we could keep it on the BlockedFileType, and that way each .rtf file has to be manually allowed. Sure, it might be slightly safer to block it this way, but it might interrupt end-users workflow too much. So essentially, we need to take hard look at each file type and decide which module in CyberLock would be optimal to perform the block. Cybersecurity is all about striking the right balance between robust security and convenience, and each attack vector / file type is a little different, and should be handled optimally. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
