Table 1: Benchmarking overview of exiting work in IoT for healthcare.
Ref Embedded platform emergency alerts Sensor
(Khan, 2020) Client computer with IoT sensors No Not done
(Rghioui et al., 2021) IoMT Based cloud infrastructure No Not done
(Islam et al., 2023) Android Device with Iot wearable Device Yes Done
Our main focus is to equip the methodology with hu-
man cognition, which is capable of performing intel-
ligent decision making independently.
These artifacts then become the object of the
study. The methodology followed in our research is
classified into four methods and activities, linked with
the corresponding steps of the DSR approach. DSR
artifact can include: Construct, Models, Method, and
Instantiation.
3.1 Construct
Let’s consider our smart IoT-based healthcare sce-
nario, in which a medical IoT device publishes the
physical condition (such as ECG or blood glucose) of
a diabetic patient to a remote healthcare center peri-
odically.
Despite their large deployment, security issues,
mainly related to data privacy, are often considered
as potential obstacles that might limit the extent of
such solutions. Hence, the constructed artifact itself
presents a challenge to explain how and why it works.
Hence, the attacker blocks critical health information
from being transmitted to physicians, threatening the
life of the patient.
Context: In general, the IoT-base healthcare system
collects sensitive data. The platform must ensure an
adequate level of security to data access and manage-
ment. At this stage, management analysis must clarify
and define functional requirements and design con-
straints. Functional requirements define quality (how
good), environment (know-that), availability (how of-
ten) and the procedural knowledge (know-how) to
make decisions. To ensure such functionalities, the
system should be able to understand the meaning of
the received data and history as well as the disease
management strategies to provide the right decisions.
Problem: If we consider deploying and activating
all the monitoring processes for each patient, this re-
quires increasing the cost. Moreover, hard coding of
all rules causes maintainability problems. Besides,
privacy is also a primary concern in the remote health
monitoring system, as health data are highly relevant
to the patient being monitored.
Solution: To deal with those challenges, our method-
ology design, are used to combine knowledge and se-
curity analyses. We defined within this methodology
a set of (1) delineating the security dynamic coordi-
nation of the management processes to deal with the
system’s context changeability and (2) cognitive abil-
ities to IoT-based systems to interact with the human
through generating new insights and to solve prob-
lems as human do.
3.2 System Model
In this sub-section, we illustrate the system model of
our case study of the diabetic patient. It is depicted
by figure 1, which consists of: (i) a trusted domain
with sensors and IoT devices under a single adminis-
trative domain (e.g. at home, or outside the home),
and (ii) an untrusted domain connected via the public
Internet, including the illegal user.
Note that we consider the application logic to be
separate from its implementation: while the design of
the application logic can be separately verified, vul-
nerabilities can still be introduced due to implemen-
tation bugs.
Proposing a system model for the patient monitor-
ing system should take into account the key character-
istics of IoT. The techniques should be asking enough
to various context. Thus, the IoT system must have
strong security guarantees.
We propose the bottom-up approach for verifying
the security of the software stack in an IoT system, to
provide a guarantee for how the software is secure.
We plan to verify the security of the actual (source
and machine) code that will run on IoT devices. By
bottom-up approach, we mean that the security of
software needs to be established at every level of ab-
straction: at the OS (Operating System), implementa-
tion, and functional design levels.
Specifically, the choice of our methodology refers
to a pluralistic methodological approach (case studies,
architecture, and narratives approach).
As shown the figure 1, the arrow model presents
the precedence relationship between the eight pro-
cesses; denoted by 1- Context; 2-Activity monitoring;
3-Information Capture; 4-Vulnerability; 5-Threats; 6-
Risk; 7-Reduces /Countermeasures; 8- Security re-
quirements.
• 1-Context: It refers to the vast amount of infor-
mation processing that normally takes place out-
side conscious awareness, even during sleep. Our
methodology should be asking enough two moti-
vating factors.
SECRYPT 2023 - 20th International Conference on Security and Cryptography
846