I
ndustrIal
C
ontrol
& C
omputIng
– can be used. These tools access hardware
components such as the TPM (Trusted Plat-
form Module) chip to protect the keys used
for decryption. The data are only accessible
to authorized users. The encryption is also
linked to the device so that hackers can-
not read any passwords or data even if they
remove the hard disk or SSD (solid state drive)
and install it into a different system.
In addition, a TPM chip integrated into a sys-
temcan be used for encrypted communication
and for uniquely identifying the hardware to
higher-level systems. TPM can also be used to
detect hardware and software tampering and,
based on this, initiate a secure boot or Roots
of Trust. TPM cannot be retrofitted because,
besides the hardware chip, the needed func-
tions must be implemented in the BIOS (basic
input/output system). More and more intel-
lectual property is in the software, making this
a favorite target for hackers and reverse engi-
neering. The ever-increasing network density
makes access to this IP substan-
tially easier in the case of systems
with weak security. Once the
core software is extracted or the
license key cracked, the software
can be transferred completely
or in parts to other systems and
used there. Individual algo-
rithms and special functions can
be extracted from unprotected
program code using reverse
engineering and then integrated
into other applications. This
represents tremendous damage
that must be prevented. Security
controllers can provide protec-
tions here.These are soldered into
the system and integrated there.
Functions that need to be specially protected,
usually small blocks of code suffice, are
encrypted during compilation so that they
later cannot be executed on the computer
CPU but only in the dedicated security con-
troller of the target system. The software can
only run on the intended target system. The
encrypted program code blocks can also not
be tracked and reverse-engineered during
runtime.
The same applies to optional added features
that can be activated with a license. If the acti-
vation only uses software, it is usually just a
question of time and effort until the needed
license strings or activation routines are
cracked. For secure protection, hardware and
software must be coordinated and the license
activations (license keys and activation rou-
tines) must be run remotely, for example, in
the security controller mentioned already. A
similar feature is known from the end user
arena in the form of hardware dongles that are
inserted into a USB port. For embedded PC
systems, however, it is advisable to implement
this feature using permanently integrated
chips. This ensures a fixed assignment to the
device or system. Secure licensing processes
can only be implemented and the IP and extra
options for a fee be appropriately protected
against abuse if this has been specified during
the development phase.
Hard-wired communication paths are usually
used within local networks or IT infrastruc-
tures. These paths are well protected from the
outside world by firewalls or the like. However,
there is a greater risk if the communication is
wireless. This is mainly the case if the com-
munication path runs directly to the internet.
When selecting communication components,
pay attention to which security features are
already included, especially when cellular
communications (2G/3G/LTE) is used to
expand integrated IoT solutions. The entire
communication chain, from the system to the
cloud, should be considered during develop-
ment. It is usually advantageous in this case to
use manufacturers who offer the communica-
tion modules with suitable software routines
for connecting to the cloud together with the
cloud services as a package deal.
New applications in the IoT area and for the
networked future often give rise to uncertainty
and doubts because it is difficult to judge the
topic of security. Security plays a central role
and, as a basic requirement, must be incorpo-
rated as early as the product definition phase
and during development. To close any gaps in
experience and to answer open questions, it
can be smart to include partners in the pro-
cess and to use platforms already in existence.
This can happen both on the component level
and on the system level.
n
Figure 2. The medical PC platform from TQ shows one
example of the implementation of all basic security features:
TPM support, security controller and wireless options that
allow for secure communication and comprehensive protection.
