December 3, 2015 By Patrick Kehoe 3 min read

The holiday shopping season is upon us, and more buyers will leave their credit cards and cash in pocket and complete their holiday purchases via convenient mobile phones and tablets.

Most mobile payment solutions are very secure — in fact, more secure than the old-fashioned swiping of a credit card at a point-of-sale terminal. But in light of the recent rash of mobile app attacks (including KeyRaider, XcodeGhost and Shuanet) and the new attack vectors that have emerged, we wanted to provide input for organizations that are revisiting their mobile payment security approach in preparation for the holiday shopping rush.

What Threats Should You Be Concerned About?

Mobile payment attack techniques continue to evolve. There are many attack points, but the most critical we see are summarized in the table below:

Of particular importance in most mobile payment apps is cryptography. We highlight cryptography because:

  • In most mobile payment apps, it’s used to encrypt data and ensure secure communications between the mobile app and the back-end server handling the transaction.
  • Many organizations don’t protect their keys or think it is too difficult to protect them. In fact, 80 percent of respondents to a Ponemon Institute survey sponsored by IBM identified broken cryptography as the most difficult risk to minimize.
  • Unfortunately, crypto keys represent a prime target. Cybercriminals are utilizing a broad set of tactics to discover keys, including extracting them though memory scraping techniques. With access to an application’s crypto keys and algorithms, attackers obtain keys to the kingdom that unveil data and app security measures, making it quite easy to circumvent security controls and/or tamper with application logic to steal information.

What Protection Techniques Should You Focus On?

There is no shortage of attack vectors, so the real question is: What are the most important factors to focus on given limited resources and time? We believe that you’ll get the best results by taking an integrated approach that includes:

(Note: With these factors addressed, network protection becomes less important!)

The table below summarizes what you can do to address the most effective techniques being used to compromise mobile payment solutions.

To protect all-important crypto keys in payment apps, we recommend applying white-box cryptography in lieu of standard cryptographic implementations. The best white-box cryptography solutions combine mathematical obfuscation with classic code obfuscation. Together, these forms of obfuscation raise the bar to higher levels for attackers trying to identify keys or algorithm implementations via either static or dynamic analysis. White-box cryptography protects:

  • Static keys, which are embedded in applications when they ship;
  • Dynamic keys, which are generated on the fly at runtime;
  • Sensitive user data.

Best Practices for Protecting Mobile Payment Information

Finally, organizations should educate those using their mobile payment apps on some best practices. The risk of your mobile payment solution getting hacked decreases dramatically if users:

  1. Download mobile apps only from official app stores (e.g., Google Play, App Store, etc.).
  2. Ensure that phone settings are set to prevent app downloads from unofficial stores. Users may want to check their mobile phone’s user guide for instructions.
  3. Ensure private data and transactions are secure when using mobile apps by asking banks, retailers and credit card providers if mobile apps have been safeguarded against attacks such as reverse engineering, tampering or malware insertion.
  4. Avoid making mobile payments over public Wi-Fi. If that’s unavoidable — because users spend a lot of time in cafes, hotels, airports, etc. — then they should consider paying for access to a virtual private network that will significantly improve privacy.
  5. Follow their instincts. If something about the payment transaction appears to be suspicious, users should consider making the payment later or by a different means.

If implemented properly, these protection techniques will dramatically decrease the risk that your mobile payment app will be compromised. They could also prevent you from squandering profits from your holiday-related mobile transactions to cover the cost of potential data breaches.

Download Arxan’s 4th Annual ‘State of Application Security’ Report to learn more

More from Application Security

What’s up India? PixPirate is back and spreading via WhatsApp

8 min read - This blog post is the continuation of a previous blog regarding PixPirate malware. If you haven’t read the initial post, please take a couple of minutes to get caught up before diving into this content. PixPirate malware consists of two components: a downloader application and a droppee application, and both are custom-made and operated by the same fraudster group. Although the traditional role of a downloader is to install the droppee on the victim device, with PixPirate, the downloader also…

PixPirate: The Brazilian financial malware you can’t see

10 min read - Malicious software always aims to stay hidden, making itself invisible so the victims can’t detect it. The constantly mutating PixPirate malware has taken that strategy to a new extreme. PixPirate is a sophisticated financial remote access trojan (RAT) malware that heavily utilizes anti-research techniques. This malware’s infection vector is based on two malicious apps: a downloader and a droppee. Operating together, these two apps communicate with each other to execute the fraud. So far, IBM Trusteer researchers have observed this…

From federation to fabric: IAM’s evolution

15 min read - In the modern day, we’ve come to expect that our various applications can share our identity information with one another. Most of our core systems federate seamlessly and bi-directionally. This means that you can quite easily register and log in to a given service with the user account from another service or even invert that process (technically possible, not always advisable). But what is the next step in our evolution towards greater interoperability between our applications, services and systems?Identity and…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today