Introduction:
The University of Oklahoma shall provide secure remote access that supports research, instruction, clinical services, administration and collaboration. This policy establishes authorization, accountability, and network boundaries while allowing research workflows to use approved methods appropriate to their operational and data requirements.
Scope:
This policy applies across al OU campuses. It covers faculty, staff, students, sponsored affiliates, collaborators, contractors, vendors, and other authorized users. It applies to remote access services controlled by OU and to connections to nonpublic OU information or systems. This includes systems that OU funds or administers in the cloud or through third parties. These responsibilities apply regardless of who owns the connecting device.
Remote access includes interactive use by a person, remote support, technical administration, and automated connections crossing an approved trust boundary. Connections between the Research Zone and other OU zones are subject to the same authorization requirements whether initiated on or off campus.
Relationship to Other Policies:
The Acceptable Use Policy (AUP) governs permissible conduct. This policy governs remote access authorization and operation, and the Remote Access Standard defines technical requirements. Identity, data classification, privacy, encryption, logging, incident response, accessibility, and contractual requirements continue to apply. A remote access approval or exception cannot waive another policy or a legal obligation.
Public Websites & Services:
Access solely to publicly released information through an approved public service does not require a user VPN or Virtual Desktop Infrastructure (VDI) session. However, administrative access to manage or publish to that public service remains strictly controlled under this policy.
Definitions
- Automated Access, means a scheduled or event-driven connection using a service identity to execute defined system functions without direct human intervention.
- Interactive access, means a connection initiated or used by a person. Automated access means a scheduled or event-driven connection using a service identity for a defined system function.
- Registered Secure Shell (SSH) Service, an identified server or managed group of hosts with an accountable owner and a maintained inventory record within the SSH registration system.
- Research Zone or Research DMZ, means an OU-governed network environment separated from enterprise networks and internally segmented according to workload and risk. It may include research login services, approved remote desktops, instruments, and data-transfer services. Placement does not authorize unrestricted internet exposure or access to other system.
- Science DMZ, means a specialized architecture for high-performance scientific data movement. A Science DMZ may form part of the Research Zone; it does not describe every research workstation or authorize removal of security controls throughout the zone.
- Virtual Desktop Infrastructure (VDI), a service provided by OU IT that offers access to protected, on-campus applications using a secure, encrypted virtual desktop.
- Virtual Private Network (VPN), a service provided by OU IT that offers a secure connection between any remote site and assets on the OU networks, such as file servers, data stores, virtual labs, enterprise applications, and more.
For a comprehensive list of definitions, see Information Technology and Security Definitions.
Policy:
It is the responsibility of university staff, faculty, students, and third-parties with remote access privileges to the OU network to ensure that their remote access connection is given the same security consideration as the user’s on-site connection to the university. All individual remote access users are responsible for protecting remote access connections, devices, and credentials in accordance with the Acceptable Use Policy.
1. Governance Roles and Responsibilities
To eliminate administrative confusion, institutional governance responsibilities and operational roles under this policy are organized below:
Remote Access Governance Roles and Responsibilities
| Role / Entity |
Governance & Operational Responsibilities |
| Chief Information Officer (CIO) |
Serves as the responsible executive for this policy. Approves high-risk exceptions jointly with executive Data Owners and maintains emergency decision paths. |
| Cybersecurity, IT Policy & Infrastructure Advisory Committee |
Reviews proposed policies, standards, remote access mechanism, and risk acceptance requests, offering recommendations. Does not approve requests or accept risk on behalf of OU. |
| Chief Information Security Officer (CISO) |
Approves remote access mechanisms and standard configurations within documented delegated authority after security assessments. Evaluates risk and approves low/moderate-risk exceptions. |
| Enterprise Risk Committee (ERCO) |
Oversees the risk delegation framework and reviews quarterly summaries of accepted risks, high-risk decisions, overdue remediation, and recurring issues. |
| IT Governance, Risk & Compliance (GRC) |
Manages exception intake, maintains the SSH registry and assessed mechanisms, coordinates risk reviews, verifies decision authority, and records approved configurations. |
| OU IT Networking |
Implements, documents, and maintains authorized boundary rules, firewalls, and routing between enterprise zones, the Research Zone, and external connections. |
| Security Operations (SecOps) |
Validates security controls, monitors security events, coordinates containment and recovery, and executes immediate restriction of active security threats. |
| Research IT & Departmental Administrators |
Maintain service inventories, host configurations, patches, credentials, logs, and continuity procedures for systems under their operational control |
| Asset Owners & Principal Investigators (PIs) |
Identify service purpose, accountable personnel, funding, data requirements, and authorized users. Register all SSH servers and lab services with GRC. |
| End Users (Faculty, Staff, Students, Affiliates) |
Protect assigned accounts and devices, complete required training, use only authorized resources, and report suspected compromises immediately. |
2. Approved Access Methods and Device Eligibility
Only mechanisms authorized for the intended use case, data classification, and configuration may be used. GRC maintains one authoritative approved-methods matrix in coordination with OU IT service owners, distinguishing permissions to use a method from central support availability and licensing costs. Approval of a product name alone does not constitute approval of every deployment or feature.
a. Summary of Approved Connection Tools
Approved Connection Tools
| Approved Method |
Primary Use Case & Scope |
Device & Posture Requirements |
| OU VPN (Secure Tunnel) |
Reaching campus administrative files and internal web applications. |
Requires managed OU devices meeting endpoint security posture defined for that service. |
| OU VDI (Cloud Desktop) |
Reaching campus applications and data from unmanaged or personal devices. |
Supported web browsers or VDI client controls; isolates data from local hard drives. |
| Registered SSH & File Transfer |
Reaching campus applications and data from unmanaged or personal devices. |
Devices meeting applicable security baseline; direct access requires GRC registration. |
| Approved RDP Controls |
Remote desktop access through central gateway security controls. |
Restricted under standard; requires gateway authentication and endpoint posture checks. |
| Approved OU Remote Support |
Attended remote technical support and screen sharing by IT technicians. |
Requires explicit user consent per session unless an approved emergency procedure applies. |
b. Personal Device Eligibility & Zone Rules
i. Research Zone Access: Personal devices and independently administered university devices may use approved Research Zone access methods when they meet the applicable security baseline. Direct access to a registered and validated research SSH service does not require VPN or VDI.
ii. Enterprise & Campus Zones: For IT Data Center and Campus Zones, personal or otherwise unmanaged devices shall use OU VDI unless an alternative is expressly authorized under the Remote Access Standard or an approved exception. VPN access requires the endpoint posture for that service. Research Zone access does not confer enterprise VPN eligibility.
iii. Device Ownership Principle: Who owns a device does not, by itself, demonstrate that the device meets security requirements.
c. Central Storage Mandate & Local Download Prohibition
OU Data shall be stored on centrally managed storage services in accordance with the Acceptable Use Policy. Remote access approval does not authorize storage on local or portable drives. Research storage, scratch space, instrument staging, and local caches shall use a compliant storage design or receive a separately approved exception before use.
3. Research Zone Architecture and Data Controls
OU IT shall design and operate Research Zone boundaries jointly with Research IT and Security Operations. The environment shall support approved coursework, undergraduate research, high-performance computing access, scientific instruments, data movement, and sponsored collaboration. Research services shall have a normal approval path under the standard rather than relying on recurring exceptions for routine workflows.
a. Boundary Enforcement and Network Traffic Rules
i. Traffic between the Research Zone and enterprise zones shall be denied by default. Networking shall permit only documented, necessary flows with named owners and approved source, destination, service, and purpose.
ii. Shared identity, DNS, time, logging, and other dependencies shall be explicitly controlled. Routing traffic through an external address does not itself establish authorization.
iii. Separate controls shall protect research login hosts, data-transfer nodes, computing resources, instruments, and sensitive workloads as their risks require. General research desktops shall not receive a blanket exemption from firewall or endpoint requirements.
iv. Tunnels, forwarding, cloud relays, dual-connected hosts, and support agents shall not bypass zone boundaries.
b. Risk-Based Admission & Public Dataset Protections
Research Zone admission shall reflect the actual information and system risk, not the discipline or whether datasets are publicly available. Regulated, restricted, export-controlled, or contractually protected information shall use a separately assessed environment approved for those obligations.
Important Rule on Public Data: Public availability of a dataset does not make server accounts, unreleased results, credentials, or administrative functions public.
4. SSH Registration and External Access Protocols
System owners shall register all OU-controlled SSH server services with GRC, including internal-only services, cloud services, appliances, and research servers. Registration identifies accountability and exposure; it does not authorize new external access. Existing enterprise asset inventories may satisfy this requirement when linked to the GRC registry with the required fields and current ownership.
a. Fleet Registration & Cluster Profiles
A managed cluster, instrument fleet, or dynamically provisioned service may use one service-level registration with a maintained host inventory and common control profile. Separate full assessments are not required for each compliant ephemeral instance. Material differences in exposure, data, authentication, or controls require additional review.
b. Mandatory 3-Step External Authorization Process
New external SSH access shall not be enabled until all three sequential operational steps are complete:
i. Step 1 - Registration: System owner submits complete server details into the GRC registry via the OU IT Service Portal.
ii. Step 2 - Security Operations Validation: SecOps validates that required endpoint controls, logging, and authentication configurations are active.
iii. Step 3 - Network Path Enablement: OU IT Networking authorizes and implements the network boundary access path.
System owners shall attest to registration details annually, update material changes promptly, and retire records when services are decommissioned.
5. Authentication and Automated Connection Controls
a. Person Interactive Access Rules
Interactive remote access shall use an approved identify and Multi-Factor Authentication (MFA). MFA may be enforced at the destination or at an approved access gateway when the authenticated identity is reliably bound to the destination authorization and bypass is prevented. Users shall have attributable individual accounts; shared accounts are prohibited. Access shall be limited to the resources and privileges needed for the authorized activity.
b. Automated Connections & Service Identities
Automated connections (e.g., scheduled data transfers, instrument communications) shall use dedicated service identities and approved machine credentials. They shall not use shared personal accounts, stored personal passwords, or automated approval of MFA prompts. Compliant automated workflows are an approved access category and do not require individual policy exceptions.
c. Session Inactivity & Long-Running Computations
An interactive user session ending or timing out shall not, by itself, require termination of authorized scheduled computations. Users and administrators shall use supported scheduling or session-persistence methods rather than disabling required security controls.
6. Collaborators, Visiting Scholars, and Vendor Support
a. Sponsored Research Collaborators & Students
Sponsored research collaboration, visiting researchers, students, and former students completing authorized project work may receive project-scoped access under the Identity and Access Management Policy. A current OU sponsor shall authorize the purpose, resources, duration, and renewal. Graduation or a change of institution shall trigger review and identity transition rather than automatic account continuation.
b. Third-Party Vendor Support Sessions
Vendor support shall use separately controlled accounts limited to supported resources and authorized support periods. Unattended support requires explicit authorization. Attended remote control requires user consent unless an approved administrative or emergency incident procedure authorizes access without it. Privileged sessions shall follow OU privileged access requirements.
7. Acceptable Use, System Privacy, and Monitoring
a. Acceptable Conduct & Prohibited Actions
Before remote access is granted, users shall acknowledge the AUP and complete applicable training. Remote access approval never authorizes credential sharing, use beyond assigned permissions, or circumvention of network controls. Remote access approval does not authorize an otherwise unapproved cloud or AI service, disclosure of OU Data, or scanning without prior approval.
b. System Monitoring Disclosure
Users have no expectation of privacy when using OU Information Systems. Monitoring, access, review, disclosure, records handling, and incident reporting shall follow the AUP, the Process for Electronically Stored Information Policy, and applicable law. Monitoring access shall be restricted to authorized personnel.
8. Administrative Exception Framework and Risk Oversight
This section integrates the formal administrative governance and risk delegation rules required by university leadership, organizing decision tiers clearly to streamline operational intake.
a. Exception Request Requirements
Requests for policy deviations shall identify the business need, affected systems and data, assessed residual risk, compensating controls, responsible owner, expiration date, and remediation plan. Exceptions shall be time-limited, approved before the deviation is implemented, and reviewed prior to renewal. Material increases in risk require a new decision.
b. Delegated Risk Approval Matrix
Delegated Risk Approval Matrix
| Risk Tier |
Required Approval Authority |
Governance Conditions |
| Low Risk |
CISO or formally designated security official within written limits. |
Documented residual risk; standard compensating controls. |
| Medium Risk |
CISO AND accountable Data Owner. |
Joint approval; documented remediation schedule. |
| High RIsk |
CIO AND account executive or Data Owner (supported by CISO assessment). |
Executive risk sign-off; reported to ERCO in quarterly summary. |
c. Governance Non-Waiver Rules & ERCO Quarterly Oversight
i. Non-Waiver Principle: Approval under this policy does not waive another policy or applicable law. The AUP's expressly non-exceptable prohibitions remain in force.
ii. No Default Approval: A late or incomplete request shall not become approved by default. No role may assume authority solely because a request is urgent.
iii. ERCO Oversight: ERCO shall oversee the delegation framework and review risk acceptance trends, significant exposures, high-risk decision, overdue remediation, and expired exceptions at its quarterly meetings.
iv. Interim Decision Path: Routine requests shall not wait for an ERCO meeting. The CIO and CISO shall maintain a documented path for decisions between meetings when a request exceeds delegated limits.
9. Operational Continuity and Emergency Actions
a. Planned Migration & Replacement Validation
Before a planned withdrawal of an existing access method, the service owner shall document requirements and validate an approved replacement for essential functions, throughput, accessibility, and continuity. Testing shall include Linux tools, graphics, low-bandwidth access, collaborators, automation, and scientific instruments.
b. Emergency Containment & Outage Rules
i. Outage Rule: A VDI or VPN outage shall not justify an uncontrolled bypass.
ii. Emergency Containment: Security Operations may immediately restrict any connection presenting an active threat or unacceptable risk under OU incident procedures. Security Operations shall notify affected owners as soon as operationally safe, preserve evidence, and coordinate restoration.
iii. Priority of Containment: Planned migration requirements do not delay emergency containment actions.
10. Policy Enforcement
OU may restrict remote access for noncompliance and address violations through applicable university procedures. GRC and service owners shall review this policy and the Remote Access Standard at least annually. Internal Audit may assess compliance independently.
Approval Authority:
Chief Information Officer
Former Policy Number:
PolicyTech # / BOR 8.2.1.10
Other Related Policies:
Web Address For This Policy
To be determined.
Revision, Review, and Approval History
- September 2023: OU IT Governance, Risk, and Compliance revised policy. Opened for comments
- November 2023: Comment period closed.
- January 2024: Faculty and Staff Research Advisory Committee review. Comments submitted.
- April 2024: OU IT Governance, Risk, and Compliance revised policy.
- November 2026: CISO created revised policy and GRC applied the new policy template style sheet/format.