Security & Encryption in Healthcare Payments PCI DSS Technical Assessment White Paper

Transcription

1 Security & Encryption in Healthcare Payments PCI DSS Technical Assessment White Paper June 05 White Paper Author: Andrey Sazonov CISA, QSA, PA-QSA Nick Trenc QSA, PA-QSA White Paper QA: Dan Fritsche CISSP, QSA, PA-QSA pg.

2 Table of Contents Executive Summary... 4 Overview... 8 About the Payment Card Industry Security Standards Council (PCI SSC)... 8 What s New in PCI DSS version 3.?... 9 What Happens if I Don t Comply with PCI Standards?... 0 PCI in Healthcare... 0 What s New in Payment Card Technology?... 0 What is EMV?... 0 What about Mobile Payments?... What Impact does Apple Pay have on Healthcare?... Point-to-Point Encryption... 3 InstaMed Healthcare Payment Solutions... 4 Cardholder Data Environment Summary... 4 About InstaMed Solutions... 5 Deployment Scenarios... 6 Network and Dataflow Diagrams for the Implementation Scenarios For the InstaMed Online - Merchant Initiated Scenario... 9 For the Integrated Merchant Initiated and Self-Service Kiosk Scenario... 0 For the Merchant Initiated - Single Sign-On Scenario with Web Services... For the ecommerce In App Apple Pay Scenario... For the ecommerce Single Sign-On Scenario... 3 For the ecommerce - Client Side Encryption Scenario... 4 For the ecommerce Web Services Scenario... 5 For the ecommerce InstaMed Patient Portal Scenario... 6 Audience... 7 Assessment Scope... 7 Methodology... 7 Merchant PCI Compliance Scope... 7 Technical Security Assessment... 7 Impact on Merchant s and Vendor s PCI DSS Audit Applicable Controls... 8 Summary Charts of Potential Impact on Merchant Audit Applicable Controls Table for each Implementation Scenario Merchant Initiated or Self-Service Kiosk payments using InstaMed Online, InstaMed Connect Web Services or InstaMed Connect.NET API... 9 ecommerce In App Apple Pay via InstaMed Connect ecommerce InstaMed Patient Portal with or without Single Sign-On... 3 ecommerce - Client Side Encryption... 3 ecommerce - InstaMed Connect Web Services Appendix A: PCI DSS Requirements Impact for Merchant Initiated Payments with InstaMed Online Appendix B: PCI DSS Requirements Impact for Merchant Initiated Payment through the website using Single Sign-On Appendix C: PCI DSS Requirements Impact for ecommerce Payment Using Client Side Encryption pg.

3 Appendix D: Secure Payment Devices... 3 Coalfire Assessment Information... 4 Assessment Environment... 4 Disk Analysis... 4 Network Traffic Assessment... 5 Tools and Techniques... 5 pg. 3

4 Executive Summary The healthcare industry has been evolving rapidly in recent years, especially with changes in healthcare reform and the increased focus on consumers, especially when it comes to payment. Healthcare providers and payers are becoming merchants who are focused on delivering consumer-friendly payment options in order to efficiently collect the co-pays, deductibles or premiums they are owed. As healthcare organizations accept electronic payments through more and more payment channels, they expose themselves to increased risks, and must be aware of the best practices and requirements in order to protect their businesses. InstaMed, the leading Healthcare Payments Network, connects to healthcare providers and payers for healthcare payment transactions. InstaMed s mission is to streamline payment processes in healthcare to promote efficiency and help businesses to thrive by delivering new and innovative payment channels to the healthcare industry. InstaMed engaged Coalfire Systems Inc. (Coalfire), a respected Payment Card Industry (PCI) Payment Application Qualified Security Assessor (PA-QSA) company, to conduct an independent technical assessment of InstaMed to assess the security of its payment solutions for providers and payers. InstaMed provides multiple deployment options that reduce PCI DSS scope for both merchants as well as application vendors in both merchant initiated and consumer initiated use cases. Scope reduction varies from completely taking the solution out of scope of PA-DSS to being able to mitigate PCI controls to address Vendor s and Merchant s compliance. Merchant Topics Merchant Initiated and Self-Service Kiosk Transactions Solutions include: PPE devices with InstaMed Online (Merchant Initiated only) PPE devices with Single Sign-On to InstaMed Online (Merchant Initiated only) PPE devices with InstaMed Connect Web Services or InstaMed Connect.NET API (Merchant Initiated and Self-Service Kiosk transactions supported) Highlights: InstaMed integrates securely with any computer that has access to the internet and InstaMed Online and/or InstaMed Connect without exposing cardholder data to other systems. InstaMed, with secure point of interaction (POI) devices, can alleviate any applicable controls involved with the PCI DSS compliance requirements for network firewall, network configuration, pg. 4

