TL;DR
This paper introduces the MIoT ontology, a novel knowledge organization system designed to address cybersecurity vulnerabilities in Internet of Medical Things (IoMT) devices used for remote patient monitoring. By formally defining concepts, relationships, and properties related to IoMT devices, vulnerabilities, and attacks, the MIoT ontology aims to improve semantic interoperability and enable more effective cybersecurity analysis and automation in healthcare.
What Problem Does This Paper Address?
The rapid growth of the Internet of Things (IoT) in healthcare, specifically the Internet of Medical Things (IoMT), has brought about significant advancements in remote patient monitoring (RPM). IoMT integrates medical devices for real-time data collection and transmission, offering benefits like improved patient care and accessibility. However, this interconnectedness also introduces substantial cybersecurity challenges, including data breaches, device vulnerabilities, and interoperability issues. Existing research has identified a critical gap in comprehensive ontologies specifically for IoMT cybersecurity, particularly for RPM settings. This paper aims to fill this gap by proposing a domain ontology that formally represents the complex relationships between medical devices, their vulnerabilities, and potential cyberattacks.
Methods
The authors developed the MIoT ontology using a structured, iterative approach based on the Ontology Development 101 methodology and a structured life cycle. This process involved several key stages:
- Specification and Scope: Defining the ontology's purpose, target users, and the specific domain of IoMT cybersecurity in RPM, explicitly excluding non-medical IoT devices.
- Data Acquisition: Gathering information from various sources, including medical device specifications, cybersecurity databases (like NVD), incident reports, and relevant literature.
- Competency Questions: Formulating specific questions that the ontology should be able to answer, guiding the development process.
- Reusing Existing Ontologies: Reviewing existing ontologies in healthcare and cybersecurity to identify potential foundational elements, though ultimately opting for a "from scratch" approach due to domain specificity.
- Term Enumeration: Identifying and listing key terms and concepts relevant to the domain.
- Conceptualization: Organizing the identified concepts into a hierarchical structure (class hierarchy) and defining their properties and relationships. This involved a top-down approach, starting with broad concepts and specializing them.
- Data Dictionary (DD): Creating a detailed document that defines concepts, their meanings, properties, instances, and attributes.
- Concepts Classification Tree (CCT): Organizing concepts into taxonomies to form class/subclass hierarchies.
- Object and Data Properties: Defining relationships between concepts (object properties) and attributes of concepts (data properties).
- Instances: Populating the ontology with specific examples of concepts.
- Formal Grounding with Description Logics (DL): Expressing the ontology formally using DL axioms to ensure logical consistency, enable sophisticated reasoning, and facilitate querying. This involved defining concept hierarchies, role definitions, and individual declarations.
Datasets
Not discussed in the paper. The authors mention using information from various sources like medical device specifications, cybersecurity databases (NVD), incident reports, and academic literature for data acquisition.
Key Insights and Ideas
- Bridging IoMT and Cybersecurity: The MIoT ontology uniquely bridges the gap between the IoMT domain and cybersecurity concerns, providing a unified framework for understanding vulnerabilities in medical devices.
- Semantic Interoperability for Security: By establishing a shared vocabulary and formal relationships, the ontology aims to enhance semantic interoperability, which is crucial for effective data sharing and analysis in cybersecurity contexts.
- Formal Reasoning for Vulnerability Detection: The use of Description Logics (DL) for formal grounding allows for logical inference and automated reasoning, enabling the system to detect inconsistencies and derive new knowledge about potential security risks.
- Focus on Remote Patient Monitoring: The ontology specifically targets the nuances of remote patient monitoring, distinguishing it from general IoMT or broader cybersecurity ontologies.
- Structured Approach to Complex Domains: The paper demonstrates a systematic methodology for developing ontologies in complex, interdisciplinary domains, highlighting the importance of clear definitions, hierarchical structures, and formal logic.
Key Results
The paper presents the development of the MIoT ontology, a conceptual model, and a case study to demonstrate its utility.
- MIoT Ontology: A formal ontology is developed, defining key concepts like
MedicalDevice,Vulnerability,Attack,Exploit,Person, andService, along with their properties and relationships. - Conceptual Model: A visual representation (Figure 2) illustrates the high-level concepts and their interrelationships within the MIoT ontology.
- Case Study: A hypothetical scenario involving a patient's remote monitoring system and compromised devices is used to illustrate how the MIoT ontology can be applied. The authors formulate propositional logic axioms based on assumptions derived from the scenario to demonstrate the ontology's ability to represent relationships and potential consequences of attacks.
- Formal Grounding: The ontology is formally grounded using Description Logics, enabling logical reasoning and the potential for automated security analysis.
Limitations and Future Work
- Limitations:
- The current work does not explicitly address caregivers or other related stakeholders in the IoMT domain.
- A significant challenge is the lack of publicly available datasets or real-time sensor data specifically for IoMT security issues. The authors relied on a case study approach for validation.
- Future Work:
- Incorporate caregivers and other stakeholders into the ontology.
- Integrate standardized vulnerability information (CVE, CVSS) from NVD for assessment and management.
- Implement and visualize the conceptual model in a knowledge graph for semantic representation and data integration.
- Develop rules to enable automated reasoning for more effective inferences and decision-making in security automation.
- Explore the application of the MIoT ontology through case studies for vulnerability analysis and reasoning.
Summary updated