Kent O’Brien
NT2580
U4:A1
Remote Access refers to the ability to access UMW network resources while off campus. Security measures for remote access should be implemented based on sensitivity and risk to University systems and data. A VPN connection is off-site remote access of sensitive IT systems to ensure exchanges of information are encrypted. With that being said I’m going to talk about a networked VPN infrastructure and what I would have in it. If I was doing a school I would have the VPN accessible to all Faculty and Staff members by default and is authenticated against the ALL_Faculty_Staff Security group in Active Directory. Students do not have VPN privileges. A Contractor, Temporary, or Volunteer worker requiring VPN access, must fill out a compulsory form in Human Resources prior to be granted access. They will require a UMW sponsor who must submit the request to the ISO for final approval. Once approved, they will be entered into Banner whereby an account will then be created in Banner and AD. They can get instructions on how to install the required Cisco software client.
Users using non-university owned equipment must follow IT Malicious Code Protection Standard. Records logging remote connections must be maintained and reviewed according to the University Monitoring and Logging Procedure. VPN authentication is required in addition to network authentication to remotely access backend servers and is limited to local accounts provisioned by the Server Administrator. Infrastructure equipment authentication is maintained on the TACACS. Local Accounts are provisioned for Network Services staff only.
"Remote Access Standard | Information Technologies." Information Technologies. N.p., n.d. Web. 15 Apr. 2014. <http://technology.umw.edu/it-policies/remote-access-standard/>.