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

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

Anticipating Government Overreaction To An Actual Conficker Attack

Most governments tend to overreact, and the U.S. probably leads the pack. Fortunately, we survived Conficker on Wednesday, but what if it had resulted in a massive amount of damage? Would the government's response have done more damage than the worm?

Apr 01, 2009 | 06:54 PM | 

By Rob Enderle
Dark Reading
Most governments tend to overreact, and the U.S. probably leads the pack. Fortunately, we survived Conficker on Wednesday, but what if it had resulted in a massive amount of damage? Would the government's response have done more damage than the worm?The odds are likely because we have a history of inordinately responding to disasters and then regretting our response later.

While it isn't clear what actually happened with Conficker yet, perhaps enough people were prepared so that no disaster occurred. Or perhaps the worm's writer decided against doing a lot of damage. Or maybe we were just crying wolf. But what about next time? We operate in a world where cybersecurity is an afterthought in most states (in the U.S., it isn't even clear who is in charge of it at the moment), and where we have increasingly fast networks that could be, and are, used to move malware almost instantly to all parts of the globe. Since we dodged the bullet this time, the loud warnings become background noise and are increasingly ignored. This makes it likely that, eventually, we are going to have a massive virus-driven outage. It will likely be a Hurricane Katrina moment for a number of governments.

One thing we can expect is that the various political bodies will overreact. You could see governments banning Windows or all Microsoft products; you could see government PCs being locked down; you could see laws holding Internet service providers liable for allowing the virus to spread; you could see hackers broadly branded as terrorists and their legal punishments escalating; you could see government scanning of private networks increasing dramatically; and you could see a sharp move away from PC technology for all critical systems.

But what you probably won't see is a measured review of what happened and a solution that focuses on ensuring a disaster like it won't happen again.

Most large firms have disaster plans -- hopefully, most now include provisions for a cyberattack. If yours doesn't, you may want to fix that. I'm actually more worried about the government overreacting and doing stupid things, like pulling the plug on most network traffic, or moving to something like 100 percent network traffic scanning and returning us to the pre-Internet age overnight. For large companies, ensure you have solid contacts in the office of cybersecurity, and know who to call in the case of a disaster. Then you'll have access to the government resources you need, and this will help ensure these agencies don't do more harm than a virus itself.

But given our recent history with everything from the response to 9/11 to that of the economic crisis, there is significant grounds to be concerned that a major successful virus attack, while damaging, will pale in the face of a poorly thought-out and executed government response. I think we should begin considering how to avoid that, or at least protect ourselves from government overreaction.

-- Rob Enderle is president and founder of Enderle Group. 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