PCI Hardware Maintenance Policy

Version 1.3

For Students, Faculty, Staff, Guests, Alumni

Purpose

The purpose of this policy is to ensure that Payment Card Industry (PCI)1 IT Resources implementations, updates, or upgrades are documented, tracked, and regularly reviewed per PCI DSS guidelines.

Scope

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

  • Office of Information Technology’s DevOps maintains PCI network information systems.
  • DevOps are responsible for maintaining the PCI hardware inventory and its annual review, per PCI DSS guidelines.
    • Documentation must include the name, location, IP address (PCI switch), function, and model/vendor information.
    • Documentation must be updated when maintenance is performed.
  • Firewall, switch, and router configuration standards must be reviewed and examined on a semi-annual basis by Information Security and Assurance.

 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 focusing on improving payment account security throughout the transaction process. The PCI DSS is administered and managed by the PCI SSC, an independent body created by the major payment card brands (Visa, MasterCard, American Express, Discover, and JCB).

Definitions

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

Related Policies and Procedures

Implementation Information

Review Frequency: Triennial 
Responsible Person: Senior Director of IT Security and Assurance 
Approved By: CISO
Approval Date: March 1, 2017

Revision History

VersionDateDescription
1.0 03/01/2017 Initial document
1.1 02/01/2018 Updated policy statement
1.1.2 05/24/2018 Updated disclaimer, scope, and definitions
1.1.3 01/03/2019 Updated links
1.2 01/16/2020 Updated policy statement
1.3 01/20/2021 Updated policy statement

Policy Disclaimer Statement

Deviations from policies, procedures, or guidelines published and approved by Information Security and Assurance (ISA) may only be done cooperatively between ISA 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 ISA written policies may be met with University sanctions.

 Need Help?


Walk-In Centers

McGinley 229 | RH
Lowenstein SL19A | LC

View Our Walk-In Hours