5 physical controls or administrative procedures for a merchant. When InstaMed is properly deployed, it can significantly reduce the risk of a data breach and is one of the most effective data security controls available to merchants today. By leveraging InstaMed Patient Payments and the InstaMed Patient Portal, a merchant can achieve most of the security and compliance benefits available from a PPE Validated Solution Provider. The integration of devices like those offered by MagTek with InstaMed Online and/or the InstaMed Connect.NET API is quick, requires very little configuration, and works effectively with all post-authorization, sales and refund transactions tested. The integration of some MagTek devices that support NFC/EMV with InstaMed Online and the InstaMed Connect.NET API works in a similar manner as the regular swipe entry. Cardholder dataflow is not impacted. To best mitigate security and compliance risk in a merchant-initiated transaction, a merchant s deployment architecture must: o Have all cardholder data captured by a PPE device, and o Communicate directly with a PCI DSS-compliant service provider and/or processor, such as InstaMed, that manages all decryption services for the merchant. In order to reduce the amount of applicable controls during a PCI DSS audit, devices such as the PTS-approved MagTek devices must be the only point where cardholder data is captured, either through EMV, NFC, swiped or keyed entry. A merchant can reduce the amount of applicable controls of PCI DSS compliance requirements required for the majority of its CDE if all cardholder data is captured by a payment device that can perform encryption at the moment of swipe. pg. 5

6 Consumer Topics ecommerce Transactions Solutions for ecommerce transactions include: Apple Pay Single Sign-On to InstaMed Patient Portal Client Side Encryption Web Services Standalone Patient Portal with Payment Notification Scenario Self Service Card Present (i.e. Kiosk) Highlights: The PCI security standards have created three levels of security and compliance for applications that accept ecommerce (card not present) payments. These three levels correspond to the following selfassessment questionnaires (SAQ): SAQ A [Integration Difficulty Level: EASY] Embed the InstaMed Patient Portal or InstaMed Premium Payments (with or without single sign-on). More information about SAQ A can be found here: SAQ A-EP [Integration Difficulty Level: MEDIUM/HIGH] Build your own user interface and use web services with Client Side Encryption to leverage InstaMed s payment solutions. More information about SAQ A-EP can be found here: SAQ D [Integration Difficulty Level: HIGH] Build your own user interface and use web services without Client Side Encryption to leverage InstaMed s payment solutions. More information about SAQ D can be found here: Vendor Topics Implementing InstaMed Patient Payments and the InstaMed Patient Portal where no card holder data is directly entered into the vendor s application makes a vendor s application not eligible for validation under PA-DSS. Not being eligible for validation for PA-DSS results in both short-term and long-term savings. The vendor will see a 5% reduction on the initial assessment, and assuming no changes are made to the application that would change its eligibility status, the vendor will avoid annual reassessments as well. The table below outlines the benefits of leveraging the.net API or the InstaMed UI (with or without SSO) for Merchant Initiated payments and the InstaMed UI (with or without SSO) for ecommerce transactions. vs. direct web pg. 6

7 services integration.. Security & Encryption in Healthcare Payments PCI Report on Validation Web Services PCI DSS Technical Assessment White Paper SSO or InstaMed UI or.net API Initial Testing Scope Full Full Initial Documentation Scope White Paper Detailed Report on Validation Initial Cost 75% 00% Trigger for Re-assessment Mandatory Annual Reassessment Ongoing Re-assessment cost Business decides based on whether it deems that impactful changes have been made. No enforcement. No None* *Assumes that no impactful changes are made that require a reassessment or a change to ineligibility Whenever an impactful change is made. Enforced by PCI Council. Yes Full pg. 7

8 Overview About the Payment Card Industry Security Standards Council (PCI SSC) The PCI Security Standards Council is a group founded by the five major payment card brands American Express, Discover, JCB, MasterCard and Visa tasked with developing and managing various standards, including the PCI Data Security Standard (PCI DSS), Payment Application Data Security Standard (PCI PA- DSS), Point-to-Point Encryption (PPE) Solution Requirements and Testing Procedures and PIN Transaction Security (PCI PTS). These security standards set the rules that must be followed by merchants, issuing banks, software developers, hardware manufacturers and all other entities involved in the processing, storage or other handling of credit card data. Merchants must ensure that they only do business with service providers who are compliant and certified with the PCI DSS. The PCI DSS process for certifying merchants and service providers is an in-depth audit of security policies, procedures, and environments against a specific set of requirements that provide a very baseline level of information security. This standard applies not only to merchants who accept credit card payments, but also to service providers (those entities that process, store or transmit cardholder data as part on behalf of merchants) such as InstaMed. The PCI PA-DSS standards apply to vendors wishing to develop software that accepts payments in the form of credit cards and ensures that these developers create a software product that will function within a PCI DSS compliant merchant environment. While merchants are not required to use software that has been PA-DSS validated, it is highly recommended to do so in order to help ensure that the PCI DSS requirements are able to be met. Some card brands mandate the use of a PA-DSS validated application for their merchants. Finally, the PCI SSC sets forth requirements for PIN Transaction Security (PTS) devices and PPE. The PTS is a set of requirements that PIN pad hardware manufacturers must abide by when creating these devices. While the SSC doesn t require the use of a PTS validated device, devices that have been validated typically offer better security and protection for cardholder data. PPE requires the use of PTS devices and is intended to shift the burden of compliance away from the merchant and to the service provider by protecting cardholder data with encryption at the point of swipe and decryption at a PPE service provider. pg. 8

