02:29 PM

Robocall Killers Seek End Of Nuisance Calls

FTC contest winners have new ideas on to how to identify and block illegal spam calls to landlines and cellphones.

Could illegal robocalls become a nuisance of the past?

The Federal Trade Commission Tuesday announced the finalists in its FTC Robocall Challenge to find a crowdsourced technique that can accurately block illegal, automated calls to landlines and mobile phones. The contest offered a first-place prize of $50,000 to the best robocall-busting solution, while promising that "solvers will retain ownership of their solutions." The FTC also announced that it would award a "Technology Achievement Award" -- no cash prize included -- for the best entry hailing from an organization with more than 10 employees.

What's wrong with robocalls? The Federal Communications Commission allows non-commercial robocalls -- referring to the practice of using computerized auto-dialers to deliver pre-canned messages -- for many types of noncommercial purposes, provided they're not sent to cellphones.

[ Meet the new cybercrime fighting proposal, same as the old cybercrime fighting proposal. See Tougher Computer Crime Penalties Sought By U.S. Legislators. ]

But as noted in the rules for the FTC's Robocall Challenge -- which ran from October 2012 to January 2013, and received nearly 800 entries -- "the vast majority of telephone calls that deliver a prerecorded message trying to sell something to the recipient are illegal" under the FTC-enforced Telemarketing Sales Rule. Furthermore, the FTC gets over 200,000 consumer complaints per month pertaining to robocalls. But thanks to low-cost VoIP telephony, the calls can be generated from anywhere in the world, which makes cracking down on them at the source difficult, if not impossible.

Enter the FTC's top two robocall-blocking finalists, separate proposals from computer engineer Serdar Danis and software developer Aaron Foss -- they'll each receive $25,000. Both proposals focus "on intercepting and filtering out illegal prerecorded calls using technology to 'blacklist' robocaller phone numbers and 'whitelist' numbers associated with acceptable incoming calls," according to the FTC. "Both proposals also would filter out unapproved robocallers using a CAPTCHA-style test to prevent illegal calls from ringing through to a user."

Full details of the proposals haven't been released, since they're proprietary, but at a high level, Danis' "Robocall Filtering System and Device with Autonomous Blacklisting,Whitelisting, GrayListing and Caller ID Spoof Detection" proposal would intercept robocalls using software either running on a mobile device, on a dedicated piece of hardware inside the home, or as a service offered by a telephone provider. The proposal from Foss, meanwhile, dubbed "Nomorobo," is meant to run in the cloud, and would force all incoming calls to ring simultaneously on a second line, which is a service already offered by most telephone carriers. If the system detects a robocall, however, the second line answers and immediately hangs up. Otherwise, it lets the call ring through.

The Technology Achievement Award went to a proposal dubbed "Crowd-Sourced Call Identification and Suppression" from Daniel Klein and Dean Jackson, both of whom are Pittsburgh-based Google employees. As with Danis' and Foss' approaches, Klein and Jackson's proposal would use algorithms to detect spam calls, in part by building threat profiles attached to any given phone number and blocking any numbers identified as being used for robocalls. Their proposal would also employ smartphone apps, VoIP software and hardware devices that would allow consumers to designate which incoming phone numbers were being used for robocalls, thus providing better threat data.

"The solutions that our winners came up with have the potential to turn the tide on illegal robocalls, and they show the wisdom of tapping into the genius and technical expertise of the public," said Charles Harwood, acting director of the FTC's Bureau of Consumer Protection, in a statement. "We're hoping these winning proposals find their way to the marketplace soon, and will provide relief to millions of American consumers harassed by these calls."

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
5/24/2013 | 7:13:12 PM
re: Robocall Killers Seek End Of Nuisance Calls
I have submitted a whitehouse.gov petition to implement a robocall suppression system.
Please sign.
User Rank: Apprentice
4/6/2013 | 1:52:23 PM
re: Robocall Killers Seek End Of Nuisance Calls
The only robocalls I get are from the Republican party and the NRA. Yes, please, make it stop, but with those two being excessive overusers I am convinced that any practical solution will be shut down by both of them.
User Rank: Apprentice
4/4/2013 | 12:25:20 PM
re: Robocall Killers Seek End Of Nuisance Calls
Please - something! we need relieve from the constant ringing of the phone for these trash calls. So much for the "do not call" list. Another weak attempt of the government to control behavior that proved ineffective. And, they want to "bolster" background checks for guns too!? The current system's been as effective as the do not call.
Drew Conry-Murray
Drew Conry-Murray,
User Rank: Ninja
4/3/2013 | 11:37:08 PM
re: Robocall Killers Seek End Of Nuisance Calls
This sounds like a great use of crowdsourcing. Glad to see the FTC being creative, or at least tapping the creativity of the technology community.

Drew Conry-Murray
Editor, Network Computing
Register for Dark Reading Newsletters
White Papers
Current Issue
Dark Reading Tech Digest September 7, 2015
Some security flaws go beyond simple app vulnerabilities. Have you checked for these?
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2015-10-05
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2014-9750, CVE-2014-9751. Reason: this ID was intended for one issue, but was associated with two issues. Notes: All CVE users should consult CVE-2014-9750 and CVE-2014-9751 to identify the ID or IDs of interest. All references and d...

Published: 2015-10-05
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2014-9750, CVE-2014-9751. Reason: this ID was intended for one issue, but was associated with two issues. Notes: All CVE users should consult CVE-2014-9750 and CVE-2014-9751 to identify the ID or IDs of interest. All references and d...

Published: 2015-10-05
ntp_crypto.c in ntpd in NTP 4.x before 4.2.8p1, when Autokey Authentication is enabled, allows remote attackers to obtain sensitive information from process memory or cause a denial of service (daemon crash) via a packet containing an extension field with an invalid value for the length of its value...

Published: 2015-10-05
The read_network_packet function in ntp_io.c in ntpd in NTP 4.x before 4.2.8p1 on Linux and OS X does not properly determine whether a source IP address is an IPv6 loopback address, which makes it easier for remote attackers to spoof restricted packets, and read or write to the runtime state, by lev...

Published: 2015-10-05
Omron CX-One CX-Programmer before 9.6, CJ2M PLC devices before 2.1, and CJ2H PLC devices before 1.5 rely on cleartext password transmission, which allows remote attackers to obtain sensitive information by sniffing the network during a PLC unlock request.

Dark Reading Radio
Archived Dark Reading Radio
What can the information security industry do to solve the IoT security problem? Learn more and join the conversation on the next episode of Dark Reading Radio.