TLP White: In this edition of Hacking Healthcare, we take an in-depth look at telework. As the spread of COVID-19 has led to social distancing and other policies meant to curb infection rates, many industries are turning to telework to continue operations to the maximum extent possible. Below we outline some of the general challenges of this transition, as well as some specific difficulties the healthcare sector faces in adopting both telework and telehealth. And speaking of which, we start with an announcement from the US National Institute of Standards and Technology (NIST) on their new telehealth initiative.
As a reminder, this is the public version of the Hacking Healthcare blog. For additional in-depth analysis and opinion, become a member of H-ISAC and receive the TLP Amber version of this blog (available in the Member Portal.)
Welcome back to Hacking Healthcare.
NIST NCCoE’s “Securing Telehealth Remote Patient Monitoring Ecosystem” Project:
The National Cybersecurity Center of Excellence (NCCoE) at NIST has moved the Securing Telehealth Remote Patient Monitoring Ecosystem project into the build phase after accepting letters of interest from the private sector. The project’s stated goal is to “provide a reference architecture that will address the security and privacy risks for healthcare delivery organizations (HDOs) leveraging telehealth capabilities such as remote patient monitoring (RPM).” The need for such guidance has increased in recent weeks as the benefits and use cases of telehealth have become apparent during the COVID-19 pandemic
Ultimately, NIST plans on publicly releasing a Cybersecurity Practice Guide that will provide “detailed implementation [guidance regarding] practical steps needed to implement a cybersecurity reference design that addresses” the challenges inherent in telehealth. The organizations partnering with NIST on this project include Accuhealth, Cisco, Inova Health System, LogRhythm, MedCrypt, MedSec, Onclave, Tenable, University of Mississippi Medical Center, and Vivify Health. More information, including a full project description, can be found on the NIST NCCoE website.
The Telework Transition: The speed at which COVID-19 went from concern to crisis caught many organizations off-guard. The sudden need to protect employees and communities by complying with health recommendations like social distancing has turned telework from luxury into necessity for many companies and government agencies needing to continue operations. While this transition has mitigated some of the economic impact that might normally be associated with such dramatic circumstances and allowed the continuation of many essential services, teleworking has its own unique challenges that need to be carefully managed.
Among the most significant issues that all organizations will face as they attempt to embrace telework is how to remain secure. Securing on-premises networks is already a challenge for thinly resourced IT teams. The added complexity of quickly scaling up secure remote access organization-wide cannot be understated. Recognition of this fact even led NIST’s Information Technology Laboratory (ITL) to release a bulletin outlining specific security concerns surrounding telework and remote access.
In that bulletin, NIST acknowledges that telework and remote access technologies increase exposure to malicious threats and require additional protections. They specifically call out the following:
- Physical Security: Additional risk of compromise due to mobile devices being off premises in uncontrolled environments
- Unsecured Networks: Increased risk is associated with the use of external networks
- External Access to Internal-only Resources: Increased risk is associated with remote access to sensitive internal resources
NIST recommends that organizations build their remote access telework security policies and controls with the assumption that devices will be exposed to external threats. They also suggest that telework security policies should clearly define requirements for working remotely, remote access servers should be correctly configured and effectively secured to enforce security policies, and that organization-controlled telework devices should be secured against common threats. One of the most effective ways of enabling that security is through multi-factor authentication (MFA). The vast majority of VPNs and online application support MFA and this should be enabled wherever possible. The ITL bulletin goes on to list several NIST documents that give more comprehensive guidance on these issues.
Capacity may also be a major hurdle to clear for many. Whereas telework in the past has generally been reserved for specific individuals, specialized tasks, or uncommon events, the sudden need to bring an entire organizational workforce or student body online has exponentially increased capacity needs across a wide spectrum of use cases. A shortage of secure take-home devices; limitations to servers and underlying infrastructure; a shortage of IT professionals to support a mass transition; and a lack of reliable low-cost, large-scale communication technologies are some of the factors cutting into the efficiency of telework.
Reports from both public and private organizations in many industries note that they simply can not scale-up to meet demand. For example, earlier this month, the U.S. Airforce’s virtual private network (VPN) software was limited to 72,000 connections at a time, far short of the roughly 275,000 civilian workers and full-time contractors that they employ. While, the U.S. Air Force might have the means to scale up relatively quickly, many organizations do not have the resources.
Zscaler’s CISO, Stan Lowe, noted that even those organizations that do have significant remote capabilities typically have the VPN infrastructure to support only 20-30% of their workforce remotely. He elaborated that scaling up can be costly and time consuming as hardware needs to be bought, shipped, deployed, and then updated and maintained. In his estimation, it can take months to successfully implement everything required to smoothly transition an organization to a primarily telework model.
A further complication of the unexpected shift to telework is availability. The FCC’s 2019 Broadband Deployment Report estimates that over 21 million Americans do not have access to broadband Internet connections. Broadband Internet connections are defined by the FCC as having at least 25 Mbps download rate and 3Mbps upload rate, and low Mbps can significantly impact file transfer rates and audio/video communication. At a time when households are recommended or required to remain indoors, the bandwidth that is available to these households is often stretched thin by multiple individuals competing for usage.
Healthcare and Public Health
In the healthcare and public health sector, telework and telehealth are currently more valuable than ever for providing a means for healthcare professionals to interact with patients who are sheltering in place or would be exposed to significant risk by physically visiting a healthcare facility. It can also mitigate the risk to healthcare providers who are not on the immediate frontlines of the COVID-19 response. Furthermore, it allows those healthcare providers who may be quarantined to still provide necessary aid.
However, while many of the technologies to enable high quality telehealth and telework exist, few healthcare organizations have invested substantially in acquiring and training personnel on those capabilities. While investment in medical tech like telehealth technologies has been slowly growing over the years, COVID-19 has shown how much more needs to be done. To further integrate telehealth and telework into their systems, healthcare organizations will have to tackle a few challenges.
First, as a highly regulated industry with a premium placed on preserving the privacy and security of patient data, telework and telehealth must contend with numerous legal and regulatory demands, such as HIPAA and other legal regimes. While the Health and Human Services Department (HHS) has recently relaxed enforcement around some of these protections in an effort to combat COVID-19, healthcare organizations must remain vigilant that their practices are compliant with laws and attentive to new privacy concerns.
Second, there is also an issue of resources. Under normal circumstances, it can be difficult for healthcare organizations to find the resources to invest in things like telework and telehealth that could be deemed a luxury. However, at a moment when teleworking and telehealth technologies are perhaps most beneficial, resource allocation for such efforts are in direct competition with the need to purchase medical equipment like ventilators and masks, re-tool for the fabrication of medical equipment, and contend with the reality of a sharp downturn in the economy. Strained resources in the present environment have taken a toll on HDOs in their efforts to efficiently and effectively roll out telework and telehealth capabilities.
For healthcare organizations that are in the midst of dealing with the issues outlined above, rest assured that various entities are working to disseminate documentation to assist during the transition. In addition to the comprehensive general guidance that NIST provides, the Healthcare and Public Health Sector Coordinating Council (HSCC) has also recently released guidance. Entitled “Management Checklist for Teleworking Surge During the Covid-19 Response,” (https://healthsectorcouncil.org/covid-checklist/) the document is “designed as a quick reference for healthcare enterprise management to consider important factors in a teleworking strategy that minimizes downtime and latency while supporting patient care, operational and I.T. security, and supply chain resilience.” It is freely available on the HSCC website, and we encourage you to read through it.
Telework and telehealth are unexpectedly experiencing the largest possible test to date with little notice for organizations to prepare themselves. While we are still only a few weeks into this situation, the early findings suggest that teleworking and telehealth are having a noticeable impact. There are limitations, but many of the initial challenges outlined above appear to be solvable with maturation of technology and telework policies. While the health effects of COVID-19 will resonate for years, it seems plausible that one of its longest legacies it will be a shift in how the world embraces these technologies.
Tuesday, March 24th:
– No relevant hearings
Wednesday, March 25th:
– No relevant hearings
Thursday, March 26th:
– No relevant hearings
International Hearings/Meetings –
EU – No relevant hearings/meetings
Conferences, Webinars, and Summits –
–H-ISAC Monthly Member Threat Briefing – Webinar (3/31/2020)
–H-ISAC Security Workshop – Frederick, MD (6/9/2020)
–AAMI Exchange – New Orleans, LA (6/12/2020-6/15/2020)
–H-ISAC Security Workshop – Lisbon, Portugal (6/17/2020)
–H-ISAC Security Workshop – Buffalo, NY (6/23/2020)
–H-ISAC 2020 Inaugural APAC Summit – Singapore (6/23/2020-6/25/2020)
–Healthcare Cybersecurity Forum – Rocky Mountain – Denver, CO (7/20/2020)
–Healthcare Cybersecurity Forum – Southeast – Nashville, TN (9/9/2020)
–H-ISAC Security Workshop – Greenwood Village, CO (9/16/2020)
–Healthcare Cybersecurity Forum – Northeast – Boston, MA (9/22/2020)
–Summit on Security & Third Party Risk – National Harbor, MD (9/28/2020-9/30/2020)
–Healthcare Cybersecurity Forum – Texas – Houston, TX (10/8/2020)
–H-ISAC Security Workshop – Mounds View, MN (10/27/2020)
–Healthcare Cybersecurity Forum – Pacific Northwest – Seattle, WA (10/28/2020)
–Healthcare Cybersecurity Forum – California – Los Angeles, CA (11/12/2020)
–Russian hackers using stolen corporate email accounts to mask their phishing attempts
–Ransomware claims more than doubled in the last year
–Windows code-execution zeroday is under active exploit, Microsoft warns
–UK coronavirus app ‘must respect privacy rights’
Contact us: follow @HealthISAC, and email at firstname.lastname@example.org