University Policy Details
Title: Security Testing and Evaluation
Author: University Information Technology Services
Effective Date: 08/31/2008
Applies To: Employees
Last Reviewed Date: 11/18/2008
Description: Security Testing and Evaluation
For More Information Contact: Director of IT Security, Policy and Quality Assurance
Contact Telephone Number: 860-486-4357

 

Security Testing and Evaluation

 

Background and Reasons for the Policy: The University of Connecticut views University Data, in all its forms and throughout its life cycle, as an asset of the University. University Data must be protected to comply with the policies of the University and to meet requirements of Federal and State laws such as the:

  • Family Rights and Privacy Act (FERPA)
  • Health Insurance Portability and Accountability Act (HIPAA)
  • Electronic Communications Privacy Act (ECPA)
  • Gramm-Leach-Bliley Act (GLBA)
  • Children's Online Privacy Protection Act (COPPA)
  • Freedom of Information Action (FOIA)
  • Connecticut Personal Data Act

Purpose of Policy: The purpose of this policy is to ensure that the University has implemented processes for periodically testing, reviewing, and revising the safeguards used to protect its information technology resources.

Expected Institutional Outcome: This policy will help demonstrate an ongoing University commitment to improvement of the safeguards used to provide security for electronic data stored, used, or transmitted using the University's computing resources.  The evaluations should demonstrate that appropriate safeguards are in place and that they are working effectively.

Applicability of Policy: This policy applies to any department within the University that stores, uses, or transmits University Data or electronic data that is subject to State or Federal regulations that require security protections for data covered by those regulations.  The policy is also recommended for all departments that have other data that should be protected from unauthorized disclosure, interrupted availability, or damage.

Definitions:

University Data: Items of information that are collected, maintained, and utilized by the University for the purpose of carrying out institutional business subject to or limited by any overriding contractual or statutory regulations. University Data may be stored either electronically or on paper and may be of many forms (including but not limited to: text, graphics, images, sound, or video). Research data, scholarly work of faculty or students, and intellectual property that do not contain personally identifiable information or other data protected by law or University policy are not covered by this policy.

Policy Statement:Each impacted department within the University will develop processes and controls for testing and evaluating the procedures, mechanisms, and other safeguards used to protect the security of data that may be electronically used, stored, or transmitted using information technology resources (including the facility, equipment, software and data) that are under its control.  At a minimum, these evaluations will include:

  1. Technical Evaluation. A program for periodically evaluating the technical procedures and mechanisms that are used to protect computing resources under the control of the department.  This evaluation will focus on the software, hardware, and other tools and mechanisms used by the department to protect its computing resources. 
  2. Administrative Evaluation:  A program for periodically evaluating the administrative safeguards that are used to protect computing resources under the control of the department.  This evaluation will focus on policies, procedures, guidelines, training, and similar safeguards used by the department.

Responsibilities:  University officials with delegated responsibilities for data as defined in the Policy on Roles and Responsibilities with Respect to University Data are responsible for the security of the information technology resources (including the facility, equipment, software and data) that are within their control and/or protection.  They are also responsible for ensuring that they remain knowledgeable about regulatory and University security requirements impacting their data.  They may delegate the programs for evaluating the security for those resources to the system administrators who they may appoint to manage the resources for them.

Departments and units must adhere to the Responsibilities of Individual Departments and Units policy when developing required processes.  The University's security policies set a minimum level of protection for information technology resources.  The processes and technologies instituted by departments must achieve that level of protection.  They may provide additional protections as needed when stricter requirements apply to the departments or operating units.  When designing or implementing security policies, procedures, or technical solutions that respond to unique departmental needs, the departments should ensure that they are in compliance with the Physical Network Access policy.

Enforcement and Review:

The Chief Information Officer has overall responsibility for this policy.

The
Chief Information Officer will review this policy on a bi-annual basis and respond to formal complaints resulting from the implementation of this policy.

Any individual who suspects a violation of this policy may report it to the Compliance Office in the Office of Audit, Compliance and Ethics at (860) 486-4526, or anonymously through the Reportline (https://www.compliance-helpline.com/uconncares.jsp).  Violations of this policy may result in appropriate disciplinary measures in accordance with University Laws and Bylaws, General Rules of Conduct for All University Employees, applicable collective bargaining agreements, and the University of Connecticut Student Conduct Code.

Policy Implementation Guidelines: Departments required to implement these security management processes should also refer to http://itpolicy.uconn.edu/,  where UITS maintains a set of documents for policies, procedures, guidelines, and standards that provide additional detail.

 

Last updated: August 2008