21.08.2013 Views

Johns Hopkins University Policy and Procedure

Johns Hopkins University Policy and Procedure

Johns Hopkins University Policy and Procedure

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

POLICY<br />

This policy applies to all entities within the <strong>Johns</strong> <strong>Hopkins</strong> Institutions.<br />

Purpose<br />

<strong>Johns</strong> <strong>Hopkins</strong> <strong>University</strong><br />

<strong>Policy</strong> <strong>and</strong> <strong>Procedure</strong><br />

The purpose of this policy is to establish a framework from which to ensure that all credit card data<br />

received by the <strong>Johns</strong> <strong>Hopkins</strong> Institutions is processed in compliance with current Payment Card<br />

Industry Data Security St<strong>and</strong>ards (PCI-DSS) st<strong>and</strong>ards. The Payment Card Industry (Master Card, VISA,<br />

American Express, Discover <strong>and</strong> other major card issuers) has established important <strong>and</strong> stringent<br />

security requirements to protect credit card data. Compliance with PCI-DSS st<strong>and</strong>ards is m<strong>and</strong>atory.<br />

Without compliance, the <strong>Johns</strong> <strong>Hopkins</strong> Institutions would be subject to financial liability <strong>and</strong> reputational<br />

risk.<br />

Oversight Committee<br />

An Oversight Committee will be established. Membership is to include representatives of the Treasury<br />

Offices of the <strong>Johns</strong> <strong>Hopkins</strong> <strong>University</strong> <strong>and</strong> the <strong>Johns</strong> <strong>Hopkins</strong> Health System, Data the Chief the Chief<br />

Information Security Officer <strong>and</strong> end users. Chairmanship of the committee will rotate between the<br />

Treasury offices of the <strong>Johns</strong> <strong>Hopkins</strong> <strong>University</strong> <strong>and</strong> the <strong>Johns</strong> <strong>Hopkins</strong> Health System on an annual<br />

basis. The Oversight Committee will provide for an efficient coordination of policies <strong>and</strong> resources to<br />

ensure that procedures <strong>and</strong> practices within the <strong>Johns</strong> <strong>Hopkins</strong> Institutions are in compliance with PCI-<br />

DSS st<strong>and</strong>ards. The Oversight Committee will meet regularly.<br />

Authority <strong>and</strong> Responsibility<br />

The Treasury Office of each institution is responsible for maintaining a relationship with an approved<br />

merchant bank. Each Treasury Office is responsible for securing credit card merchant accounts when a<br />

requester demonstrates a business need. Unused merchant accounts should be closed.<br />

An authorized person within each affiliate or university department is responsible for completing an<br />

annual PCI Self Assessment Questionnaire <strong>and</strong> must certify that their organization is PCI-DSS compliant.<br />

A current version of the SAQ is posted at pcisecurityst<strong>and</strong>ards.org/saq/index.shtml. The appropriate<br />

Treasury Office will provide assistance as requested. The Treasury Office will collect the assessments<br />

<strong>and</strong> submit an annual Report on Compliance to the Oversight Committee.<br />

The Data Security OfficeChief Information Security Officer (CISO) or designee will provide guidance in the<br />

area of network security as it pertains to credit card information transmitted or stored on a <strong>Johns</strong> <strong>Hopkins</strong><br />

network. When it is appropriate, the Data Security OfficeCISO, with the agreement of each Treasury<br />

Office, may engage the services of a consultant with expertise in network security <strong>and</strong> PCI-DSS<br />

St<strong>and</strong>ards.<br />

Scope<br />

This policy applies to each person who comes in contact with credit card information. It also applies to all<br />

computing <strong>and</strong> network software or equipment, whether it is owned or leased by the <strong>Johns</strong> <strong>Hopkins</strong><br />

Institutions, which is used to process or store credit card data.


Internal Compliance Requirements<br />

<strong>Johns</strong> <strong>Hopkins</strong> <strong>University</strong><br />

<strong>Policy</strong> <strong>and</strong> <strong>Procedure</strong><br />

