Endpoint
10/2/2009
01:49 PM
Connect Directly
RSS
E-Mail
50%
50%

Tech Insight: Beating Bots And Scareware On A Budget

Free tools, like the Squid Web caching proxy, can add extra layers of protection for your users

Cybercriminals will do nearly anything to make a buck, using social engineering lures like natural disasters or the recent injury of University of Florida football player Tim Tebow to distribute malware and infect computer systems. And the more the better.

The reality is that security vendors cannot keep up with the threat. Both corporate and consumer users can easily fall victim to malware and bot infections because these social engineering techniques are so good at duping them. And corporate systems, meanwhile, are being targeted by smaller and stealthier botnets, ranging from just a few hosts to a few hundred, affecting up to 9 percent of computers in an enterprise, according to Damballa.

Keeping bots and scareware from gaining a foothold in your enterprise network requires a layered approach, or defense in-depth. It also requires an active effort by security professionals to ensure their protection measures are updated at all times, often supplemented by bleeding-edge research and budget-friendly open-source tools. Leveraging open-source tools, such as the Squid Web caching proxy, with layered access control, content filtering, and security intelligence, can help provide an edge in the battle against bots and scareware.

The two major sources of external threats to enterprise networks are e-mail and the Web. Because of the ridiculous volumes of spam, nearly every enterprise has something in place to filter their e-mail, but not so for the Web. Why aren't companies rallying to stomp out Web-based malware like they did with email spam?

Until that revolution happens, we are left with varying offerings for Web content filtering using technology that has been around and actively used for years. The Squid Web caching proxy is probably the best known and most widely used free, open-source Web proxy available. What's ironic is that although Squid is free, many enterprises have paid for it and are using it right now -- not realizing it's embedded in their commercial Web filtering appliances and used by popular Web sites like Flickr.

Squid can perform content caching, access control, authorization, and logging. Many add-ons have been developed to extend Squid's functionality to include security features like antivirus scanning. It's the flexibility of Squid that allows it to layer those controls into an effective Web filter to block malicious Web sites and potentially harmful executables.

The most basic blocking functionality is based on file extension, IP address, and URL. How many of your users need to be downloading executable files? That number is likely to be few to none, so using Squid makes it easy to block files ending in .exe, .com, .bat, .msi, etc. There are ways around this method, but it is a basic filtering technique within Squid that can stop most of the scareware downloads we've seen and analyzed today.

Taking access control to the next level, IP addresses and URLs (or just domain names) known to be hosting malware can be easily blocked. There are numerous resources that provide security intelligence on malicious sites. DNS-BH provides a malware-domain blacklist based on information from several leading malware researchers and groups. A new update to the DNS-BH released this week included more than 130 new domains hosting scareware and rogue antivirus, which seems small considering its current listing includes more than 16,000 malware-related domains.

Antivirus is the last layer in Squid for catching the malware that gets by the other layers. Add-ons like Viralator, or passing the traffic off to another proxy like HTTP antivirus proxy HAVP, allow usage of antivirus software like ClamAV, F-Prot, AVG, Kaspersky, Sophos, Trend Micro, Nod32, and McAfee. The recent reports from NSS Labs on performance of antivirus solutions indicate that Trend Micro and Kaspersky Labs anti-malware tools would be great choices.

When all of those layers of protection are combined, a Squid-based Web proxy is a powerful solution for preventing bots and scareware from getting into your network through Web-based channels. It's important to remember that the security intelligence feeding those blacklists changes often, so security teams need to stay on top of it and automate the update mechanisms.

But Web filtering is just one layer of defense. It's based on blacklisting mechanisms, which are not foolproof. You also such need technologies as intrusion prevention systems, proper security practices (like principle of least-privilege), and application whitelisting on desktops.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.