9 What s New in PCI DSS version 3.? The changes to the PCI Data Security Standard in Version 3. of the rules focus on the following themes to help organizations take a proactive approach to protecting cardholder data by focusing on security, not just compliance: Education and awareness Updates to the standards are geared towards helping organizations better understand the intent of requirements and how to properly implement and maintain controls across their business. Increased flexibility New rules provide more flexible ways to meet the requirements that protect organizations from data compromise, such as weak passwords and authentication methods, malware, and poor self-detection. Security as a shared responsibility New rules focus on helping organizations understand their business partners PCI DSS responsibilities to ensure cardholder data security The PCI DSS self-assessment questionnaires (SAQs) are validation tools intended to assist merchants and service providers report the results of their PCI DSS self-assessment. The different SAQ types relevant for PCI DSS Version 3. are shown in the table below to help you identify which SAQ best applies to your organization. Detailed descriptions for each SAQ are provided within the applicable SAQ. SAQ A A-EP B B-IP C-VT C PPE- HW Description Card-not-present merchants (e-commerce or mail/telephone-order) that have fully outsourced all cardholder data functions to PCI DSS compliant third-party service providers, with no electronic storage, processing, or transmission of any cardholder data on the merchant s systems or premises. Not applicable to face-to-face channels. E-commerce merchants who outsource all payment processing to PCI DSS validated third parties, and who have a website(s) that doesn t directly receive cardholder data but that can impact the security of the payment transaction. No electronic storage, processing, or transmission of any cardholder data on the merchant s systems or premises. Applicable only to e-commerce channels. Merchants using only: Imprint machines with no electronic cardholder data storage; and/or Standalone, dial-out terminals with no electronic cardholder data storage. Not applicable to e-commerce channels. Merchants using only standalone, PTS-approved payment terminals with an IP connection to the payment processor, with no electronic cardholder data storage. Not applicable to e-commerce channels. Merchants who manually enter a single transaction at a time via a keyboard into an Internet-based virtual terminal solution that is provided and hosted by a PCI DSS validated third-party service provider. No electronic cardholder data storage. Not applicable to e-commerce channels. Merchants with payment application systems connected to the Internet, no electronic cardholder data storage. Not applicable to e-commerce channels. Merchants using only hardware payment terminals that are included in and managed via a validated, PCI SSC-listed PPE solution, with no electronic cardholder data storage. Not applicable to e-commerce channels. pg. 9

10 D SAQ D for Merchants: All merchants not included in descriptions for the above SAQ types. SAQ D for Service Providers: All service providers defined by a payment brand as eligible to complete a SAQ. What Happens if I Don t Comply with PCI Standards? Merchants and vendors who do not comply with applicable PCI standards expose themselves to the risk of data breaches. If you handle both cardholder data and personally identifiable information you greatly increase the likelihood of becoming a target for data breaches. A data breach could increase the chances for lawsuits, reputational damages, government fines and many other consequences. For example, in 03, a major retail corporation experienced a payment card breach that resulted in a 46 percent decline in profit. Another key benefit of following the PCI standards is that it could lead you to be better prepared for other regulatory audits such as HIPAA, SOX, etc. PCI in Healthcare As healthcare costs continue to increase, patient payment responsibility for healthcare bills has also increased. More and more patients are being forced to cover medical payments on credit card accounts. In addition to this, the healthcare industry has started moving toward electronic transactions to improve billing efficiency. For both of these reasons, the use of payment cards in healthcare is drastically increasing. Payment cards are becoming a common payment method for consumer-to-provider, consumer-to-payer and payer-to-provider payments. When providers and payers accept payment cards, they expose themselves to increased security risk, and at a minimum they must ensure that they maintain compliance with all applicable PCI standards. What s New in Payment Card Technology? With the recent breaches in the U.S., many merchants are trying to understand how to protect against these risks. No one solution provides a silver bullet but taken together, PPE, tokenization and EMV offer a strong defense against today s threats. What is EMV? EMV, often referred to as chip and PIN, is slowly gaining traction in the United States. Conceived in 994 and formalized in 999 by Europay, MasterCard and Visa, EMV is a framework that calls for integrating a microprocessor or chip into an otherwise normal credit card. This microprocessor allows for functionality that normal credit cards could not have. The benefits of EMV include: Fraud protection In the event of a breach, card-present fraud is likely to be eliminated. (Please note that card-not-present transactions are not made more secure by this technology. Card-not-present includes online transactions.) pg. 0

11 Liability shift Details vary by merchant, but as of October 05, a merchant who has not implemented EMV may be financially liable for any card-present fraud that could have been prevented with the use of EMV at the point-of-sale (POS). An EMV transaction occurs a little differently than normal transactions. Instead of simply swiping a card, a consumer must dip or insert their card into a PIN device, and enter a PIN before a transaction is processed. It is important to note that using EMV does NOT secure credit card data; it simply provides assurances to the merchant and financial institutions that have it in place that the user of a credit card is the true owner of the card. It is important for healthcare organizations to prepare now for the liability shift coming in October 05 by implementing an EMV Solution, and to start educating consumers on the eventual acceptance of chip cards. What about Mobile Payments? Consumers have adopted mobile technology as a means of making payments. Mobile payment capabilities offer convenient and frictionless payments and provide a simple and friendly experience. Consumer convenience and preferences is making an impact on healthcare organizations today. Healthcare organizations that recognize this are benefitting by delivering a smoother consumer experience and collecting payments across more channels, faster. However, mobile payments create major risks to the healthcare industry from a security and compliance perspective. The most significant of these risks is a compromised device that has been taken over by malware that circumvents the security of the device and allows hackers access to the mobile device s data. A second important risk is the fact that mobile devices are portable, making it easy for these devices to be removed from a secured environment to a location where a malicious individual can work to gain access. Finally, mobile technology is still relatively new, and we are still learning about the potential vulnerabilities contained within mobile operating systems and applications. To combat these risks when it comes to accepting mobile payments, PCI has issued mobile guidance documentation for merchants seeking to accept payments on a mobile device within their environment, as well as guidance to developers who are designing mobile solutions. PCI s preferred solution for accepting payments via mobile devices is the use of a validated PPE solution. pg.

