global system design Although this aspect is related to the deployment view, it has
impacts on the design of the overall system and trust
evaluation.
Consider the impact of
security/performance tradeoffs
on trust
This must be evaluated for each use case during the design
phase by means of tests such as simulation. For that reason,
no DC can be proposed.
Use security imprinting Out of scope for IoT-A since devices are not covered in the
IoT Reference Architecture.
Balance privacy vs. non-
repudiation (accountability)
If system requirements include non-repudiation, these will
necessarily impact the privacy feature of the designed
system. Privacy can be granted by using Identity
Management. This component, run by a third party is trusted
for what concerns both privacy protection and ability to track
back malicious actions.
Table 23 : Omitted tactics for the Trust Perspective.
5.2.10.5 Design Choices addressing Security
In Section 4.3.3.2 the Security Perspective together with a set of tactics is
presented. The Design Choices addressing security are presented in Table 24
showing the impact on architectural views by applying tactics relevant for
security concerns.
Tactic
Impact on Views
Functional Information Deployment and Operation
Subject
Authentication
Authentication over
encrypted channel
(DC S.1)
No impact
Integration of IoT-A
Authentication FC (DC
S.2)
Crypto-based
authentication over
open channel (DC S.3)
No impact
Peer-to-peer
authenticated
communications over
an insecure channel
must be possible (DC
S.4)
Use access policies
Policy-based service
access (DC S.5)
Stored Information
must be managed in a
way to support access
control mechanisms
(DC S.6)
IoT-A Authorisation FC
component (DC S.7)
Unrestricted access to
service (DC S.8)
Stored Information is
not protected (DC S.9) No impact^
Secure
communication
infrastructure
End-to-end encryption
(DC S.10)
Information
transmission channel
between device and
application is secured
(DC S.11)
IoT-A End to End
Communication FC,
Network
Communication FC
and Key Exchange
and Management FC
(DC S.12)
Hop-to-hop encryption Information IoT-A Hop To Hop