IT Policies and Procedures

Home Information Technology IT Policies and Procedures


Welcome to the OPSU IT Policies and Procedures page. Here you’ll find comprehensive documentation outlining the university’s technology policies, guidelines, and best practices for using OPSU’s IT resources. These policies are designed to ensure a secure, efficient, and productive technology environment for all students, faculty, and staff.

Policies

Acceptable Use Policy

Overview

This policy establishes the acceptable usage guidelines for all OPSU-owned technology resources. These resources can include, but are not limited to, the following equipment:

  • Computers
    • Desktop Computers, Mobile Devices, Servers, etc.
  • Network Equipment
    • Switches, Routers, Network and Communications Cabling, Wall Plates, Wireless Antennas, Wireless Bridge Devices, Fiber Optic Lines, Fiber Optic Equipment, VoIP Phones, etc.
  • Audio/Video Equipment
    • Video Codecs, HDTVs, Document Cameras, Projectors, Security Cameras, Miscellaneous Cabling, Digital Cameras and Camcorders, Printers, Copiers, Fax Machines, etc.
  • Software
    • Operating Systems, Application Software, etc.
  • Resources
    • Group Drive File Storage, Website File Storage, Email Accounts, Social Networking Accounts, etc.

This policy applies to all employees, contractors, consultants, temporaries, and other workers at OPSU, including any and all personnel affiliated with third parties, including vendors. This policy applies to all equipment that is owned or leased by OPSU.

Policy

While OPSU’s IT Department desires to provide a reasonable level of freedom and privacy, users should be aware that all OPSU-owned equipment, network infrastructure, and software applications are the property of OPSU and therefore are to be used for official use only. Also, all data residing on OPSU-owned equipment is also the property OPSU and therefore, should be treated as such, and protected from unauthorized access.

The following activities provide a general roadmap to use OPSU’s technology resources in an acceptable manner:

  • All passwords used to access OPSU systems must be kept secure and protected from unauthorized use.
  • No user account can be shared between individuals without a valid reason and written permission from the OSU A&M Chief Information Officer. Authorized users are responsible for the security of their own passwords and accounts.
  • Do not transfer personally identifiable information on portable equipment and storage
  • Public postings by employees from a OPSU email address should contain the following disclaimer stating that the opinions expressed are strictly their own and not necessarily those of OPSU, unless the posting is in the course of business duties:
    • Any views or opinions presented in this message are solely those of the author and do not necessarily represent those of Oklahoma Panhandle State University. Employees of Oklahoma Panhandle State University are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by electronic communications. Any such communication is contrary to OPSU policy and outside the scope of the employment of the individual concerned. OPSU will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising.
  • All computers residing on the internal OPSU network, whether owned by the employee or OPSU, shall be continually executing approved virus-scanning software with a current, up-to- date virus database.
  • Employees must use extreme caution when opening e-mail attachments received from unknown senders.
  • Personally identifiable information cannot be sent via electronic means and should be transferred within the internal network or through secure VPN connections.
  • Off-campus work should be completed via a secure VPN connection so that no data is transferred off-network.
  • All workstations should be kept Users should lock the workstation when not attended to protect unauthorized users from accessing secure files.

The following activities are, in general, prohibited. Employees may be exempted from these restrictions during the course of their legitimate job responsibilities (e.g., systems administration staff may have a need to disable the network access of a host if that host is disrupting production services).

Under no circumstances is an employee of OPSU authorized to engage in any activity that is illegal under local, state, federal or international law while utilizing OPSU-owned resources.

The lists below are by no means exhaustive, but attempt to provide a framework for activities which fall into the category of unacceptable use.

The following activities are strictly prohibited, with no exceptions:

  • Violations of the rights of any person or company protected by copyright, trade secret, patent or other intellectual property, or similar laws or regulations, including, but not limited to, the installation or distribution of “pirated” or other software products that are not appropriately licensed for use by OPSU.
  • Unauthorized copying of copyrighted material including, but not limited to, digitization and distribution of photographs from magazines, books or other copyrighted sources, copyrighted music, and the installation of any copyrighted software for which OPSU or the end user does not have an active license is strictly prohibited.
  • Exporting software, technical information, encryption software or technology, in violation of international or regional export control laws, is The appropriate management should be consulted prior to export of any material that is in question.
  • Introduction of malicious programs into the network or server environments (e.g., viruses, worms, Trojan horses, rootkit, etc.).
  • Revealing your account password to others or allowing use of your account by This includes family and other household members when work is being done at home.
  • Using a OPSU computing asset to actively engage in procuring or transmitting material that is in violation of sexual harassment or hostile workplace laws in the user’s local jurisdiction.
  • Making fraudulent offers of products, items, or services originating from any OPSU account.
  • Making statements about warranty, expressly or implied, unless it is a part of normal job duties.
  • Effecting security breaches or disruptions of network communication. Security breaches include, but are not limited to, accessing data of which the employee is not an intended recipient or logging into a server or account that the employee is not expressly authorized to access, unless these duties are within the scope of regular duties. For purposes of this section, “disruption” includes, but is not limited to, network sniffing, pinged floods, packet spoofing, denial of service, and forged routing information for malicious purposes.
  • Port scanning or security scanning is expressly prohibited unless prior notification to the OPSU IT Department is made.
  • Executing any form of network monitoring which will intercept data not intended for the employee’s host, unless this activity is a part of the employee’s normal job/duty.
  • Circumventing user authentication or security of any host, network or account.
  • Interfering with or denying service to any user other than the employee’s host (for example, denial of service attack).
  • Using any program/script/command, or sending messages of any kind, with the intent to interfere with, or disable, a user’s terminal session, via any means, locally or via the Internet/Intranet/Extranet.
  • Sending unsolicited email messages, including the sending of “junk mail” or other advertising material to individuals who did not specifically request such material (email spam).
  • Any form of harassment via email, telephone or paging, whether through language, frequency, or size of messages.
  • Unauthorized use, or forging, of email header information.
  • Solicitation of email for any other email address, other than that of the poster’s account, with the intent to harass or to collect replies.
  • Creating or forwarding “chain letters”, “Ponzi” or other “pyramid” schemes of any type.
  • Use of unsolicited email originating from within OPSU’s networks of other Internet/Intranet/Extranet service providers on behalf of, or to advertise, any service hosted by OPSU or connected via OPSU’s network.

Back To Top

Access Control Policy

Overview

Access controls are designed to minimize potential exposure to the institution resulting from unauthorized use of resources. These controls would also help to preserve and protect the confidentiality, integrity, and availability of the institution networks, systems, and applications.

Policy

Access to institution-owned systems will only be provided to users based on business requirements, job function, responsibilities, or need-to-know requirements. All additions, changes, and deletions to individual system access must be approved by the appropriate supervisor via the appropriate process, with a valid business justification. Access controls to institution-owned systems are implemented via an access control application. Account creation, deletion, and modification as well as access to protected data and network resources is managed using these processes. On an annual basis, the institution will audit all user and administrative access to institution-owned systems. Discrepancies in access will be reported to the appropriate supervisor in the responsible unit and remediated accordingly.

Separation of Duties – Access should be given to individuals based upon their separate duties for each position they hold within the institution. This is to help reduce the likelihood that access is given for which the individual has no legitimate business need.

