Skip to main content

PCI Security Testing Policy

Version 1.0.3


The purpose of this policy is to ensure security testing complies with the Payment Card Industry Data Security Standard (PCI DSS).1


This IT policy, and all policies referenced herein, shall apply to all members of the University community including faculty, students, administrative officials, staff, alumni, authorized guests, delegates, and independent contractors (the “User(s)” or “you”) who use, access, or otherwise employ, locally or remotely, the University’s IT Resources, whether individually controlled, shared, stand-alone, or networked.

Policy Statement

  • Access to IT Resources and Card Holder Data (CHD) must be tracked, monitored, and tested at least quarterly, per PCI DSS guidelines.
  • Departments or individuals that handle CHD must verify that:
    • Strong access control measures are taken which restrict access to CHD on a need-to-know basis;
    • Unique IDs are assigned and administered to each person with CHD IT Resources access and;
    • Restrictions to physical access to CHD are in place.

1 The Payment Card Industry Security Standards Council (PCI SSC) was launched on September 7, 2006, to manage the ongoing evolution of the Payment Card Industry (PCI) security standards with a focus on improving payment account security throughout the transaction process. The PCI DSS is administered and managed by the PCI SSC, an independent body that was created by the major payment card brands (Visa, MasterCard, American Express, Discover and JCB).


IT Resources include computing, networking, communications, application, and telecommunications systems, infrastructure, hardware, software, data, databases, personnel, procedures, physical facilities, cloud-based vendors, Software as a Service (SaaS) vendors, and any related materials and services.

Related Policies and Procedures

Implementation Information

Review Frequency: Annual
Responsible Person: Director, IT Risk and Data Integrity
Approved By: CISO
Approval Date: February 28, 2017

Revision History

Version: Date: Description:
1.0 02/01/2017 Initial document
1.0.1 02/28/2017 Definitions edit; no change to policy
1.0.2 05/24/2018 Updated disclaimer, scope, and definitions
1.0.3 01/03/2019 Updated links
  01/16/2020 Reviewed; no changes

Policy Disclaimer Statement

Deviations from policies, procedures, or guidelines published and approved by the University Information Security Office (UISO) may only be done cooperatively between the UISO and the requesting entity with sufficient time to allow for appropriate risk analysis, documentation, and possible presentation to authorized University representatives. Failure to adhere to UISO written policies may be met with University sanctions.