New York University University Policies
|
|
- Lorena Cain
- 5 years ago
- Views:
Transcription
1 New York University University Policies Title: Payment Card Industry Data Security Standard Policy Effective Date: April 11, 2012 Supersedes: N/A Issuing Authority: Executive Vice President for Finance and Information Technology Responsible Officer: Executive Vice President for Finance and Information Technology Office Name: Office of the Bursar Policy The University is committed to safeguarding personal and account information conveyed in processing debit and credit card payments. Also, the privilege of accepting payment cards from the leading card brands depends upon compliance with specified security standards. To comply with these standards, it is the policy of the University that security standards relating to payment card transactions be specified and applied. Purpose of this Policy The purpose of this policy is to establish a framework for processing payment cards, to safeguard against the exposure and possible theft of cardholder data received by NYU, and to comply with the current Payment Card Industry Data Security Standard (PCI DSS) requirements. This policy does not address New York State laws or the laws of other states or jurisdictions that may apply to payment card transactions. Scope of this Policy This policy applies to the NYU schools and units that have access to cardholder data and to the people, processes and technology that handle cardholder data at or on behalf of NYU: any NYU school, unit, employee (full-time, part-time and temporary), student, volunteer, contractor, consultant, vendor, or other person or entity that processes, transmits, or stores cardholder data in a physical or electronic format for NYU or using NYU resources or that has access to the NYU cardholder data environment. All technical and operational system components, including software, computers and wired or wireless electronic devices, involved in processing cardholder data, whether owned or leased by NYU, are subject to PCI DSS and this policy. Background The Payment Card Industry Security Standards Council, which was founded by American Express, Discover, JCB International, MasterCard and Visa, has established stringent security requirements to safeguard credit or debit payment cardholder data called the Payment Card Industry Data Security Standard (PCI DSS). PCI DSS applies pursuant to contract to all entities that store, process or transmit cardholder data, including information printed on a card or stored on its magnetic stripe or chip and personal identification numbers entered by the cardholder. Compliance is enforced by the Council s founding members. In addition to PCI DSS, each payment card brand has defined its own specific requirements for compliance, validation and enforcement. Page 1 of 12
2 The University is required by contract to safeguard cardholder data, whether printed, stored or transmitted. Therefore, every NYU school/unit that accepts payment cards must be PCI DSS compliant. In addition, any affiliated or unaffiliated party involved with accepting or processing credit/debit card payments for goods or services on the University s behalf must be PCI DSS compliant and provide validation of its compliance to NYU. NYU is obligated to identify such parties responsibilities for securing cardholder data and monitor such parties PCI DSS compliance. This policy defines the framework to allow NYU to ensure that all cardholder data it receives is processed in compliance with the current PCI DSS and related security standards. All NYU schools/units accepting payment cards must comply with the security requirements involved with being a payment card merchant. All NYU schools/units that process payment card transactions also must comply with NYU s defined methodologies and acceptable technology. Complete cardholder data may not be transmitted, processed, or stored on any University-owned or University-controlled devices. The Office of the Bursar oversees NYU s method for accepting and processing payment card transactions as well as distribution of policies, procedures, and other guidance required under PCI DSS and ongoing maintenance of a the PCI DSS compliance program. All schools/units wishing to process payment card transactions are advised to visit the epayment website at for complete instructions and a template for the Business Plan required to be submitted for approval. The University Bursar will review a school/unit s completed Business Plan and, upon approval, will establish a specialized Merchant Account Number for the school/unit. The school/unit then becomes responsible for achieving and maintaining compliance with PCI DSS and this policy. The Policy Specifications set out in Section IV below are mandated to help meet PCI DSS. A glossary of certain terms used in this policy is provided in Appendix A. Policy Specifications I. General Requirements Schools/Units Accepting Payment Cards A. A school/unit desiring to accept payment cards must obtain advance approval from the University Bursar which will issue a specialized Merchant Account Number upon approval. B. Using the procedural templates available at the epayment web site ( a school/unit must prepare and maintain documented security procedures that clearly define information security responsibilities for all people within the school/unit who handle or will have access to cardholder data. C. Cardholder data is considered Restricted data under NYU s Data and Computer Security Policy ( and the Data Classification at NYU table ( with high institutional risk from disclosure. D. University Bursar approval is required before implementing software and installing equipment that processes, transmits, or stores cardholder data. Page 2 of 12
3 E. When processing payment card transactions, a school/unit must use only approved technologies. See Appendix B. F. A schools/unit with a Merchant Account Number must maintain and secure an inventory of payment card processing devices and implement a system to track removal or substitution of these devices. G. Appropriate facility entry controls must be used to limit and monitor physical access to systems in the cardholder data environment. i. Appropriately identify restricted areas with visible signage (e.g., Authorized Personnel Only). ii. All keys allowing access to restricted areas must be unique to the site. H. A school/unit processing payment card transactions must annually complete a Self Assessment Questionnaire (SAQ). The SAQ is a PCI-mandated attestation intended to allow each school/unit to demonstrate their compliance with the PCI DSS. II. General Requirements Employees with Access to Cardholder Data A. Access to system components and cardholder data must be limited to only those individuals whose job requires such access. Schools/units must ensure that: i. Each employee is given access to as little cardholder data as necessary to perform his or her job. ii. Employees are instructed not to share cardholder information with other employees unless deemed necessary by a supervisor. iii. All employees who are involved with the acceptance of payment cards must be trained on this policy and the applicable school/unit s procedures relevant to payment card processing. B. Relevant personnel must complete NYU Security Awareness Education (SAE) training. All schools/units must: i. Create and maintain a list of employees whose jobs expose them to cardholder data. ii. Send requests to the University Bursar to onboard personnel who need to take SAE training. iii. Ensure personnel attend NYU s SAE training upon hire or engagement and at least annually thereafter. C. This policy must be disseminated to all relevant persons and entities who must acknowledge at least annually that they have read this policy and the applicable school/unit s procedures. III. STORAGE of Sensitive Authentication Data and Cardholder Data A. Payment systems that involve receiving sensitive authentication data must have processes in place to delete such data after authentication and verify that it is unrecoverable. B. All systems that store sensitive authentication data after authorization must adhere to the following requirements: Page 3 of 12
4 i. The complete payment card number is not to be stored under any circumstances. ii. The card-validation code or value (three-digit or four-digit number printed on the front or back of a payment card) used to verify card-not-present transactions, and the personal identification number (PIN), or the encrypted PIN block is not to be stored under any circumstances. C. The Primary Account Number (PAN) must be masked when displayed (the first six and last four digits are the maximum number of digits permitted to be displayed). This must done through the following means: i. Truncation by the POS system. ii. If using a paper imprinter slip for card-present transactions and retention of the slip is necessary, the imprint slip should be photocopied after all digits of the PAN except the last four are masked. Merchant then can retain the photocopied version, but must cross shred the original copy. iii. If paper forms are used for card-not-present transactions (e.g., telephone and mail order) and retention of a section of the form is necessary, then the cardholder data section of the payment form must be removed and cross shredded. The form can be photocopied and retained after all digits of the PAN except the last four are masked. Merchants must cross shred the original copy. D. All paper and electronic media that contain cardholder data must be physically secured. Cardholder data that must be stored for business or legal reasons must be stored according to the NYU Policy on Retention and Destruction of Records ( and the Retention Periods for General Categories of Retainable Records ( Cardholder data storage should be kept to a minimum and retention time should be limited to that which is required for a business, legal, and/or regulatory purpose. E. All cardholder data must be kept in a locked filing cabinet in a secure area or a safe that is accessible only by employees whose jobs require that they have access to cardholder data. The filing cabinet or safe containing the cardholder data must be locked both during and after business hours. IV. TRANSMISSION of Sensitive Authentication Data and Cardholder Data A. Transactions processed using a standalone dial-out POS terminal must be settled daily. B. Unencrypted PANs must never be sent by end-user messaging technologies (e.g., or instant messaging). C. Each school/unit must maintain strict control over the internal or external distribution of any kind of media that contain cardholder data. All material moved from a designated secure area must be marked confidential, documented on a media removal tracking log, and transported by a document service such as Fed Ex or the U.S. Post Office with a tracking number. Page 4 of 12
5 D. No material containing cardholder data may leave the premises of the school/unit that accepted it for processing. V. DESTRUCTION of Sensitive Authentication Data and Cardholder Data A. All physical cardholder data (e.g., paper documents) that is deemed not essential must be properly destroyed. All electronic storage data also must be properly destroyed if there is no business or legal reason for which it should be kept. Proper means of destroying hard-copy material include physical destruction, such as shredding, incineration, or pulping hard copy materials, so that cardholder data cannot be reconstructed. Electronic cardholder data must be rendered unrecoverable via a secure wipe program in accordance with industry-accepted standards for secure deletion. B. If storage of cardholder data is necessary for business or legal purposes, portable media used to store cardholder data, including hard-copy material, must be stored in a locked cabinet. All electronic cardholder data must be encrypted and password protected. VI. Processing Using External Service Providers A. When cardholder data is shared with external service providers, procedures to manage these providers must be developed and maintained by the applicable school/unit utilizing their services. These procedures must include: i. Creating and maintaining a complete list of service providers who can access any POS system or any cardholder data, including companies or individuals who are not employees of NYU. ii. Coordinating with the University s Office of Purchasing Services & Contract Administration to obtain and maintain a written agreement with the service provider that includes the service provider s acknowledgement that it is responsible for the security of cardholder data that it stores, processes, or transmits. iii. Obtaining and monitoring each service provider s PCI DSS compliance status by requesting a copy of its annual Self Assessment Questionnaire (SAQ) or Report on Compliance (ROC). B. The process for engaging service providers must include proper due diligence prior to engagement. Merchants should liaise with the University s Office of Purchasing Services & Contract Administration to contract work only with PCI DSS compliant service providers and check the references of such providers. Contracts with external service providers must incorporate NYU s third party service requirements language. VII. Incident Management A. Anyone who learns of an actual or potential cardholder data security breach must immediately inform the school/unit Merchant Account Manager and the University Bursar. B. NYU will respond to and investigate any incident in which there is a risk that cardholder data has been accessed without authorization. Indications that such an investigation may be necessary include, but are not limited to, the following: Page 5 of 12
6 i. A computer or device involved in credit card processing is compromised. You may observe a virus or other malware installed on the system or that unauthorized configuration changes have been made that cannot be adequately explained. ii. Vulnerability is discovered that could be used to gain unauthorized access to cardholder data. iii. An external report is received that indicates that NYU may be a source of fraudulent transactions, or that cardholder data from NYU has been accessed without authorization. iv. Paper, tapes, usb-keys, laptops, or other media containing cardholder data have been lost or cannot be accounted for. v. Cardholder data has been discussed in public or overheard without authorization. vi. Any of the above occurs with a service provider or other third party involved in payment card processing for NYU. C. If a cardholder data security breach involving electronic resources is suspected, the NYU IT Security Information Breach Notification Procedure ( must be followed. You must notify the relevant school/unit Merchant Account Manager immediately to report the suspected breach. The school/unit Merchant Account Manager is required to report the suspected breach to ITS Technology Security Services and the University Bursar. D. In the event a cardholder data breach involving non-electronic resources (for example, paper documents) is suspected, you must notify the relevant school/unit Merchant Account Manager immediately to report the suspected breach. The school/unit Merchant Account Manager is required to notify the University Bursar. E. If you suspect credit card fraud, please follow the procedures outlined in the NYU Identity Theft Prevention Program ( VIII. Enforcement of On-Going Compliance A. Periodic reviews of safeguarding and storing of payment card information are conducted by the University Bursar, and payment card handling procedures are subject to audit by NYU Internal Audit, the Office of Compliance and Risk Management, and external auditors. In addition, NYU ITS Technology Security Services periodically conducts assessments of security controls put in place to safeguard technology implementations, including but not limited to periodic networkbased vulnerability scans. B. NYU schools/units with Merchant Account Numbers that do not comply with this policy and approved protection, storage, and processing procedures may lose the privilege to serve as a payment card merchant and to accept payment card payments. C. Individuals in violation of this policy are subject to the full range of sanctions. I. Related Policies and Legal Considerations The following University policies address topics that are related to this policy: Page 6 of 12
7 Policy on Responsible Use of NYU Computers and Data ( University Data Management Policy ( Data and Computer Security Policy ( Reference for Data and System Classification ( Data and System Security Measures ( Many states and countries have laws that apply to payment card transactions with which schools/units accepting payment cards for goods or services must comply. Current applicable New York State law is summarized in Appendix D. For further information regarding applicable law, schools/units accepting payment cards should contact the Office of General Counsel.. Appendices Appendix A: PCI DSS Definitions Appendix B: NYU Approved Payment Card Processing Technologies Appendix C: Roles and Responsibilities Appendix D: Other Applicable Law Page 7 of 12
8 Appendix A: PCI DSS Definitions 1. Cardholder Data: At a minimum, cardholder data consists of the full PAN. Cardholder data also may appear in the form of the full PAN plus any of the following: cardholder name, expiration date and/or service code. See the definition of Sensitive Authentication Data for additional data elements that constitute account data and may be transmitted or processed (but not stored) as part of a payment transaction. As generally used in this policy, cardholder data refers to all of the information specified above. 2. Cardholder Data Environment: The people, processes and technology that store, process or transmit cardholder data or sensitive authentication data, including any connected system components. 3. Payment Card: Any payment card, including debit cards, which is issued by one of the leading payment card brands or associations. 4. Merchant: Any person or entity (such as a school/unit) that accepts payment cards bearing the logos of any of the five founding members of PCI SSC (American Express, Discover, JCB, MasterCard or Visa) as payment for goods and/or services. 5. Payment Application Data Security Standard (PA DSS): Requirements and security assessment procedures that apply to software vendors and others who develop payment applications that store, process, or transmit cardholder data as part of authorization or settlement where these payment applications are sold, distributed, or licensed to third parties. This standard includes what a payment application must support to facilitate an entity s PCI DSS compliance. 6. Payment Card Industry Data Security Standard (PCI DSS): A comprehensive set of requirements established by the PCI SSC for enhancing payment account data security. It is a multifaceted standard that includes requirements for security management, policies, procedures, network architecture, software design, and other critical safeguard measures. 7. PCI Security Standards Council (PCI SSC): The organization founded by American Express, Discover, MasterCard, JCB and Visa that defines credentials and qualifications for assessors and vendors, as well as maintaining the PCI DSS. 8. Point of Sale (POS): Hardware and/or software used to process payment card transactions at merchant locations. 9. Primary Account Number (PAN): The composite number code of 14 or 16 digits embossed on a bank or payment card and encoded in the card's magnetic strip. The PAN identifies the issuer of the card and the account including part of the account number, and contains a check digit that verifies the authenticity of the embossed account number. 10. Report on Compliance (ROC): Report containing details documenting an entity s compliance status with the PCI DSS. 11. Self Assessment Questionnaire (SAQ): Tool used by any entity to validate its own compliance with the PCI DSS. 12. Sensitive Authentication Data: Security-related information including, but not limited to, card validation codes/values (e.g., three-digit or four-digit value printed on the front or back of a payment card, such as CVV2 and CVC2 data), full magnetic-stripe data, PINs, and PIN blocks) used to authenticate cardholders and/or authorize payment card transactions. Sensitive authentication data must not be stored after authorization. Page 8 of 12
9 Appendix B: NYU Approved Payment Card Processing Technologies 1. Payment Gateway The NYU Payment Gateway is the preferred service for accepting online electronic payments at NYU. The NYU Payment Gateway is NYU's Electronic Payment processing system. It is a transaction-based system that accepts epayment transactions for both one-time and recurring payments. This service may be implemented to receive payment for items such as online gift donations, conference registration, and specific fees related to a university event, or other products and services. Specific instructions to establish this service for your school/unit are available at Note: The Payment Gateway service provides only electronic payment processing. Additional functionality, such as event enrollment or inventory sales, is not specifically provided by this service. Alternative technologies for accepting online electronic payments must be approved by the University Bursar. 2. Standalone Point of Sale (POS) terminals Standalone POS terminals will be used to process card-present, phone order, mail order, and faxed credit card payments. These terminals, which have a built in key pad and magnetic card reader, encrypt cardholder data at the point of swipe or entry and can be configured to communicate via an IP network, a plain old telephone service (POTS) line, or a cellular wireless connection. The following are approved standalone terminals at NYU: VeriFone s Vx570 o Supports wired, IP or POTS, connectivity First Data s FD400 o Supports wireless, GPRS or CDMA, connectivity Page 9 of 12
10 Appendix C: Roles and Responsibilities The following tables contain recommended roles and responsibilities for compliance activities within NYU PCI Compliance Program. The tasks, which have been broken down by their frequency, are standard activities that would be required of any merchant who processes payment cards. Quarterly Activities PCI Support Framework PCI Compliance Manager Responsible Party Merchant ITS Review logging and monitoring Maintain summary reports Review and confirmation of all Maintain storage locations for payment card data and systems inventory Review change control effectiveness Maintain and completeness Ensure any stored cardholder data Assess, maintain that exceeds its data retention timeline is removed Review of all network operating procedures Assess, maintain Annual Activities PCI Support Framework Policy review Review of individual risk assessments for any changes to the payment card processing environment Audit information security program, i.e. ensure all aspects of this document are updated as appropriate and completed Employee and 3 rd party security awareness training Review and test incident response plan Employee acknowledgement of understanding and acceptance of the company s security policies PCI Compliance Manager Coordinate review, maintain Maintain Maintain Coordinate awareness program, ensure participation, maintain Review, maintain Ensure participation, maintain Merch ant Responsible Party IT Treasur NYU S y Complia Systems nce Page 10 of 12
11 PCI Support Framework Review service provider PCI compliance Complete SAQ PCI Compliance Manager Maintain Ensure participation, maintain Merch ant Responsible Party IT S Treasur y Systems NYU Complia nce Other Ongoing PCI Compliance Manager Activities On-boarding merchants to the PCI Compliance Program Training and supporting merchants to use the proposed compliance tool Monitoring compliance tool activities Coordinating/ assembling SAQ for submission to the acquiring bank Fielding and addressing compliance questions Maintaining an inventory of payment systems and coordinating upgrades as necessary Tracking merchant accounts for deactivation Ensuring merchants have appropriate access control to cardholder data Page 11 of 12
12 Appendix D: Other Applicable Law New York State Law Schools/units accepting payment cards for goods and services in New York must apply with New York state law. In summary, current New York State law mandates that: A. A merchant in a sales transaction is prohibited from imposing a surcharge on a purchaser who elects to use a credit card in lieu of payment by cash, check, or similar means. B. A merchant who accepts credit cards and who imposes minimum purchase amounts for use of a credit card or excludes card payments for discounted items must conspicuously post such limitations or conditions and include them in all advertisements that otherwise mention that credit cards are accepted. C. A merchant must use paper forms for payment card transactions which do not produce carbon copies or render a separate piece of paper that readily identifies the cardholder by name or number, except as necessary to allow the merchant to complete the transaction. A merchant is prohibited (i) from writing or requiring a cardholder to write any personal identification information (such as an address or phone number) on such form or any attachment to it that is not required to complete the sales transaction (such as a shipping address) and (ii) from printing the expiration date of the card or more than the last five digits of the card number on any receipt provide to the cardholder. See the following sections of New York General Business Law for further information. New York General Business Law 518. Credit card surcharge prohibited. New York General Business Law 519. Disclosure by commercial establishments honoring credit. New York General Business Law 520-a. Certain credit and debit card transaction forms required. Schools/units accepting payment cards in or from other jurisdictions should contact the Office of General Counsel regarding applicable law. Page 12 of 12
Section 3.9 PCI DSS Information Security Policy Issued: June 2016 Replaces: January 2015
Section 3.9 PCI DSS Information Security Policy Issued: June 2016 Replaces: January 2015 I. PURPOSE The purpose of this policy is to establish guidelines for processing charges on Payment Cards to protect
TERMINAL CONTROL MEASURES
UCR Cashiering & Payment Card Services TERMINAL CONTROL MEASURES Instructions: Upon completion, please sign and return to cashandmerchant@ucr.edu when requesting a stand-alone dial up terminal. The University
University Policy Accepting and Handling Payment Cards to Conduct University Business
BROWN UNIVERSITY University Policy Accepting and Handling Payment Cards to Conduct University Business Table of Contents Purpose... 2 Scope... 2 Authorization... 2 Establishing a new account... 2 Policy
CREDIT CARD SECURITY POLICY PCI DSS 2.0
Responsible University Official: University Compliance Officer Responsible Office: Business Office Reviewed Date: 10/29/2012 CREDIT CARD SECURITY POLICY PCI DSS 2.0 Introduction and Scope Introduction
TREASURER S OFFICE ADMINISTRATIVE STANDARDS FOR THE TREASURER S FISCAL PROCEDURE No. 08-01 MERCHANT DEBIT AND CREDIT CARD RECEIPTS
TREASURER S OFFICE ADMINISTRATIVE STANDARDS FOR THE TREASURER S FISCAL PROCEDURE No. 08-01 MERCHANT DEBIT AND CREDIT CARD RECEIPTS 1. Introduction Debit and Credit Card Receipt Standards apply to the administration
POLICY & PROCEDURE DOCUMENT NUMBER: 3.3101. DIVISION: Finance & Administration. TITLE: Policy & Procedures for Credit Card Merchants
POLICY & PROCEDURE DOCUMENT NUMBER: 3.3101 DIVISION: Finance & Administration TITLE: Policy & Procedures for Credit Card Merchants DATE: October 24, 2011 Authorized by: K. Ann Mead, VP for Finance & Administration
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire B and Attestation of Compliance
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire B and Attestation of Compliance Merchants with Only Imprint Machines or Only Standalone, Dial-out Terminals Electronic Cardholder
Policies and Procedures
Policies and Procedures Provided by PROGuard The following are policies and procedures which need to be enforced to ensure PCI DSS compliance. In order to answer yes to the questions and pass the SAQ,
How To Complete A Pci Ds Self Assessment Questionnaire
Department PCI Self-Assessment Questionnaire Version 1.1 2009 Attestation of Compliance Instructions for Submission This Department PCI Self-Assessment Questionnaire has been developed as an assessment
PCI General Policy. Effective Date: August 2008. Approval: December 17, 2015. Maintenance of Policy: Office of Student Accounts REFERENCE DOCUMENTS:
Effective Date: August 2008 Approval: December 17, 2015 PCI General Policy Maintenance of Policy: Office of Student Accounts PURPOSE: To protect against the exposure and possible theft of account and personal
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire B and Attestation of Compliance
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire B and Attestation of Compliance Imprint Machines or Stand-alone Dial-out Terminals Only, no Electronic Cardholder Data Storage
Accepting Payment Cards and ecommerce Payments
Policy V. 4.1.1 Responsible Official: Vice President for Finance and Treasurer Effective Date: September 29, 2010 Accepting Payment Cards and ecommerce Payments Policy Statement The University of Vermont
EAA Policy for Accepting and Handling Credit and Debit Card Payments ( Policy )
EAA Policy for Accepting and Handling Credit and Debit Card Payments ( Policy ) Background Due to increased threat of identity theft, fraudulent credit card activity and other instances where cardholder
PCI Training for Retail Jamboree Staff Volunteers. Securing Cardholder Data
PCI Training for Retail Jamboree Staff Volunteers Securing Cardholder Data Securing Cardholder Data Introduction This PowerPoint presentation is designed to educate Retail Jamboree Staff volunteers on
Appendix 1 Payment Card Industry Data Security Standards Program
Appendix 1 Payment Card Industry Data Security Standards Program PCI security standards are technical and operational requirements set by the Payment Card Industry Security Standards Council to protect
Information Technology
Credit Card Handling Security Standards Overview Information Technology This document is intended to provide guidance to merchants (colleges, departments, organizations or individuals) regarding the processing
INFORMATION SECURITY POLICY. Policy for Credit Card Acceptance to Conduct College Business
DELAWARE COLLEGE OF ART AND DESIGN 600 N MARKET ST WILMINGTON DELAWARE 19801 302.622.8000 INFORMATION SECURITY POLICY including Policy for Credit Card Acceptance to Conduct College Business stuff\policies\security_information_policy_with_credit_card_acceptance.doc
University Policy Accepting Credit Cards to Conduct University Business
BROWN UNIVERSITY University Policy Accepting Credit Cards to Conduct University Business Purpose Brown University requires all departments that are involved with credit card handling to do so in compliance
Dartmouth College Merchant Credit Card Policy for Managers and Supervisors
Dartmouth College Merchant Credit Card Policy for Managers and Supervisors Mission Statement Dartmouth College requires all departments that process, store or transmit credit card data remain in compliance
6-8065 Payment Card Industry Compliance
0 0 0 Yosemite Community College District Policies and Administrative Procedures No. -0 Policy -0 Payment Card Industry Compliance Yosemite Community College District will comply with the Payment Card
This policy applies to all GPC units that process, transmit, or handle cardholder information in a physical or electronic format.
Policy Number: 339 Policy Title: Credit Card Processing Policy, Procedure, & Standards Review Date: 07-23-15 Approval Date: 07-27-15 POLICY: All individuals involved in handling credit and debit card transactions
Credit Card Processing and Security Policy
Credit Card Processing and Security Policy Policy Number: Reserved for future use Responsible Official: Vice President of Administration and Finance Responsible Office: Student Account Services Effective
CREDIT CARD PROCESSING POLICY AND PROCEDURES
CREDIT CARD PROCESSING POLICY AND PROCEDURES Note: For purposes of this document, debit cards are treated the same as credit cards. Any reference to credit cards includes credit and debit card transactions.
Becoming PCI Compliant
Becoming PCI Compliant Jason Brown - brownj52@michigan.gov Enterprise Security Architect Enterprise Architecture Department of Technology, Management and Budget State of Michigan @jasonbrown17 History
CREDIT CARD PROCESSING & SECURITY POLICY
FINANCE AND TREASURY POLICIES AND PROCEDURES E071 CREDIT CARD PROCESSING & SECURITY POLICY PURPOSE The purpose of this policy is to establish guidelines for processing charges/credits on Credit Cards to
University of Dayton Credit / Debit Card Acceptance Policy September 1, 2009
University of Dayton Credit / Debit Card Acceptance Policy September 1, 2009 Effective Date of this Policy: August 1, 2008 Last Revision: September 1, 2009 Contact for More Information: UDit Internal Auditor
GRINNELL COLLEGE CREDIT CARD PROCESSING AND SECURITY POLICY
GRINNELL COLLEGE CREDIT CARD PROCESSING AND SECURITY POLICY PURPOSE The Payment Card Industry Data Security Standard was established by the credit card industry in response to an increase in identify theft
b. USNH requires that all campus organizations and departments collecting credit card receipts:
USNH Payment Card Industry Data Security Standard (PCI DSS) Version 3 Administration and Department Policy Draft Revision 3/12/2013 1. Purpose. The purpose of this policy is to assist the University System
Standards for Business Processes, Paper and Electronic Processing
Payment Card Acceptance Information and Procedure Guide (for publication on the Treasury Webpages) A companion guide to University policy 6120, Payment Card Acceptance Standards for Business Processes,
Accounting and Administrative Manual Section 100: Accounting and Finance
No.: C-13 Page: 1 of 6 POLICY: It is the policy of the University of Alaska that all payment card transactions are to be executed in compliance with standards established by the Payment Card Industry Security
PCI Policies 2011. Appalachian State University
PCI Policies 2011 Appalachian State University Table of Contents Section 1: State and Contractual Requirements Governing Campus Credit Cards A. Cash Collection Point Approval for Departments B. State Requirements
COLUMBUS STATE COMMUNITY COLLEGE POLICY AND PROCEDURES MANUAL
PAYMENT CARD INDUSTRY COMPLIANCE (PCI) Effective June 1, 2011 Page 1 of 6 (1) Definitions a. Payment Card Industry Data Security Standards (PCI-DSS): A set of standards established by the Payment Card
SECTION: SUBJECT: PCI-DSS General Guidelines and Procedures
1. Introduction 1.1. Purpose and Background 1.2. Central Coordinator Contact 1.3. Payment Card Industry Data Security Standards (PCI-DSS) High Level Overview 2. PCI-DSS Guidelines - Division of Responsibilities
Payment Cardholder Data Handling Procedures (required to accept any credit card payments)
Payment Cardholder Data Handling Procedures (required to accept any credit card payments) Introduction: The Procedures that follow will allow the University to be in compliance with the Payment Card Industry
Payment Card Industry (PCI) Policy Manual. Network and Computer Services
Payment Card Industry (PCI) Policy Manual Network and Computer Services Forward This policy manual outlines acceptable use Black Hills State University (BHSU) or University herein, Information Technology
Saint Louis University Merchant Card Processing Policy & Procedures
Saint Louis University Merchant Card Processing Policy & Procedures Overview: Policies and procedures for processing credit card transactions and properly storing credit card data physically and electronically.
EASTERN OKLAHOMA STATE COLLEGE ACCEPTING AND HANDLING CREDIT AND DEBIT CARD PAYMENTS POLICIES AND PROCEDURES
EASTERN OKLAHOMA STATE COLLEGE ACCEPTING AND HANDLING CREDIT AND DEBIT CARD PAYMENTS POLICIES AND PROCEDURES This document describes Eastern Oklahoma State College s policy and procedures for the proper
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire A and Attestation of Compliance
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire A and Attestation of Compliance Card-not-present Merchants, All Cardholder Data Functions Fully Outsourced Version 3.0 February
Merchant Card Processing Best Practices
Merchant Card Processing Best Practices Background: The major credit card companies (VISA, MasterCard, Discover, and American Express) have published a uniform set of data security standards that ALL merchants
Credit and Debit Card Handling Policy Updated October 1, 2014
Credit and Debit Card Handling Policy Updated October 1, 2014 City of Parkville 8880 Clark Ave. Parkville, MO 64152 Hours: 8:00-5:00 p.m. Monday -Friday Phone Number 816-741-7676 Email: cityhall@parkvillemo.gov
BUSINESS POLICY. TO: All Members of the University Community 2012:12. CREDIT CARD PROCESSING AND SECURITY POLICY (Supersedes Policy 2009:05)
BUSINESS POLICY TO: All Members of the University Community 2012:12 DATE: April 2012 CREDIT CARD PROCESSING AND SECURITY POLICY (Supersedes Policy 2009:05) Contents Section 1 Policy Statement... 2 Section
PCI DSS FAQ. The twelve requirements of the PCI DSS are defined as follows:
What is PCI DSS? PCI DSS is an acronym for Payment Card Industry Data Security Standards. PCI DSS is a global initiative intent on securing credit and banking transactions by merchants & service providers
Key Steps to Meeting PCI DSS 2.0 Requirements Using Sensitive Data Discovery and Masking
Key Steps to Meeting PCI DSS 2.0 Requirements Using Sensitive Data Discovery and Masking SUMMARY The Payment Card Industry Data Security Standard (PCI DSS) defines 12 high-level security requirements directed
. Merchant Accounts are special bank accounts issued by a merchant. . Merchant Level: This classification is based on transaction volume.
Credit Card Procedures and Policies Texas A&M Health Science Center offers university departments the convenience of accepting credit cards in payment for goods and services provided. All University departments
Payment Card Industry Data Security Standards
Payment Card Industry Data Security Standards PCI DSS Rhonda Chorney Manager, Revenue Capital & General Accounting Today s Agenda 1. What is PCI DSS? 2. Where are we today? 3. Why is compliance so important?
Why Is Compliance with PCI DSS Important?
Why Is Compliance with PCI DSS Important? The members of PCI Security Standards Council (American Express, Discover, JCB, MasterCard, and Visa) continually monitor cases of account data compromise. These
Minnesota State Colleges and Universities System Procedures Chapter 5 Administration. Guideline 5.23.1.10 Payment Card Industry Technical Requirements
Minnesota State Colleges and Universities System Procedures Chapter 5 Administration Payment Card Industry Technical s Part 1. Purpose. This guideline emphasizes many of the minimum technical requirements
PCI Data Security and Classification Standards Summary
PCI Data Security and Classification Standards Summary Data security should be a key component of all system policies and practices related to payment acceptance and transaction processing. As customers
POLICY SECTION 509: Electronic Financial Transaction Procedures
Page 1 POLICY SECTION 509: Electronic Financial Transaction Procedures Source: NDSU President NDSU VP for Finance and Administration NDSU VP for Information Technology A. Purpose / Rationale Many NDSU
POLICY NAME : MERCHANT (PCI) POLICY AND PROCEDURES ACCEPTING CREDIT/DEBIT CARD PAYMENTS
Publication Date 2009-08-11 Issued by: Financial Services Chief Information Officer Revision V 1.0 POLICY NAME : MERCHANT (PCI) POLICY AND PROCEDURES ACCEPTING CREDIT/DEBIT CARD PAYMENTS Overview: There
Purpose: To comply with the Payment Card Industry Data Security Standards (PCI DSS)
Procedure Credit Card Handling and Security for Departments/Divisions and Elected/Appointed Offices Last Update: January 19, 2016 References: Credit Card Payments Policy Purpose: To comply with the Payment
Dartmouth College Merchant Credit Card Policy for Processors
Mission Statement Dartmouth College Merchant Credit Card Policy for Processors Dartmouth College requires all departments that process, store or transmit credit card data remain in compliance with the
Clark University's PCI Compliance Policy
ï» Clark University's PCI Compliance Policy Who Should Read this Policy: All persons who have access to credit card information, including: Every employee that accesses handles or maintains credit card
UNL PAYMENT CARD POLICY AND PROCEDURES. Table of Contents
UNL PAYMENT CARD POLICY AND PROCEDURES Table of Contents Payment Card Merchant Security Standards Policy and Procedures... 2 Introduction... 4 Payment Card Industry Data Security Standard... 4 Definitions...
University of Sunderland Business Assurance PCI Security Policy
University of Sunderland Business Assurance PCI Security Policy Document Classification: Public Policy Reference Central Register IG008 Policy Reference Faculty / Service IG 008 Policy Owner Chief Financial
UTAH VALLEY UNIVERSITY Policies and Procedures
Page 2 of 7 POLICY TITLE Section Subsection Responsible Office PCI DSS Compliance Facilities, Operations, and Information Technology Information Technology Office of the Vice President of Administration
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire C and Attestation of Compliance
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire C and Attestation of Compliance Payment Application Connected to Internet, No Electronic Cardholder Data Storage Version
Vanderbilt University
Vanderbilt University Payment Card Processing and PCI Compliance Policy and Procedures Manual PCI Compliance Office Information Technology Treasury VUMC Finance Table of Contents Policy... 2 I. Purpose...
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire Instructions and Guidelines Version 1.1 February 2008 Table of Contents About this Document... 1 PCI Data Security Standard
MONTSERRAT COLLEGE OF ART WRITTEN INFORMATION SECURITY POLICY (WISP)
MONTSERRAT COLLEGE OF ART WRITTEN INFORMATION SECURITY POLICY (WISP) 201 CMR 17.00 Standards for the Protection of Personal Information Of Residents of the Commonwealth of Massachusetts Revised April 28,
Miami University. Payment Card Data Security Policy
Miami University Payment Card Data Security Policy IT Policy IT Standard IT Guideline IT Procedure IT Informative Issued by: IT Services SCOPE: This policy covers all units within Miami University that
Cyber Security: Secure Credit Card Payment Process Payment Card Industry Standard Compliance
Cyber Security: Secure Credit Card Payment Process Payment Card Industry Standard Compliance A Non-Technical Guide Essential for Business Managers Office Managers Operations Managers Compliant? Bank Name
Reducing PCI DSS Scope with the TransArmor First Data TransArmor Solution
First Data First Data Market Market Insight Insight Reducing PCI DSS Scope with the TransArmor First Data TransArmor Solution SM Solution Organizations who handle payment card data are obligated to comply
CREDIT CARD MERCHANT POLICY. All campuses served by Louisiana State University (LSU) Office of Accounting Services
Louisiana State University Finance and Administrative Services Operating Procedure FASOP: AS-22 CREDIT CARD MERCHANT POLICY Scope: All campuses served by Louisiana State University (LSU) Office of Accounting
This appendix is a supplement to the Local Government Information Security: Getting Started Guide, a non-technical reference essential for elected
This appendix is a supplement to the Local Government Information Security: Getting Started Guide, a non-technical reference essential for elected officials, administrative officials and business managers.
Sales Rep Frequently Asked Questions
V 02.21.13 Sales Rep Frequently Asked Questions OMEGA Processing Data Protection Program February 2013 - Updated In response to a national rise in data breaches and system compromises, OMEGA Processing
McGill Merchant Manual
McGill Merchant Manual The McGill Merchant Manual is a complementary document to the Merchant (PCI) Policy and Procedures and serves to aid Merchants in ensuring their operations comply with Payment Card
Credit Card Handling Security Standards
Credit Card Handling Security Standards Overview This document is intended to provide guidance to merchants (colleges, departments, auxiliary organizations or individuals) regarding the processing of charges
Office of Finance and Treasury
Office of Finance and Treasury How to Accept & Process Credit and Debit Card Transactions Procedure Related Policy Title Credit Card Processing Policy For University Merchant Locations Responsible Executive
CAL POLY POMONA FOUNDATION. Policy for Accepting Payment (Credit) Card and Ecommerce Payments
CAL POLY POMONA FOUNDATION Policy for Accepting Payment (Credit) Card and Ecommerce Payments 1 PURPOSE The purpose of this policy is to establish business processes and procedures for accepting payment
UTAH VALLEY UNIVERSITY Policies and Procedures
Page 1 of 7 Proposed Policy Number and Title: 457 PCI DSS Compliance Existing Policy Number and Title: Not applicable Approval Process* X Regular Temporary Emergency Expedited X New New New Revision Revision
Credit Card Security
Credit Card Security Created 16 Apr 2014 Revised 16 Apr 2014 Reviewed 16 Apr 2014 Purpose This policy is intended to ensure customer personal information, particularly credit card information and primary
PCI Compliance. Top 10 Questions & Answers
PCI Compliance Top 10 Questions & Answers 1. What is PCI Compliance and PCI DSS? 2. Who needs to follow the PCI Data Security Standard? 3. What happens if I don t comply? 4. What are the basic requirements
CREDIT CARD NUMBER HANDLING PROCEDURES POLICY. 2014 October
CREDIT CARD NUMBER HANDLING PROCEDURES POLICY 2014 October Royal Roads University Page 1 of 6 21 October 2014 Table of Contents Policy Statement... 3 Rationale... 3 Applicability of the Policy... 3 Definitions...
Managed Hosting & Datacentre PCI DSS v2.0 Obligations
Any physical access to devices or data held in an Melbourne datacentre that houses a customer s cardholder data must be controlled and restricted only to approved individuals. PCI DSS Requirements Version
PAYMENT CARD INDUSTRY (PCI) COMPLIANCE WORKBOOK. PCI SAQ TYPE B Level 4. Virtual Terminals
COAST GUARD MORALE WELL-BEING AND RECREATION (MWR) PROGRAM PAYMENT CARD INDUSTRY (PCI) COMPLIANCE WORKBOOK PCI SAQ TYPE B Level 4 Virtual Terminals 31 December 2014 COPYRIGHT NOTICE Copyright 2008-2014
2.0 PAYMENT CARD INDUSTRY DATA SECURITY STANDARDS (PCI-DSS)
CSU, Chico Credit Card Handling Security Standard Effective Date: July 28, 2015 1.0 INTRODUCTION This standard provides guidance to ensure that credit card acceptance and ecommerce processes comply with
ACCEPTING CREDIT CARDS AND ELECTRONIC CHECKS TO CONDUCT UNIVERSITY BUSINESS
UNIVERSITY OF NORTH DAKOTA FINANCE & OPERATIONS POLICY LIBRARY ACCEPTING CREDIT CARDS AND ELECTRONIC CHECKS TO CONDUCT UNIVERSITY BUSINESS Policy 2.3, Accepting Credit Cards and Electronic Checks to Conduct
FORT HAYS STATE UNIVERSITY CREDIT CARD SECURITY POLICY
FORT HAYS STATE UNIVERSITY CREDIT CARD SECURITY POLICY Page 1 of 6 Summary The Payment Card Industry Data Security Standard (PCI DSS), a set of comprehensive requirements for enhancing payment account
Title of the Policy: PCI DSS Compliance Policy
Title of the Policy: PCI DSS Compliance Policy Functional Area: Finance and IT Services Applies To: See Scope Section Below Policy Reference(s): PCI Security Standards Council Number: Version 1.0 Date
The following are responsible for the accuracy of the information contained in this document:
AskUGA 1 of 5 Credit/Debit Cards Responsible administrator: Senior Vice President for Finance and Administration Related Procedure: The Credit/Debit Card Processing Procedures Responsible department: Bursar's
Viterbo University Credit Card Processing & Data Security Procedures and Policy
The requirements for PCI-DSS compliance are quite numerous and at times extremely complicated due to their interdependent nature and scope. The University has deemed it necessary for those areas currently
Payment Application Data Security Standard
Payment Card Industry (PCI) Payment Application Data Security Standard ROV Reporting Instructions for PA-DSS v2.0 March 2012 Changes Date March 2012 Version Description Pages 1.0 To introduce PA-DSS ROV
What To Do if Compromised. Visa USA Fraud Investigations and Incident Management Procedures
What To Do if Compromised Visa USA Fraud Investigations and Incident Management Procedures Table of Contents Introduction......................................................... 1 Identifying and Detecting
Policy Title: Payment Cards Policy Effective Date: 5/5/2010. Policy Number: FA-PO-1214 Date of Last Revision: 11/5/2014
Policy Title: Effective Date: 5/5/2010 Policy Number: FA-PO-1214 Date of Last Revision: 11/5/2014 Oversight Department: Financial Services Next Review Date: 10/1/2016 1. PURPOSE The for Radford University
Andrews University Payment Card Acceptance Policies & Procedures. Prepared by Financial Administration
Andrews University Payment Card Acceptance Policies & Procedures Prepared by Financial Administration July 12, 2011 Part I: Introduction of Policy and Purpose Formatted: Font: 12 pt In order to protect
Payment Card Industry Data Security Standard (PCI DSS) Q & A November 6, 2008
Payment Card Industry Data Security Standard (PCI DSS) Q & A November 6, 2008 What is the PCI DSS? And what do the acronyms CISP, SDP, DSOP and DISC stand for? The PCI DSS is a set of comprehensive requirements
COLORADO STATE UNIVERSITY Financial Procedure Statements FPI 6-6
1. Procedure Title: PCI Compliance Program COLORADO STATE UNIVERSITY Financial Procedure Statements FPI 6-6 2. Procedure Purpose and Effect: All Colorado State University departments that accept credit/debit
PCI Compliance. What is New in Payment Card Industry Compliance Standards. October 2015. cliftonlarsonallen.com. 2015 CliftonLarsonAllen LLP
cliftonlarsonallen.com PCI Compliance What is New in Payment Card Industry Compliance Standards October 2015 Overview PCI DSS In the beginning Each major card brand had its own separate criteria for implementing
The Design Society. Information Security Policy
The Design Society Policies and Forms That Conform to PCI DSS SAQ A Version 2.0 June 2014 About this Document This document contains The Design Society information security policies. This document is
And Take a Step on the IG Career Path
How to Develop a PCI Compliance Program And Take a Step on the IG Career Path Andrew Altepeter Any organization that processes customer payment cards must comply with the Payment Card Industry s Data Security
Payment Card Acceptance Administrative Policy
Administrative Procedure Approved By: Brandon Gilliland, Associate Vice President for Finance & Controller Effective Date: October 1, 2014 History: Approval Date: September 25, 2014 Revisions: Type: Administrative
688 Sherbrooke Street West, Room 730 James Administration Building, Room 524
'McGill Sylvia Franke, LL.B., B.Sc. Albert Caponi, C.A. Chief Information Officer Assistant Vice-Principal (Financial Services) 688 Sherbrooke Street West, Room 730 James Administration Building, Room
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire D and Attestation of Compliance
Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire D and Attestation of Compliance All other SAQ-Eligible Merchants and Service Providers Version 2.0 October 2010 Document
CREDIT CARD POLICY DRAFT
APPROVED BY Ronald J. Paprocki I. Policy Statement Any office of the University that processes credit card transactions may do so only in the manner approved by the University Treasury Office and in compliance
PCI Compliance Overview
PCI Compliance Overview 1 PCI DSS Payment Card Industry Data Security Standard Standard that is applied to: Merchants Service Providers (Banks, Third party vendors, gateways) Systems (Hardware, software)
CREDIT CARD MERCHANT PROCEDURES MANUAL. Effective Date: 5/25/2011
CREDIT CARD MERCHANT PROCEDURES MANUAL Effective Date: 5/25/2011 Updated: May 25, 2011 TABLE OF CONTENTS Introduction... 1 Third-Party Vendors... 1 Merchant Account Set-up... 2 Personnel Requirements...