12 Furthermore, PCI recommends the following guidelines for merchants: ) Prevent unauthorized physical device access (physically lock or tether the device) ) Prevent unauthorized logical access (restrict who can use the device, set a password or code to unlock the device, and implement encryption of the disk drive) 3) Protect the device from malware (use security software, install only trusted software) 4) Ensure the mobile device is in a secure state (scan devices with security software, do not jailbreak or root the device) 5) Disable unnecessary device functions (turn off cell data, Bluetooth or NFC if not needed) 6) Detect loss or theft (mark the device with a unique identifier, set GPS boundaries for the device, set periodic re-authentication of the user) 7) Ensure secure disposal of old devices (remove any business identification, contract a vendor to securely dispose of the device) What Impact does Apple Pay have on Healthcare? The number of merchants accepting Apple Pay has grown significantly since its initial release in September 04. Consumer adoption of this payment type has increased rapidly as well, with major retailers reporting up to a 400 percent increase in Apple Pay transactions. The success of Apple Pay can largely be attributed to Apple s consumer-first approach product design. The role of the consumer in the healthcare payments process is growing rapidly. Approximately 0 percent of consumers in the U.S. have unpaid healthcare bills due to confusion in the payments process, which will only grow as more and more consumers are enrolled in high deductible health plans. As a result of this, healthcare organizations need to adopt Apple s consumer-first approach. Apple Pay is available in both retail and ecommerce environments. In a retail environment (In Store Apple Pay), credit card reading devices leverage near-field communication (NFC) to process the payment. Near field communication (NFC) is a technology that enables mobile devices and contactless chip cards to establish radio communication with payment processing devices by touching them together or bringing them near each other. Digital wallet capabilities like Apple Pay can process payments on NFC-enabled devices. In an ecommerce environment, consumer-facing mobile applications can leverage In App Apple Pay to process payments. In App Apple Pay allows ios users to make payments using compatible mobile devices. pg.

13 The payment is processed using Visa's PayWave, MasterCard's PayPass, American Express's ExpressPay, and Discover s D-PAS contactless payment technologies. In both In Store and In App Apple Pay, public key encryption and tokenization are used to secure the payment card data. By accepting Apple Pay at both the point of service, as well as via a patient-facing mobile application, healthcare organizations can provide consumers with a simple, easy, and convenient method of making their payments. Point-to-Point Encryption Almost all healthcare organizations now accept payment cards as a payment method. While expanding and accepting different payment methods is important to ensuring a successful business, it does not come without added risk. Over the last 4 months, several organizations have made headlines due to data breaches that resulted in millions of credit card numbers being exposed. These breaches cause both financial and reputational risk for an organization. Combating these security threats can be a challenge, but employing a solution that leverages Point-to-Point Encryption (PPE) can both protect networks from data exposure and reduce the applicable controls of the PCI DSS. PPE is a methodology for securing credit card data by encrypting it from the time a card is swiped or keyed until it reaches the payment processor where it is decrypted. When implemented properly, these types of solutions make payment card transactions more secure by preventing the theft of credit card data while unencrypted on a POS device, or in transit. Merchants large and small face the high risk of a data breach, most frequently caused by inadequate security controls or insecurely developed and deployed applications, which leak or allow access to sensitive cardholder data. Security professionals, service providers, application developers and hardware manufacturers are working across a number of security domains to address the data security needs of merchants. One of the leading solutions intended to address the security of cardholder data in the merchant network is point-to-point encryption. Point-to-point encryption is designed to encrypt cardholder data at the time of swipe or keyed point-ofinteraction (POI) utilizing an encryption key that is built in to the POI. Once encrypted, sensitive cardholder data is not decrypted until it arrives at a secured end point, typically an acquirer, processor or gateway. In a well-designed PPE workflow, the merchant has no access to cryptographic keys or the decryption process. By encrypting cardholder data at the POI, merchants can significantly reduce the risk of a data breach and the scope of PCI DSS compliance requirements. pg. 3

