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.

Vulnerabilities / Threats

12:52 PM
Dark Reading
Dark Reading
Products and Releases

New ISP Anti-Bot Code Just Passed

Voluntary code is the first unified industry effort to cooperatively address the bot problem on a broad scale

San Francisco, March 22, 2012 – The new U.S. Anti-Bot Code of Conduct for Internet Service Providers announced today by the U.S. Federal Communications Commission is a major step forward in the fight against malware and will greatly reduce online risk to end-users, according to the Messaging, Malware and Mobile Anti-Abuse Working Group. The voluntary code is the first unified industry effort to cooperatively address the bot problem on a broad scale and was developed with wide industry support by the FCC’s Communications Security, Reliability and Interoperability Council’s (CSRIC) Working Group 7, which was chaired by the M3AAWG Co-Chairman Michael O’Reirdan. The new code, called the ABCs for ISPs, grew out of the experience of private industry security experts working with government as part of the FCC CSRIC working group focused on bot mitigation. Other M3AAWG members who are participating in CSRIC Working Group 7 represent AT&T, CAUCE, Comcast, Cox, Damballa, ISC, PayPal, Sprint, Time Warner Cable and Verizon, and also included M3AAWG Senior Technical Advisor Joe St Sauver. (M3AAWG is also known as M3 for Messaging Malware and Mobile.) M3AAWG Will List ISP Code Participants ISPs and network operators adhering to the practices recommended by the code will be allowed to state their participation publicly and to be identified on official industry listings of participating service providers. This includes a Web page (http://www.maawg.org/abcs-for-ISP-code) maintained by M3AAWG that is now available where ISPs and network operators can request to be listed as meeting the code prerequisites. By announcing participation, ISPs and network operators demonstrate to their customers and the Internet community their commitment to working against bots and malware that can covertly infect end-users computers. The new code describes actions that network operators should take to educate end-users, detect infected computers, notify their customers, provide information to help them remove the malware, and share feedback with other ISPs about the problem. “Bots are a serious concern for end-users, the economy and the nation. Looking at the significant reduction in spam over the years, we know that cooperative industry action is effective against online abuse. This anti-bot code was developed as a voluntary industry-led initiative in CSRIC Working Group 7 and is a new framework for attacking the problem and reducing the danger,” said Michael O’Reirdan, M3AAWG co-chairman and also WG #7 chair. Bots are malicious programs installed on a users’ system, usually without their knowledge, that are used by criminals to steal personal identity information, send spam, launch attacks against websites and other nefarious actions. In 2009, M3AAWG issued the first best practices to help network operators mitigate bots and the IETF is currently working on an industry mitigation standard, but the new code goes beyond technical considerations. About the Messaging, Malware and Mobile Anti-Abuse Working Group (M3AAWG) The Messaging, Mobile and Malware Anti-Abuse Working Group (M3AAWG) is where the industry comes together to work against bots, malware, spam, viruses, denial-of-service attacks and other online exploitation. M3AAWG (www.M3AAWG.org) – or M3 for Messaging, Malware and Mobile ­– represents more than one billion mailboxes from some of the largest network operators worldwide. It leverages the depth and experience of its global membership to tackle abuse on existing networks and new emerging services through technology, collaboration and public policy. It also works to educate global policy makers on the technical and operational issues related to online abuse and messaging. Headquartered in San Francisco, Calif., M3AAWG is an open forum driven by market needs and supported by major network operators and messaging providers.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...