Central Michigan University Payroll and Travel Services 3

 Merchant Account Manager  PCI DSS – What is it?  Cardholder Data vs Payment Data  Security Guidelines  Incident Response Plan  Upcoming Changes  Questions 4

All departments accepting credit card payments are required to designate someone as the Merchant Account Manager. They will be responsible for the following… 5

Responsibilities  You will be the main point of contact for all changes and updates to credit card processing. You are responsible for sharing this information with your dept.  You are responsible for reporting/requesting any changes to online reporting access.  Keep an updated list of employees who have access to cardholder data. This includes databases, filing cabinets, offices, etc.  Contact Treasury and Investment Services to eliminate the merchant account if you no longer wish to accept credit cards.  Reporting any changes to your credit card process to Treasury and Investment Services. 6

 Read, understand and follow the CMU Merchant Sites Security Guidelines. Make sure that all employees involved in the processing of credit card transactions do the same.  Recognize the importance of credit card security and make sure that your department is processing transactions in a secure manner. Educate other individuals in your department about the importance of credit card security.  In the event of a credit card breach/compromise, you will be responsible for reporting the issue to the CMU Security Incident Response Team (CMU-SIRT). You will be responsible for assisting with the investigation and resolving the incident. It is understood that it is the department’s responsibility to cover any fines/fees charged by the credit card companies for fraud related to negligence. 7 Who in your department should be responsible for this?

 ALL departments that accept credit cards (regardless of the volume of payments processed and the method used to process the payment) are required to comply with Payment Card Industry Data Security Standard (PCI DSS). 8 For more information about PCI DSS visit

What is PCI Compliance? The PCI Data Security Standard represents a common set of industry tools and measurements to help ensure the safe handling of sensitive information. Initially created by aligning Visa's Account Information Security (AIS)/Cardholder Information Security (CISP) programs with MasterCard's Site Data Protection (SDP) program, the standard provides an actionable framework for developing a robust account data security process - including preventing, detecting and reacting to security incidents. 9 For more information about PCI DSS visit

 All merchants will fall into one of the four merchant levels based on transaction volume over a 12-month period. 10

11 Merchant Level MasterCardVisa Merchant Requirements Level 1 >6 MM trans. Regardless of channel, or Hacked/attacked in past, or Otherwise ID’d by V/MC >6 MM trans. Regardless of channel, or Hacked/attacked in past, or Otherwise ID’d by V/MC Report on Compliance (ROC) Quarterly scan showing no high vulnerabilities Level 2 Any e-commerce merchant processing between 150M and 6MM transactions per year Any merchant processing 1MM to 6 MM transactions per year. PCI self-assessment questionnaire (all “Yes” or “N/A”) Quarterly scan showing no high vulnerabilities Level 3 Any e-commerce merchant processing between 20M and 150M transactions per year Any e-commerce merchant processing between 20M and 1MM transactions per year PCI self-assessment questionnaire (all “Yes” or “N/A”) Quarterly scan showing no high vulnerabilities Level 4 All other merchants regardless of channel Compliance mandatory Validation Optional

 It is required in order to accept credit cards.  We want to protect our customers.  A security breach/compromise of cardholder data has many consequences. 1. Regulatory notification requirements 2. Loss of reputation 3. Loss of customers 4. Potential financial liabilities (regulatory and other fees and fines) 5. Litigation 12 For more information about PCI DSS visit

Build and Maintain a Secure Network Requirement 1Install and maintain a firewall configuration to protect cardholder data Requirement 2Do not use vendor-supplied defaults for system passwords and other security parameters Protect Cardholder Data Requirement 3Protect stored cardholder data Requirement 4Encrypt transmission of cardholder data across open, public networks Maintain a Vulnerability Management Program Requirement 5Use and regularly update anti-virus software Requirement 6Develop and maintain secure systems and applications 13 For more information about PCI DSS visit

Implement Strong Access Control Measures Requirement 7Restrict access to cardholder data by business need-to-know Requirement 8Assign a unique ID to each person with computer access Requirement 9Restrict physical access to cardholder data Regularly Monitor and Test Networks Requirement 10Track and monitor all access to network resources and cardholder data Requirement 11Regularly test security systems and processes Maintain an Information Security Policy Requirement 12Maintain a policy that addresses information security 14 For more information about PCI DSS visit

CMU has already done many things to comply.  Many departments are using PCI approved service providers.  Other departments have changed their processes.  Providing credit card security awareness training.  Updated contracts to include PCI language.  Updated policies and procedures. 15 For more information about PCI DSS visit

PROTECT CARDHOLDER DATA!!!  Every department that accepts credit card payments needs to evaluate their current credit card process and verify that they are doing everything possible to ensure the security of cardholder data.  Two truths about PCI Compliance 1.It is very possible that your costs for card acceptance will go up. 2.You may have to change the way you process payment cards. 16 For more information about PCI DSS visit

 Not all information related to a credit card transaction need to be protected.  There is cardholder data and payment data.  Payment data should be kept for auditing purposes.  Cardholder data should not be stored. 17

 Payment data includes  Cardholder name  Transaction date  Last 4 Digits of credit card number  Authorization code  Card type  Amount This information should be stored for 3 years per the record retention schedule. 18

19 Cardholder Data – Should NOT be stored.