1) All credit card merchant accounts must be approved by the Treasury Office.<br />

2) Management <strong>and</strong> employees are familiar with <strong>and</strong> adhering to PCI st<strong>and</strong>ards.<br />

3) Each affiliate or department (as determined by the Treasury Office) must complete the annual self<br />

assessment questionnaire.<br />

4) Any proposal for a new process (electronic or paper) must be approved by the Treasury Office<br />

<strong>and</strong> the Data Security OfficeCISO or designee.<br />

5) Approved methods of processing credit card payments are:<br />

a-Point of Sale processing using dedicated phone lines.<br />

b-Web-based processing using a PCI compliant service approved by the Treasury Office.<br />

c-Alternate methods approved on a case by case basis by the Treasury Office <strong>and</strong> the<br />

Data Security OfficeCISO.<br />

6) Cardholder data is considered “restricted Information” under <strong>Johns</strong> <strong>Hopkins</strong> Institution Information<br />

Technology policies (located at http://it.jhu.edu/policies/itpolicies.html) <strong>and</strong> is subject to the<br />

controls described in the policies including technical <strong>and</strong> security controls.<br />

7) If a workforce member observes the unauthorized or inappropriate use of restricted information<br />

such as cardholder information, it is the responsibility of that person to notify a supervisor, an<br />

institutional officer or the Compliance Hotline 1-877-932-6675.<br />

8) Any breach of network security involving credit card information must be reported to the CISO.<br />

PCI - DSS Requirements<br />

1) Maintain a firewall configuration to protect cardholder data.<br />

2) Vendor-supplied defaults for passwords or other security should not be used.<br />

3) Protect cardholder data.<br />

4) Encrypt transmission of cardholder data.<br />

5) Maintain <strong>and</strong> update anti-virus software.<br />

6) Develop <strong>and</strong> maintain security systems <strong>and</strong> applications.<br />

7) Restrict access to cardholder data to a “need to know” basis.<br />

8) Assign a unique user ID to each computer user.<br />

9) Restrict physical access to cardholder data.<br />

10) Track <strong>and</strong> monitor all access to network resources <strong>and</strong> cardholder data.<br />

11) Regularly test systems <strong>and</strong> processes.<br />

12) Maintain <strong>and</strong> update policies that address security for employees <strong>and</strong> contractors.<br />

PCI – DSS System Validation Requirements<br />

For purposes of selecting a compliance level, it is assumed that the <strong>Johns</strong> <strong>Hopkins</strong> Institutions are at a<br />

Merchant Level 2. Accordingly, an annual self assessment questionnaire must be completed <strong>and</strong> a<br />

quarterly Network scan must be performed by an approved consultant. The oversight committee will<br />

review data concerning payment card transactions at the <strong>Johns</strong> <strong>Hopkins</strong> institutions. A determination<br />

based on that review will be made to identify the institution’s “Merchant Level” as defined by the Payment<br />

Card Institute. The actions taken to validate compliance with PCI DSS will be appropriate to the Merchant<br />

Level.<br />

Definition of Terms<br />

Merchant Account A relationship established by the Treasury Office with a bank to process credit<br />

cards.


<strong>Johns</strong> <strong>Hopkins</strong> <strong>University</strong><br />

<strong>Policy</strong> <strong>and</strong> <strong>Procedure</strong><br />

Credit Card Data Full magnetic stripe or the PAN (primary account number) plus a cardholder<br />

name, card expiration date or service code.<br />

PCI-DSS Payment Card Industry Data Security St<strong>and</strong>ard<br />

The PCI-DSS is a comprehensive set of requirements established by the PCI<br />

Security St<strong>and</strong>ards Council for enhancing payment account data security. It is a<br />

multifaceted st<strong>and</strong>ard that included requirements for security management,<br />

policies, procedures, network architecture, software design <strong>and</strong> other critical<br />

protective measures.<br />

PCI Security This organization defines credentials <strong>and</strong> qualifications for assessors <strong>and</strong><br />

St<strong>and</strong>ards Council vendors as well as maintaining the PCI-DSS.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!