• 0

What happens if Webroot SecureAnywhere misses a virus?


Question



In this video Webroot purposely infect a machine running Webroot SecureAnywhere. They even disable the behaviour shield to replicate what would happen if a threat was missed and it executed on your PC.

We estimate there to be somewhere in the region of 50,000 new strains of malware every single day, so it's frankly impossible for the legacy signature-based approaches to keep up with the vast volume of threats.

Webroot SecureAnywhere adopts a new cloud-driven approach, ensuring that users always have access the the latest security "definitions" without needing to download any updates. This, coupled with a 700Kb agent, ensures optimal performance and enhanced security.

Webroot also recognise that the ever-rising volume of malware means that they'll miss threats, too. While they do have industry leading detection rates (See: http://www.av-test.o...er/mayjun-2012/) they have introduced unique protection against information-stealing malware, so even if they do miss something, the data that you really care about cannot be tampered with.

Recommended Posts

  • 0

"Webroot SecureAnywhere adopts a new cloud-driven approach"

That's great and all...until malware kills your internet connection.

Also, is it just me or does the "article" read like an ad?

  • 0

Neowin now sponsors Info-mercials...

Funny how they completely avoid discussing how this would work with an infection which blocks/alters your internet connection so you can't access the cloud.

  • Like 3
  • 0

I guess it kinda is an ad. The video and content came from Webroot themselves. Doesn't mean it can't stir up some interesting debate on a new approach to AV. When was the last time an AV vendor purposely infected a PC running their software....?

There is, of course, offline protection. Some of which is highlighted in the video.

  • 0

There is, of course, offline protection. Some of which is highlighted in the video.

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.

  • 0

I like the idea of a constantly-updated "cloud" definition-base, but it would have to work as a hybrid system that also periodically downloads it locally. That way you generally get the very latest definitions, but in the event of malware that kills your internet connection, you still have a relatively-recent offline copy it can use to scan the system. I'm sure that's what er0n mentioned, but I am at work atm and can't view the video, so I can't be sure of how it works.

So then, Rohdekill, the advantage would be that in most cases you have a very up-to-date solution. Not sure which AV you use, but most people's don't update that frequently, so it may provide some benefit for an "average" user.

  • 0

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

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.

  • 0
I like the idea of a constantly-updated "cloud" definition-base, but it would have to work as a hybrid system that also periodically downloads it locally. That way you generally get the very latest definitions, but in the event of malware that kills your internet connection, you still have a relatively-recent offline copy it can use to scan the system. I'm sure that's what er0n mentioned, but I am at work atm and can't view the video, so I can't be sure of how it works. So then, Rohdekill, the advantage would be that in most cases you have a very up-to-date solution. Not sure which AV you use, but most people's don't update that frequently, so it may provide some benefit for an "average" user.

Honestly, do we need AV that is updated every second? Unless you're a high value target (e.g.: government, banking, super rich...) are you really at risk of being hit with 0-day attacks?

Even if the 0-day threat is real for average users, which I don't think it is, the frequency of the definition downloads are less important than the total time it takes the AV vendor to discover, classify, and add a definition for it... The AV venders don't publish those numbers though...

  • 0

Honestly, do we need AV that is updated every second? Unless you're a high value target (e.g.: government, banking, super rich...) are you really at risk of being hit with 0-day attacks?

Even if the 0-day threat is real for average users, which I don't think it is, the frequency of the definition downloads are less important than the total time it takes the AV vendor to discover, classify, and add a definition for it... The AV venders don't publish those numbers though...

I think most users will be absolutely fine, and it really depends how you use the internet, how highly you value your sensitive data, and how highly you value your time. If you don't do online banking or store your resume/CV on your PC, then you'll probably be fine with one of the legacy signature-based solutions.

Your last comment is exactly why we have decided to take the approach that we have. There are approximately 7 million users currently using Webroot SecureAnywhere today - whenever a new file is observed for the first time on one of our customer's PCs, it's executed on the PC in a isolated sandbox environment where we'll capture the intial behaviour of the file. We'll then make a determination as to whether the behaviour is good or bad - if it's bad, all of our 7 million customers are instantly protected without having to wait for us to publish a signature or get them to download anything.

If the behaviour doesn't appear to be bad, the file is executed on the endpoint but the user/PC is still protected using the methods shown in the video.

The window of exposure to a new threat (1 in ~50,000 per day) is dramatically reduced using this model.

FWIW, 0-day threats are not necessarily targetted attacks. They can spread through software vulnerabilities and infected legitimate web-sites.

