Unit 4 Material
Unit 4 Material
The IoT is bridging the virtual, digital, physical worlds and mobile
networks need to scale to match the demands of billions of things, while the
processing capabilities require addressing the information provided by the
"digital shadow" of these real things. This need focusing on the developments
in the virtual world and the physical world for solving the challenges of IoT
applications.
In the virtual world, network virtualization, software-defined
hardware/networks, device management platforms, edge computing and data
processing/analytics are developing fast and urgency to be endeavoured as
enabling technologies for IoT. Connecting the virtual, digital, physical worlds
generates knowledge through IoT applications and platforms, while
addressing security, privacy and trust issues across these dimensions.
Smart IoT applications modify the way people interact with the
intelligent spaces (called also cyber-spaces), from how remotely control
appliances at home to how the care for patients or elderly persons is perform.
The massive deployment of IoT devices represents a tremendous economic
impact and at the same time offers multiple opportunities.
IoT’s potential is underexploited, the physical and intelligent are
largely disconnected, requiring a lot of manual effort to find, integrate, and
use information in a meaningful way. IoT and its advances in intelligent
spaces advances can be categorised along with the key technologies at the
core of the Internet.
Ensuring the security, reliability, resilience, and stability of Internet
applications and services is critical to promoting the concept of trusted IoT
based on the features and security provided of the devices at various levels of
the digital value chain.
Security needs to be designed into IoT solutions from the concept phase
and integrated at the hardware level, the firmware level, the software level
and the service level. IoT applications need to embed mechanisms to
continuously monitor security and stay ahead of the threats posed by
interactions with other IoT applications and environments.
Trust is based on the ability to maintain the security of the IoT system
and the ability to protect application/customer information, as well as being
able to respond to unintended security or privacy breaches.
In the IoT, it is important to drive security, privacy, data protection and
trust across the whole IoT ecosystem and no company can "do it alone" in the
IoT space; success will require organizations to partner, value chains to be
created and ecosystems to flourish. Yet, as IoT users start to bring more
players, service providers and third-party suppliers into their value chain, tech
firms and IoT solutions providers will face increasing pressure to demonstrate
their security capabilities.
A layered IoT architecture is proposed for a trust management control
mechanism. The IoT infrastructure is decomposed into three layers: sensor,
core and application. Each layer is controlled by a specific trust management
under the following purposes: self-organisation, routing and multi-service,
respectively. The final decision-making is executed by the service requester
(i.e. the user) according to the collected trust information and the requester
policy. A formal semantics-based and fuzzy set theory are used to realise the
trust mechanism.
The distinction between trust and the related concepts of
trustworthiness, confidence and the act of entrusting something to someone
are extremely important. Uncertainty and vulnerability are two of the core
elements in trust relations. In addressing issues of trust, actors select strategies
that reduce uncertainty or decrease vulnerability, depending on the particular
context in which the issues emerge. Mechanisms for reducing vulnerability
in the face of increased contact with unknown things include enforceable
contracts, insurance schemes, etc. The characteristics of different types of
trust relations include faith, confidence, legal trust and trust/distrust.
Since it is a sign of a more usual quality known to be correlated with
trustworthiness (for example, same group, class, family, or same source),
identity ‘signals’ trustworthiness in many cases.
This graph represents the required trust levels given a certain need for
privacy. There we see, that even when the need for privacy is at a maximum, at
1, the required trust level towards a service / architecture is below 0.75.
Such a mismatch is due to the fact that for users it is impossible to trust a
service / architecture 100% since there are too many unknown factors in the
current state of things. An individual sharing personal data usually does not have
a complete understanding of how the architecture is built up, about how security
measures are realised or how trustworthy potentially involved third parties are.
The graph also implies that that the user is not able to trust the service at the
expected level in relation to his privacy needs – leaving room for improvement
on the side of IoT device and software vendors. IoT-EPI researchers have
therefore included an “Ideal Trust” line in Figure 15 to indicate the user trust
levels that vendors should be striving towards.
The biggest challenge for IoT is therefore to fill this information
asymmetry with users by means of technical and organisational user-friendly
solutions.
One idea could be to deploy a solution which measures the level of
trustworthiness of a service using the traffic light metaphor. Alternatively, a more
elaborate dashboard could be used to give the user an overview of trust values
and make adequate suggestions about which services to use.
Yet in some different contexts, like in the smart cities domain, users should
be involved when carrying out Privacy Impact Assessments on the envisaged
smart city initiative.
The informed consent process has now been adopted to regulate the
interactions of citizens within the digital world. From a legal perspective, the
notion of informed consent is essential for the data protection of information and
communication technology (ICT) systems as the consent of a data subject is often
necessary for a third party to legitimately process personal data.
To provide informed consent regarding the use of personal data, the citizen
must have a clear understanding on how his/her personal data will be used by the
ICT systems and applications. This may not be an easy task, especially for a
citizen with a limited understanding of the complexities of ICT. On the other
hand, informed consent must be collected before ICT applications can be used.
There is a need for a more sophisticated tool for informed consent, which
would provide the following features at a minimum:
1. Support different types of users across the full spectrum of users in the
digital divide (i.e., from the most ICT literate to the least) and/or support
different user roles.
2. Be customizable so that the user can change settings if he/she wishes
to within preestablished parameters, as defined by the regulations or the
application developer.
3. Support different type of contexts or changes in the environment.
Beyond the ICT domain, the issue of providing a tool for “informed
consent” with these features is further complicated by the evolution of the IoT.
The definition of EULAs for end users may be further complicated by the limited
processing capabilities of IoT devices, the distributed nature of the IoT, and the
integration of the digital with the real world. The numbers of potential data
operations in a fully deployed IoT make the adoption of EULA less practical. In
addition, the nature of the informed consent required would vary depending on
the data provided by the IoT device and the related data flow.
To ensure the policy enforcement, the whole system is built on an IoT platform that
embeds policy enforcement components and the policy framework, as described in the rest of
this chapter. To be implemented successfully, the system must address the following
requirements:
1. Support different types of users across the full spectrum of users in the digital divide (i.e.,
from the most ICT literate to the less) and/or the different roles. This includes the necessity of
providing the user with easily understood information in a simple GUI, and also the setup of
mechanisms to train and motivate the user to define policies (i.e., to ensure regular use of the
system).
2. Be customizable so that the user can change settings if he/she wishes. One of the challenges
of customization is to adapt the GUI to follow the user proficiency.
3. Support different type of contexts or changes in the IoT environment and ensuring the
enforcement of the policies chosen by the user.