This policy explains how individual, group and temporary accounts are managed and privileges assigned.
It applies to all holders of a University username and password.
1.1 The University will operate a user management process which will ensure that access to the University’s information and IT systems is provided to appropriately authorised users and which will prevent unauthorised access.
1.2 The user management process will ensure that access is reviewed and, if necessary, revoked in a timely manner when a user’s circumstances change.
1.3 The management of accounts and privileges will be restricted to trained and authorised members of staff.
1.4 Due to the volume of user accounts managed by the University, and the need to operate a responsive user management process, automated processes deriving information about users from central University databases will be established to manage user access wherever possible.
1.5 Password management procedures will be implemented in line with best practice guidelines. These procedures will include University password expiry schedules and automated password strength checking. Details will be maintained in the ‘Method Statement Password Requirements’.
1.6.1 A University username and password, known as a ‘personal account’, will be provided to individuals in the following circumstances:
1.6.2 Data on individuals who meet the criteria in 1.6.1 will be drawn from central University databases such as the University student management system, to ensure that accounts will only be provided in valid circumstances.
1.6.3 A minimum set of privileges will be allocated to a personal account when it is created. Further specific privileges may be requested and approved if required for a role. The process for managing access to specialised University database and information systems is described in the ‘Method Statement – Managing User Access to University Information Systems’ [TO BE DEVELOPED]
1.6.4 Where an individual has multiple affiliations with the University, such as being both a member of staff and a student, only one personal account will be provided. The privileges associated with the account will be appropriate for all the account holder’s affiliations.
1.6.5 A personal account will be unique to an individual and will be for his or her individual use and must not be shared. Where possible, accounts will be reissued if an individual leaves the University and returns, otherwise account names will not be recycled after an account is closed.
1.6.6 A user will be informed of the requirement to comply with the University regulations and University information policy when they undertake the account registration process. The act of registration is the explicit agreement of the user to comply with regulations and policy.
1.7.1 A University username and password will be provided in the form of a ‘non-personal account’’ in specific cases where information cannot readily be accessed or shared via personal accounts e.g. single points of contact such as firstname.lastname@example.org, Student Societies requiring access to make room bookings.
1.7.2 Non-personal accounts will usually be shared between multiple users but must have a
designated owner and will expire when that owner’s affiliation with the University ends. Unlike a personal account, the ownership of a non-personal account may be transferred, allowing the account to remain current when its original owner leaves. Owners of non-personal accounts are responsible for nominating a new account owner prior to leaving. Non-personal accounts will be allocated a ‘class’ which determines the account expiry policy.
1.7.3 Non-personal accounts have restricted access to some facilities. Access to subscription-based services provided by the Library is not available, for example.
1.7.4 Requests for non-personal accounts will be processed by authorised staff within the IT Services department.
1.8.1 A username and password will be provided in the form of a ‘temporary account’ for a specific academic purpose where personal and non-personal accounts cannot be used e.g. academic conferences where the delegates are academics without Eduroam credentials; one-off or short-term teaching events where the students are not enrolled at the University.
1.8.2 A temporary account must be requested by a member of University staff who will be the designated account owner and will specify the account expiry date.
1.8.3 Requests for temporary accounts will be processed by authorised staff within the IT Services department.
1.8.4 A minimal set of privileges will be assigned to the account. The privileges will enable a user to access the campus network using a University PC or a personal device and access a limited set of standard facilities.
1.9.1 For conferences which are organised by external organisations on a commercial basis or for internal conferences which do not have an academic purpose, a username and password will be provided in the form of a ‘conference account’ to a conference delegate. Issuance procedures will be agreed between IT Services, the University Conference Office and individual conference organisers.
1.9.2 A minimal set of privileges will be assigned to the conference account. These will enable the user to access the campus network via their personal device but will prevent access to standard facilities such as email and filestore and to subscription-based services provided by the Library. Access to campus PCs will not be available due to software licensing restrictions.
1.10.1 A username and password will be provided to Alumni of the University to provide access to email facilities only. The username and password will be managed in a dedicated domain for this purpose.
1.10.2 Alumni accounts will be created and expired in line with the Alumni Office’s data management policy.
2.1 This policy applies to all holders of a University username and password.
2.2 This policy supplements University Regulation 11 “Regulations for the use of computing equipment” and University policy on Records Management and Data Protection.
3.1 The Information Security Board, chaired by the Director of Information, will monitor the effectiveness of this policy and carry out regular reviews.
4.1 All information users are responsible for protecting and ensuring the security of the information to which they have access.
4.2 University Officers, Heads of Departments and Line Managers are responsible for ensuring that all information in their area is managed in conformance with this policy.
4.3 All account holders who act in breach of this policy, or who do not act to implement it, may be subject to disciplinary procedures or other appropriate sanctions.
4.4 Any breach of information security or violation of this policy must be reported to the Director of Information who will take appropriate action and inform the relevant authorities.
5.1 This document, together with related information security policies and implementation documents is available at: http://www.york.ac.uk/.
5.3 Method Statement - Managing User Access to University Information Systems [TO BE DEVELOPED]
|27 November 2013||Approved by Information Policy Executive|
|02 December 2013||Approved by Information Security Board|
Review cycle: Three yearly
Date of next review: December 2016