|
![]() |
|||||||||||||||||||||||||||||||||
|
|
|
|
||||||||||||||||||||||||||||||||
|
|
1.0 Background 2.0 Purpose 3.0 Scope 4.0 Policy 4.1 Approved Access Types 4.2 Unapproved Access Types 4.3 General 4.4 Requirements 5.0 Exceptions 6.0 Enforcement 7.0 Definitions 8.0 Related Documentation 9.0 Revision History 1.0 Background With the introduction of the various remote access applications, services and products, accessing the Keene State College Local Area Network from outside the campus security perimeter has become an area of concern with regards to Information Technology security. This policy addresses these issues. The intent of the policy is to identify remote access methods and procedures to ensure an acceptable level of security to protect the KSC Information Technology resources. The resources include network infrastructure, KSC servers, KSC user workstations, financial data, student information, academic research data and other information necessary to support the academic mission and business functions. The policy's guiding philosophy is to keep the protected KSC information within the KSC LAN. As such, it is designed to enable users' full access to authorized resources necessary to perform their jobs while minimizing the exposure of KSC IT resources to external threats. For example, copying or moving files containing protected KSC information from a system within the KSC LAN to a remote workstation is prohibited. All policy decisions not explicitly outlined in the policy, will be based on this philosophy. 2.0 PurposeThe purpose of the KSC Remote Access Policy is to define standard approved remote access methods for connecting to KSC network resources by any/all authorized users. It establishes a guideline for managing and protecting the information resources and services on the KSC LAN enabling the use of hardware, software and procedures for implementing the policy. This policy does not identify approved users or their authorization. It only identifies the method of access and authentication and defines the process for requesting access. Access privileges are granted by the Data Steward, Principal Administrator, or manager of the Business unit or application owner responsible for the information being accessed. 3.0 ScopeThis policy applies to all KSC employees, faculty, staff, contractors, vendors and agents granted remote access privileges to the KSC network, the KSC network resources and KSC computers. It applies whether access from a KSC owned or non KSC owned computer or workstation. 4.0 Policy4.1 Approved Access Types 4.1.1 Unauthenticated access to non sensitive resources Examples of this include, web access to home pages, web access to faculty/staff personal web sites, web cameras, streaming media. Servers offering these services must be closely monitored network location and in a separate firewalled network, e.g. the DMZ, with access limited to only the service offered. 4.1.2 Authenticated secure employee access to resources Examples of this include, secure web access to Exchange via Outlook Web Access. 4.1.3 Authenticated secure non-employee access to resources with proper approval 4.1.4 Authenticated employee access to resources protected by centrally managed encryption device Examples of this include but are not limited to, access to faculty/staff network storage via the VPN/Terminal server solution, access to servers/workstations running specific user defined services such as campus safety and physical plant. 4.1.5 Authenticated non-employee access to resources protected by centrally managed encryption device Examples of this include but are not limited to, contractor access to energy/power management resources. 4.1.6 Authenticated USNH employee access to resources protected by centrally managed encryption device4.2 Unapproved Access Types 4.2.1 External services which proxy or tunnel over ports to obscure intent Examples of this include but are not limited to, GoToMyPC.com 4.2.2 Client/Server implementations bypassing the established KSC remote access solution(s) Examples of this include but are not limited to, PCAnyWhere. 4.3 General
Any exceptions to this policy are reviewed and approved by the Security Manager in KSC IT Group. For example, current systems are grandfathered. System out of compliance with this policy will not be affected until a major upgrade to the system or application is implemented. At that time, compliance will be required. 6.0 EnforcementViolations of this policy may result in but are not limited to lose of remote access privileges. Other disciplinary actions may be taken by the appropriate governing department or individual, e.g. Human Resources, PA, Director. 7.0 Definitions
8.0 Related Documentation Keene State College Computer Network Use Policy Keene State College Data Policy Remote access request Form 9.0 Revision History 1.0 10/19/2006 Original document |
||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||