Risk
9/23/2011
12:40 PM
Connect Directly
RSS
E-Mail
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
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.