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
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20399
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
CVE-2020-7915
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.
CVE-2019-20391
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r3 in the function resolve_feature_value() when an if-feature statement is used inside a bit. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20392
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r1 in the function resolve_feature_value() when an if-feature statement is used inside a list key node, and the feature used is not defined. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20393
PUBLISHED: 2020-01-22
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an empty description is used. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.