Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

4/1/2009
06:54 PM
Rob Enderle
Rob Enderle
Commentary
50%
50%

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?

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.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
SOC 2s & Third-Party Assessments: How to Prevent Them from Being Used in a Data Breach Lawsuit
Beth Burgin Waller, Chair, Cybersecurity & Data Privacy Practice , Woods Rogers PLC,  12/5/2019
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: "This is the last time we hire Game of Thrones Security"
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0242
PUBLISHED: 2019-12-09
mod_wsgi module before 3.4 for Apache, when used in embedded mode, might allow remote attackers to obtain sensitive information via the Content-Type header which is generated from memory that may have been freed and then overwritten by a separate thread.
CVE-2015-3424
PUBLISHED: 2019-12-09
SQL injection vulnerability in Accentis Content Resource Management System before the October 2015 patch allows remote attackers to execute arbitrary SQL commands via the SIDX parameter.
CVE-2015-3425
PUBLISHED: 2019-12-09
Cross-site scripting (XSS) vulnerability in Accentis Content Resource Management System before October 2015 patch allows remote attackers to inject arbitrary web script or HTML via the ctl00$cph_content$_uig_formState parameter.
CVE-2015-7892
PUBLISHED: 2019-12-09
Stack-based buffer overflow in the m2m1shot_compat_ioctl32 function in the Samsung m2m1shot driver framework, as used in Samsung S6 Edge, allows local users to have unspecified impact via a large data.buf_out.num_planes value in an ioctl call.
CVE-2015-0841
PUBLISHED: 2019-12-09
Off-by-one error in the readBuf function in listener.cpp in libcapsinetwork and monopd before 0.9.8, allows remote attackers to cause a denial of service (crash) via a long line.