P.S. I have no idea whether i'm actually allowed to be posting on this thread. I hope I'm not breaking any rules.

  • Like 2
  • 0

I think most users will be absolutely fine, and it really depends how you use the internet, how highly you value your sensitive data, and how highly you value your time. If you don't do online banking or store your resume/CV on your PC, then you'll probably be fine with one of the legacy signature-based solutions.

Your last comment is exactly why we have decided to take the approach that we have. There are approximately 7 million users currently using Webroot SecureAnywhere today - whenever a new file is observed for the first time on one of our customer's PCs, it's executed on the PC in a isolated sandbox environment where we'll capture the intial behaviour of the file. We'll then make a determination as to whether the behaviour is good or bad - if it's bad, all of our 7 million customers are instantly protected without having to wait for us to publish a signature or get them to download anything.

If the behaviour doesn't appear to be bad, the file is executed on the endpoint but the user/PC is still protected using the methods shown in the video.

The window of exposure to a new threat (1 in ~50,000 per day) is dramatically reduced using this model.

FWIW, 0-day threats are not necessarily targetted attacks. They can spread through software vulnerabilities and infected legitimate web-sites.

P.S. I have no idea whether i'm actually allowed to be posting on this thread. I hope I'm not breaking any rules.

How is this dynamic scanning any different than heuristic engines that have been built into AV scanners for the last decade? Unless you're saying that every file a user opens is transmitted to Webroot for additional analysis?

  • 0

How is this dynamic scanning any different than heuristic engines that have been built into AV scanners for the last decade? Unless you're saying that every file a user opens is transmitted to Webroot for additional analysis?

Hi Frazell,

Traditional AV products typically utilize basic local heuristics which are renowned for generating false positives and being largely ineffective.

Webroot SecureAnywhere sends the behaviour of the file, along with its meta data to the Webroot Intelligence Network (cloud) where the behaviour is compared to tens of thousands of advanced behavioural rules. In addition to the behaviour, Webroot is able to make a more accurate 'estimation' by considering the age (how long it's been known to the Webroot community) and popularity (how many users in the Webroot community are using it). Some other solutions have also started to adopt cloud reputation lookups.

The key thing here is that while our 'heuristics' should be more effective, we recognise that the bag guys are getting smarter, so we don't rely on them. We've implemented generic protection against information-stealing malware and implemented a unique feature for perfect remediation - you can see these features in action in the video in the OP.

  • 0

Webroot_Will,

Why doesn't the product have any kind of email scanning, and what about webpage scanning (ex. sites hacked to run malicous code in an iframe or script)...I also noticed it does not actively scan downloads like NOD32 does, including inside ZIP files.

  • 0

Hi Mr. Black,

Email Scanning isn't a focus for us right now. We tend to find that most home users use Webmail with AV and Anti-Spam built-in, and most businesses use a dedicated email security solution. Besides, if a user were to receive a virus by emal and execute it, we'd catch it at that point, so from a security stand-point the user/PC is still secured. We have a 'Web Threat Shield' designed to prevent the execution of malicious content from web-sites and to prevent software vulnerabilities from being exploited. Even if we 'miss' one of these attacks, something has to execute on the PC in some way for malicious modifications to take place, and we're sitting there at the kernel layer watching every single operating system activity.

From a security stand-point, scanning benign files like Zip files in real-time is unneccessary; a Zip file in itself cannot execute and harm the PC in anyway. As soon as the user extracts the contents or if the Zip file changes in some way so that it could potentially pose a threat, Webroot will step in and protect the PC/user. There are pros and cons to this approach, but our customers really appreciate the performance boost they receive without compromising on security.

  • 0

When was the last time an AV vendor purposely infected a PC running their software....?

Hopefully every single time they test their definitions and heuristics...otherwise without testing it's pointless.

That would be like asking...when was the last time a chef intentionally tasted their own food to make sure that it was good...

You want to be a good chef? You taste your own food.

You want to make sure your AV product works? You infect a system and see what happens.

  • Like 3
  • 0

Hopefully every single time they test their definitions and heuristics...otherwise without testing it's pointless.

That would be like asking...when was the last time a chef intentionally tasted their own food to make sure that it was good...

You want to be a good chef? You taste your own food.

You want to make sure your AV product works? You infect a system and see what happens.

Hi Shane,

The point is that the other vendors would never publish a video showing what happens if they miss a threat. Why not? Because the PC would be trashed and the customer's data would be stolen.

  • 0

Hi Shane,

The point is that the other vendors would never publish a video showing what happens if they miss a threat. Why not? Because the PC would be trashed and the customer's data would be stolen.

Indeed, and the logic behind that is usually these types of attack go after the antivirus/antimalware program first, and disable all of the settings like this and often kill the process itself and prevent it from doing its job.

Then it deploys the keyloggers & various other nasty bits, and then it still steals the data.

So the video only shows what happens IF the virus/malware doesn't target the AV product itself and it can keep itself up and running with its policies in place.

Any 'good' virus/malware these days takes out the security first before doing the dirty work. So what keeps them from attacking the processes that you use and just proceeding?

I ask because with claims of this kind there needs to be some pretty heavy duty assurances in place to prevent that scenario. ;)

  • 0

