, 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); })(); iPad Security | ÃÛÌÒapp

ÃÛÌÒapp

Skip to main content

iPad Security

Table of Contents


Guidelines

  • University provided devices should have a College Asset tag.
  • A passcode to gain access into the device is required. This helps prevent unauthorized individuals from gaining access to the device.
  • An idle timeout lock is required. This ensures that the device will automatically prompt for a passcode if left idle and unattended. The current idle timeout is 15-20 minutes.
  • All software should be regularly patched, including the operating system and installed "Apps". This helps protect the device from attack and compromise.
  • Do not "jailbreak" or "root" your device. "Jailbreaking" and "rooting" introduces instabilities and increases the risk of malware infections.
  • College provided devices must be joined to the CIT mobile managed environment. This helps configure and maintain device security and privacy settings. Removal or disabling of the management software is prohibited. See the Responsible Use of Technology Policy Appendix C
  • College provided devices will be a part of a remote wiping service and is also recommended for personal devices that are used for College business. This will assist in locating or wiping the device if lost or stolen.
  • If the device is lost or stolen, Campus Safety and the CIT Service Desk should be contacted. Local law enforcement may also need to be contacted.
  • Confidential college data should not be stored on the device for privacy, security, and compliance reasons. Confidential data includes but is not limited to Social Security Numbers, credit card numbers (PCI-DSS), financial / banking information (GLBA), Health records (HIPAA), Student protected education records (FERPA). See the Responsible Use of Technology Policy Appendix B for further definition of "Confidential" 
  • The College, through the Information Security Office and CIT reserves the right to periodically inspect and audit the device for proper security configuration and compliance.

Basic information

Date issued
Last updated
Audience
Staff
Approved by
Adam Vedra, Information Security Officer; Henry DeVries III, VP of Information Services