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.

Endpoint //

Authentication

3/4/2015
04:20 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

Apple Pay Fraud Gives Us A New Reason To Hate Data Breaches And SSNs

There may already be millions of dollars in losses, but you can't blame Apple for this one.

The fact that attackers may have already made millions of dollars in fraudulent Apple Pay purchases is another example of how even the best security technology is rendered useless by poor implementation.

Just last week, payment security experts told Dark Reading that Apple's secure mobile payment technology -- first released in September -- is superior to any of the other payment tech on the market. Since then, however, they became aware of "rampant" Apple Pay fraud, detailed well by The Guardian. The perpetrators are linking their iOS devices to victims' payment card accounts, and using Apple Pay to make in-person purchases (often at Apple Stores) which are then charged to the victim's account.      

While the quickness of the attackers and extent of the fraud surprised experts, they maintain that the technology is strong.

"Apple Pay is great," says Gartner distinguished analyst Avivah Litan. "It’s the bank processes for identity-proofing that are weak."

In other words, Apple Pay fraud has nothing to do with Apple -- nor its encryption, nor its tokenization protocol -- and everything to do with the banks that provision payment cards/tokens.

"The one constant we have seen for every mobile financial service thus far has been the issue of [bank account] takeovers, whether that be mobile banking, mobile RDC, or mobile payments," says Al Pascual, director of security, risk, and fraud for Javelin Strategy and Research. "More needs to be done to ensure that the device to which data is provisioned belongs to the legitimate accountholder."

When an iOS user adds their credit account information to the Apple Pay system on their device, the data is encrypted and sent "along with other information about your iTunes account activity and device (such as the name of your device, its current location, or if you have a long history of transactions within iTunes) to your bank," according to Apple.

Some banks give approval on that information alone, and others add an additional method of authorization. Oftentimes that extra check is simply to call the person claiming to be the accountholder and ask them to verify the last four digits of their Social Security number. In that case, fraudsters don't need to try to crack into the issuing bank or into Apple's token vault -- they can get personal data, including SSNs, by breaching third parties' databases or by simply buying it on the black market.

SSNs overlap two sorts of authentication factors -- "something you know" and "something you are" -- and offer only the worst characteristics of both. A last-four-digit combination is as easy to brute force as any 4-digit PIN. SSNs are impossible to change, unless you've already had extensive identity theft problems, joined the Witness Protection Program, or proven you have intense religious objections to your particular number. Plus, it is impossible to verify an SSN is really "you," because the Social Security Administration will neither confirm nor deny that a certain SSN matches with a certain name.

"Consider that 66 percent of the top 50 [financial institutions] allow consumers to authenticate with an SSN according to our research," says Pascual, "and we just witnessed a breach of 80 million SSNs. Fortunately, we have better options for call center authentication, such as biometrics or through phone print authentication."

Litan recommends that financial institutions reduce their reliance on static data (like SSNs), increase use of dynamic data (like behavior analysis), and layer multiple authentication methods upon one another. For example, examining linkages between a device, email address, phone number, mailing address, and name; and examining behavior, like navigation and network habits; and examining endpoint-centric factors like geolocation and device fingerprinting. She also recommends that for high-risk cases, financial institutions consider implementing biometrics tools or slowing the authorization process down by using snail mail or requiring in-person interactions.

"As for tying the device to the accountholder," says Pascual, "there are some technologies out there that authenticate the mobile device by leveraging the [mobile network operator] relationship. We can expect these solutions to become more popular, if not central to addressing this issue."

"The problem for Apple," says Litan, "is that consumers see Apple Pay and the banks as one and the same entity here," but "I doubt it will slow Apple Pay adoption down in any meaningful way."

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Page 1 / 2   >   >>
HAnatomi
50%
50%
HAnatomi,
User Rank: Apprentice
3/5/2015 | 1:19:45 AM
Convenience improved by bringing down security
Apple is also expected do something about the vulnerability that their Touch ID brings:  Biometrics operated with a password in the OR/disjunction way (as in the case of iPhone) offers a lower security than when only the password is used.

Threats that can be thwarted by biometric products operated together with fallback/backup passwords can be thwarted more securely by passwords only.

We could be certain that biometrics would help for better security only when it is operated together with another factor by AND/Conjunction (we need to go through both of the two), not when operated with another factor by OR/Disjunction (we need only to go through either one of the two) as in the cases of Touch ID and many other biometric products on the market that require a backup/fallback password, which only increase the convenience by bringing down the security.

 
Pablo Valerio
50%
50%
Pablo Valerio,
User Rank: Strategist
3/5/2015 | 6:20:36 AM
I don't get the US Banks' mentality
@Sara, are US banks really stupid, or their systems so archaic?

