We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Keeping safety-critical programs alive when Linux isn’t able to

Formal Metadata

Title
Keeping safety-critical programs alive when Linux isn’t able to
Subtitle
Using OP-TEE to deliver availability to applications in a Trusted Execution Environment.
Title of Series
Number of Parts
542
Author
Contributors
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Increasingly, industry is using Linux on embedded systems to take advantage of its flexibility and existing (open source) functionality. This allows them to connect Cyber-Physical Systems, which have stringent safety requirements, to the Internet so that they can do remote management and monitoring. However, the flip side of the flexibility coin is decreased availability. Not only can a lot more go wrong in such a complex operating system, if an attacker would be able to get root access on such systems, all bets are off. Our research project makes use of hardware Trusted Execution Environments (TEE), now readily available on even low-end commodity devices, to provide a secure and always available execution context for safety-critical programs. By integrating a real-time scheduler inside of OP-TEE OS running in an Arm TrustZone TEE, it is possible to safeguard the real-time execution requirements of these programs, even under the influence of Linux kernel panics and remote attackers with root privileges. This presentation will explain the system architecture that resulted from our research, its implementation on a common Arm processor and a quick demo showcasing the core functionality.