AGL Security Blueprint

Description

Create a blueprint for AGL security. What are the features that will be enforced and what are the limits of security within AGL. What security is provided for app developers "out of the box".

Architecture proposal from IoT.bzh was made at the All Member Meeting https://www.automotivelinux.org/sites/agl/files/pages/files/security-proposal-agl20-fulup.pdf

Previously we have released a security white paper which can be found at https://www.automotivelinux.org/automotive-grade-linux-security-white-paper

IoT.bzh has written a white paper on lessons learned from Tizen that can be found here. http://iot.bzh/download/public/2015/tizen-security-lessons-learnt-initial.pdf

Environment

None
100% Done
Loading...

relates to

Activity

Show:

Jan-Simon Moeller 
July 22, 2017 at 11:21 AM

Merged.

Hammad Ahmed 
July 17, 2017 at 1:21 PM

Fulup Ar Foll 
January 26, 2017 at 10:51 AM

It is clear that current Blueprint is far from being completed. Nevertheless as each new version of AGL will improve cybersecurity protection this work might never finish. As José noted as we have now the foundation for a blueprint in the documentation, it might be better to close this generic thread to open more dedicated item that would be easier to track and to map on next to come AGL releases.

Jose Bollo 
January 26, 2017 at 8:58 AM
(edited)

Many work was done (see http://docs.automotivelinux.org/docs/architecture/en/dev/). Can we close?

Walt Miner 
September 27, 2016 at 10:07 PM

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Priority

Epic Name

Created March 11, 2016 at 5:49 PM
Updated October 13, 2017 at 3:28 PM
Resolved July 22, 2017 at 11:21 AM