Secured Industrial Embedded Linux

The framework is presented in its current state of January 2017: its history, its features and its goals: opening securely AGL to as many companies as possible. Then, focus will turn to the expected state of the framework at end of 2017, browsing the remaining tasks and giving an agenda. This includes at least these items, reviewed technically and logistically: integration with systemd (cgroup handling, tiny namespacing, ...), permission policy and enforcement, cryptography and PKI for domain protection.

Slideshow of the presentation at AGL AMM Winter 2017 Tokyo : [here]

Keeping user experience control is critical for every OEM. To enable an easy way to tailor UI and user experience, AGL in general and homescreen in particular should provide a clear separation in between business logic and graphic rendering. This talk propose a new homescreen architecture. In this new approach the homescreen is a platform service accessible through a set of normalized API. Every OEM/Tier1 should be able to easily reshape user experience by simply connecting a new UI on a platform provided homescreen service. The new architecture should support not only both HTML5 & QT user interface, but should also support multi-screens, multi-users, local & remote screens and obviously should implement security built in by design.

Download PDF presentation:  [here]

The hundreds of millions of cars on our roads every day is a unique source of highly valuable data. While technically, connected car already makes those data available outside the vehicle, this export raises serious questions on how to secure the process. Connected cars raise premium challenges for the integrity of vehicle global security.

Next generation of car will be connected and connected car will be attacked. They is absolutely no doubt about those two assertions, and AGL should prepare itself to face this reality. This presentation given during Tokyo AGL/AMM/2016 reviews major security challenges that Automotive Grade Linux should address and will expose some existing technical options to address them.

  • Application Framework
  • Security Model
  • Applications and Operating System Update
  • Secure Boot 

Download slides [here]

The document provides a feedback on lessons learned through the implementation of Tizen security framework in version 2 & 3. Tizen security framework mostly
relies on: Smack for rules and Cynara for privileges, completed by a mix of DBus,  application manager and security manager for the orchestration.

The document starts with an introduction of Tizen Security Model before presenting lessons learnt from its implementation. Reader interested in further information will find an annex with more details about Tizen security concepts, as well as a few  pointers to external references.

Download PDF [here]

Archived Publications