14 InstaMed Healthcare Payment Solutions InstaMed engaged Coalfire Systems Inc. (Coalfire), a respected Payment Card Industry (PCI) Payment Application Qualified Security Assessor (PA-QSA) Company, to conduct an independent technical assessment of InstaMed. Coalfire conducted assessment activities, including technical testing, an architectural assessment and a compliance assessment. In the following document, Coalfire will describe how InstaMed, integrated with the PCI PIN Transaction Security (PTS) approved MagTek secure payment card devices for PPE, can reduce the number of applicable PCI DSS controls when properly configured using InstaMed s Implementation Guide. Additionally, we will describe how InstaMed Payments reduces scope for the ecommerce implementations, as well as supports additional cardholder data input and processing methods that were introduced in 05 and were reviewed by Coalfire. The reduction of scope applies to both vendors that develop payment application as well as Merchants that utilize the InstaMed solution. Cardholder Data Environment Summary The PCI DSS guidelines require compliance within a merchant s cardholder data environment (CDE), which includes all systems, connecting systems, and devices that store, transmit, or process cardholder data. To reduce the scope of PCI DSS compliance requirements a merchant can segment its network in order to separate the systems that store, transmit or process cardholder data from those that do not. This method removes systems that are unrelated to payment card processing from PCI DSS scope. To further reduce scope, a merchant can implement PPE to isolate the CDE to the POI. Implementing PPE can have a significant impact on the control applicability within a merchant s CDE. PPE encrypts cardholder data when the card is swiped or keyed at the POI, then transmits it to an outside gateway processor (in this case, InstaMed) for decryption. When implemented correctly, PPE logically segments the encrypted data that passes across the network, since the merchant does not access this data. This process reduces the need to utilize network segmentation to remove systems from CDE scope. Finally, since the cardholder data must be decrypted, most PPE devices tie the merchant to the gateway processor (again, in this case, InstaMed) in order to complete the payment transaction. It s important to mention that with the new ecommerce implementations available in the latest InstaMed release (05), CDE scope would vary for both merchants and vendors. In some scenarios CDE scope would not be limited by the POI, however the scope of the CDE will still be greatly reduced. We will review all implementations in details further in the whitepaper. pg. 4

15 About InstaMed Solutions Integrating with InstaMed can consist of various solution options for merchant initiated transactions and ecommerce transactions. For merchant initiated transactions at the POI, MagTek s devices can be configured for user authenticated login, single sign on (SSO) to InstaMed Online, or leveraged via InstaMed Connect.NET API. All cardholder data that is captured by the MagTek devices is encrypted when the merchant or cardholder processes a swipe, keyed, NFC, or EMV transaction. InstaMed decrypts and transmits the cardholder data to the appropriate payment network to authorize and complete the transaction. For ecommerce transactions, card reader devices are not in scope. Rather, the cardholder data is captured in an online environment. Merchant Initiated and Self-Service Kiosk transactions Device Support Merchant PCI Compliance Vendor PCI Compliance User Interface Vendor Development Effort Postback InstaMed Online* InstaMed Connect Web Services InstaMed Connect.NET API Single Sign-On to InstaMed Online* Inherent support Inherent support Inherent support for Inherent support for for MagTek for MagTek secure MagTek secure devices MagTek secure devices secure devices devices (See (See Appendix D) (See Appendix D) (See Appendix D) Appendix D) High scope Low scope High scope reduction High scope reduction reduction reduction N/A Low scope High scope reduction High scope reduction reduction InstaMed User Vendor User Vendor User Interface InstaMed User Interface w/ Interface Interface w/ configurability configurability Low High Low Low EOD File (batch) Web Service Web Service response EOD File (batch) or or Webhook response (realtime) (real-time) Webhook (real-time) (real-time) *Self-Service Kiosk scenario not supported. pg. 5

16 ecommerce transactions Device Support Merchant PCI Compliance Vendor PCI Compliance User Interface Vendor Development Effort Postback In App Apple Pay Single Sign-On to InstaMed Patient Portal Client Side Encryption InstaMed Connect Web Services InstaMed Patient Portal N/A N/A N/A N/A N/A High scope reduction High scope reduction Medium scope reduction Low scope reduction High scope High scope Medium scope Low scope reduction reduction reduction reduction Vendor User InstaMed User Vendor User Vendor User Interface Interface w/ Interface Interface configurability Low Low Low High Low Web Service EOD File (batch) Web Service Web Service response or Webhook response (realtime) response (real-time) (real-time) (real-time) High scope reduction N/A InstaMed User Interface w/ configurability EOD File (batch) or Webhook (real-time) Deployment Scenarios InstaMed solutions can be deployed in multiple scenarios by vendors or merchants. ) Merchant Initiated and Self-Service Kiosk Scenarios: Merchant initiated transaction. Currently, the following scenarios are supported: a. Merchant logs in to InstaMed Online directly through their web browser. Card is inputted through the card reader device (either swipe, tap, Manual entry or EMV) and is immediately encrypted. This data is then further sent to the processor and there is no way for the merchant or vendor to access encrypted data locally. Please refer to Figure for a detailed description of the data flow. Scope reduction for this scenario is further described in Appendix A. b. Vendor s application is integrated to InstaMed Connect.NET API. Card is inputted through the card reader device (either swipe, tap, Manual entry or EMV) and is pg. 6

