Rohdekill, on 28 August 2012 - 11:53, said:
Then it provides no benefit over its competition. My AV checks for updates every hour. If within that hour I get hit with something new which totally blocks my AV from grabbing an update (which may or may not resolve the issue) then I am hosed.
If I run the service you suggest and I get hit within the hour, I can't reach the cloud to grab the update so off-line mode can't fix it. Hosed either way.
Hi Rohdekill,
Let me explain how our offline protection works.
When a new file is introduced to a PC we try to obtain a classification from the Webroot Intelligence Network (cloud). If the connection cannot be established because the user is offline, the file is assumed to be 'unknown'.
Files that have an 'unknown' classification will be executed in a 'Monitor' state. Even though it's running on the endpoint, we're carefully watching the file to make sure it can't make any malicious modifications to your PC. Also, every single change that the file
does make to your PC while in the Monitor state will be recorded in a local change-journal database.
Once the connection to the internet has been established, and we send down a 'bad' classification to the PC, all of those changes are perfectly reversed. There is a lot of protection built into the product to protect and verify the integrity of the internet connection, including LSP chain protection and kernel-mode connectivity.
So in summary your endpoint is benefiting from a degree of generic protection to stop your PC being 'trashed' and you're also getting a perfect clean-up routine.
It could be argued that we're no better/worse than the competition at protecting your PC when it's offline, but the benefits when conneced to the internet are clear.
Let me know if you have any other concerns on this topic.
Thanks,
Will
Rohdekill, on 28 August 2012 - 11:53, said:
If I run the service you suggest and I get hit within the hour, I can't reach the cloud to grab the update so off-line mode can't fix it. Hosed either way.
Edit: Take a look at the last part of the video and you'll see the journaling and rollback in action. In the unlikely scenario that the situation you describe occurs, the user will be able to manually 'block' the infected file, and every single change it made to the system will be perfectly reversed. This requires no active connection to the internet.