Monday, February 21, 2011

Realtime protection with ClamAV on Windows

One of the major features in Immunet 3.0 powered by ClamAV is the integration of the full ClamAV engine for "offline protection, advanced archive and unpacking support, and custom signature creation". What does that mean though?

First of all it means that when you are not connected to the cloud then you are protected by the locally installed ClamAV engine. What may not be clear from that feature description is that ClamAV is also used when you are online, and it is used for realtime protection (on-access scanning) too!

Is the ClamAV engine enabled by default in Immunet 3.0?
That depends on how you install it, but you can always change the settings later. In fact it is easy to test if the local ClamAV engine is enabled and working, as I'll show you next:

Download the Immunet 3.0 powered by ClamAV installer from here, and run it.
Make sure you select Cloud + ClamAV as shown here, and then proceed with the installation:

Once installed you can check whether ClamAV is enabled (and enable if not):
Then check that archive and packed file scanning is enabled:
Finally click on "Update Now" to make sure your antivirus database is up-to-date:

To test the local ClamAV engine you can use the following test file, (which is completely safe, it is not even executable):
Open notepad, then Copy and Paste this text exactly as shown here:
$CEliacmaTrESTuScikgsn$FREE-TEST-SIGNATURE$EEEEE$

Once you save the file (lets call it clam.txt for example) you should get a popup from Immunet showing that it has detected Clam.ClamAV-Test-Signature:
You can open the folder you tried to save the file in, and check that it is really gone.

Now you should be confident that you are protected by ClamAV's engine in "Immunet 3.0 powered by ClamAV".

How do you know which engine detected the file?
  • if the virusname starts with "W32." then it is a cloud detection
  • if it starts with "W32.SPERO.", it is a cloud detection from the SPERO heuristic engin
  • if it starts with "W32.ETHOS.", it is a cloud detection from the ETHOS heuristic engine
  • if it starts with "W32.Clam.", it is a file that was detected by ClamAV on the cloud
  • if it starts with "Clam.", it is a local ClamAV detection
  • if it starts with "Clam." and ends with ".UNOFFICIAL", then it is your custom signature
If you are interested in some of the technical details of how the ClamAV engine
works together with the cloud read on.

A scan can be triggered by:
  • on-access, i.e. realtime protection: when you launch an application, copy or move files
  • on-demand, via the "Scan Now" button
  • scheduled scan, which can be configured in "Scan Settings", "Add New Scheduled Scan
Once a scan is triggered the following happens:
  • scans the file using the cloud (by sending the file's fingerprints), if you are online
  • if the ClamAV engine is enabled it starts scanning the file, as usual:
  • using its (official or custom) signatures database
  • scanning files inside archives (if enabled in Settings)
  • scanning inside packed executables (if enabled in Settings)
  • each of these inner files (inside archives, packed executables) is
  • scanned using the cloud as well
  • ClamAV checks its local whitelist when it detects a virus
  • as soon as either engine finds a malware, scanning is stopped
  • the cloud also checks its whitelist for both its own detections and ClamAV's detections
For a file to be considered malicious it is enough that just one engine considers it as such. For it to be considered clean both must consider it clean.

If a malware is detected the file is quarantined, and the malicious process is blocked, prevented from execution.

So you see when you have both the cloud and ClamAV enabled it performs a more thorough scan than when scanning with both individually.

What if a file is detected by both the cloud and the local ClamAV engine?
Currently the detection from the cloud wins, but that may change as we work on optimizing the integration of the engine. Also just because you see a cloud detection, it doesn't mean the local engine wouldn't have detected it.

5 comments :

  1. Hi,

    Well, finally managed to have Immunet 3.0 Free + ClamAV working on my Windows XP Laptop... but this wasn't really straight forward !
    First download from the download page and default language setting (Fr). Chose Free version assuming it included ClamAV... Installed v2.0.17 and no ClamAV: #FAIL. Remove. Reboot.
    Second download from this page (downloaded filename different from the download page !?). Launched setup and kept my default langage (Fr): only Free and Plus install options ! Clicked back button, chosen English langage... and finally got the option to install Free+ClamAV !! #SUCCESS :-)
    Then had all the wanted configuration options and just had to update databases (which was so long to start that I actually cancelled it the first time I tried).
    After all this, I'm very happy to finally have a ClamAV based, on access Free AV on my W$ machine !
    Thank you very much for this peace of software wich I'm seriously considering to upgrade together with buying CloudMark DesktopOne...
    Thank yall again for this nice peace of software and keep on the good work.

    Bests
    Jeremie

    ReplyDelete
  2. Wow, sorry you had such a hard time. Normally, it's just a normal Windows install.

    ReplyDelete
  3. How to know the port number where the ClamAV is running???

    ReplyDelete
  4. "Immunet 3.0 Free + ClamAV " is not available, no matter how I download the link or start the install.

    How about a link to the installer itself, instead of a download manager app?

    ReplyDelete
  5. After deciding to install anyway it turns out that the the free version (once installed) can be configured to use ClamAV as one of the detection engines, and it seems to use the normal freshclam download procedures, etc. to keep up to date.

    So the detailed instructions are incorrect, but the general idea is correct.

    ReplyDelete