Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
3/25/2019
09:30 AM
Mark Hearn, Director of IoT Security, Irdeto
Mark Hearn, Director of IoT Security, Irdeto
Sponsored Article
50%
50%

Cybersecurity & The Internet of Medical Things

How a trusted and SIEMple solution helps healthcare providers meet the challenges of the new world of digital medicine while ensuring data privacy and patient safety.

Internet of Medical Things (IoMT) devices are revolutionizing the healthcare business.  They are delivering on the promises of improved data access, convenience, operational efficiencies and automation for healthcare providers (HCP). Plus, additional drivers like patient engagement and safety, accuracy of vitals, and mobility within the institution promise continuing, potentially explosive growth in smaller, connected medical instruments.

That’s the good news. The bad news is that healthcare IT groups are struggling with the proliferation of IoMT devices, which currently average three to six monitoring devices per admitted patient. In this new world of digital medicine, the big challenge is in ensuring that both data privacy and patient safety remain top priorities.

Security Information Event Management (SIEM) systems, like IBM’s QRadar, are the major tool HCPs are using to successfully deal with this explosive growth in connected devices and data. Gartner’s Magic Quadrant for Security Information and Event Management 2018 report (Registration Required) defines the SIEM market as "the customer’s need to analyze event data in real time for early detection of targeted attacks and data breaches, and to collect, store, investigate and report on log data for incident response, forensics and regulatory compliance.” SIEM promises to make security events more digestible and actionable, especially when cognitive computing is brought to bear on the large volume of aggregated data that floods in from the networked devices.

But even the most sophisticated SIEM systems struggle in today’s hyper-connected medical institutions. Here are three examples:

Example 1: Integrating instruments based on small, embedded processors and real-time operating systems
It can be a challenge to extend the reach of the SIEM into devices that have very constrained resources and may not be able to support standard logging. Supporting the wide diversity of device platforms and operating systems within the healthcare environment is equally daunting.

Example 2: Allowing for untrusted devices
Mobile devices like smartphones and tablets that host medical applications must be considered as hostile environments.  They are often unmanaged (or even user-owned BYOD) that can leave the premises and allow a hacker the luxuries of time and access in order to craft an attack. This is also a concern for the emerging category of patient wearables.

Example 3: Scaling to thousands of devices
The problem of scaling boils down to a matter of trust in the data. If a motivated hacker compromises the device, they can manipulate the data being sent or block it entirely. SIEM systems use a combination of forensics, behavior and data from multiple sources to combat this, but as the numbers of connected devices deployed in medical institutions grow exponentially, the shear volume of log events that must be processed to discern critical security events becomes untenable. This is especially a problem for SIEM systems that may use artificial intelligence/cognitive processing to detect bad behavior of a device to use as a cybersecurity event alert. The increasing numbers of alerts put severe pressure on the ability of the system to produce timely security events as well.

One solution to these problems is via a "trusted" security telemetry agent and associated services. By using software protection techniques, it is possible to conceive of a secured telemetry agent, that could produce reliable and robust critical security events in near real-time, without any complicated forensics and additional processing required.

The agent should be written in protected source code for easy portability between platforms and operating systems with a small footprint in code and memory size for instruments with constrained resources. The agent would leverage software protection features for anti-reverse engineering, and anti-tampering, as well as utilizing integrity verification to establish a software-based root-of-trust.

End-to-end protected communications to a dedicated server for aggregation, filtering and reporting rounds out the high-level feature set.

With the features above in place, critical security events can be logged, and the data cannot be compromised by attackers in the generation phase, at rest, or in transit. Such a self-protecting, security-in-depth implementation means you can extend trust to untrusted devices and the pre-qualified security events would help the SIEM extend its reach and scale to thousands of IoMT devices easily!

For more information, please click http://bit.ly/2WWexj6

About the Author

Mark Hearn, Director of IoT Security, Irdeto

Mark Hearn is the director of IoT Security at Irdeto. He is responsible for leading business development strategies to secure organizations IoT applications and connected devices. Mark has been with Irdeto since 2003, through Irdeto’s acquisition of Cloakware. He is a seasoned product management executive with 20 years of bringing technology and business requirements together to solve market problems, particularly within the media entertainment and security markets. In addition to being a product leader in the private sector, Mark has also provided business analysis security consulting into the Canadian government and has spoken at security conferences. Mark holds a Bachelor of Computer Science from Acadia University in Nova Scotia, Canada and has received certifications in product management, technical marketing and strategic marketing.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
NSA Appoints Rob Joyce as Cyber Director
Dark Reading Staff 1/15/2021
Vulnerability Management Has a Data Problem
Tal Morgenstern, Co-Founder & Chief Product Officer, Vulcan Cyber,  1/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-27852
PUBLISHED: 2021-01-20
A stored Cross-Site Scripting (XSS) vulnerability in the survey feature in Rocketgenius Gravity Forms before 2.4.21 allows remote attackers to inject arbitrary web script or HTML via a textarea field. This code is interpreted by users in a privileged role (Administrator, Editor, etc.).
CVE-2021-3137
PUBLISHED: 2021-01-20
XWiki 12.10.2 allows XSS via an SVG document to the upload feature of the comment section.
CVE-2020-27850
PUBLISHED: 2021-01-20
A stored Cross-Site Scripting (XSS) vulnerability in forms import feature in Rocketgenius Gravity Forms before 2.4.21 allows remote attackers to inject arbitrary web script or HTML via the import of a GF form. This code is interpreted by users in a privileged role (Administrator, Editor, etc.).
CVE-2020-27851
PUBLISHED: 2021-01-20
Multiple stored HTML injection vulnerabilities in the "poll" and "quiz" features in an additional paid add-on of Rocketgenius Gravity Forms before 2.4.21 allows remote attackers to inject arbitrary HTML code via poll or quiz answers. This code is interpreted by users in a privile...
CVE-2020-13134
PUBLISHED: 2021-01-20
Tufin SecureChange prior to R19.3 HF3 and R20-1 HF1 are vulnerable to stored XSS. The successful exploitation requires admin privileges (for storing the XSS payload itself), and can exploit (be triggered by) admin users. All TOS versions with SecureChange deployments prior to R19.3 HF3 and R20-1 HF1...