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
Threaded  |  Newest First  |  Oldest First
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment:   It's a PEN test of our cloud security.
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
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-18898
PUBLISHED: 2020-01-23
UNIX Symbolic Link (Symlink) Following vulnerability in the trousers package of SUSE SUSE Linux Enterprise Server 15 SP1; openSUSE Factory allowed local attackers escalate privileges from user tss to root. This issue affects: SUSE SUSE Linux Enterprise Server 15 SP1 trousers versions prior to 0.3.14...
CVE-2019-19837
PUBLISHED: 2020-01-23
Incorrect access control in the web interface in Ruckus Wireless Unleashed through 200.7.10.102.64 allows remote information disclosure of bin/web.conf via HTTP requests.
CVE-2020-7210
PUBLISHED: 2020-01-23
Umbraco CMS 8.2.2 allows CSRF to enable/disable or delete user accounts.
CVE-2019-19835
PUBLISHED: 2020-01-23
SSRF in AjaxRestrictedCmdStat in zap in Ruckus Wireless Unleashed through 200.7.10.102.64 allows a remote denial of service via the server attribute to the tools/_rcmdstat.jsp URI.
CVE-2020-5216
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.9.0, 5.2.0, and 6.3.0. If user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection. Upon seei...