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.

Risk

10/6/2006
05:08 PM
50%
50%

Bots Bad, People Worse

Less than 24 hours since InformationWeek went live with its exclusive pointing to evidence of bot infiltration within computers of federal and state government agencies, the reaction has been strong. Based on feedback to my colleague Tom Claburn's blog posting and through

Less than 24 hours since InformationWeek went live with its exclusive pointing to evidence of bot infiltration within computers of federal and state government agencies, the reaction has been strong. Based on feedback to my colleague Tom Claburn's blog posting and through Slashdot, readers clearly understand the gravity of the situation and the need to do something about it. Plenty of finger pointing--at the government, at Microsoft, even at the media--but, above all, a message that it's people, not technology, that are to blame for the bot problem. People are to blame for creating the bots, and people are to blame for not adequately defending themselves.One commentator, identified as rahrens (939941) and claiming to be a government employee, notes, "If an Agency is willing to spend the money, time and energy to put in place the protections that the typical Government information system deserves, this wouldn't be a problem ... It is not a perfect system, and it takes constant diligence to maintain and periodically upgrade, but I think we do a pretty good job."

Another reader, "Doug from San Diego," who contacted Tom Claburn directly, observes, "You put up a good story Thomas but the only thing I would have added was a twist/comment on how not only do these businesses THINK they are protected when many are not, they don't even change when it is found they are NOT protected as in the case with the virus/BOT which took so many government and business offices down. They just patch and react to the current issue and keep doing the same over and over." The capitalized words came directly from Doug's e-mail.

Government even criticized government. "As someone who has worked in government IT, I can tell you that the biggest problem that we faced security-wise was the bureaucracy of the government ... What you end up with in government IT (and, hence cyber-security) is often a bunch of guys used to doing the same thing every day; never learning anything new; who have grown burned-out, disenchanted, and cynical with the whole process," writes elrous0 (869638).

Several commentators blamed the government's use of Microsoft Windows and Internet Explorer as contributing greatly to the problem (one even criticized the media for not taking Microsoft to task for its poor security track record). Included in this criticism was mention of the Homeland Security Department's warning two years ago that users of MS Internet Explorer should use another browser.

"not [sic] one organization at the state or local level took any action when the Department of Homeland Security(DHS) put out a warning against using MS Internet Explorer when a major risk was found and left open by Microsoft for over 3 months. Heck, three departments in my city were shutdown for a day when one of the Microsoft Windows bot software was 'failing' and resulted in some of the infected computers to constantly reboot. Yet, after that, questions presented about continued use of MS IE resulted in answers like, 'with limited budgets they are doing the best they can' and 'balancing financial impacts and security risks results in some tough choices', etc."

And finally, this observation from webweave (94683): "Should the headline then read 'Government gives Microsoft billions and still has bot problem'? So much for the idea that paying for commercial software produces better software."

Everyone's a critic. Anyway, you can read more about our research into the botnet problem--in both the public and private sectors--in the Oct. 9 issue of InformationWeek. Be sure to drop us a line after you read the story and share your thoughts.

 

Recommended Reading:

Comment  | 
Email This  | 
Print  | 
RSS
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Healthcare Industry Sees Respite From Attacks in First Half of 2020
Robert Lemos, Contributing Writer,  8/13/2020
Register for Dark Reading Newsletters
White Papers
Video
All Videos
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: It's a technique known as breaking out of the sandbox kids.
Cartoon Archive
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Back Issues | Must Reads
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20383
PUBLISHED: 2020-08-13
ABBYY network license server in ABBYY FineReader 15 before Release 4 (aka 15.0.112.2130) allows escalation of privileges by local users via manipulations involving files and using symbolic links.
CVE-2020-24348
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.
CVE-2020-24349
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
CVE-2020-7360
PUBLISHED: 2020-08-13
An Uncontrolled Search Path Element (CWE-427) vulnerability in SmartControl version 4.3.15 and versions released before April 15, 2020 may allow an authenticated user to escalate privileges by placing a specially crafted DLL file in the search path. This issue was fixed in version 1.0.7, which was r...
CVE-2020-24342
PUBLISHED: 2020-08-13
Lua through 5.4.0 allows a stack redzone cross in luaO_pushvfstring because a protection mechanism wrongly calls luaD_callnoyield twice in a row.