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 //

Compliance

National 'Do Not Call' Registry Is Working, FTC Says

Commission pats itself on the back, but marketers and consumers are still holding the phone

Ignore that ringing phone in your house -- the National "Do Not Call" Registry is working well, the Federal Trade Commission said today.

In a report filed this morning, the FTC said the "Do Not Call" list is "by every available measure, an effective consumer protection initiative." The Commission has called for the 145 million telephone numbers in the database to be registered permanently, rather than limited to five years as was previously proposed.

"The Commission believes that the fundamental goal of the National Registry -- to provide consumers with a simple, free, and effective means to limit unwanted telemarketing calls -- has been achieved," the report states.

But marketers and consumers are not quite so convinced. In a statement last month, the Direct Marketing Association registered concern that the information in the database is not accurate.

“Congress was very concerned that the National Do Not Call Registry be accurate — a goal that is even more vital now that consumers' numbers remain on the registry permanently, rather than for five years,” said Jerry Cerasale, senior vice president of government affairs for the DMA. "According to data that DMA members have provided, the registry is far from accurate." The FTC is reviewing procedures to improve accuracy, he said.

In a Harris Interactive poll conducted last year, 73 percent of consumers who have signed up for the Registry said they still receive some telemarketing calls. However, the vast majority said they are receiving fewer calls than they did prior to signing up.

The FTC says it has filed a total of 25 cases alleging violations of the Registry, and reached settlements in 22 of them. In 13 of the cases, defendants paid civil penalties totaling more than $8.7 million. In the remaining cases, defendants paid redress totaling more than $8.4 million.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
Breaches Are Inevitable, So Embrace the Chaos
Ariel Zeitlin, Chief Technology Officer & Co-Founder, Guardicore,  11/13/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19010
PUBLISHED: 2019-11-16
Eval injection in the Math plugin of Limnoria (before 2019.11.09) and Supybot (through 2018-05-09) allows remote unprivileged attackers to disclose information or possibly have unspecified other impact via the calc and icalc IRC commands.
CVE-2019-16761
PUBLISHED: 2019-11-15
A specially crafted Bitcoin script can cause a discrepancy between the specified SLP consensus rules and the validation result of the [email protected] npm package. An attacker could create a specially crafted Bitcoin script in order to cause a hard-fork from the SLP consensus. All versions >1.0...
CVE-2019-16762
PUBLISHED: 2019-11-15
A specially crafted Bitcoin script can cause a discrepancy between the specified SLP consensus rules and the validation result of the slpjs npm package. An attacker could create a specially crafted Bitcoin script in order to cause a hard-fork from the SLP consensus. Affected users can upgrade to any...
CVE-2019-13581
PUBLISHED: 2019-11-15
An issue was discovered in Marvell 88W8688 Wi-Fi firmware before version p52, as used on Tesla Model S/X vehicles manufactured before March 2018, via the Parrot Faurecia Automotive FC6050W module. A heap-based buffer overflow allows remote attackers to cause a denial of service or execute arbitrary ...
CVE-2019-13582
PUBLISHED: 2019-11-15
An issue was discovered in Marvell 88W8688 Wi-Fi firmware before version p52, as used on Tesla Model S/X vehicles manufactured before March 2018, via the Parrot Faurecia Automotive FC6050W module. A stack overflow could lead to denial of service or arbitrary code execution.