In Europe, for many years, we need several special second authentication systems such as one-time security codes, coordinate cards, Chip+PIN.

Just the fact that the new EMV cards in the US will be Chip+Signature doesn't make sense. Are US banks implying that Americans won't use their cards becuase they have to enter a PIN? As you know we have that system here in Europe for many years and very few people complain.

They had the opportunity, with Apple Pay, to have a robust, secure, mobile payment system, and they are committed to blow it.
Technocrati
50%
50%
Technocrati,
User Rank: Ninja
3/5/2015 | 4:27:54 PM
Re: I don't get the US Banks' mentality

I was about to rant about Apple Pay until I read further, and it makes sense that the security shortcomings are due in large part to the banks' inability to understand and carry out security with these types of transactions.

I get the feeling many banks know they are in over there heads when it comes to these mobile payments, but since it was Apple they just couldn't admit it.

I did not realize SSN#'s were so ingrained into their authentication process, but as a result of breeches it is certainly time to rethink using this as a be all, end all. 

Those days are over.  Thanks big business.   What would we do without you ?

 

Probably still have our identities - But of course it is too late for that.

Technocrati
50%
50%
Technocrati,
User Rank: Ninja
3/5/2015 | 4:32:27 PM
Re: I don't get the US Banks' mentality
"....are US banks really stupid, or their systems so archaic?"

 

@Pablo   Both.   And you can add arrogant to that as well.   The World has become too complicated for Banks.  They must think whatever happen to the good old days ?  

When all they had to do is take your money.
Technocrati
50%
50%
Technocrati,
User Rank: Ninja
3/5/2015 | 4:41:52 PM
And Yet Another Reason To Hate Breeches .....

Recently read that Target is cutting thousands of jobs due in large part to their recent breech.     Same old story.  CEO keeps his or her job (not quite sure if they axed that pho CIO they had)  but as usual the focus is misplaced.

 

And as usual those who had nothing to do with it must pay for it.

Technocrati
50%
50%
Technocrati,
User Rank: Ninja
3/5/2015 | 4:46:10 PM
Re: I don't get the US Banks' mentality

I don't understand the chip/signature rationale either.  Is a signature supposed to be more secure than a pin # ?   The Banks need some serious help, and I have a group of experts willing for a fee (of course).

Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
3/5/2015 | 4:46:39 PM
Re: And Yet Another Reason To Hate Breeches .....
@Technocrati  The Target CEO did loose his job as a result of the breach. He stepped down last May. 
Technocrati
50%
50%
Technocrati,
User Rank: Ninja
3/5/2015 | 4:49:09 PM
Re: I don't get the US Banks' mentality

"...As you know we have that system here in Europe for many years and very few people complain."

 

@Pablo    This is where that arrogance comes in that I mentioned earlier.  Go to Europe and see how others are doing it ?   No Way.   Europe is only for vacations and hiding assets.

Technocrati
50%
50%
Technocrati,
User Rank: Ninja
3/5/2015 | 4:50:55 PM
Re: And Yet Another Reason To Hate Breeches .....

@Marilyn     Ah Thank you !   So there is some justice, not much but some.

Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
3/5/2015 | 4:55:38 PM
Re: And Yet Another Reason To Hate Breeches .....
It was justice and also a watershed for the industry. A first for a CEO to get the axe as the result of a company data breach. Probably won't be the last....
Page 1 / 2   >   >>
Overcoming the Challenge of Shorter Certificate Lifespans
Mike Cooper, Founder & CEO of Revocent,  10/15/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-27605
PUBLISHED: 2020-10-21
BigBlueButton through 2.2.8 uses Ghostscript for processing of uploaded EPS documents, and consequently may be subject to attacks related to a "schwache Sandbox."
CVE-2020-27606
PUBLISHED: 2020-10-21
BigBlueButton before 2.2.8 (or earlier) does not set the secure flag for the session cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session.
CVE-2020-27607
PUBLISHED: 2020-10-21
In BigBlueButton before 2.2.8 (or earlier), the client-side Mute button only signifies that the server should stop accepting audio data from the client. It does not directly configure the client to stop sending audio data to the server, and thus a modified server could store the audio data and/or tr...
CVE-2020-27608
PUBLISHED: 2020-10-21
In BigBlueButton before 2.2.8 (or earlier), uploaded presentations are sent to clients without a Content-Type header, which allows XSS, as demonstrated by a .png file extension for an HTML document.
CVE-2020-27609
PUBLISHED: 2020-10-21
BigBlueButton through 2.2.8 records a video meeting despite the deactivation of video recording in the user interface. This may result in data storage beyond what is authorized for a specific meeting topic or participant.