, but this code // executes before the first paint, when

app

is not yet present. The // classes are added to so styling immediately reflects the current // toolbar state. The classes are removed after the toolbar completes // initialization. const classesToAdd = ['toolbar-loading', 'toolbar-anti-flicker']; if (toolbarState) { const { orientation, hasActiveTab, isFixed, activeTray, activeTabId, isOriented, userButtonMinWidth } = toolbarState; classesToAdd.push( orientation ? `toolbar-` + orientation + `` : 'toolbar-horizontal', ); if (hasActiveTab !== false) { classesToAdd.push('toolbar-tray-open'); } if (isFixed) { classesToAdd.push('toolbar-fixed'); } if (isOriented) { classesToAdd.push('toolbar-oriented'); } if (activeTray) { // These styles are added so the active tab/tray styles are present // immediately instead of "flickering" on as the toolbar initializes. In // instances where a tray is lazy loaded, these styles facilitate the // lazy loaded tray appearing gracefully and without reflow. const styleContent = ` .toolbar-loading #` + activeTabId + ` { background-image: linear-gradient(rgba(255, 255, 255, 0.25) 20%, transparent 200%); } .toolbar-loading #` + activeTabId + `-tray { display: block; box-shadow: -1px 0 5px 2px rgb(0 0 0 / 33%); border-right: 1px solid #aaa; background-color: #f5f5f5; z-index: 0; } .toolbar-loading.toolbar-vertical.toolbar-tray-open #` + activeTabId + `-tray { width: 15rem; height: 100vh; } .toolbar-loading.toolbar-horizontal :not(#` + activeTray + `) > .toolbar-lining {opacity: 0}`; const style = document.createElement('style'); style.textContent = styleContent; style.setAttribute('data-toolbar-anti-flicker-loading', true); document.querySelector('head').appendChild(style); if (userButtonMinWidth) { const userButtonStyle = document.createElement('style'); userButtonStyle.textContent = `#toolbar-item-user {min-width: ` + userButtonMinWidth +`px;}` document.querySelector('head').appendChild(userButtonStyle); } } } document.querySelector('html').classList.add(...classesToAdd); })(); Virtual Private Network (VPN) Usage | app

app

Skip to main content

Virtual Private Network (VPN) Usage

Table of Contents


I. Purpose

The purpose of this guideline document is to define requirements and responsibilities when connecting to app's networks and/or IT infrastructure from untrusted computer information systems and networks. These guidelines and requirements are designed to minimize the potential exposure to app from damages which may result from unauthorized use of app resources. Damages include, but are not limited to, the loss of sensitive or company confidential data, intellectual property, damage to public image, damage to critical app internal systems, and fines or other financial liabilities incurred as a result of those losses.

II. Scope

These guidelines are applicable to all app staff, faculty, contractors, vendors and agents with a app-owned or personally-owned computer or workstation that will be used to connect to app networks. These guidelines apply to any remote connections used to do work on behalf of app, including but not limited to, accessing file shares, connecting to web/application servers, or any other access to internal technology resources.  These guidelines cover any and all technical implementations of remote access used to connect to app networks.

III. Guidelines

It is the responsibility of app employees, contractors, vendors and agents with remote access privileges to app's corporate network to ensure that their remote access connection is given the same consideration as the user's on-site connection to app.

General access to the Internet for recreational use through the app network is strictly limited to app employees, contractors, vendors and agents (hereafter referred to as “Authorized Users”).  When accessing the app network from a personal computer, Authorized Users are responsible for preventing access to any app computer resources or data by non-Authorized Users.  Performance of illegal activities through the app network by any user (Authorized or otherwise) is prohibited.  The Authorized User bears responsibility for and consequences of misuse of the Authorized User’s access.  For further information and definitions, see the Acceptable Use Policy and Information Security Policy.

A. Requirements

  1. Remote Access connectivity must be established according to app guidelines. Accepted methods include use of the GlobalProtect VPN agent, or in limited (and subject to approval) situations, manual IPSec connections. For further information, see the Policy on Responsible Use of Technology.
  2. While using a app-owned computer to remotely connect to app's corporate network, Authorized Users shall ensure the remote host is not connected to any other network at the same time, with the exception of personal networks that are under their complete control or under the complete control of an Authorized User or Third Party.
  3. Use of non-app owned and/or managed resources to conduct app business may be subject to additional security checks.
  4. All hosts that are connected to app internal networks via remote access technologies must use the most up-to-date anti-virus software and patched with the latest operating system and software patches, this includes personal computers.

B. Guideline Compliance

  • Compliance Measurement - app CIT will verify adherence to these guidelines (as applicable within the app Information Security Policy) through various methods, including but not limited to, periodic walk-thrus, firewall reports, internal and external audits, and inspection via various security tools. CIT will provide feedback to the appropriate employee supervisor.
  • Exceptions - Any exception to the app Information Security Policy must be approved by app’s Information Security Officer in advance and must be documented accordingly.
  • Non-Compliance - An employee found to have violated the app Information Security Policy may be subject to disciplinary action, up to and including termination of employment.

IV. Related Standards, Policies, and Processes

Please review the following policies for details of protecting information when accessing the corporate network via remote access methods, and acceptable use of app's network:


Last updated
Audience
Full-time faculty
Instructor
Staff
Part-Time/Adjunct
Approved by
Adam Vedra