| Policy Category | Policy Owner | Version Effective Date | Review Cycle | Policy Contact |
|---|---|---|---|---|
| X. Information Governance, Security & Technology | Chief Transformation Officer | Aug. 29, 2023 | Annual | UMGC Information Security |
- Purpose
The purpose of this policy is to establish information security standards for Payment Card Industry – Data Security Standards (PCI-DSS) compliance relevant to University of Maryland Global Campus ("UMGC" or "University") Information Technology Resources. - Scope and Applicability
This policy applies to all University Information Systems and Information Technology Resources. All Users are responsible for adhering to this policy. - Definitions
Defined terms are capitalized throughout this Policy and can be found in the Information Governance Glossary. - Information Technology PCI-DSS Compliance
All Users must adhere to the requirements of the Information Technology PCI-DSS Compliance Policy to ensure safe-handling of sensitive information related to credit card transactions that are supported by any University Information Technology Resources. UMGC must comply with the complete PCI DSS requirements which can be referenced at the PCI SSC website.- A firewall must be configured and maintained to protect cardholder data.
- Information System Stewards should not use vendor-supplied defaults for system passwords and other security parameters.
- Cardholder data must be protected. Card holder data is defined as:
- Primary Account Number (PAN)
- Card Validation Code (CVV, CVV2, and CVC2)
- Credit Card Personal Identification Number (PIN)
- Any form of magnetic stripe data from the card (Track 1, Track 2).
- Cardholder data must be protected when stored or in transit over public (or untrusted) networks.
- Transmission of cardholder data across open, public networks must be encrypted.
- All Information Technology Resources must be protected against malware and anti-virus software, or programs must be regularly updated. System components within the cardholder data network must be part of an active vulnerability maintenance program.
- Information System Stewards should develop and maintain secure systems and applications.
- Cardholder data must be restricted on a need-to-know basis.
- Information System Stewards should identify and authenticate access to system components. A unique identification (ID) should be assigned to each person with access to critical systems or software.
- Information System Stewards should identify and restrict physical access to cardholder data.
- Information System Stewards should track and monitor all access to network resources and cardholder data.
- Information System Stewards should regularly test security systems and processes.
- Information System Stewards should maintain a policy that addresses information security for all personnel. Consistent policies and procedures are required to be practiced and followed at all times.
- Exceptions
Exceptions to this policy should be submitted to Information Security for review and approval. If an exception is requested, a compensating control or safeguard should be documented and approved. - Enforcement
- Any Employee, Contractor, or third-party performing duties on behalf of the University with knowledge of an alleged violation of this Policy shall notify Information Security as soon as practicable.
- Any Employee, Contractor, or other third-party performing duties on behalf of the University who violates this Policy may be denied access to Information Resources and may be subject to disciplinary action, up to and including termination of employment or contract or pursuit of legal action.
- Standards Referenced
- USM IT Security Standards, v.5, dated July 2022
- NIST SP 800-171r2 "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations," dated February 2020
- Cybersecurity Maturity Model Certification (CMMC), v.2.0, December, 2021
- Related Policies and References
- Effective Date: This policy is effective as of the Version Effective Date set forth above.