SUPPLEMENT THE INTERNET OF THINGS
IOT SECURITY BEGINS WITH THE HARDWARE
The IoT has significantly changed the way medical devices are developed. Usually they need to be connected to the net, plus the services are becoming increasingly complex. Security is one of the biggest obstacles developers have to overcome. Hardware platforms are a good starting point, as they already have numerous security features integrated for IoT applications. congatec has just the solution
CONNECTIVITY Connectivity, i. e. the ability to communicate via various methods, is principally enabled on most platforms, at least the corresponding interfaces are available. An IoT–enabled platform has to facilitate easy and safe communication. This is where the software comes in. An IoT-enabled platform has to provide secure encryption on all communication channels. Ideally, a combination of hard- and software is used. A TPM (Trusted Platform Module) can ensure that completely random numbers are used. So if a platform already uses TPM, this is convenient for application developers as they do not need to delve too deeply into the details. Hard disk encryption using BitLocker is just one example. TPM runs a check to detect whether the hardware is unchanged – i.e. trustworthy – and whether the keys are stored securely.
MANAGEABILITY W
ith the vast possibilities that come with increasing Internet bandwidth and the
availability of cloud and virtualisation technologies, which make services portable and scalable, real and virtual worlds are coalescing to the Internet of Things. Medical device manufacturers can individualise their product ranges solely by software licensed over the net. Plus, they can create completely new solutions for home care and the emergency services. Other relevant areas are more efficient asset logistics due to continuous localisation of devices and IT-based allocation. With more and more networked devices and the consequent increase in data volumes, security requirements are on the rise too. In addition to operational safety which ensures that medical computers, devices and gateways are safe for humans and the environment, a second safety aspect is gaining tremendous importance: protection against attacks. Devices have to be reliably protected against unauthorised access, misuse and manipulation of the data and the know-how. In most hospitals, security is well catered for in standard servers and workstations. However, medical computers and equipment are often still considered to be stand-alone devices in a closed, self-contained system. Increasing networking means that vast improvements have to be made here too, especially as these devices are often used at
S6 JULY/AUGUST 2016 | ELECTRONICS Figure 1:
Thanks to this starter kit, a combination of technologies from Intel, Windriver, McAfee and congatec, today’s and future IoT challenges can be overcome more easily
the point of care. In addition, the integrated IP (Intellectual Property) is the device manufacturers’ know-how. Consider the ongoing innovations in algorithms for imaging procedures. Plus, these devices are usually also linked up to store data via DICOM in PACS (picture archiving and communication systems). How hard would it then be to hack this type of network, if nuclear power plant networks can be infiltrated? So how can a medical device be securely integrated onto the net? Basically four aspects have to be considered: reliability - connectivity - manageability - security.
RELIABILITY Reliability is very much determined by the hardware. The design has to be durable. Compared to a classic office PC with its average eight hour workday, an IoT application basically works around the clock. IoT systems are designed to deliver 24/7 operation over a long number of years. Choosing the right components is therefore essential, so ceramic capacitators are preferable to electrolytic capacitors and industrial CPUs are the right choice for non-stop operation. Long-term availability and support over a period of seven years or more are imperative too. Security starts with the BIOS/UEFI of the computer. It is only embedded CPU boards/modules manufacturers who can make necessary firmware updates available during the product’s lifetime.
IoT-connected devices also need safe management methods. Remote access and remote maintenance need secure data connections. Clear identification of these devices also has to be executed via this data path. Either a TPM can carry out the required authentication, or alternatively, technologies common to the telecommunications sector can be deployed. TR-069, for example, is a protocol for data exchange between the server of a communication provider and a connected terminal at the end user side. This protocol is, for example, used for secure remote configuration of DSL routers. Mobile phones use OMA DM for initialisation, configuration, upgrades and error management. This protocol can also be used for the IoT. Functions on an IoT device are precisely defined,
which means that software initiation can be protected via ‘whitelisting‘. This guarantees that only authorised software is run and malware cannot be initiated. To realise these quite diverse demands on IoT
devices as quickly, easily and securely as possible, congatec has developed a starter kit, that offers exactly these features and is based on Qseven computer modules with the latest Intel Celeron and Pentium processors. The kit further features ‘Intel Gateway Solutions for IoT‘ with software from Wind River and McAfee. The certified combination of hard- and software enables developers of IoT applications to first and foremost concentrate on functionality. One major step in IoT security has already been taken.
congatec
www.congatec.com T: +49 991 27000
/ ELECTRONICS
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56
