Site Menu
- Policy
- University
- State & Federal
- Institutional Data
- Tools & Templates
- Standards & Frameworks
- FAQ
- Links
- Contact Us
- Site Map
What's New?
Gramm-Leach-Bliley Training New training created for those with access to customer information at the university.
Units Can Access Information Security Monthly Status Reports via Web Form Colleges and administrative units can submit their monthly information security status reports online using a web form. Use the links below to access the form and download instructions.
Hot Topics
- Institutional Data Policy Training
- Data Classification
- Implementation Plan
- University Security Standards (UCSS)
- Relevant Federal Laws & Regulations
Incident Response
Restricted Data FAQ
Below are commonly asked questions regarding restricted data. Additional quetions on data classification are available in the Data Classification and Access Control FAQ.
- What data elements have been identified as Restricted Data?
- What constitutes appropriate use of Restricted Data?
- What requirements are there on Restricted Data?
- Who is responsible for classifying a data element as Restricted Data?
- Who are the Data Stewards?
- When will it be necessary to classify and inventory data?
- Faculty and staff in my department primarily have access to Social Security Number information via reports generated from the student system. What actions are being taken to protect the Social Security Number information on these reports?
- We currently incorporate a portion of the Social Security Number (or other restricted data element) in new user passwords as a default. What other options are available?
- Can you provide examples of what other areas have done to protect restricted data?
- How are historical records that contain restricted data affected by the Institutional Data policy?
- What other requirements should be considered?
- Is it appropriate to include Restricted Data while responding to an Ohio Public Records Request?
- Who can I contact for additional information on responding to Public Records Requests?
Download a PDF copy of these FAQ
Further Questions?
If you have additional questions, please use the email form at the bottom of this page to contact us.
What data elements have been identified as Restricted Data?
- Social Security Numbers and other personally identifiable information such as driver’s license, state identification card, etc.
- Bank account information
- Credit card information
- Student record information that is linked to an individual student by name such as grades/transcripts, class enrollment information, student financial aid, grants and loans, etc.
- Patient health information
What constitutes appropriate use of Restricted Data?
What requirements are there on Restricted Data?
- Restricted Data must be encrypted if stored or used on portable devices, if removed from a secure university location, or if electronically transmitted.
- Restricted Data must never be stored on a personally-owned computer or storage device.
- Restricted Data must not be stored or used by an external service provider or agent without a contractual agreement to provide appropriate protection to the same standards as applied at the university.
Who is responsible for classifying a data element as Restricted Data?
Who are the Data Stewards?
When will it be necessary to classify and inventory data?
Faculty and staff in my department primarily have access to Social Security Number information via reports generated from the student system. What actions are being taken to protect the Social Security Number information on these reports?
We currently incorporate a portion of the Social Security Number (or other restricted data element) in new user passwords as a default. What other options are available?
- The longer the password, the more secure it is. Most areas are encouraging at least ten digits with a combination of alphabetic (both lower and upper case), numeric and special characters.
- New users should always be forced to the default password at the first login
- Users should be forced to periodically change passwords, preferably every 90 to 120 calendar days
Can you provide examples of what other areas have done to protect restricted data?
- Utilize shredding for document destruction. This has included installing an office shredder or contracting with a shredding service.
- Modified forms to eliminate the restricted data field or moved the restricted data field to the bottom so it can be torn off and destroyed
- Requested that third party vendors/agencies implement protection of restricted data that is being used/provided on behalf of the University
- Obtain restricted data directly from employees or students so the University can stop sending it through files and spreadsheets
- Installed a central secure server where customers can access data and files
- Implemented encryption software on desktops, laptops and other portable devices to protect the data should the equipment be stolen or lost
How are historical records that contain restricted data affected by the Institutional Data policy?
What other requirements should be considered?
- Anyone with access to Restricted or Limited Access Institutional Data shall have unique and individual user credentials such as a user id and password.
- Access shall be deactivated after a period of inactivity not to exceed twelve months.
- Terminated employees shall lose access as of their termination date.
- The data access request process shall be formalized and auditable. The request process must include appropriate approvals, a description of the specific data requested, the level of access requested (read, write), and the purpose for accessing the data. Data access requests should be maintained in order to support the need to audit data access permissions throughout the complete data access lifecycle (creation through termination).
- Once data access is approved for a data user or data custodian, data stewards are responsible for providing access to the Institutional Data Policy and the following information specific to the data being requested: 1) data documentation and usage guidelines, 2) the data classification policy including information on associated state and federal regulations, and 3) required minimum safeguards for protected data.
- A robust authentication process in compliance with university computer security standards and consistent with the level of risk associated with unauthorized access is required for access to all limited Access and Restricted data.
- Maintain and monitor user access and login information.
- Data access processes, procedures and authorizations must be reviewed on an annual basis by each data steward to ensure that access remains appropriate.
Is it appropriate to include Restricted Data while responding to an Ohio Public Records Request?
Who can I contact for additional information on responding to Public Records Requests?
Further Questions?
If your question is not listed in the above FAQ, please use the form below to contact us. We will respond to your inquiry as soon as possible.
