Vulnerability Assessment Policy
This policy covers all of Loyola University Chicago’s computing, networking, telephony and information resources.
The purpose of this policy is to grant authorization to appropriate members of the Information Security Team to conduct audits, consisting of vulnerability assessments and penetration tests, against the University’s computing, networking, telephony and information resources.
Audits may be conducted to:
- Investigate possible security incidents
- Ensure conformance to the University’s ITS policies and corresponding regulations (FERPA, PCI/DSS, HIPAA, GLBA, etc.)
- Confirm the security of information systems
- Ensure that information is only accessible by the individuals who should be able to access it
- Ensure that system resources are available to support the mission of the University
- Ensure that information is protected from modification by unauthorized individuals
For the purpose of performing an audit, consent to access identified systems will be provided to members of the Information Security Team through the ITS Vulnerability Assessment Authorization Form. With completion of the form the University hereby provides its consent to allow members of the Information Security Team to access its computing, networking, telephony and information resource devices to the extent necessary to perform the scans authorized in this policy.
This access may include:
- User level and/or system level access to any University computing, networking, telephony or information resource
- Access to information (electronic, hardcopy, etc.) that may be produced, transmitted or stored on the University’s equipment or premises
- Access to work areas (labs, offices, cubicles, storage areas, etc.), through the assistance of Campus Safety
- Access to interactively monitor and log traffic on the University’s networks in accordance with ITS policies and regulatory requirements
The Information Security Team will communicate the details of the vulnerability assessment with the Department Head before scheduling and deploying any assessments.
Periodic Vulnerability Scanning
The Information Security Team will run periodic, internal vulnerability scans at least quarterly. Results of these scans will be addressed in accordance with the risk posed to the University. The Information Security Team will use the Common Vulnerability Scoring System (CVSS) to aid in setting patching guidelines.
Service Degradation and/or Interruption
Network and server performance and/or availability may be affected by network scanning. The University releases the Information Security Team of any and all liability for damages that may arise from network and server availability restrictions caused by approved network scanning.
PCI Environment Requirements
The Information Security Team will run internal and external network vulnerability scans at least quarterly and after any significant change in the network. Results of these scans will be addressed in accordance with the PCI-DSS. Although the University utilizes access controls to prevent the deployment of rogue access points in the PCI-DSS environment, the Network Services Team will use wireless scanners in the University’s cardholder environment on at least a quarterly basis to ensure that rogue wireless networks are not present. To aid in the identification of non-authorized access points, the Network Services Team will maintain an inventory of authorized wireless access points including a documented business justification for each instance.
Vulnerability Risk Idnetification and Ranking
On a bi-weekly basis the Informaion Security Team along with an assigned SME from each of the functional areas of ITS will review all published vulnerabilities to determine if applicable to any operating systems or applications that are in use at the university and will rank each applicable vulnerability according to the published US-CERT and MITRE CVE scores along with the university's risk priority descriptions. Based on risk each vulnerability will be assigned to the appropriate team for response and remediation scheduling and tracking.
The information Security Team will run internal and external penetration testing annually on the PCI-DSS environment as well as on a selected rotation of non-PCI applications. Penetration tests include network-layer penetration tests and application-layer penetration tests.
Application of System/Application Patches
Patches must be applied following the patching schedule below. Any exploitable findings must be corrected and the vulnerability scan or penetration test repeated to verify corrections.
|Within 120 days||4.0-6.9|
In addition to the above patching guidelines, vulnerabilities and exploitable findings deemed critical by the Information Security Team must be patched as soon as possible.
Automated Monitoring and Alerting
Loyola employs the use of intrusion-prevention systems (IPS). All traffic at the perimeter of the cardholder data environment as well as at critical points in the cardholder data environment are monitored. All IPS monitoring points are configured to alert personnel of suspected compromises. IPS configurations and devices are configured, maintained, and updated per vendor instructions to ensure optimal protection.
Exceptions to this policy will be handled in accordance with the ITS Security Policy.
This policy will be maintained in accordance with the ITS Security Policy.
In emergency cases, actions may be taken by the Incident Response Team in accordance with the procedures in the ITS Incident Response Handbook. These actions may include rendering systems inaccessible.
CVE - The Common Vulnerabilities and Exposures (CVE) system provides a reference-method for publicly known information-security vulnerabilities and exposure.
SME - Subject Matter Expert
ITS Incident Response Handbook
ITS Security Policy
ITS Vulnerability Assessment Authorization Form
- September 30, 2008: Initial Policy
- September 18, 2012: Added section for PCI Compliance
- June 17, 2015: Annual review for PCI Compliance
- July 24, 2015: v1.3 Added additional PCI 3.1 information
- August 8, 2014: v1.2 Added section for PCI 3.0 Compliance
- August 4, 2015 : v1.4 Added risk rangking meeting section and definitions