17 immediately encrypted. This data is sent directly to the card processor and there is no way for the merchant or vendor to access encrypted data locally. To limit PCI scope, keyed payments should be prevented from being entered into the vendor s application. Please refer to Figure for a detailed description of the data flow. Scope reduction for this scenario is further described in Appendix A. c. Vendor s payment application is integrated via Single Sign-On to InstaMed Online. Card is input through the card reader device (either swipe, tap, or EMV) or is keyed into InstaMed Online, and is immediately encrypted. This data is sent directly to the card processor and there is no way for the merchant or vendor to access encrypted data locally. This gives the merchant the flexibility to choose their device, while reducing the vendor s PCI scope. Please refer to Figure 3 for a detailed description of the data flow. Scope reduction is further described in Appendix A. d. Vendor s application is a self-service kiosk with a card reader. Card is inputted through the card reader device (either swipe, tap, Manual entry or EMV) and is immediately encrypted. This data is sent directly to the card processor and there is no way for the merchant or vendor to access encrypted data locally. To limit PCI scope, keyed payments should be prevented from being entered into the vendor s application. Please refer to Figure for a detailed description of the data flow. Scope reduction for this scenario is further described in Appendix A. ) ecommerce Scenarios: Consumer initiated transactions require merchant to configure ecommerce the solution based on their needs. Currently the following methods of card input on the customer device are supported: a. Apple Pay Scenario: Card payments are made via In App Apple Pay with any ios based mobile device using any Vendor developed application leveraging InstaMed. In this scenario no cardholder data is inputted in the application and the card number exchange happens between Apple s partner Issuing bank and the InstaMed servers. The ios device operates only with tokens. Since no cardholder data is flowing through the merchant s environment and there is no data persisting on the mobile device, the PCI DSS scope is significantly reduced. InstaMed then processes data directly and no cardholder data is ever stored neither on the mobile device nor in the merchant s environment. Please refer to Figure 4 for a detailed description of the data flow. b. Single Sign-On Scenario: Card payments made through the web or a mobile device with a Vendor developed application. In this scenario cardholder data is inputted in the application forms pulled from the PCI DSS compliant InstaMed hosted webserver (which pg. 7

18 was validated as part of the service provider validation). Since forms do not persist on a mobile device merchants can reduce their PCI DSS scope (details are provided in Appendix B). Payment information is sent back to vendor either via real-time webhook or via batch EOD file. Please refer to Figure 5 for a detailed description of the data flow. c. Client Side Encryption Scenario: Card payments made through the web or a mobile device with a Vendor developed application installed using InstaMed s Client Side Encryption. In this scenario cardholder data is inputted in the application forms hosted on the merchant s webserver. However, the data is immediately encrypted in the application similar to how TLS encryption works. This allows merchant and vendor to reduce the PCI DSS scope (details are provided in Appendix C). Please refer to Figure 6 for a detailed description of the data flow. d. Web Services Scenario: Card payments can be submitted to the merchant using web services. In this scenario cardholder data is inputted in the application forms hosted by the merchant and the data is submitted to the InstaMed servers using TLS encryption while in transit. Please refer to Figure 7 for a detailed description of the data flow. e. Standalone with Payment Notification Scenario: Card payments made through the web or mobile device directly into the InstaMed Patient Portal. In this scenario cardholder data is inputted in the application forms pulled from the PCI DSS compliant InstaMed hosted webserver (which was validated as part of the service provider validation). Payment information is sent back to vendor either via real-time webhook or via batch EOD file. Please refer to Figure 8 for a detailed description of the data flow. The data flow diagrams below depict InstaMed workflows for different scenarios mentioned above. pg. 8

19 Network and Dataflow Diagrams for the Implementation Scenarios. For the InstaMed Online - Merchant Initiated Scenario Figure : Direct login to InstaMed Online with cardholder data entry via MagTek s devices Typical sale transaction ) Merchant launches web browser and logs in to InstaMed Online. ) Merchant initiates payment in InstaMed Online. 3) InstaMed Online engages credit card device. 4) Cardholder data is encrypted at the POI and transmitted to the InstaMed Platform. 5) InstaMed decrypts the cardholder data using MagTek Magensa Services, then repackages the data. 6) InstaMed transmits the unencrypted cardholder data to the payment network via TLS (versions. and. are supported). 7) The payment network transmits a response (approval or decline) back to InstaMed. 8) InstaMed forwards the response to the device. 9) If EMV, the device approves or declines the transaction and sends the response back to InstaMed. pg. 9

20 For the Integrated Merchant Initiated and Self-Service Kiosk Scenario Figure : Integrated workflow with cardholder data entry via MagTek s devices Typical sale transaction ) Merchant launches vendor application. ) Merchant initiates payment in vendor application. 3).NET API engages credit card device. 4) Merchant taps, inserts (DynaPro), or swipes payment card (DynaPro, Dynamag, udynamo or IPAD) or keys in (IPAD or DynaPro) card data. 5) Card data is encrypted at the POI and transmitted via the.net API to InstaMed Connect. 6) InstaMed decrypts the card data using MagTek Magensa Services, then repackages the data. 7) InstaMed transmits the unencrypted card data to the payment network via TLS (versions. and. are supported). 8) The payment network transmits a response (approval or decline) back to InstaMed. 9) InstaMed forwards the response to the device through the.net API. 0) If EMV, the device approves or declines the transaction and sends the response back through the.net API to the vendor application. pg. 0

21 For the Merchant Initiated - Single Sign-On Scenario with Web Services Figure 3: Integrated workflow with Single Sign-On Scenario with Web Services Typical sale transaction ) User logs on to vendor application and initiates payment from vendor application. ) Vendor application makes Single Sign-On authentication request to InstaMed. 3) InstaMed sends back Single Sign-On authentication response token. 4) Vendor application passes payment transaction to InstaMed with SSO token. 5) InstaMed receives payment request and logs user on to requested page using SSO token, prepopulating data passed in request. 6) User clicks button on InstaMed screen to engage device. 7) Cardholder taps, inserts, swipes card or keys in cardholder data. 8) Cardholder data is encrypted at the POI and transmitted to InstaMed. 9) InstaMed decrypts the cardholder data using MagTek Magensa Services, then repackages the data. 0) InstaMed transmits the unencrypted cardholder data to the payment network via TLS (versions. and. are supported). ) The payment network transmits a response (approval or decline) back to InstaMed. ) InstaMed displays payment receipt to user. 3) Response is received using webhook. pg.

