Presentation on theme: "Mobile Payment Security The Good, the Bad and the Ugly"— Presentation transcript:
1 Mobile Payment Security The Good, the Bad and the Ugly Tony Bates
2 This PresentationThis Presentation is a discussion of the business issuesPose questions rather than provide answersThis Presentation is NOT a technical presentationNo techy twaddle
3 Payment : Security : Compliance With offices in the USA, Canada, UK and Australia, PSC is a leading global PCI and PA-DSS Assessor and Approved Scanning Vendor.One of a select few companies qualified worldwide to provide expert services and solutions to organizations that require specialist compliance or consulting support in the areas of Payments, Security or Compliance.Our focus is exclusively on Clients that accept or process payments or technology companies in the payment industry.To ensure Independence, PSC does not represent, resell or receive commissions from any third party hardware, software or solutions vendors.PSC specializes in payment transaction process, security and compliance
4 What is Mobile Payments ? Payment Presentment✔ - Digital Wallets✔ - Mobile Web payments✔ - Online Wallets✔ - NFC Contactless✔ - Cash✔ - Checks✔ - Credit/Debit Card✔ - FastTrack✔ - Vehicle License PlatePayment Acceptance✔ - Mobile Point of Sale✔ - Smart Phone✔ - PDA✔ - iPad/Tablet? - Bus or Train? - Laptop✗- Desktop
5 Mobile Payment Software - Presentment Security Card Holder’s responsibilityCard company’s Cardholder AgreementNo industry standards for digital wallets solutionsWallet application security?Wallet interoperability?Multiple payment instruments in a single wallet?Which one is “on top”?What about release of personal data ?
6 Mobile Payment Software - Interoperability Too many protocolsIP over 3G/4GBluetoothNFCToo few “true” standardsSolutions tend to be monolithicChicken and egg problems with adoptionLack of compatibility with other solutionsSecurity models vary greatly in maturity
7 Mobile Payment Software - Acceptance Payment Card Industry Security Standards CouncilPCI Data Security Standard (PCI DSS)Applies to Services Providers and MerchantsPayment Application Data Security Standard (PA-DSS)Applies to Payment applications used by Services Providers and MerchantsCard Company RegulationsState Regulations regarding Personal Information
8 OK for PADSS Category 1 Category 2 Payment application operates only on a PTS-approved mobile device.Category 2Payment application meets ALL of the following criteria:Payment application is only provided as a complete solution “bundled” with a specific mobile device by the vendorUnderlying mobile device is purpose-built (by design or by constraint) with a single function of performing payment acceptancePayment application, when installed on the “bundled” mobile device (as assessed by the Payment Application Qualified Security Assessor (PA-QSA) and explicitly documented in the payment application’s Report on Valication (ROV), provides an environment which allows the merchant to meet and maintain PCI DSS compliance.
9 NOT OK for PADSS Category 3 Payment application operates on any consumer electronic handheld device (e.g., smart phone, tablet, or PDA) that is not solely dedicated to payment acceptance for transaction processing
10 Visa Mobile Acceptance Best Practices Consumer Mobile Device:Any electronic handheld device (e.g., smart phone, tablet or PDA) that is not solely dedicated to payment acceptance and that has the ability to wirelessly communicate account data (via GSM, GPRS, CDMA, etc.) for transaction processing.Mobile Payment Acceptance Solution:Consists of mobile payment application, a consumer mobile device and, where account data is electronically read from a payment card, a hardware accessory capable of reading account data.Solutions that do not electronically read account data may not be acceptable in all territories or may face some restrictions. Clients must review local Visa Operating Regulations prior to providing mobile payment acceptance solutions to merchants.
11 MasterCard PADSS Mandate Effective 1 July 2012, MasterCard will revise the MasterCard SDP Program Standards to require all merchants and Service Providers that use third party-provided payment applications to only use those applications that are compliant with the Payment Card Industry Payment Application Data Security Standard (PCI PA-DSS), as applicable.The applicability of the PCI PA-DSS to third party-provided payment applications is defined in the PCI PA-DSS Program Guide.In addition, MasterCard will establish a new PA-DSS compliance validation requirement for Level 1, Level 2, and Level 3 merchants as well as Level 1 and Level 2 Service Providers.
12 Mobile Payment Security Testing Current solutions choose time-to market over securityE.g. Square – currently no encryption in readersThe usual “web” tools don’t do itMuch more technical and specialized than the webA mustComplexity breeds security problemsMultiple protocols, devices, networksGood penetration testing by experts
13 Apple “iWallet” patent – Parental Controls Granted on Tuesday March 6A method, comprising: defining one or more rules using a handheld electronic device, wherein the one or more rules establish restrictions on transactions made using a financial account associated with an account holder other than the user of the handheld electronic device; and applying the one or more rules to the financial account.
14 Summary Poor definition of marketplace Hard to define security solutions and standardsStandards don’t fully apply – or protectCard brand mandates cover what the way they would like to see the industryNot the way the industry isRisk based assessments and penetration testing poor in this areaNot enough experts