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
Malicious USB Drive Hides Behind Gift Card Lure
Dark Reading Staff 3/27/2020
How Attackers Could Use Azure Apps to Sneak into Microsoft 365
Kelly Sheridan, Staff Editor, Dark Reading,  3/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
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-2020-10560
PUBLISHED: 2020-03-30
An issue was discovered in Open Source Social Network (OSSN) through 5.3. A user-controlled file path with a weak cryptographic rand() can be used to read any file with the permissions of the webserver. This can lead to further compromise. The attacker must conduct a brute-force attack against the S...
CVE-2020-5527
PUBLISHED: 2020-03-30
When MELSOFT transmission port (UDP/IP) of Mitsubishi Electric MELSEC iQ-R series (all versions), MELSEC iQ-F series (all versions), MELSEC Q series (all versions), MELSEC L series (all versions), and MELSEC F series (all versions) receives massive amount of data via unspecified vectors, resource co...
CVE-2020-5551
PUBLISHED: 2020-03-30
Toyota 2017 Model Year DCU (Display Control Unit) allows an unauthenticated attacker within Bluetooth range to cause a denial of service attack and/or execute an arbitrary command. The affected DCUs are installed in Lexus (LC, LS, NX, RC, RC F), TOYOTA CAMRY, and TOYOTA SIENNA manufactured in the re...
CVE-2020-10940
PUBLISHED: 2020-03-27
Local Privilege Escalation can occur in PHOENIX CONTACT PORTICO SERVER through 3.0.7 when installed to run as a service.
CVE-2020-10939
PUBLISHED: 2020-03-27
Insecure, default path permissions in PHOENIX CONTACT PC WORX SRT through 1.14 allow for local privilege escalation.