20  EuroPay MasterCard Visa (EMV) Technology or Chip and Pin  From October 2015, any US retailer taking payment with any of the major credit cards will be obliged to use chip and pin technology or accept full liability for any resulting fraud.  CMU Merchant Accounts that process card-present transactions must have EMV enabled devices. ▪ EMV enabled credit cards contain an embedded computer microchip that encrypts the credit card data while processing the transaction. ▪ Chip and pin enabled cards are either “dipped” into a terminal and the pin is physically entered by the cardholder or it can be “tapped” on the terminal if using radio-frequency identification technology. ▪ The combination of card validation using the chip and pin entry provides stronger protection against the fraudulent use of lost, stolen or counterfeit cards.

NEVER store CVV2 data (3 or 4 digit code found on the back of a card)  If you have this stored somewhere – DESTROY IT.  If it is stored in old records, you need to go back and DESTROY IT. In the event of a compromise, if you have this information, the severity of the compromise greatly increases. *If your terminal asks for this code and you would rather not be responsible for it, let me know and we can have your terminal reprogrammed to not ask for this code. 21

 Cardholder data – You do not need it, SO DON’T STORE IT.  Misconception - I need to keep the credit card number.  Process refund – There are other ways to do this. ▪ Ask the cardholder for their card number. ▪ You can get the credit card number off of the processors online reporting website. ▪ If you are using an approved service providers website, you do not need to cardholder data to process a refund. ▪ You can call the processor helpdesk for assistance.  Any other reasons you need cardholder data? 22 *Think about whether the storage of cardholder data and the business purpose it supports are worth the risk of having data compromised.

Take inventory of all the places you store cardholder data and destroy it especially if you have the CVV2 (3 or 4 digit code). 23

 If you are a terminal merchant, accept cardholder data by telephone, mail, or in person only, not through electronic mail.  All face-to-face transactions should have the payment card present and obtain a signature. Always verify that the card is valid and signed. Compare signatures and check for ID where possible and feasible. Never ask a chip and pin cardholder for their four digit pin – it is confidential and they must enter it themselves.  When it is necessary to store cardholder data prior to processing the transaction, it must be stored in a “secure” environment.  Secure environments include locked drawers, file cabinets, offices and safes.  All documentation containing cardholder data must be destroyed in a manner that will render them unreadable (cross-cut shredded) after the payment has been processed. 24 To see all Security Guidelines go to

 Cardholder receipts generated from a point-of-sale terminal must include only the last four digits of the account number. The expiration date must be excluded.  Merchant receipts generated from a point-of-sale terminal must exclude the card expiration date and should only have the last 4 digits of the account number. (beginning Oct 2008)  Transactions should be batched on a daily basis to get better rates and to clear out credit card transactions.  Access to cardholder information should be limited to only those individuals whose job requires such access. 25 To see all Security Guidelines go to

 Merchants are required, in good faith, to maintain a fair policy for the exchange and return of merchandise and for resolving disputes over merchandise and/or services purchased with a payment card. If a transaction is for non-returnable, non-refundable merchandise, this must be indicated on all copies of the sales draft before the cardholder signs it. A copy of your return policy must be displayed in public view.  Merchants should not, under any circumstances, pay any card refund or adjustment to a cardholder in cash. If cash is refunded and the cardholder files a dispute your department will bear the loss of income from the transaction.  Retain the payment data from all transactions and any original, signed documentation in a secure location for a minimum of 3 years per record retention guidelines.  Wherever possible, storage areas should be protected against destruction or potential damage from physical hazards, like fire or floods. 26 To see all Security Guidelines go to

 Under no circumstances should cardholder data be entered and stored on any computer database in the department unless it is part of a secure system that has been approved by Treasury and Investment Services.  Cardholder data must remain in the department processing the transaction. This information should never be distributed to another department.  All cardholder data and payment information should be classified as confidential. If it is necessary to send payment data to a third party it should be done by a secured courier or other delivery method that can be accurately tracked. 27 To see all Security Guidelines go to

 All employees involved in the processing of credit card transactions must read, understand and follow the CMU Merchant Sites Security Guidelines.  Duties within a department should be segregated so that one person does not perform processing from the beginning to the end of a process. For example, one employee should not be processing credit cards, recording the revenue and reconciling the accounts.  Treasury and Investment Services must be contacted if you are disposing of any credit card processing equipment. This includes terminals and computers used to process transactions. Questions? 28 To see all Security Guidelines go to

 Do not store cardholder data in student files.  Do not copy or distribute documents that has cardholder data on it.  If you are accepting cardholder data on a form, put the payment section at the bottom of the form. Once the payment is processed, cut the cardholder data off and destroy it (cross-cut shredded). 29 To see all Security Guidelines go to

 In the event that one or more credit cards have been compromised or appear to have been compromised, it is the responsibility of the department to inform the CMU Security Incident Response Team (CMU-SIRT) immediately.  If you receive a call from your approved service provider regarding an actual or suspected breach, contact Treasury and Investment Services ASAP.  A compromise can include documentation with cardholder data as well as cardholder data located on computer systems. 30

1. Contain and limit your exposure and contact CMU-SIRT ASAP. 2. An assessment of the situation will be made. 3. The CMU-SIRT will contact the appropriate parties (this includes our payment processor, CMU Police, the Associate VP of Financial Services and Reporting, Internal Audit, Public Relations and Marketing). 4. The Merchant Account Manager will need to be available for questions and will need to help complete the Incident Response Report. 5. Depending on the situation, a Forensic Investigation may be necessary. 6. Once the situation has been resolved, a meeting will be set up to go over your credit card process and changes may be made. 31

 Assign a Merchant Account Manager for your department.  Train other employees in your office that handle cardholder data the importance of security.  Review your current credit card process and make necessary changes to be secure.  Destroy cardholder data that is currently being stored. 32