22 Typical void or refund ) User logs on to vendor application. ) User initiates void or refund from vendor application. 3) Vendor application sends request to InstaMed Connect. 4) InstaMed Connect processes void or refund and sends response back to vendor application. For the ecommerce In App Apple Pay Scenario Figure 4: Mobile Application workflow with Apple Pay processing implemented. When the user presses Apple Pay button the App performs the following: ) Create a payment request including a. Amount, b. Apple Pay merchant ID, c. Description. ) Initializes Apple Pay UI Controller with the payment request. 3) Implements Callback method. 4) Hands control to Apple Pay UI Controller. 5) Apple Pay UI is displayed. The user selects the card and confirms with the fingerprint scanner. 6) Apple Pay invokes the callback method with the encrypted data block. 7) App sends encrypted data block to InstaMed to convert it to a single use token. 8) App sends single use token with payment request to InstaMed. pg.

23 9) InstaMed decrypts the token and processes the payment and returns a response. 0) App receives response and displays receipt. For the ecommerce Single Sign-On Scenario Figure 5: ecommerce Single Sign-On from vendor application to InstaMed Patient Portal workflow Typical sale transaction ) Consumer initiates payment on vendor application. ) Vendor initiates a Single Sign-On authentication request to InstaMed Patient Portal. 3) InstaMed Patient Portal send vendor application Single Sign-On token. 4) Vendor sends information with Single Sign-On token to InstaMed Patient Portal. 5) InstaMed Patient Portal launches in browser window on consumer s device. 6) Consumer enters card data into InstaMed s application hosted in a PCI Level Compliant platform. 7) Card data is encrypted in the secure browser via TLS (versions. and. are supported) 8) InstaMed decrypts the data transmits the unencrypted card data to the payment network via TLS (versions. and. are supported). 9) The payment network transmits a response (approval or decline) back to InstaMed. 0) InstaMed displays payment receipt to consumer. pg. 3

24 For the ecommerce - Client Side Encryption Scenario Figure 6: ecommerce workflow with Client Side Encryption Scenario Typical sale transaction ) Consumer includes encrypt.js on their web page and calls InstaMed.init(). ) Consumer adds encrypted-field-name="cardnumber", encrypted-field-name="cvn", encryptedfield-name="cardexpdate" to their cardnumber, cvn, and expdate fields. 3) When the user submits the form, encrypt.js automatically encrypts and masks required fields and sends them to the Vendor Server. 4) Consumer adds logic on the server side to validate card number and card expiration and if the user entered data is valid, the consumer s/vendor s server sends the encrypted card number, cvn, and cardexpdate to InstaMed in the "encrypted-cardnumber," "encrypted-cvn" and "encrypted-cardexpdate" fields via InstaMed Connect Web Services. 5) InstaMed then processes the payment by performing the decryption of the cardnumber, cvn and cardexpdate on the server side and processes the payment pg. 4

25 For the ecommerce Web Services Scenario Figure 7: ecommerce Vendor application InstaMed Connect Web Services Typical sale transaction ) Consumer enters card data via mobile or web browser into vendor application. ) Card data is transmitted to InstaMed Connect 3) InstaMed Connect transmits the card data to the payment network via TLS (versions. and. are supported). 4) The payment network transmits a response (approval or decline) back to InstaMed Connect. 5) InstaMed Connect sends response back to vendor application pg. 5

26 For the ecommerce InstaMed Patient Portal Scenario Figure 8: ecommerce Stand-alone InstaMed Patient Portal Typical sale transaction ) Consumer launches InstaMed Patient Portal in mobile or web browser. ) Consumer enters card data into InstaMed s application hosted in a PCI Level Compliant platform. 3) Card data is encrypted in the secure browser via TLS (versions. and. are supported) 4) InstaMed decrypts the data transmits the unencrypted card data to the payment network via TLS (versions. and. are supported). 5) The payment network transmits a response (approval or decline) back to InstaMed. 6) InstaMed displays payment receipt to consumer. pg. 6

27 Audience This white paper has three target audiences: ) Merchants and service providers interested in reducing the number of applicable PCI DSS controls. ) Vendors implementing applications used by merchants to accept or record credit card payments 3) The QSA and Internal Audit community that is evaluating InstaMed or the impact on scope of PCI DSS compliance in general on behalf of merchant or service provider clients. Assessment Scope Coalfire assessed the critical elements that validate the security and effectiveness of InstaMed. As part of this assessment, Coalfire conducted in-depth analysis of essential compliance fundamentals for merchants, service providers and the QSA community. Methodology Coalfire uses industry best practices in its assessment and testing methodologies, including standard audit methods. Coalfire conducted technical lab testing with systems installed in the Coalfire lab, examination of the MagTek device integration with InstaMed Online, transactional testing, device assessment and forensic analysis. Merchant PCI Compliance Scope There will always be certain controls for PCI DSS compliance that must be independently assessed in any merchant s environment. PCI DSS compliance will always apply to a merchant that transmits, processes or stores cardholder data anywhere in its physical environment. By properly implementing InstaMed Patient Payments and the InstaMed Patient Portal, a merchant can potentially lower the amount of applicable controls during a PCI DSS compliance audit. Technical Security Assessment Coalfire s technical security assessment included a comprehensive set of administration, technical and physical control requirements for each deployment scenario (user authenticated login or SSO to InstaMed Online). During this assessment, Coalfire validated that InstaMed adheres to the applicable compliance control requirements for potentially reducing the applicable controls during a merchant s PCI DSS compliance audit. The assessment included the following components: InstaMed Online, InstaMed Connect, or InstaMed Connect.NET API MagTek secure readers: o MagTek DynaPro Debit/Credit MSR with MagneSafe (PCI PTS 3.x approved, EMV Compatible, NFC Compatible) pg. 7

