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
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This gives a new meaning to blind leading the blind.
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-21441
PUBLISHED: 2021-06-16
There is a XSS vulnerability in the ticket overview screens. It's possible to collect various information by having an e-mail shown in the overview screen. Attack can be performed by sending specially crafted e-mail to the system and it doesn't require any user intraction. This issue affects: OTRS A...
CVE-2020-9493
PUBLISHED: 2021-06-16
A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution.
CVE-2021-28815
PUBLISHED: 2021-06-16
Insecure storage of sensitive information has been reported to affect QNAP NAS running myQNAPcloud Link. If exploited, this vulnerability allows remote attackers to read sensitive information by accessing the unrestricted storage mechanism. This issue affects: QNAP Systems Inc. myQNAPcloud Link vers...
CVE-2021-3535
PUBLISHED: 2021-06-16
Rapid7 Nexpose is vulnerable to a non-persistent cross-site scripting vulnerability affecting the Security Console's Filtered Asset Search feature. A specific search criterion and operator combination in Filtered Asset Search could have allowed a user to pass code through the provided search field. ...
CVE-2021-32685
PUBLISHED: 2021-06-16
tEnvoy contains the PGP, NaCl, and PBKDF2 in node.js and the browser (hashing, random, encryption, decryption, signatures, conversions), used by TogaTech.org. In versions prior to 7.0.3, the `verifyWithMessage` method of `tEnvoyNaClSigningKey` always returns `true` for any signature that has a SHA-5...