Indeed, and the logic behind that is usually these types of attack go after the antivirus/antimalware program first, and disable all of the settings like this and often kill the process itself and prevent it from doing its job.

Then it deploys the keyloggers & various other nasty bits, and then it still steals the data.

So the video only shows what happens IF the virus/malware doesn't target the AV product itself and it can keep itself up and running with its policies in place.

Any 'good' virus/malware these days takes out the security first before doing the dirty work. So what keeps them from attacking the processes that you use and just proceeding?

I ask because with claims of this kind there needs to be some pretty heavy duty assurances in place to prevent that scenario. ;)

Hi Shane,

You make a great point, and it's one we've thought long and hard about.

One of the key benefits of being so lightweight (the entire program is <700kb) is that Webroot SecureAnywhere is able to sit at the kernel-layer watching every single operating system event. After a few minutes of being installed on a typical machine, we've normally observed millions of events. If the traditional, heavy-weight solutions tried to do this, the machine would be so slow it would be unusable. This allows us to have exceptional self-protection.

As you will have seen in the video, the first thing we do prior to allowing a file to execute is obtain a classification for the file (Good, bad or unknown). We can assume that a brand new 0-hour virus is unknown, so it will be executed in the monitor state shown in the video. This already limits the malicious modifications the file can make to the system, and it certainly means that we won't let the file get anywhere near terminating the Webroot agent.

We've yet to see a virus which can circumvent this approach. Will it happen in the future? No doubt about it, but I'd like to think we're already a step-ahead of the game.

We can prove that we have an industry leading detection rate (most vendors do!). The difference is we come with a plan B.

with 0day and 0hr infections, no antimalware software can protect you, cloud or traditional. Good luck fighting the battle you already lost.

Hi sc302,

Did you watch the video? Keen to hear your thoughts on why you think this protection model can't protect you.

  • 0

Didn't watch the video. I really don't need to.

How is it that you think you can predict the future or the unknown?

All I can suggest is that if you watch the video, all will become clear.

The key fundamental here is that the Webroot Intelligence Network doesn't just include classifications for known-bad files, it also includes classifications for known-good files. The files inbetween are considered to be unknown, and you get all of the protection benefits highlighted in the video.

  • 0

while your newest software has gotten significantly better reviews than your previous rendition of your cloud based software, I will eventually test your software when I have time or have an infection that I need to dissect to see if it lives up to the reviews. I am sorry I don't believe in videos made by the manufacturer they are a bit one sided and always tout their services and make it seem that theirs is better than everyone elses. I am even a bit skepticle on reviews until it has been proven by myself to work.

  • 0

while your newest software has gotten significantly better reviews than your previous rendition of your cloud based software, I will eventually test your software when I have time or have an infection that I need to dissect to see if it lives up to the reviews. I am sorry I don't believe in videos made by the manufacturer they are a bit one sided and always tout their services and make it seem that theirs is better than everyone elses. I am even a bit skepticle on reviews until it has been proven by myself to work.

Hi sc302,

I can't argue with that - I think you're right to be sceptical, and I'm exactly the same.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
    • Tor Browser 15.0.17 by Razvan Serea Protect your privacy. Defend yourself against network surveillance and traffic analysis. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody from watching your Internet connection and learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked. The Tor Browser Bundle lets you use Tor on Windows, Mac OS X, or Linux without needing to install any software. It can run off a USB flash drive, comes with a pre-configured web browser to protect your anonymity, and is self-contained. Tor Browser 15.0.17 changelog: All Platforms Updated Tor to 0.4.9.11 Updated NoScript to 13.6.25.1984 Build System / All Platforms Bug tor-browser-build#41821: Update gpg subkeys for boklm Bug tor-browser-build#41827: Update morgan's keychain with renewed key Download: Tor Browser (64-bit) | Tor Browser (32-bit) | 109.0 MB (Open Source) View: Tor Browser Website | Other Operating Systems Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      530
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      148
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!