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

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
Comments
Newest First  |  Oldest First  |  Threaded View
Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
Architectural Analysis IDs 78 Specific Risks in Machine-Learning Systems
Jai Vijayan, Contributing Writer,  2/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19325
PUBLISHED: 2020-02-17
SilverStripe through 4.4.x before 4.4.5 and 4.5.x before 4.5.2 allows Reflected XSS on the login form and custom forms. Silverstripe Forms allow malicious HTML or JavaScript to be inserted through non-scalar FormField attributes, which allows performing XSS (Cross-Site Scripting) on some forms built...
CVE-2020-1693
PUBLISHED: 2020-02-17
A flaw was found in Spacewalk up to version 2.9 where it was vulnerable to XML internal entity attacks via the /rpc/api endpoint. An unauthenticated remote attacker could use this flaw to retrieve the content of certain files and trigger a denial of service, or in certain circumstances, execute arbi...
CVE-2020-1828
PUBLISHED: 2020-02-17
Huawei NIP6800 versions V500R001C30, V500R001C60SPC500, and V500R005C00; and Secospace USG6600 and USG9500 versions V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, and V500R005C00 have an input validation vulnerability where the IPSec module does not validate a field in a specific message. ...
CVE-2020-1857
PUBLISHED: 2020-02-17
Huawei NIP6800 versions V500R001C30, V500R001C60SPC500, and V500R005C00SPC100; and Secospace USG6600 and USG9500 versions V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, and V500R005C00SPC100 have an information leakage vulnerability. Due to improper processing of some data, a local authent...
CVE-2020-1858
PUBLISHED: 2020-02-17
Huawei products NIP6800 versions V500R001C30, V500R001C60SPC500, and V500R005C00SPC100; Secospace USG6600 versions V500R001C30SPC600, V500R001C60SPC500, and V500R005C00SPC100; and USG9500 versions V500R001C30SPC600, V500R001C60SPC500, and V500R005C00SPC100 have a denial of service vulnerability. Att...