Welcome Guest. | Log In| Register | Membership Benefits
Dark Reading's hacked-off Weblog

Topics:   Hacked Off
  • Email this page E-mail this page
  • |  Print Print this page
  • |   Bookmark and Share

Lessons From Fighting Cybercrime

The history of anti-spam teaches us about half-baked ideas and how people succeeded or failed to implement them. The analogy of evolution, while limited, demonstrates how reactionary solutions can achieve strategic goals before they are made obsolete by countermeasures.

May 17, 2009 | 03:51 AM | 

By Gadi Evron
Dark Reading
The history of anti-spam teaches us about half-baked ideas and how people succeeded or failed to implement them. The analogy of evolution, while limited, demonstrates how reactionary solutions can achieve strategic goals before they are made obsolete by countermeasures.How do you herd cats? In a series of blogs starting today, I'll explore the history of fighting cybercrime and how and why certain solutions worked while others failed, how we can recreate success, and what lessons we can distill to build business solutions, affect change in communities -- and even fight terrorism.

One of many failed spam-fighting ideas is the idea of charging for email (raising the cost of sending email): spammers would have supposedly made less money, making it less beneficial for them to spam.

Asking for money (or postage stamps) with email to combat spam is doomed to fail--the spammers already use technology that avoids such measures. Even if they didn't, implementation doesn't seem likely.

Spam is sent by botnets (armies of compromised computers controlled by criminals). These would adapt and use stamps already bought by users who own the computers. It's an example of evolution teaching criminals how to be better at crime.

Thus, by fighting criminals and forcing them to learn, we make our situation worse. I had the honor of being the first to introduce this argument into modern security discussion, which was later elaborated upon by respected colleague Paul Vixie. Paul introduced the idea that as cybercrime results from financial incentive, so must the solution be economic in nature.

A permanent solution to cybercrime, economic or otherwise, doesn't exist yet; the nature of combating it is mostly reactive.

The criminals have a direct economic incentive to retain their ROI and reach their quarterly goals. Therefore, reactive solutions are quickly defeated, again and again, much like we have seen in terrorism and the drug wars. On the other hand, in fighting cybercrime, knee-jerk reactions are often the only viable option we have. At the very least we can strategize for a desired outcome.

When ISPs started blocking port 25/TCP outgoing (SMTP) and limiting it to their servers alone, spammers changed their tactics. Previously, bots sent email directly to any server in the world. Now, they had to go through the ISP's own mail servers. This caused spammers to develop new bots that used real user email accounts -- and thus the ISP's servers -- to send out spam.

While it wasn't popular at first, I was a proponent of blocking port 25, introducing it and advocating for it whenever and wherever I could. (To my knowledge it was a colleague, Dave Rand, who first introduced the concept).

The strategy had some tradeoffs. Mainly, ISPs had to invest resources upgrading their infrastructure to cope with the extra email. The positive results outweigh the negative, however: service providers can now easily pinpoint who offenders are, and automate the abuse-handling process. Not to mention save bandwidth.

Criminals were forced to evolve in a desirable direction, which is a victory on its own. Evolution in capabilities occurs to circumvent security measures. By limiting the spammers' options they evolved to a technological battleground where we have more control.

In my next blog post, I'll discuss why some spam solutions get implemented and others never get past the drawing board, and the role of user psychology here.

Follow Gadi Evron on Twitter: http://twitter.com/gadievron

Gadi Evron is an independent security strategist based in Israel. 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