Tools
Tools
Viana, Thiago 
ORCID: 0000-0001-9380-4611 and Tyler, Dan
(2021)
Trust No One? A Framework for Assisting Healthcare Organisations in Transitioning to a Zero-Trust Network Architecture.
Applied Sciences, 11 (16).
Art 7499.
doi:10.3390/app11167499
|
Text (Peer Reviewed Version)
10103 Tyler and Thiago (2021)Trust No One A Framework for Assisting Healthcare Organisations in Transitioning to a Zero-Trust Network Architecture.pdf - Accepted Version Available under License Creative Commons Attribution Share Alike 4.0. Download (706kB) | Preview |
Abstract
Traditional networks are designed to be hard on the outside and soft on the inside. It is this soft inside which has made the traditional perimeter model laughable to attackers, who can easily breach a network and run away with the data without even having to deal with the hardened perimeter. The zero-trust security model, created by John Kindervag in 2010, addresses the security flaws of the traditional perimeter model and asserts that all network traffic on the inside should not be trusted by default. Other core principles of zero trust include verification and continuous monitoring of all communication, as well as encryption of all data in transit and data at rest, since the goal of zero trust is to focus on protecting data. Although the zero-trust model was created in 2010, with some of the associated security practices existing even before that, many healthcare organisations are still choosing to focus primarily on securing the perimeter instead of focusing on the vulnerabilities within them. The current COVID-19 pandemic which healthcare providers are struggling with further highlights the need for improvements to security within the network perimeter, as many healthcare providers and vaccine developers are still using vulnerable, outdated legacy systems which could become compromised and indirectly have a detrimental effect on patient care. Legacy systems which are technologically limited, as well as medical devices which cannot be controlled or managed by network administrators, create boundaries to transitioning to a zero-trust architecture. It is challenges like this that have been explored during the research phase of this project in order to gain a better understanding of how a health organisation can adopt zero-trust practices despite the limitations of their current architecture. From the information gathered during this research, a framework was developed to allow a health organisation to transition to a more secure architecture based on the concept of zero-trust. Aspects of the proposed framework were tested in Cisco Modelling Labs (CML), and the results were evaluated to ensure the validity of some of the recommendations laid out in the framework. The main objective of this research was to prove that if a host within the local area network (LAN) were to be compromised, the damage would be limited to that host and would not spread throughout the rest of the network. This was successful after the qualitative research performed in CML. One of the other takeaways from testing the framework in CML was that medical devices could be secured by placing firewalls directly in front of them. This placement of firewalls may seem like an unorthodox approach and was shown to increase latency, but the blocking of all unnecessary traffic on the rest of the network will result in a performance boost and should balance it out in a real-world application.
| Item Type: | Article |
|---|---|
| Article Type: | Article |
| Uncontrolled Keywords: | Zero-Trust Networks; Healthcare; Legacy Systems |
| Subjects: | Q Science > QA Mathematics > QA76 Computer software R Medicine > RA Public aspects of medicine |
| Divisions: | Schools and Research Institutes > School of Business, Computing and Social Sciences |
| Research Priority Areas: | Applied Business & Technology |
| Depositing User: | Kate Greenaway |
| Date Deposited: | 03 Sep 2021 16:09 |
| Last Modified: | 01 Sep 2023 12:32 |
| URI: | https://eprints.glos.ac.uk/id/eprint/10103 |
University Staff: Request a correction | Repository Editors: Update this record
