Welcome Guest. | Log In | Register | Membership Benefits
Dark Reading's evil-bytes Weblog

Topics:   Evil Bytes
  • |   Email this page E-mail
  • |  Print Print
  • |   Bookmark and Share

Enhancing Botnet Detection With Manpower

The average computer user (a.k.a. most of my family) doesn't have a fighting chance. I hate to say it, but the malware we're seeing on a daily basis makes this scary fact evermore true. There is absolutely no way that most home users are going to be able to protect themselves against modern malware like Zeus. Malware authors have become extremely good and proficient at what they do because it's making them money.

Feb 22, 2010 | 02:14 PM | 

By John H. Sawyer
Dark Reading
The average computer user (a.k.a. most of my family) doesn't have a fighting chance. I hate to say it, but the malware we're seeing on a daily basis makes this scary fact evermore true. There is absolutely no way that most home users are going to be able to protect themselves against modern malware like Zeus. Malware authors have become extremely good and proficient at what they do because it's making them money.I'm not saying there's no hope for anyone out there, just that the average user doesn't stand a chance. Our previous preachings on staying patched, keeping antivirus updated, and not running as administrator are still sound. I've seen plenty of fully patched, AV-protected machines running the latest AV get infected through an unpatched vulnerability or social engineering where the user was duped into installing the malware because it appeared to be AV, audio codecs, or a kitty screensaver.

Lately, there have been a few articles and blogs with tips on how to address the botnet threat, and I haven't seen one say you need to dedicate at least the equivalent of one full time person to the issue. The recommendations are good and include the typical things like user awareness, patching your software, and keeping your antivirus updated.

But where is the increase manpower? Nowhere to be seen. Why keep promoting Band-Aids when these companies could really use an extra person or three to aid in detection, remediation, and prevention by using the free intelligence that's out there? If you compare the cost of many security solutions to the salary of an additional staff member, then you'll probably find the find that the cost is about the same; however, I think you'll likely get more bang for the buck.

Wondering what do you do with the new person? Task them with keeping up-to-date on the latest malware--distribution methods, attack vectors, and purpose. Next, if you're not using Snort, consider implementing a Snort sensor to monitor your company's Internet connection. Then scrap all the rules that come with Snort and subscribe to the Emerging Threats mailing list and use their signatures. Have them pay special attention to alerts from the malware, virus, and current-events categories.

Once your new person has had a few weeks under their belt, they should start noticing trends in malware like Zeus, Koobface, Torpig, and similar bots. Suddenly, seemingly innocuous HTTP requests stand out because of discrepancies in the UserAgent, URL, or payload. They will start developing their own Snort signatures and finding new behaviors from the latest variants before they're disclosed publicly.

Maybe I'm a bit of a masochist in that I love doing those things above. I like detecting new attacks, finding an attacker's dump site, and submitting new samples to VirusTotal with zero detections. With the exception of a few security solutions I've seen, you're not getting that type of detection with off-the-shelf products.

Try it yourself. Give Snort and the Emerging Threats rules a shot. Take a look at BotHunter and monitor for your systems communicating with hosts in the Zeus Tracker. I'd be shocked if you don't turn up at least one Web-based attack within 24 hours and an infected host within a few days that your current security solution has missed

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark Reading.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS









  1. Cookies, Social Media And FireSheep
  2. SMB Guide To Credit Card Regulations, Part 2: The Low-Hanging Fruit
  3. HP And The Scary Corporate Fifth Column Concept
  4. Taking USB Attacks To The Next Level
  5. NoSQL: Not Much, Anyway
  1. Taking Cybersecurity Lessons To The Bank
  2. Researchers See Real-Time Phishing Jump
  3. 'BlackSheep' Sniffs Out Firesheep WiFi-Hacking
  4. Slideshow: Ten Free Security Monitoring Tools
  5. A Different Spin On Sleuthing Stuxnet
  6. M&A Activity Muddles Database Security
  1. Secure Managed Web Hosting Saves 960.gs from Malicious Hackers
  2. Access Governance as a Business Service: An Integrated Strategy for Automation with ITSM
  3. Business Driven Access Management and Governance: Simplifying the Delivery and Governance of Access Throughout
 
 


 
  Ars Technica
Boing Boing
Channel 9 Forums
CRN Blogs
Dr.Dobb's Portal: Blogs
Engadget
Gizmodo
GrokLaw
  Lifehacker
Schneier on Security
Slashdot
TechCrunch
Techdirt
Techmeme
Valleywag
 
  February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
  May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008