XDL120 | User Manual
22 | 25
Data subj ect to change without notice
Bosch Connected Devi ces and Sol utions
4.2
Stakeholders and Roles
The following definitions list the stakeholder of the security concept. In addition, their possible actions are defined, which
can be performed relating to security aspects.
4.2.1
XDL user
The user is the owner of the XDK device and can use the XDL120 to log XDK sensor data. The user can do the following:
Flash and run the XDL120 on the XDK
Stream sensor data to a network computer
Convert files with sensor data using the provided auxiliary components
4.2.2
Bosch Connected Devices and Solutions
Bosch Connected Devices and Solutions GmbH is the developer of the XDK device and offers documentations, libraries,
and demonstration applications via the XDK.io platform, as well as the XDL120 embedded application and auxiliary files.
4.3
Physical and Environmental Security
The XDK device is not limited to a specified environment. It can be deployed at all suitable places of action. Especially, the
physical and environmental security goals depend on the use cases given by the XDK user. BCDS determined three typical
use cases. This can help the user to derive his security goals by assigning to one of the following described use case
scenarios. The XDK device should not be used as a safety relevant device controlling critical processes.
For further information, please refer to the “general information” guide at
www.xdk.io
4.3.1
Use Case Scenario 1 (Deployment at private area)
In the first use case the XDK user uses the XDK device inside the corresponding Personal Area Network (PAN) or Local
Area Network (LAN). In this case it is assumed that the physical access of the XDK device is limited to the XDK user. It
should be nearly impossible to gain physical access to the XDK device by unauthorized third parties. Additionally, the
access network, gateway, and network participants are assumed to be trustworthy. The likelihood of security events
triggered by unauthorized physical access is assumed to be low.
4.3.2
Use Case Scenario 2 (Deployment in industry)
In the second use case scenario the XDK user deploys the XDK device inside industrial environments. These areas are
usually protected by access controls. It is also possible to determine third parties who had access at the time of security
incidents. Additionally, the access network, gateway, and network participants are assumed to be partially trustworthy. Due
to the access controls and the non-repudiation of the security incidents, the likelihood of unauthorized physical access or
unintentional misusage of the XDK device is assumed to be medium.
4.3.3
Use Case Scenario 3 (Deployment in public area)
In the third use case scenario the XDK device is used in an unprotected environment (e.g. public Hotspot and public area).
In this case, it is difficult to protect an unauthorized physical access to the XDK device and the WLAN network.
Additionally, the access network, gateway, and network participants are assumed not trustworthy. Due to non-existing
access controls and the possibility of repudiation of involvement in security incidents, the likelihood of unauthorized
physical access and malicious usage of the XDK device is assumed high. In summary, the infrastructure must be assumed
as inherently untrustworthy.
4.4
Asset Management / Media Handling
The XDK user own different types of assets, which have to be discussed separately. There are the primary assets, which
are data with different security attributes. Besides data processes also belong to the primary assets. Primary assets cannot
be replaced or restored if they got lost. Thus, depending on the security attributes the user has to realize different
measures to ensure the confidentiality, integrity, and availability of the data or processes. Another class of assets are the
supporting assets. These assets are replaceable like system components, software/applications and network components.
