Cybersecurity in connected medical devices: a policy agenda for the NHS
Cybersecurity in connected medical devices: a policy agenda for the NHS
https://www.nature.com/articles/s41746-026-02534-4
Publish Date: 2026-03-10 05:17:00
Source Domain: www.nature.com
Using an unordered list, summarize the following article with between 4 and 8 key points. The cloud layer acts as a shared central node for collecting, processing, and routing CMD data. It interfaces with the physical layer, via the network layer, using integration protocols, typically implemented as application programming interfaces (API) or on-premises gateways (OPGs). While experts often frame vulnerabilities in cloud environments as issues of software, firmware, or hardware, rooted in architectural design, computational limitations, or proprietary systems, the likelihood of cloud-layer compromise, and its capacity to propagate downstream into patient harm, is more accurately understood as a socio-technical problem. This rationale refers to the interdependent relationship between people (e.g., developers, security operatives, or high-level executives), organisational processes (e.g., software supply chain verification), and technologies (e.g., identity management systems and notably connected medical devices).As organisations such as the NHS are confronted with the growing complexity of cloud infrastructure, one of the most prevalent risks they may face is cloud-level misconfiguration (CLM). This often manifests as vulnerabilities in authentication and access control mechanisms, allowing attackers to gain unauthorised access to private integration protocols, such as the CMD API. In such cases, security mechanisms are bypassed, potentially exposing sensitive patient data at the cloud layer. The underlying causes of CLM, especially at larger CMD vendors, are less attributed to the absence of broken user authentication and more about broader organisational challenges, including a shortage of skilled professionals and outdated practices.Identity and access management (IAM) failures are another major risk in modern cloud environments, referring to the inability to adequately control which users can and cannot access sensitive data, applications, and other resources. A common manifestation of this is excessive account permissions (EAP), where users or services are granted access that is broader than required. While the principle of least privilege (PoLP) offers a well-established framework for mitigating such risks by restricting access strictly to what is necessary, its implementation is often inadequate. Additionally, organisational culture and attitudes, such as complacency or negligence, can further undermine the security of the cloud layer.Cross-domain threats are also a significant concern to cloud infrastructure, as they often come from outside the organisation through compromised vendors, third-party tools, or shared identity systems, making traditional perimeter defences less effective. The recent Synnovis cyber-attack impacting the NHS is a clear example, where a third-party supplier was targeted with ransomware and caused significant disruptions to hospital and primary care services6. As the NHS becomes increasingly reliant on interconnected services and external platforms, the ability to detect and respond to threats across domains becomes crucial for maintaining clinical continuity.Recognising these risks, NHS England and the Department of Health and Social Care launched a new supplier engagement programme in January 2026. The voluntary Cyber Security Supply Chain Charter strengthens collaborative assurance across key controls, including patch management, access control, and backup resilience7. While this represents a positive step in addressing supply chain vulnerabilities, it must be complemented by robust regulatory frameworks to ensure accountability across the CMD ecosystem.
