Working Securely: The Device Security Project - Next Steps
Many of our technical teams have been working hard on the Device Security Project. This article aims to give a clear outline of the next steps for the project - the likely impacts, who may be affected and where to get support.
It is vital that our University community and the ways we work remain secure and compliant. We recognise that working from home and teaching online has placed additional responsibilities on many of us – managing multiple priorities, working in new ways and delivering more information online. Ultimately, our focus is upon delivering excellent educational experiences for our students - securely.
Work securely: '3 Ways to Connect' - a quick reference guide
All devices – whatever make, model, format or operating system – must be appropriately secure.
From 12th December 2020, we will implement the first phase of our '3 Ways to Connect' to University systems project - These are:
- Using a University-owned, central or departmentally-managed device (such as a WMG/WBS managed Windows computer or a School of Life Sciences managed Mac). This is the University’s preferred option and principal direction in the medium term. It will be funded if individuals and departments make specific requests and existing equipment cannot be provided or relocated by other routes.
- Using a University-owned but self-managed device which must be enrolled in the Device Security System (DSS) to ensure it meets our minimum security requirements. Self-managed Windows computers can enrol here now. Self-managed macOS computers can enrol here now.
- If you are using a personal, privately-owned device (not issued or funded by the University or through University-linked research funding), please either request a University-managed device, or use the Workspace virtual desktop service to access University data. It is browser-based, will run on any platform (including Mac and Linux) and gives access to all widely-used applications, email, calendar and Teams.
What happens after 12 December?
We have complex computer usage arrangements across the University and so have developed a phased approach to meet a range of different situations: use this reference guide to understand how your device and work may be impacted.
Device/OS |
Approach |
Implementation date |
University-owned and managed Windows 10 devices |
|
Available from 12 December
|
University owned, self-managed Windows 10 devices |
|
Available now – controlled access to services implemented from 12 Dec |
University owned, self-managed macOS devices |
|
Available now – controlled access to services implemented from 12 Dec |
Personal, privately-owned devices (not issued or funded by the University or through University research funding). |
|
Available now – controlled access to services implemented from 12 Dec Web-accessed Office tools will be granted from 12 December Exception Request process available here |
iOS phones/tablets Android phones /tablets |
|
Available now Personal devices will continue to have unchanged access until a solution is agreed. |
Linux devices |
|
Standard Workspace available now Exception Request process available here |
Need something for obsolete OS’s Any other devices or other situation where suggested solutions ‘cannot’ work |
|
Exception Request process available here |
USB controls |
|
Centrally-managed devices from 18 January 2021. Exception required for continued access to USB storage devices, request here Self-managed devices – date TBC Personal devices on VDI – from w/c 14 December Personal devices not on VDI – available once Exception Request agreed. |
Help and support
After the implementation dates shown (From 12 December) if your device is unable to access University systems or you experience any other technical issues, contact the Helpdesk immediately.
The team will be able to restore access, document your situation and provide advice on the next steps and best solution for your circumstances.
The Exception Request Process is available here
Read our Device Security Project background information here
Read our detailed Device Security Project FAQs here