Least Privilege Access – All access should begin with least privilege within the system. Additional access above and beyond basic query or user access should be requested and applied based upon the user’s position, job duties, and requirements set forth in their job description or by their supervisor. All access should be issued through the identity management system (O-Key/C-Key/LionKey/GoldKey/AggieAccess) or the system access request form (https://apps.okstate.edu/access_request).

Automated Session Time-Out – Where capable, all systems should employ an automated timeout mechanism so users will be automatically logged off the system upon a predetermined amount of time away from the system.

Unsuccessful Login Attempts – When possible, all unsuccessful login attempts should be logged for all systems and upon a specified number of unsuccessful attempts (no more than 5), the user account should be locked temporarily to decrease the likelihood of a brute-force attack on our systems.

Concurrent Login Limitation – Where available, all systems should employ concurrent login limitations so that a given user account can only login once to any given system.

Security Use Banner – Where available, all systems should display a security banner warning of unauthorized access to the given system and should reference any punishment should the user try to gain access to resources for which they are not allowed.

Previous Login Notification – Where available, all systems should notify the user of the last previous login with a date and time stamp.

Remote Access Control – All remote access to systems should be restricted to only those users that require access from outside the campus network. When available, external access should mirror internal access as if the employee was sitting at their desk.

Use of Systems by Third Parties –All third-party access should be granted through the similar mechanisms employed for standard employees using separation of duties and least privilege access.

Risk Management – All recommendations herein should be adhered to when possible. However, it is understood that some systems have limitations technologically that may not allow the deployment of some recommendations above. Due to this, the institution should manage the risk associated with not deploying a specific recommendation and choose an appropriate option:

  • Identify and accept the risk on a permanent basis
  • Identify and accept the risk temporarily until a suitable replacement system is identified and implemented that fulfills all requirements
  • Do not accept the risk and immediately identify another system that will fulfill all requirements

Back To Top

Accessibility Policy

Overview

This policy establishes the accessibility guidelines for all OPSU-owned technology resources. The purpose of this policy is to ensure that every OPSU student is presented with an equal opportunity to learn and that all employees can adequately use the required technology equipment for the purpose of their required occupation. These requirements must be met where any learning impairment exists for any OPSU student or work limitation exists for any OPSU employee. These types of accessibility requirements may include, but are not limited to, the following applications or devices:

  • Screen reading software
  • Screen magnification software
  • Stereo headsets or other sound devices

This policy applies to all OPSU-owned technology resources in labs and other learning areas for student use and in departmental or teaching areas for employee use.

Policy

A reasonable attempt shall be made at all times to address the needs of our students and employees, particularly when those needs are due to an accessibility issue presented by a physical impairment or learning disability of some kind. The OPSU IT Department shall make every effort to ensure that each and every student is presented with an equal or comparable learning environment regardless of the hurdle they may face.

The OPSU IT Department will always strive to offer technology solutions that help improve the learning environments for all students but will be particularly diligent in ensuring that no student will be unable to learn within a classroom due to a physical impairment or learning disability of some kind. The same will be provided for any employee requiring accommodation due to a physical impairment or learning disability of any kind.

Please note that advance notice of these needs is required and may change due to the request. For instance, additional software needs will take some time to produce an order and install the software so it will be unreasonable to expect a request such as this to have an immediate turnaround time.

Casting aside the general expectations above, the OPSU IT Department cannot be held liable for issues surrounding software application issues, hardware failures, or the inability of employees or students to convey their respective needs in a reasonable amount of time to allow such software or hardware to be properly installed.

With that said, the OPSU IT Department will continually strive to ensure that all learning environments have the necessary technology and are adequately structured in a way to provide the most conducive learning environment possible, regardless if a learning disability or physical impairment may be present for any student. The OPSU IT Department will also ensure that all employee areas are adequately designed to facilitate a productive working environment as well.
Back To Top

Asset Management Policy

Overview

This policy helps establish standards for managing IT assets. Assets are defined as both hardware devices and software systems that are owned by the institution. This policy will dictate how assets are managed through the full lifecycle of the asset.

It is important to note that state requirements may change or vary to require us to include assets that are purchased at specific monetary value thresholds. However, IT maintains the policy that all IT-related assets should be tagged and tracked appropriately.

All institution-owned IT assets are subject to this policy.

Policy

The steps in the asset lifecycle are as follows:

  • Acquisition
  • Deployment/Installation
  • Utilization
  • Decommission
  • Disposal/Destruction/Recycling

Asset Management focuses on the maintenance, support, tracking, and usage of an asset between the first step, Acquisition, and the fifth step, Disposal/Destruction/Recycling.

As soon as an asset is acquired and arrives on campus it reaches the deployment/installation step. Here, it should be prepared for use and immediately tagged with an institutional asset tag and added to the campus inventory system. IT should work closely with Finance since state requirements dictate all institutions should supply an annual IT asset report. It is important that all assets are tagged appropriately in inventory. IT should be part of this process to ensure accurate data is included in the inventory. Relevant asset data should be included, but are not limited to, the following items:

  • Make
  • Model
  • Acquisition Date
  • Cost
  • Serial Number
  • Asset Number
  • Location
  • Owner

Once an asset is placed into service it reaches the utilization stage. At this point, the location and owner should also be recorded in relevant systems (i.e. SCCM, Meraki Dashboard, Computrace/Absolute). As this changes, it should be updated accordingly in all relevant locations to maintain a complete view of our inventory.

After an asset has reached its useful end-of-life, it then reaches the decommission stage. All relevant data or portions of the asset hosting data should be removed (i.e. hard drives, memory, storage drives). These parts of the asset are separate and sensitive and should be treated as such.

When decommission is completed, the asset may move to Disposal/Destruction/Recycling step. All data removed from the asset should be stored securely and eventually securely destroyed and disposed of. This can be performed by certified drive destruction techniques that are approved by the State of Oklahoma. The remaining portions of the asset should be stored until disposal/recycling can occur. Options for the remaining portions are surplus, agency transfer, or eventual disposal. Once this is completed, the asset should be removed from the inventory list as it is no longer owned by the institution.

Care should be taken to ensure this process is upheld for all orders with relevant IT assets. Maintaining a proper inventory list is critical to knowing what inventory the institution currently has on-hand and in-use. This is important for planning purposes and helps us to be good stewards of state resources.
Back To Top

Auditing Policy

Overview

This policy addresses third-party entities and their ability to conduct an internal technology audit. This type of audit is basically a “stress-test” on our technology resources to evaluate the level of security our technology systems present as well as the level of scrutiny it can withstand.

Vulnerabilities are a primary focus for the OPSU IT Department. Seeking these vulnerabilities out before they develop into potential problems is best for OPSU, IT resources, employees, associates, and students. To accomplish this, internal audit is necessary to periodically determine what vulnerabilities may exist within OPSU’s technology resources.

The purpose of this agreement is to set forth a policy regarding network security scanning offered by a third-party audit group to OPSU. The OPSU IT Department shall allow the utilization of various methods (both hardware and software) to perform electronic scans of our networks, firewalls, and other hardware devices located at OPSU.

Audit may be conducted to:

  • Ensure integrity, confidentiality and availability of information and resources
  • Investigate possible security incidents to ensure conformance to the established OPSU IT Department’s security policies
  • Monitor user or system activity where appropriate

Policy

This policy covers all computers, equipment, and communication devices owned or operated by OPSU. This policy also covers any computers, equipment, and communications devices that are present on OPSU premises, but which may not be owned or operated by Oklahoma Panhandle State University. The third-party audit group will not perform Denial of Service activities at any time during an audit.

When requested, and for the purpose of performing an audit, consent for the access required to perform the scan will be provided to members of the third-party audit group by the OPSU IT Department. The OPSU IT Department hereby provides IT consent to allow the third-party audit group to access IT networks, firewalls, and other hardware devices to the extent necessary to perform the scans authorized in this agreement. The OPSU IT Department shall provide protocols, addressing information, and network connections sufficient for the third-party audit group to perform network scanning.

The access involved in the scan may include:

  • User level and/or system level access to any computing, networking equipment, and communications devices
  • Access to information (electronic, hardcopy, ) that may be produced, transmitted, or stored on OPSU equipment and/or premises
  • Access to work areas (labs, offices, cubicles, storage areas, )
  • Access to interactively monitor and log traffic on OPSU networks

Since OPSU gains access to certain resources from third-party entities, cooperation from these resources may be required to perform a full network scan. For instance, OneNet provides the Internet connections to the OPSU networks. Because of this, a comprehensive network scan may require the assistance of OneNet or other third-party service providers should part of the scanning activities originate outside the OPSU network.

Network performance and/or availability may be affected by the network scanning. The OPSU IT Department releases any third-party audit group of any and all liability for damages that may arise from network availability restrictions caused by the network scanning, unless such damages are the result of the third-party audit group’s gross negligence or intentional misconduct.

The OPSU IT Department shall identify, in writing, a person to be available should the third-party have questions regarding data discovered or should the third-party require assistance.

OPSU and the third-party audit group shall identify, in writing, the allowable dates for the audit vulnerability scan to take place. Permission to conduct a vulnerability scan will be obtained from the Director of IT, Vice President of Outreach, the President, or a designee a minimum of 48 hours prior to the test.
Back To Top

Backup Policy

Overview

The OPSU IT Department maintains systems to hold and retain all essential data for each individual department. This storage area, or group drive as it is referred to, is used to securely store all data for any given department. Because of this centralized storage arrangement, the OPSU IT Department is

able to offer secure backup capability ensuring all data will be accessible in the event of a disaster or other event in which the data would be destroyed.

This policy establishes regular backup schedules for our group drive storage devices and pertains to all this data. With that said, this does not pertain to individual, departmental, or computer lab devices, mobile devices, or other portable storage medium where the data resides locally on the device or medium. The OPSU IT Department does not guarantee backup for any of these types of devices or storage medium.

Policy

Every effort shall be made by the individual departments and employees at OPSU to store sensitive, important, and confidential data on their respective group drive. As mentioned above, the OPSU IT Department cannot be held liable for issues with data stored elsewhere.

Regular backup schedules are in place within the group drive storage device to ensure that backups occur at regular intervals and over a time span to provide ample opportunity for the OPSU IT Department to recover a file, folder, or group of such. It should be noted that the OPSU IT Department does require immediate notification in the event a file, folder, or collection of either is found to be missing, corrupt, or otherwise damaged. Waiting to inform the OPSU IT Department decreases the probability of successful recovery.

Specific information regarding backup restoration on an institution scale can be found in the OPSU IT Department’s Disaster Recovery Plan (DRP) or the associated Backup Priority List (BPL). These deal with catastrophic recovery needs that affect multiple departments or the institution as a whole.

The hardware that the OPSU IT Department uses consists of a Dell server to house departmental data. A dedicated backup repository is setup at Oklahoma State University as an off-campus backup location in the event data or the campus is compromised.

The primary device in Goodwell holds all data and backups and serves as the primary device for file access and immediate backup. The secondary, off-site device at OSU replicates all data from the Goodwell device to create a stable off-site copy of the data and backups present.

For this document, considering the type of hardware described above, normal backups do not necessarily retain the same meaning as when used in conjunction with other hardware devices. Because of this, the following descriptions are provided, based on the current hardware being used, so as to better understand the overall backup process.

  • Backups: These refer to snapshots taken of the file structure and database. These snapshots are essentially pointers to changes occurring within the storage device since the last scheduled snapshot. This greatly reduces the file storage requirements necessary to hold backups while still providing the same or superior level of backup capability found in other devices.
  • Replication: This refers to the copying process of all data and associated backups from the primary backup device in Goodwell to the secondary backup device at OSU. During a replication, all data and backups are replicated so that a mirror copy is retained at the OSU location for off-site, backup capability should a disaster or other issues occur.

Regularly scheduled backups and replications shall be performed by the OPSU IT Department using the following schedule:

Daily Local Backups Held at OPSU

  • 5:30 p.m. Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday
  • Data is baked up locally via a script managed by OPSU IT Daily Replication to OSU
  • 12:01 a.m. Monday, Tuesday, Wednesday, Thursday
  • Incremental data is replicated from the OPSU Goodwell Campus to the OSU location Weekly Full Backups to OSU
  • 5:30 p.m. Friday
  • Full backup is transmitted from the OPSU Goodwell Campus to the OSU location

All backups are clearly labeled so as to distinguish one from another easily. At minimum, the following information is provided for each backup file:

  • Time (CST) – g. 12:00:00 AM or 12:34:59 PM
  • Date – e.g. 12/31/10 or 2/29/12
  • Backup Type – e.g. Hourly, Daily, Weekly, Incremental, End of Year

Testing for data integrity will be performed at regularly scheduled intervals by the backup hardware but may also be performed manually at random times to verify the validity, accuracy, and authenticity of the backup. These random tests should total no less than six per year and it is recommended that these tests fall approximately two months apart, less if more than the minimum number of tests are used.

We encourage that backup tests be taken within one week of the completion of the yearly and mid- yearly backups with the remaining backups spaced throughout the remaining months of the year. If six are used, it should follow this testing schedule:

  • Test 1 – January 1-7
  • Test 2 – March 1-7
  • Test 3 – May 1-7
  • Test 4 – July 1-7
  • Test 5 – September 1-7
  • Test 6 – November 1-7

If more than six tests are used, then the schedule may be set at the discretion of the OPSU IT Department, however, two of the tests must occur no later than one week after the yearly and mid- yearly backups are completed.

Testing shall consist of one or more of the following methods of data validation and verification of accuracy and authenticity:

  • Random Dummy File Restoration: Six to twelve dummy files are inserted on the file server at random locations. Afterwards, we will intentionally delete these dummy files. Then, recovery will be tested to verify data is being restored properly. If this verifies the data is being restored properly, the test is completed and the dummy file may be removed.
  • Random Actual File Restoration: Recovery of a six to twelve actual random files located on the Comparisons will then be made with current versions of the same files to verify content and accuracy of restoration process. If the comparisons verify that the recovery was successful, then the test is completed.
  • Random File Location Verification: Movement of a single dummy file to various locations on the file server. Initially the file is inserted onto the file server and backups are tested to verify the file exists in backups at the initial location. If this is confirmed, then the file is moved on the file server to a second location and backups are tested yet again to verify that

the file is in the second location. Once this is confirmed, the file is moved for a third time and backups are once again tested to verify the file exists in the new location. If this is confirmed, then the test is completed and the dummy file may be removed. Backups are working correctly and file contents and locations are being updated appropriately.

  • Miscellaneous: Other tests may be used at the discretion of the OPSU IT Department with only one restriction: they may not interfere with access or otherwise cause any data loss on the file server.

All restoration processes will follow, at minimum, one of the following methods:

  • Re-routing primary traffic from backup and storage device in Goodwell to accompanying device in OSU or vice-versa
  • Physically transporting one device to another location
  • Copying all files or a subset of files from the backup equipment to the file server
  • Via the testing process described in this document
  • Utilizing the OPSU IT Department’s Disaster Recovery Plan
  • Utilizing the OPSU IT Department’s Backup Priority List
  • Other methods, approved by the OPSU IT Department, that do not interfere with access or otherwise cause any data loss on the file server

If it is found that a scheduled backup process is incomplete or missing due to a hardware or software malfunction, then the backup will be completed as soon as possible and a hardware test will be needed to verify no long-term problems exist that may affect backups in the future. Should a hardware test yield results that indicate serious issues, then a replacement for the faulty hardware should be found as soon as possible in order to prevent such issues from occurring in the future.

If these issues prevent backups from occurring, then the off-site backup device in OKC will be transferred to primary backup duties and a secondary device should be purchased and then placed at Goodwell to regain primary functionality.

The following is the maximum number of backups and replications that the OPSU IT Department will retain at any one time. Once these backups or replications reach the maximum count, the oldest will be recycled so that the newest may be retained.

  • Daily Local Backup
    • Copies on file: 1 per day
    • 7 days’ worth of data at hourly intervals
  • Weekly Backup
    • Copies on file: 4 total
    • 4 weeks (approx. 1 months) worth of data at weekly intervals 

Online log files are retained consisting of information for each backup or replication process, hardware/software errors, access issues, or other critical errors involving the backup hardware.
Back To Top

Data Retention Policy

Overview

This policy will determine how long data shall be retained under the guidelines of federal and state law and within institutional policies as dictated herein.

Policy

All data shall be retained, at minimum, the time frame as specified in any current, standing federal or state law. No data residing within any OPSU facility or technology equipment will knowingly be destroyed prior to this timeframe unless such laws are modified to reflect a new time frame. If such changes do occur, the new timeframe will be susceptible to the new law and all data will be retained within the new specifications.

Under no circumstances is data to be removed, discarded, disposed of, or otherwise destroyed that will compromise legal compliance, data integrity, or institutional needs. The OPSU IT Department shall make every effort to extend the data retention timeframes of all data as long as the institution requires access without compromising any legal statues set forth regarding storage or destruction of such data. No data will be destroyed prior to or retained longer than any legal requirement dictates.

The OPSU IT Department will continually utilize backup equipment, secondary-site storage, and regular backup schedules to ensure that critical data is retained and kept from corruption or other types of data loss. Every effort shall be made to ensure the institutional data needs are given top priority in the event of a loss of data, corruption of data, or if data recovery is necessary.

This policy shall never decrease the retention time under any state or federal law but may only increase the retention timeframe required by the institution. This increase may only be applicable as long as it does not compromise the integrity, storage capability, or otherwise degrade the overall storage capability of the system being used.
Back To Top

Electronic Communications Policy

Overview

Electronic communication is necessary to fulfill multiple roles and activities here at OPSU. Because of the varying types of electronic communication, we will focus on those used primarily here at OPSU:

  • Email
  • Phone
  • Videoconferencing
  • Digital Signage

Email is the official method of communication at OPSU, both for students and employees. Business is conducted every day via email. Since email has both positive and negative connotations, it is imperative that we recognize that the positive aspects greatly outweigh the negative aspects.

However, we must also realize that the negative aspects exist and ensure that this method of communication is used effectively, efficiently, and for IT’s intended purpose.

OPSU’s phone system is used to transmit and receive audio/video within the institution to facilitate direct communication amongst employees and departments. It is also used to transmit and receive audio outside the institution to facilitate direct communication with vendors, students, other institutions, and other third-party entities. Because of this capability, we must ensure that it is used for work purposes.

Videoconferencing equipment is used primarily for instructional classrooms requiring connectivity to other OPSU locations and to local area high schools. Videoconferencing equipment is also used to facilitate conferences and meetings with other institutions, state agencies, or other third-party entities. Since this type of communication conveys not only audio, but video as well, it is particularly important for it to be used for IT intended purposes.

Digital signage is used on campus to convey student activities, important academic dates, campus events, and other information to students, employees, and visitors. Since this is also a visual and auditory communication mechanism, it is also important to ensure it is used for IT intended purpose as well.

Policy

Regardless of the type of technology being used, electronic communication is meant to serve the needs of the college by sharing information with students, employees, vendors, other state agencies, campus visitors, and other individuals. Because of the unique capabilities of each system it is important to realize that each type of communication method contains unique issues that must be addressed on a case-by-case basis; however, general rules can be set forth to ensure that any communication method is used wisely and according to IT intended purpose.

In general, OPSU’s electronic communication mechanisms are to be used to share information with students, employees, vendors, other state agencies, campus visitors, and other individuals.

It is also important to note that the true definition of information sharing at OPSU is to adequately convey the appropriate knowledge so that the College mission is not hindered but enhanced. This information is always to be distributed under the following assumptions:

Electronic communication from a OPSU resource…

  • …is always understood to represent an official statement from the institution.
  • …shall never be used for the creation or distribution of any information that meets the following criteria:
    • Disruptive
    • Offensive
    • Derogatory
    • Specific comments about race, gender, hair color, disabilities, age, sexual orientation, pornography, religious beliefs and practice, political beliefs, or national origin.
    • Any information that could be used to sabotage institutional progress.
    • Any personally identifiable information
  • …shall not be used for personal gain
  • …shall not be used extensively for personal use
  • …shall not be used to distribute malicious or harmful software or information. 

Back To Top

Emergency Notification Policy

Overview

OPSU maintains an emergency notification system that is used to notify students and employees who have opted in to the service via the AggieAccess website. This system is updated daily to reflect the current student data available so that any notification message will be delivered to the required student and employee list.

Policy

The OPSU Emergency Notification System is to be used, at all times, for emergency purposes or purposes deemed necessary by the President or designee only. The notification system is to be used to send messages via text to email addresses and mobile phones, via voice to office phones, personal phones, and mobile devices, and via applications to desktops and office phones.

At no time shall this system be used for normal messaging, notifications, or otherwise standard contact as this would compromise the importance of these messages and may create an environment where students and employees are able to overlook these types of messages because of the frequency with which they could occur.

With that said, tests of this system shall be conducted once a semester at minimum to ensure the system is functioning properly. Additional tests may be conducted but are not required; however,

more than four tests per semester may be too many to retain the importance of such messages when an actual emergency arises requiring the system to be operational.

Only users defined below shall be able to send emergency notification messages via this system:

  • Director of IT
  • Director of Communications
  • Vice President for Outreach
  • Other designee deemed necessary by the President

Back To Top

Encryption Policy

Overview

The purpose of this policy is to provide guidance that limit the use of encryption to those algorithms that have received substantial public review and have been proven to work effectively. Additionally, this policy provides direction to ensure that Federal regulations are followed, and legal authority is granted for the dissemination and use of encryption technologies outside of the United States.

While OPSU employees do not typically use encryption methods to a great extent, it is wise to follow the policy below if encryption of information is necessary on any device residing on campus.

Policy

A proven, standard algorithm such as Advanced Encryption Standard (AES) should be used as the basis for encryption technologies. This algorithm represents the actual cipher used for an approved application.

Additionally, the NSA mentions that AES encryption with 128-bit keys provides adequate protection for classified information up to the SECRET level so this should be the minimum level utilized by any encryption tool. Similarly, Ephemeral Unified Model and the One-Pass Diffie Hellman (ECDH) and the Elliptic Curve Digital Signature Algorithm (ECDSA) using the 256-bit prime modulus elliptic curve as specified in FIPS PUB 186-3 and SHA-256 provide adequate protection for classified information up to the SECRET level. During the transition to the use of elliptic curve cryptography in ECDH and ECDSA, DH, DSA and RSA can be used with a 2048-bit modulus to protect classified information up to the SECRET level.

The use of proprietary encryption algorithms is not allowed for any purpose, unless reviewed by qualified experts outside of the vendor in question and approved by the OPSU IT Department. Be aware that the export of encryption technologies is restricted by the U.S. Government. Residents of countries other than the United States should make themselves aware of the encryption technology laws of the country in which they reside.

Recent developments in the field of encryption have indicated that it is possible for an encryption key to stay resident in volatile memory long enough after shutdown for it to be stolen and used to break the encryption protecting the associated PC. Because of this, even though the use of encryption is recommended, specific rules are required in order to protect the encryption and, therefore, the data on the drive.

  • Never leave any PC unattended that contains confidential OPSU data or a method to access confidential OPSU data.
  • If you must leave a PC unattended that contains confidential information (i.e. in an open office or a conference room), only do so if proper encryption has been enabled and the PC has been powered off for no less than 5 minutes.
  • Never authenticate the encryption on a PC which contains confidential OPSU data or a method to access confidential OPSU data and leave it unattended, allow a non-OPSU user to utilize the device, or permit the device to be copied in any way.
  • Never disable or bypass the encryption on a PC which contains confidential OPSU data or a method to access confidential OPSU data.

If any user is unsure of the appropriate encryption standard to use or if encryption is necessary, he/she may take advantage of OPSU’s open-door policy and request assistance and information regarding these encryption standards and how to encrypt his/her data to secure it appropriately.
Back To Top

Enforcement Policy

Overview

This policy is to establish enforcement guidelines to ensure that all OPSU IT Department policies and procedures are adhered to and observed by all departments and individuals at OPSU including students, employees, visitors, vendors, etc. Anyone using technology resources at OPSU will be required to operate within the parameters described in this document or the following enforcement options may be administered.

Policy

All policies herein are applicable to any and all users of technology resources at OPSU.

If it is found that any individual, department, or external entity disobeys the policies and procedures set forth within this document, whether knowingly or unknowingly, then the enforcement of such policy may include, but may not be limited to:

  • Forced compliance with the policy
  • Disciplinary action including termination of employment, if an employee
  • Disciplinary action including expulsion from the College, if a student
  • Termination of vendor contract and or service agreement
  • Prosecution to the fullest extent of the law

Back To Top

Equipment Configuration Policy

Overview

This policy has been established to create a standard configuration for all technology resources at OPSU. Because of the variances between the types, makes, models, configurations, builds, versions, and brands of technology resources available, it is necessary to standardize all technology resources to make service and maintenance easier and also to help keep costs down.

Policy

All employees shall order and utilize equipment that is serviceable and recommended by the OPSU IT Department. Since equipment availability changes over time, especially when referring to technology, a comprehensive list indicating appropriate hardware would be virtually impossible to create. Because of this, any individual or department wishing to purchase technology equipment should first consult a OPSU IT Department personnel member for current specifications for any given piece of equipment.

This applies to any and all technology equipment including, but not limited to:

  • Computers (Servers, Desktop, Laptop, Tablets and Mobile Devices, )
  • HDTVs
  • Printers, scanners, copiers, fax machines, or all-in-one devices
  • Projectors, screens, and SmartBoards
  • Phones
  • Digital cameras and camcorders
  • Software (Application, Operating System, Network-Based, )
  • Other technology equipment not specifically mentioned here

For more details on procedures required to place an order for technology equipment, please see the Equipment Ordering Procedures included in this document for detailed instructions. OPSU IT shall approve all technology related purchases in the OKCorral purchasing system.
Back To Top

Guest/Visitor Access and Technology Use Policy

Overview

OPSU maintains an atmosphere that is open and allows guests and visitors access to resources, as long as such access does not compromise the integrity of the systems or information contained within the campus and does not introduce malicious software or intent to the internal network.

Policy

Guest and visitor access shall be classified into two types as described below:

  • Standard – Access granted to internet resources and institutional resources located
  • Special – Access granted above plus any internal access as requested by an individual with the authority to do so:
  • Vice President for Fiscal Services, Vice President for Academic Affairs, President, or other designee deemed necessary by the President

Internal Access may include:

  • Wireless VLANs (i.e. OPSU Public Wifi, OPSUstaff)
  • Wired VLANs (i.e. housing, guest)
  • Singular or multiple file access
  • System access such as Learning Management System, ID Card System, etc.

Under no circumstances should visitors be given special access unless permission has been obtained from the appropriate administrative personnel (i.e. a signature from one of the personnel above) along with detailed description of access.

To obtain guest/visitor access users should contact the OPSU IT Department with their requested system access requirements using the attached Authorization of User Access form.

For vendor access, please see the appropriate vendor access policy included herein.
Back To Top

Illegal File Sharing

Overview

Legal compliance is a primary focus at OPSU. Because of this, we have set forth this policy which addresses illegal file sharing legislation, legal alternatives to illegal file sharing, and penalties for violating state and federal copyright laws.

This policy applies to all OPSU employees, students, vendors, or visitors utilizing OPSU-owned computers, equipment, or the OPSU network.

Policy

File sharing (peer-to-peer) software programs have led to significant increases in anti-piracy efforts and legislation. Peer-to-peer software allows the sharing of files often consisting of copyrighted content such as music, movies, and software which usually occurs without the consent of the owner.

It is the policy of OPSU to respect copyright ownership and protections given to authors, owners, publishers, and creators of copyrighted work. It is against OPSU policy for any employee, student, affiliate, or visitor to copy, reproduce, or distribute any copyrighted materials on OPSU-owned equipment or the OPSU-managed network unless expressly permitted by the owner of such work.

OPSU also discourages the use of any file-sharing program as these types of programs may allow copyrighted material to be downloaded to a OPSU-owned computer or device. Many of these programs automatically place downloaded files in a shared folder on your computer, which means you could be sharing files without your knowledge. This also means that you may be held responsible for illegal file sharing, whether you are aware that copyrighted files are being shared or not.

OPSU also employs the use of network appliances, equipment, and rules to limit the amount of file- sharing traffic on the OPSU network. Active blocking of peer-to-peer traffic is used to protect the OPSU network from unwanted traffic and the presence of potentially malicious files introduced through file-sharing programs.

OPSU encourages employees, students, affiliates, and visitors to utilize legal alternatives to illegal file sharing. There are a variety of free and pay-per-use options available that can be used instead of illegal file sharing programs. Several of these free and pay-per-use options are listed below; however, this is in no way an all-inclusive list. OPSU leaves it to the discretion of the employee, student, affiliate, or visitor to decide which alternative to utilize. They are provided herein for reference only and OPSU does not endorse or provide any guarantee or support for any of the legal alternatives located below.

Educause – Legal Sources of Online Content

Pay-per use services (Per-Song, Per-Album, Per-Movie, etc.) or Subscription-based services (Per- Month)

Hulu Netflix
Amazon: Books/Newspapers, Video, Music, Games Disney+
YouTubeTV fuboTV
Philo SlingTV
iTunes CinemaNow
Vudu GameFly
MP3 eMusic
Napster

Free services

Pandora iHeartRadio
Spotify YouTube
Blip.fm [adult swim]
Last.fm TV.com
LiveXLive FOX
ESPN360 ABC
CBS NBC

Back To Top

Information Sensitivity Policy

Overview

Information sensitivity is a primary focus at OPSU. Since we are an educational entity, we deal with many different types of information, some for public use, some not. To make these distinctions, this document will address both types of information.

This policy is intended to help employees determine what information can be disclosed to non- employees, as well as the relative sensitivity of information that should not be disclosed outside of OPSU without proper authorization.

The information covered in these guidelines includes, but is not limited to, information that is either stored or shared via any means. This includes: electronic information, information on paper, and information shared orally or visually (such as via phone and videoconferencing).

All employees should familiarize themselves with the information labeling and handling guidelines that follow this introduction. It should be noted that the sensitivity level definitions were created as guidelines and to emphasize common sense steps that you can take to protect confidential information (e.g. confidential information should not be left unattended in conference rooms.).

NOTE: The impact of these guidelines on daily activity should be minimal.

Questions about the proper classification of a specific piece of information should be addressed to your supervisor or the OPSU IT Department. Questions about these guidelines should be addressed to the OPSU IT Department.

Policy

By grouping information into two different categories, we can adequately address the needs of each type of information. The first type, public Information, is information that has been declared public knowledge by someone with the authority to do so, and can freely be given to anyone without any possible damage to the institution. The second type, confidential information contains all other information. It is a continuum, in that it is understood that some information is more sensitive than other information, and should be protected in a more secure manner. Included is information that should be protected very closely, such as specific personnel information, student data, billing information, etc. Also included in confidential information is information that is less critical, such as telephone directories, personnel information, etc., which does not require as stringent a degree of protection.

A subset of the latter is third-party confidential information. This is confidential information belonging or pertaining to another corporation which has been entrusted to OPSU by that company under non- disclosure agreements and other contracts. Examples of this type of information include everything from joint development efforts to vendor lists, customer orders, and supplier information. Information in this category ranges from extremely sensitive to information about the fact that we’ve connected a supplier / vendor into OPSU’s network to support our operations.

OPSU personnel are encouraged to use common sense judgment in securing confidential information to the proper extent. If an employee is uncertain of the sensitivity of a particular piece of information, he/she should contact their supervisor and/or the OPSU IT Department for more information and instructions on how this information should be handled.

The sensitivity guidelines below provide details on how to protect information at various sensitivity levels. Use these guidelines as a reference only, as OPSU Confidential Information at each level may necessitate more or less stringent measures of protection depending upon the circumstances and the nature of the OPSU Confidential Information in question.

  • Minimal Sensitivity:
    • Description: General information, some personnel, and technical
    • Access: OPSU employees, associates, or third-parties with a business need to
    • Distribution internal to OPSU: Approved electronic mail and approved electronic file transmission methods.
    • Distribution external to OPSU: Approved electronic mail and approved electronic file transmission methods.
    • Storage: When viewing data, do not allow viewing by unauthorized individuals. Do not leave data open and/or unattended in any Protect data from loss, theft, or misplacement. Electronic information should have individual access controls where possible and appropriate.
    • Disposal/Destruction: Electronic data should be permanently expunged or Reliably erase or physically destroy media. Data retention policy and federal and state retention guidelines should be observed for original copies.
  • More Sensitive
    • Description: Business, financial, technical, and most personnel
    • Access: OPSU employees, associates, or third-parties with signed non-disclosure agreements with a business need to know.
    • Distribution internal to OPSU: Approved electronic file transmission
    • Distribution external to OPSU: Approved electronic file transmission methods via a private link to approved recipients external to OPSU locations.
    • Storage: Individual access controls are highly recommended for more sensitive electronic information.
    • Disposal/Destruction: Electronic data should be permanently expunged or Reliably erase or physically destroy media. Data retention policy and federal and state retention guidelines should be observed for original copies.
  • Most Sensitive
    • Description: Operational, personnel, financial, source code, & technical information integral to the security of the institution.
    • Access: Only those individuals (OPSU employees and associates) designated with approved access and signed non-disclosure agreements.
    • Distribution internal to OPSU: Approved electronic file transmission
    • Distribution external to OPSU: Approved electronic file transmission methods to recipients within OPSU. Strong encryption is highly recommended.
    • Storage: Individual access controls are very highly recommended for electronic information. Physical security is generally used, and information should be stored on a physically secured computer.
    • Disposal/Destruction: A Electronic data should be permanently expunged or cleared. Reliably erase or physically destroy media. Data retention policy and federal and state retention guidelines should be observed for original copies.

Back To Top

Password Policy

Overview

Passwords are an important aspect of computer security. They are the front line of protection for user accounts. A poorly chosen password may result in the compromise of OPSU’s entire network. As such, all OPSU employees (including contractors and vendors with access to OPSU systems) are responsible for taking the appropriate steps, as outlined below, to select and secure their passwords.

The policy is applicable to all personnel who have or are responsible for an account (or any form of access that supports or requires a password) on any system that belongs to OPSU, resides at any OPSU location, has access to the OPSU network, or stores any OPSU information.

Policy

All passwords will meet the following criteria:

  • All system-level passwords (e.g., root, admin, application administration accounts) must be changed at least every 180 days.
  • All user-level passwords (e.g., email, web, desktop computer, ) must be changed at least every 120 days.
  • User accounts that have system-level privileges granted through group memberships or programs such as “sudo” must have a unique password from all other accounts held by that
  • Passwords must NOT be inserted into email messages or other forms of electronic
  • Where SNMP is used, the community strings must be defined as something other than the standard defaults of “public,” “private” and “system” and must be different from the passwords used to log in interactively. A keyed hash must be used where available (e.g., SNMPv2).
  • All user-level and system-level passwords must conform to the guidelines described

Passwords are used for various purposes at OPSU. Some of the more common uses include: user level accounts, web accounts, email accounts, screen saver protection, voicemail password, and local router logins. Very few systems have proper support for one-time tokens (i.e., dynamic passwords that are only used once); therefore, every OPSU employee should know how to select strong passwords.

Poor, weak passwords have the following characteristics:

  • The password contains less than eight characters
  • The password or a subset of the password is a word found in a dictionary (English or foreign)
  • The password is a common usage word such as:
  • Names of family, pets, friends, co-workers, fantasy characters,
  • Computer terms and names, commands, sites, companies, hardware, software
  • The words “OPSU”, “oklahoma”, “panhandle”, “state”, ” university” or any derivation
  • Birthdays and other personal information such as addresses and phone numbers
  • Word or number patterns like aaabbb, qwerty, zyxwvuts, 123321,
  • Any of the above spelled backwards
  • Any of the above preceded or followed by a digit (e.g., secret1, 1secret) Strong passwords have the following characteristics:
  • Contain between 8 and 32 characters
  • Contain both upper and lower case characters (e.g., a-z, A-Z)
  • Contain at least one number (e.g., 0-9)
  • Contain special characters (e.g., ~, !, @, #, $, ^, (, ), _, +, =, -, ?, or ,)
  • Does not contain a dictionary word in any language, slang, dialect, jargon,
  • Does not contain personal information, names of family,

Passwords should never be written down or stored on-line. Try to create passwords that can be easily remembered. One way to do this is creating a password based on a song title, affirmation, or other phrase. For example, the phrase might be: “This May Be One Way To Remember” and the password could be: “TmB1w2R!” or “Tmb1W>r~” or some other variation.

NOTE: Please do not use either of these examples as passwords!

Do not use the same password for OPSU accounts as for other non-OPSU access (e.g., personal ISP account, option trading, benefit, etc.). Do not share OPSU passwords with anyone, including administrative assistants or secretaries. All passwords are to be treated as sensitive, confidential OPSU information.

Here is a list of “don’ts”:

  • Don’t reveal a password over the phone to
  • Don’t reveal a password in an email
  • Don’t reveal a password to a
  • Don’t talk about a password in front of
  • Don’t hint at the format of a password (e.g., “my family name”).
  • Don’t reveal a password on questionnaires or security
  • Don’t share a password with family
  • Don’t reveal a password to co-
  • Don’t reveal a password to
  • In short, don’t reveal a password to
  • Do not use the “Remember Password” feature of applications (e.g., Eudora, Outlook, Netscape Messenger, Internet Explorer, Firefox, Thunderbird).
  • Do not write passwords down and store them anywhere in your
  • Do not store passwords in a file on ANY computer system (including Palm Pilots or similar devices) without proper encryption.
  • Change passwords at least once every three Other items to remember:
  • If someone demands a password, refer them to this document or have them call the OPSU IT Department to determine the validity of their request.
  • If an account or password is suspected to have been compromised, report the incident to the OPSU IT Department immediately and change all passwords as soon as possible.

Password cracking or guessing may be performed on a periodic or random basis by the OPSU IT Department or IT delegates. If a password is guessed or cracked during one of these scans, the user will be required to change it.

Never give your password out to anyone. This may or may not include your supervisor, a friend or relative, a student or part-time worker, or even a co-worker.
Back To Top

Patch Management Policy

Overview

This policy will establish guidelines for patch management of all institution-owned or managed IT resources. Software is under the continuous process of improvement, modification, and repair. This is typically through patches that provide updates for functionality improvements, issue resolution, or vulnerability remediation.

Policy

All IT resources must be part of a patch management cycle. IT resources including computing, networking, applications, telecommunications systems, infrastructure, software, cloud-based vendors, Software as a Service (SaaS vendors, and others not listed here but utilized by the institution.

All patches or configuration changes must be deployed to institution-owned or managed IT resources when a vulnerability is determined. A patch is a software update comprised of code inserted (i.e., patched) into the code of an executable program. Typically, a patch is installed into an existing software program. Patches are often temporary fixes between full releases of a software package. Patches include, but are not limited to the following:

  • Updating software
  • Fixing a software bug
  • Installing new drivers
  • Addressing new security vulnerabilities
  • Addressing software stability issues

It is important to note that patches should be applied as available, but care should be taken to ensure that patches are thoroughly tested and approved. Patches should be deployed in a timely manner through the use of technology to help ensure all systems are up-to-date.

Criticality should also be considered when evaluating which patches to apply. Often, vulnerabilities will cause patches to reach deployment quickly to resolve zero-day or sudden issues that are discovered in existing code. In this case, it would be wise to apply these patches as quickly as possible to reduce the likelihood a system can be compromised.

Patching Cycles/Schedules

All patches should be applied as soon as possible, provided they do not cause any adverseeffects to the system for which they are prescribed. Due to this, we do not advocate immediate deployment. However, application of all critical, zero-day, and system patches should be applied according to SCCM policy or within 72 hours to ensure no issues may occur.

Testing

Since the institution has limited IT staff to perform patch testing, this requirement may be performed at OSU, by using best practices and recommendations from vendors (i.e Microsoft, Cisco), or tracking usage and deployment statistics for given patches from other consumers to determine patch viability and stability.

Approvals

All patches will be approved by the system administrator, OSU IT, using tools such as SCCM, Meraki Dashboard, etc., or a combination of these.

Exceptions

Possible exceptions may occur which would require deviation from a typical patch deployment schedule. Exceptions may include, but are not limited to:

  • System incompatibility issues
  • Patch performance issues
  • Patch side effects
  • Manufacturer delays
  • Incomplete prerequisite software Risk Identification and Management

Due to possible issues with patches for the exceptions noted above, we must identify any risks that may present themselves if we deviate from our patch schedule. Once these risks are identified, a determination must be made to ascertain whether the risk associated with not patching a system is greater than patching the system.

Upgrades for End-of-Life Systems

All systems will be upgraded fully while in service. Once a system reaches end-of-life, care should be taken to identify if service extensions can be purchased to obtain subsequent software upgrades. Once software upgrades cease for a given end-of-life system, the services provided by the system should be migrated to another system and the system should be decommissioned as soon as possible.

Governance

This policy will be approved by the A&M CIO and institution IT Director to ensure little to no impact to services and adherence to this patch management policy.

Change/Configuration Management

This policy will work in cooperation with the change management policies established at OSU and in accordance with other restrictions, requirements, and regulations established within the System and within systems managed by OSU such as SCCM.
Back To Top

Physical Security Policy

Overview

This policy will establish physical security guidelines that apply to all computing and networking equipment locations. It is important to note that incremental degrees of security will be needed for each area depending on the actual equipment configuration and critical need to the institution.

Policy

All areas will be classified into two categories:

  • Office
  • Restricted

Office areas are simply that, office locations for OPSU IT Department employees. These areas contain computing equipment and other data that should be protected at all times.

Restricted areas are those areas that belong to the OPSU IT Department and contain equipment owned and/or operated by the OPSU IT Department or a third-party vendor (i.e. OneNet) such as:

  • Switch closets
  • Server rooms
  • Telecommunications rooms
  • IT Department storage areas

At the time of this policy, our current physical security offerings are somewhat limited so more advanced options cannot currently be used. As upgrades occur, recommended options will be changed to required options to increase and enhance security.

At minimum, all office and restricted locations require the following security mechanisms:

  • Solid wood or steel door
  • Either keyed handle or deadbolt lock

All OPSU IT Department restricted and office locations should contain the following recommended security mechanisms:

  • Reinforced steel doors and frames
  • Keyed deadbolt locks
  • ID card access
  • Steel bars over windows

Back To Top

Personally Identifiable Information Policy

Overview

This policy will establish OPSU’s definition of Personally Identifiable Information (PII) and indicate what information may be shared, if any, with third-party entities.

Policy

It is important to note that information should never be shared without cause or requirement, unless dictated by state or federal government regulations such as annual reporting guidelines and statistical reporting data, in the course of preset institutional operations or vendor agreements, or due to the request of OPSU’s President or designee.

PII is the type of information that should be kept safe using the highest level of security. PII is described as information about an individual that identifies, links, relates, or is unique to, or describes him or her. This information may include:

  • Name
  • SSN
  • Address(es)
  • Phone Number(s)
  • Birth date
  • Birth place
  • Mother’s maiden name
  • Family names
  • Other family data such as addresses, contact information,
  • Financial information such as bank account information, account balances,
  • Other information that, alone or in combination, is linked or linkable to a specific student that would allow a reasonable person in the school community, who does not have a personal knowledge of the relevant circumstances, to identify the student with a reasonable certainty
  • Information requested by a person who the educational agency or institution believes knows the identity of the student to whom the educational record directly relates

Under no circumstances should PII be transported off-campus. On-campus storage of PII should meet other policy requirements as dictated herein. Off-campus use of this type of data may be facilitated via the OPSU IT Department’s Remote Access Policy.
Back To Top

Personal Technology Service Policy

Overview

This policy will set forth the rules and regulations which will determine how the OPSU IT Department personnel are to perform work on personally-owned employee or student technology products.

The OPSU IT Department does not service technology equipment for individuals who are not OPSU employees or students.

Policy

The OPSU IT Department always strives to ensure that OPSU employees, students, affiliates, and visitors receive the best possible technology assistance available for us to provide. However, this can leave something to be desired for non-OPSU, personally-owned technology equipment owned by employees, students, affiliates, and visitors.

This policy will set forth the rules, regulations, and guidelines for which the OPSU IT Department personnel may provide services for personally-owned technology equipment and/or projects outside of normal work hours.

NOTE: All technology requests for configuration or connectivity to the OPSU network from personal technology devices will be handled at no cost. This policy applies only to technology issues related to the personal needs of the user.

All requests for personal technology assistance will begin with a preliminary diagnosis and troubleshooting process which is provided for FREE. If additional work is authorized by the user, then the accompanying Personal Technology Service Policy Consent Form must be read and signed before any work may begin.

The OPSU IT Department offers no implied warranty or guarantee on any work performed on personal technology equipment. All work is performed as-is as a service to our students and as a cost-saving alternative for their benefit. However, it is beneficial to note that all work is performed on the same level as comparable service on OPSU owned equipment.

All personal technology work will be performed within the following restrictions:

  • Personal technology work may be performed during regular business hours, only if such work does not directly interfere or delay the normal operations or job duties of the OPSU IT Department employee.
  • No on-site All equipment must be brought to the OPSU IT Department for a preliminary diagnosis and troubleshooting.
  • No parts All parts to be installed must be purchased by the user.
  • No illegal Only legally licensed software may be installed.
  • No work without proper authorization signature on consent

All issues should be expected to take approximately 24-48 hours to complete; however, they may take longer depending upon the severity of the problem at hand. Please expect to leave any equipment for a minimum of 48 hours for proper problem resolution.

Oklahoma Panhandle State University cannot be held responsible for any work done after hours by OPSU IT Department personnel on any personal technology equipment. All work provided is not warranted or guaranteed. By signing the Personal Technology Service Policy Consent Form, you agree to these terms and conditions and waive any damages which may occur due to any work on your personal technology equipment. All work is done and once completed is left as is and no standing warranty or guarantee is implied.
Back To Top

Remote Access Policy

Overview

This policy establishes the official rules set forth to allow users to remotely access and manipulate personally identifiable information, network applications, and other data from off-campus.

Policy

Any user who seeks to work off-campus for the purpose of working from home or at another location can facilitate this through the use of the OPSU or OSU VPN connection. All users needing access to Banner or other applications requiring network connectivity to the campus can facilitate this by connecting from home via a VPN connection.

This type of connection establishes a secure, encrypted connection, to the campus network to allow the user to manipulate and access the data at a distance. At no time should any PII be transferred off-campus on any type of device. If a given user wishes to work while off-campus, he/she should use the enclosed Remote Access Procedure to obtain a secure connection to the network and work from a distance.

This type of connection allows the user to remotely manipulate and access the data without actually transferring any data off-site thus ensuring all PII and other data is kept safe and secure from unauthorized access.
Back To Top

Security Camera Policy

Overview

Security cameras have a place at our institution to help protect our students, faculty, and staff. It is important that we manage them effectively, so they are operational when needed and the footage gathered is retained properly for retrieval.

Policy

All security cameras should be properly catalogued at the institution with the following information. This can be through a manual management process but the preferable method is using a campus- wide software-based system to manage security cameras and control the feeds:

  • Make
  • Model
  • Camera IP (if network-based)
  • DVR Management IP (if a DVR-based system)
  • Location
  • Status

All cameras installed at the institution should have access restricted to only relevant individuals or departments:

  • Campus Security
  • IT
  • Camera location owners:
  • Bursar
  • Financial Aid
  • Registrar
  • Housing

All cameras should be kept up to date with the latest firmware and maintained to be kept in proper working order. The institution will employ some or all the following options to ensure cameras are fully functional, in order of preference:

  • Vendor preventative maintenance agreement
  • Typically, we request 16-24 hours per month (2-3 days) for a technician to visit campus
  • Self-support and maintenance
  • IT will regularly review camera inventory and update or service accordingly
  • Security assistance and support
  • IT will rely on campus security to notify us of camera issues where we will perform reactive maintenance to restore connectivity

All camera footage will be securely stored with access limited in coordination with the camera access noted above. The institution may opt to restrict access to security camera footage to only campus security and IT staff and only provide footage to other relevant departments (or law enforcement) when a request is made through the proper channels (i.e. campus security, administration, and/or legal counsel).

Security camera footage should be retained for as long as possible given the storage limits of the hardware (DVR or server if IP-based). Security camera footage should be retained for a minimum of 30 days. If storage limits are exceeded, then the institution should employ one or more of the following methods to increase/improve storage capabilities to reach the 30-day recommended retention mark:

  • Add storage capability to system*
    • Additional hard drives
    • Additional DVR systems
    • System upgrades
    • Video compression improvements
  • Modify/Reduce camera storage requirements^
    • Adjust camera sensitivity
    • Adjust camera resolution
    • Adjust camera recording length
    • Adjust motion sensitivity
  • Remove non-critical cameras^

*NOTE: These options do not compromise the capabilities of the system. These are preferred to the other options as they improve and expand the system.

^NOTE: These options presented should only be used on a temporary basis so as not to lose footage. They compromise the capabilities of the system to ensure footage is kept for the recommended 30- days. As soon as possible, the institution should employ one of the previous options to expand the system properly to support all current cameras.
Back To Top

Student Rights and Responsibilities Policy

Overview

It is the understanding of all students, upon being admitted to OPSU, that the technology resources and equipment provided are for the benefit of all students. This policy explains what rights students have with respect to this technology and also what responsibilities are expected of each student.

Policy

Every student that attends OPSU shall be given an equal opportunity to learn and equal access to technology to help facilitate learning. All students, regardless of major, classification, student-type, housing location, or other identifying factor shall receive the same technology access as any other student.

Students should expect to receive access to wireless connections in classrooms, learning areas, common areas, dorms, etc. Students should also expect up-to-date computers in labs and teaching areas, multimedia equipment in most classrooms, state-of-the-art instructional television classrooms, and easily accessible online systems such as the Learning Management System, OPSU e-mail, AggieAccess, etc. Students should also expect to receive reliable, free internet service while on campus at speeds unobtainable through any normal ISP.

With all of these rights and amenities, the OPSU IT Department does make some responsibilities and assumptions of our students. These responsibilities are as follows:

  • Students are expected to activate a AggieAccess account thereby creating an e-mail account.
  • Students are expected to maintain their respective AggieAccess account through their career at OPSU.
  • Students are expected to utilize their OPSU e-mail address as it is the official method of communication with OPSU.
  • Students are required to safeguard login credentials and not share user accounts.
  • Students are expected to respect others privacy and equipment.
  • Students are expected to use only permissible equipment on campus:
    • Computers such as laptops, desktops, mobile devices, etc.
  • Students are to observe prohibited devices in dorm areas:
    • Personal routers, wireless access points, bridges, or other network equipment.
  • Students are expected to observe all local, state, and federal laws concerning technology.
  • Students are required to comply with all policies included in this document.

Back To Top

Vendor Access Policy

Overview

This policy will set forth parameters for vendors to abide by when access to our internal or external network, workstations, or servers is required. All vendors, regardless of status, frequency of visitation, work being performed, or size of entity shall abide by this policy at all times unless such work does not require access to the OPSU network or computing resources.

Policy

All vendors shall notify their contact on campus of any work that will require access to any of the following OPSU resources:

  • Internal network
  • External network
  • On-campus workstation(s)
  • On-campus server(s)
  • Network infrastructure
  • Any other computing device on campus

Upon notification of the need for access, the OPSU IT Department shall create login credentials and access requirements necessary to facilitate the access required for the vendor to complete their job function. Access shall always be restrictive meaning un-warranted or un-needed access will not be available until deemed necessary by the requirements of the project. All requests for access shall be evaluated on a case-by-case basis to ensure that proper access is granted and no un-warranted or un-needed access is given without cause.

At all times, the vendor shall:

  • Fulfill their primary job responsibility only;
  • Not seek to undermine or circumnavigate the access which has been provided;
  • Not tamper or adjust security settings on existing network infrastructure or devices;
  • Ensure that access credentials are not shared with anyone other than those individual approved for access;
  • Work to ensure that OPSU’s information is kept safe and secure from loss or theft;
  • Never disclose any information he or she may come to know from working with or on any OPSU technology resource with a separate third-part entity;
  • Notify the OPSU IT Department IMMEDIATELY upon any inclination that loss or theft has occurred, access has been lost or tampered with, or there is a concern that any other type of access violation has occurred;
  • Never seek to use any of OPSU’s information for personal or other monetary gain;

Not use any access or technology resource in a manner that has been prohibited for employees, students, or visitors in any of the other, enclosed policies herein.
Back To Top

Wireless Communication Policy

Overview

Wireless implementations are a benefit to OPSU as well as IT’s faculty, staff, and students. Maintaining this equipment can be a tedious process but is a necessity.

At present, this policy allows access to the OPSU wireless network via any data communication device containing the hardware required to connect. Connecting to the OPSU wireless network does not grant a user access to the internal networking infrastructure or any internal information of OPSU, only external access to the internet. Utilizing OPSU’s wireless network for access to the internal network and/or information requires additional software that must be obtained through the OPSU IT Department.

This policy covers all wireless data communication devices (e.g., personal computers, cellular phones, PDAs, etc.) connected to any of OPSU’s wireless networking access points. This includes any form of wireless data communication device capable of transmitting packet data.

Policy

All wireless data communication devices connected with OPSU’s wireless network will be required to have current virus-scanning software installed with the most recent updates and perform a full system scan a minimum of once per week.

All wireless data communication devices connected with OPSU’s wireless network that require access to OPSU’s internal network and/or information will be required to utilize specific software and/or access credentials obtained through the OPSU IT Department to do so.

At no time shall any device connected to the OPSU wireless network operate outside the parameters defined in the Acceptable Use Policy provided herein. All wirelessly connected devices may be monitored and their information such as IP address, MAC address, general hardware profile, etc. be archived for future use. Random scans may also be performed to ensure the security of the wireless networks and connected devices and to obtain a general device survey to further enhance the accessibility and usability of OPSU’s wireless networks.
Back To Top


Procedures

Emergency Operating Procedure

In the event of an emergency, normal operating procedures should be restored as quickly as possible. Due to the small size of our department, it is beneficial that all employees learn laterally to allow for greater ability to maintain operations should any individual employee be unavailable. The steps below will indicate how operations should continue in the event of an emergency directly affecting the OPSU IT Department.

  1. Assess situation and determine if any personnel impact to the OPSU IT Department If so, go to step 2. If not, go to step 3.
  2. Given any personnel impact below, the following options are available to ensure IT operations can continue in an If the IT Department suffers the loss of any of the following employees, the available options are:
    1. Director of IT
      1. Responsibilities will defer to the President or designee until a suitable appointment can be made.
    2. Assistant Director of Technology
      1. Responsibilities will defer to the
      2. Interim assistance can be performed by PTCI or another suitable vendor to facilitate network management.
      3. Network management is more specialized than workstation management so vendor assistance will most likely be a necessity.
    3. Computer Technician
      1. Responsibilities will be shared between remaining personnel.
      2. Emergency/Interim hiring may be required.
      3. Interim assistance can be performed by OSU or another A&M institution willing to assist.
      4. Emergency/Interim hiring may be required.
    4. Departmental catastrophe (3+ users unavailable to perform duties)
      1. Responsibilities will defer to the President or designee until emergency hiring can be finalized.
      2. If necessary, assistance may be obtained from other institutions and/or vendors:
        1. Banner Operations: OSU A&M System Institutions
        2. Networking: OSU, PTCI
    5. NOTE: Emergency approval for costs associated with assistance will need to be obtained under any scenario.
  3. Determine if any equipment loss has If so, proceed to step 4. If not, proceed to step 5.
  4. Determine what resources are affected and bring them back up as soon as possible:
    1. Network and connectivity equipment
    2. Mission critical services (Banner, group drives, ID card system, )
    3. Non-mission critical services (security cameras, wireless infrastructure, dorm connectivity, etc.)
  5. Once all connectivity and resources have been restored, normal operations can now

NOTE: Please see the OPSU IT Department’s detailed Disaster Recovery Plan for detailed information regarding disaster scenarios and specific planning information.
Back To Top

Equipment Ordering Procedure

This document is to serve as a set of guidelines for all OPSU Faculty and Staff who choose to order computing equipment.

  1. Contact the OPSU IT Department to obtain a quote and or information regarding the equipment you wish to purchase.
  2. For Dell computers and some other specific technology equipment, the IT Department will create a shopping cart for you and submit the order for If this is the case, skip to Step 5, otherwise go to Step 3.
  3. Obtain the quote(s) for your order from the IT Department and create a new cart on the OKCorral website: http://okcorral.okstate.edu
  4. Submit your
  5. Your order will be routed through the appropriate approving channels, including the IT Department, since it is a technology equipment purchase.
  6. Once your order has been approved, you may check the progress via
  7. When your equipment arrives, the Bookstore may notify you to pick up the equipment. Otherwise, the IT Department will retrieve your equipment and configure it, if necessary, prior to delivering it to you.

NOTE: All technology orders must be received by the IT Department before it can be released to the purchaser. This is to ensure that the proper software is installed and all equipment is properly tagged and placed in inventory.
Back To Top

Guest/Visitor Access Procedure

This procedure will indicate how guests and visitors to campus should obtain access to OPSU’s technology resources.

  1. Obtain contact information from user needing access:
    1. Name
    2. Phone
    3. Email
  2. Fill out the enclosed Authorization of User Access
  3. Submit the form to the OPSU IT
  4. Access will be created as soon as Confirmation will be sent to requesting employee once access has been created.

Back To Top

Incident Management Procedure

This procedure addresses how incidents should be handled when related to technology. This includes thefts, data corruption, etc.

  1. Determine scope of incident.
  2. Fill out attached Incident Management Form
  3. Ensure supervisor of employee that reported or caused incident has been notified.
  4. Submit form to Director of IT.
  5. Administration will be notified of incident.
  6. Resolution will be drafted given incident scope and individuals involved.

Back To Top

Remote/VPN Access Procedure

For users that require access to sensitive information at home or on the road, please use these remote access procedures:

  1. Open your browser and visit OSU’s VPN location.
    1. OSU: http://osuvpn.okstate.edu
  2. Login with your AggieAccess account credentials.
  3. Allow the client to download and install.
  4. Follow the on-screen prompts as software is requested to be installed.
  5. If the installer gets “stuck”, simply refresh screen by selecting browser’s refresh button or hitting the “F5” key on the keyboard.
  6. Once complete, the client will show up in your task bar on the bottom right indicating you are connected.
  7. You may now access Banner, Cognos, group drives, or your office computer as noted below:
    1. Banner: You may access Banner by visiting the portal page: http://my.opsu.edu
    2. Cognos: You may access Cognos: https://cognos.okstate.edu/cognos10/
    3. Group Drives: Open “My Computer”, if group drives do not show up by default, simply type the following in the address bar at the top to navigate to the group drive server and see your available group drives: \\server\share
    4. Office Computer: Open a remote desktop connection on your computer and type in your office computer Login with your AggieAccess credentials to gain access.
      1. You must know the name of your office computer to use this method.
      2. To obtain your office computer name, simply hold the Windows key on the keyboard and press the Pause/Break key while you are at your office computer.
      3. The resulting dialog box will show you your computer name.

Back To Top

Vendor Access Procedure

If any vendor requires access to technology resources, please follow these steps:

  1. Submit Authorization of User Access Form to OPSU IT Department.
  2. IT Department will evaluate request and grant access based upon need and policies.
  3. Vendor access will be created to comply with existing policies.
  4. Requesting employee will receive email once appropriate access has been created.

Back To Top