Risk
9/23/2011
12:40 PM
50%
50%

Feds Seek Advice To Battle Botnets

Homeland Security and Commerce Departments want to develop voluntary, standard practices that will protect and mitigate attacks on the private sector.

Inside DHS' Classified Cyber-Coordination Headquarters
(click image for larger view)
Slideshow: Inside DHS' Classified Cyber-Coordination Headquarters
Two federal agencies are seeking ideas for creating a code of conduct that private-sector Internet service providers (ISPs) can adopt to protect their customers against botnet attacks.

The Department of Homeland Security (DHS) and two Department of Commerce organizations--the National Institute for Standards and Technology (NIST) and the National Telecommunications and Information Administration--are asking the public to weigh in on requirements and approaches to creating a "voluntary industry code of conduct to address the detection, notification, and mitigation of botnets "via a request for proposal on the Federal Register.

Botnets are collections of computers that remote parties control to mount cyber attacks and act in other malevolent ways. These types of attacks are increasing in number, according to the agencies, with various negative results such as remote "monitoring of a consumer's personal information and communication, and exploitation of that consumer's computing power and Internet access," according to the RFP.

[ Botnets are a growth industry. Read Inside The Booming Botnet Industry ]

Once a botnet infects a network, compromised computers also can be used to spread spam, store and transfer illegal content, and attack both public and private-sector networks with denial of service attacks, according to the RFP.

The DHS and Commerce are asking "all Internet stakeholders" to comment on potential models for detection, notification, prevention, and mitigation of botnets' illicit use of computer equipment. The comment period is open until Nov. 4.

The RFP provides a list of questions for those interested in submitting ideas to consider, including pondering what practices already have proved effective against detecting botnets before an attack and what mechanisms already are in place to share information about botnets that would help prevent, detect, and mitigate attacks by them.

The agencies answered the first question themselves in the RFP, noting that there has been successful protection against botnets when Internet service providers (ISP) can identify an attack and notify customers that their network has been infected. They also suggest the creation of a resource center, run either by the private sector, the government, or some kind of hybrid public-private partnership, to provide centralized support for ISP customers to deal with botnet threats.

The feds increasingly are working with the private sector on cybersecurity, especially in the adoption of standards and other best practices that the industry can use to better protect U.S. critical infrastructure.

Join us for GovCloud 2011, a day-long event where IT professionals in federal, state, and local government will develop a deeper understanding of cloud options. Register now.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-5426
Published: 2014-11-27
MatrikonOPC OPC Server for DNP3 1.2.3 and earlier allows remote attackers to cause a denial of service (unhandled exception and DNP3 process crash) via a crafted message.

CVE-2014-2037
Published: 2014-11-26
Openswan 2.6.40 allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon restart) via IKEv2 packets that lack expected payloads. NOTE: this vulnerability exists because of an incomplete fix for CVE 2013-6466.

CVE-2014-6609
Published: 2014-11-26
The res_pjsip_pubsub module in Asterisk Open Source 12.x before 12.5.1 allows remote authenticated users to cause a denial of service (crash) via crafted headers in a SIP SUBSCRIBE request for an event package.

CVE-2014-6610
Published: 2014-11-26
Asterisk Open Source 11.x before 11.12.1 and 12.x before 12.5.1 and Certified Asterisk 11.6 before 11.6-cert6, when using the res_fax_spandsp module, allows remote authenticated users to cause a denial of service (crash) via an out of call message, which is not properly handled in the ReceiveFax dia...

CVE-2014-7141
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and crash) via a crafted type in an (1) ICMP or (2) ICMP6 packet.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?