28 o MagTek IPAD Debit/Credit MSR with MagneSafe (PCI PTS.x approved) o MagTek Dynamag MSR USB Keyboard Emulator MagneSafe swipe o MagTek Dynamag MSR USB HID MagneSafe swipe o MagTek udynamo MSR headphone jack for mobile devices (also includes USB for Windows/Mac PCs) o MagTek ImageSafe MSR USB HID device that supports check processing and EMV. Payment through the website using Apple Pay o Apple iphone 6 was used for testing Payment through the website using Single Sign-On o Apple iphone 6 and Samsung Galaxy S4 were used for testing Payment through the website using Client Side Encryption o Apple iphone 6 was used for testing Payment through the website using Web Services Impact on Merchant s and Vendor s PCI DSS Audit Applicable Controls PCI DSS compliance will always apply to a merchant that transmits, processes or stores cardholder data anywhere in its physical environment. However, by properly implementing InstaMed Patient Payments and the InstaMed Patient Portal, a merchant may be able to reduce the amount of applicable controls during a PCI DSS compliance audit. NOTE: The reduction of applicable controls introduced in the table below only applies to PTS-approved (.0 or greater at a minimum) devices such as the MagTek IPAD Debit/Credit MSR and MagTek DynaPro Debit/Credit MSR that are supported by InstaMed. Reduction of applicable controls for all other supported devices (Dynamag and udynamo) is entirely at the discretion of a merchant s acquiring bank during PCI DSS audits. pg. 8

29 Summary Charts of Potential Impact on Merchant Audit Applicable Controls Table for each Implementation Scenario. In the charts below we show how a particular implementation scenario impacts requirements of the PCI DSS standard. This is a high level overview that is supported with detailed review in the Appendix section. Merchant Initiated or Self-Service Kiosk payments using InstaMed Online, InstaMed Connect Web Services or InstaMed Connect.NET API In this scenario cardholder data is inputted through the attached Card reader and would support multiple methods of input, including: Swipe, manual entry, EMV, NFC. Depending on the model of the reader attached, multiple methods of cardholder data input are supported, however data is always immediately encrypted at the moment of input. PCI DSS requirement Major Impact Moderate Impact Minor Impact X X 3 X 4 X 5 X 6 X 7 X 8 X 9 X 0 X X X The application is not in scope for the PA-DSS requirements and significantly reduce the amount of PCI- DSS requirements, therefore merchants and vendors might be eligible for SAQ attestation, however that should be decided by the acquirer. For detailed information on which requirement was impacted please refer to the Appendix A: PCI DSS requirements impact for InstaMed Online. pg. 9

30 ecommerce In App Apple Pay via InstaMed Connect In this scenario Merchants do not operate with credit cards, and instead have access to tokens only. This technology never requires credit card data to be inputted in the application. Table below shows the impact of this solution for the vendor: PCI DSS requirement Major Impact X X 3 X 4 X 5 X 6 X 7 X 8 X 9 X 0 X X X This scenario is the least impactful for the merchant and would keep their application out of scope of PA- DSS as well as significantly reduce scope of PCI DSS requirements for the merchant and vendor. pg. 30

31 ecommerce InstaMed Patient Portal with or without Single Sign-On In this scenario cardholder data is inputted by the end user through the merchant s application that displays InstaMed content in the frame and only support manual card input. PCI DSS requirement Major Impact Moderat e Impact The application is not in scope for the PA-DSS requirements and significantly reduce the amount of PCI- DSS requirements, therefore merchants and vendors might be eligible for SAQ attestation, however that should be decided by the acquirer. Minor Impact X X 3 X 4 X 5 X 6 X 7 X 8 X 9 X 0 X X X For detailed information on which requirement was impacted please refer to the Appendix B: PCI DSS requirements impact for payment through the website using Single Sign-On. pg. 3

32 ecommerce - Client Side Encryption In this scenario cardholder data is inputted by the end user through the merchant application that is creating forms using InstaMed encryption libraries that would perform encryption on the manually typed in cardholder data. PCI DSS requirement Major Impact Moderate Impact Minor Impact X X 3 X 4 X 5 X 6 X 7 X 8 X 9 X 0 X X X The application is not in scope for the PA-DSS requirements and significantly reduce the amount of PCI- DSS requirements, therefore merchants and vendors might be eligible for SAQ attestation, however that should be decided by the acquirer. For detailed information on which requirement was impacted please refer to the Appendix C: PCI DSS requirements impact for payment through the website using Client Side Encryption. pg. 3