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.

Analytics

PayPal Outlines Strategy to Slow Phishing

Web's biggest phishing target published multi-layered plan to reduce delivery of fake emails and warn users of phishing sites

Over the last few years, security researchers have estimated that fake messages from PayPal and its parent company, eBay, make up more than half of all the spam sent over the Internet. So why, you may ask, isn't PayPal doing something about it?

Last week at the RSA 2008 conference in San Francisco, the popular payment company quietly revealed what it's doing to stop -- or at least slow -- the proliferation of phishing attacks. In a paper published without fanfare at the show, PayPal outlined a multi-pronged approach that might make an impact on the huge volume of "phishmail" currently transmitted over the Web.

The paper begins with a practical premise: that phishing will never stop as long as there's potential profit in it and that there will never be a single tool, technology, or strategy that can completely prevent it.

"We have not identified any one solution that will singlehandedly eradicate phishing; nor do we believe one will ever exist," the paper says. Instead, PayPal offers a multi-layered strategy: "While no single layer can defeat phishing on its own, in tandem they can make a huge difference, with each layer shaving off some percentage of crime."

In a nutshell, PayPal proposes a combination of strategies to identify and block phishmail from ever reaching the user while also warning and blocking users from accessing phishing sites. The paper also addresses other strategies such as user education, law enforcement, authentication, and phishing site shutdowns, but its primary proposal is to focus on the first two areas.

To slow delivery of phishmail, PayPal is proposing widespread adoption of two technologies for "signing" sent email -- DomainKeys and Sender Policy Framework -- which would allow ISPs to drop all emails that are not verified to be from PayPal (or other popular phishing targets). PayPal has been testing DomainKeys with Yahoo Inc. since October, and the test blocked more than 50 million messages in the first few months and caused phishers to reduce their use of Yahoo! Mail to deliver phishmail, the companies said. (See New Spec Could Cut Phishing, Spam.)

At the same time, PayPal has also been testing a client software package from Iconix that could be embedded in any email application, allowing PCs to identify signed messages and block those that aren't signed. In the tests, this client has helped users to identify and stop phishmail transmitted by ISPs that don't support DomainKeys or SPF.

In addition to email signing and blocking, PayPal is proposing to expand its efforts to block phishing sites and warn users when they are about to go to a suspicious site. In addition to supporting Extended Validation SSL, which is now part of Microsoft's IE7 browser and some others, PayPal says it will warn users of older browsers of their vulnerabilities, implement blacklists to expose known phishing sites, and set up warning pages to discourage users from accessing them.

While a number of reports have cast doubt on the effectiveness of EV SSL, PayPal says it has begun to see changes in user behavior since it implemented the technology nine months ago. "For example, we're seeing lower abandonment rates on signup flows for IE7 users vs. other browsers," the company says. (See Study: Consumers Don't Use Anti-Phishing Defenses.)

PayPal concedes that standards such as DomainKeys and EV SSL are in their early stages of adoption. But the company also suggests that the recent increase in phishmail and spam may be phishers' response to the fact that they are having trouble getting their messages through, and getting victims to bite. "We believe we can already see the 'balloon squeeze' effect at work," the paper says.

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
Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
5 Common Errors That Allow Attackers to Go Undetected
Matt Middleton-Leal, General Manager and Chief Security Strategist, Netwrix,  2/12/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20477
PUBLISHED: 2020-02-19
PyYAML 5.1 through 5.1.2 has insufficient restrictions on the load and load_all functions because of a class deserialization issue, e.g., Popen is a class in the subprocess module. NOTE: this issue exists because of an incomplete fix for CVE-2017-18342.
CVE-2019-20478
PUBLISHED: 2020-02-19
In ruamel.yaml through 0.16.7, the load method allows remote code execution if the application calls this method with an untrusted argument. In other words, this issue affects developers who are unaware of the need to use methods such as safe_load in these use cases.
CVE-2011-2054
PUBLISHED: 2020-02-19
A vulnerability in the Cisco ASA that could allow a remote attacker to successfully authenticate using the Cisco AnyConnect VPN client if the Secondary Authentication type is LDAP and the password is left blank, providing the primary credentials are correct. The vulnerabilities is due to improper in...
CVE-2015-0749
PUBLISHED: 2020-02-19
A vulnerability in Cisco Unified Communications Manager could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack on the affected software. The vulnerabilities is due to improper input validation of certain parameters passed to the affected software. An attacker ...
CVE-2015-9543
PUBLISHED: 2020-02-19
An issue was discovered in OpenStack Nova before 18.2.4, 19.x before 19.1.0, and 20.x before 20.1.0. It can leak consoleauth tokens into log files. An attacker with read access to the service's logs may obtain tokens used for console access. All Nova setups using novncproxy are affected. This is rel...