Reply to thread

Message

<blockquote data-quote="cruelsister" data-source="post: 952025" data-attributes="member: 7463">D- Although I have found WVSX to be a remarkable product, those additional security modalities (FW, HIPS) found in version 3 may not yield significant benefit when CF(cruel) is also being used.Although I haven&#039;t done anything extensive with the new version, what I have done did not result in any incompatibilities between WV and CF. On this topic, I should report that on my production system (and a VM clone of it for fun) I have had installed WVSX 2.73 (default), Cruel CF, and WD (default) for the last 6 months. Essentially this results in 3 dumb (signature based) detection routines (VirusScope, WVSX, WD), one smart (AI) modality of WiseVector, and Comodo auto-Containment to catch them if they fall. With the addition of excellent Outbound protection of CF things are fairly well covered.I have found no issues with the dumb detection routines as for in the wild malware there were samples caught by one and allowed by others but overall leading to additive protection. But the AI component of WV still impresses, and along with Comodo&#039;s auto-sandbox true zero day malware really don&#039;t have much of a chance. Last week I coded up&nbsp; a ransomware file loosely based on Ryuk (true zero-day) and although undetected by the dumb components, the WV AI after less than a minutes &quot;thought&quot; came back with a detection (potential.ransomware.A), detected and cleaned up my ransomware nor and some trivia dropped in AppData/Local). Poor malware didn&#039;t even make it to the sandbox.(and regarding WF- seems not to matter if it is enabled or disabled as it neither helps nor detracts)M</blockquote>

[QUOTE="cruelsister, post: 952025, member: 7463"] D- Although I have found WVSX to be a remarkable product, those additional security modalities (FW, HIPS) found in version 3 may not yield significant benefit when CF(cruel) is also being used. Although I haven't done anything extensive with the new version, what I have done did not result in any incompatibilities between WV and CF. On this topic, I should report that on my production system (and a VM clone of it for fun) I have had installed WVSX 2.73 (default), Cruel CF, and WD (default) for the last 6 months. Essentially this results in 3 dumb (signature based) detection routines (VirusScope, WVSX, WD), one smart (AI) modality of WiseVector, and Comodo auto-Containment to catch them if they fall. With the addition of excellent Outbound protection of CF things are fairly well covered. I have found no issues with the dumb detection routines as for in the wild malware there were samples caught by one and allowed by others but overall leading to additive protection. But the AI component of WV still impresses, and along with Comodo's auto-sandbox true zero day malware really don't have much of a chance. Last week I coded up a ransomware file loosely based on Ryuk (true zero-day) and although undetected by the dumb components, the WV AI after less than a minutes "thought" came back with a detection (potential.ransomware.A), detected and cleaned up my ransomware nor and some trivia dropped in AppData/Local). Poor malware didn't even make it to the sandbox. (and regarding WF- seems not to matter if it is enabled or disabled as it neither helps nor detracts) M [/QUOTE]

Verification