blob: 8004f5250b2aec551b02092786e07aa8be1a71ce (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
---
edit_link: ''
title: SOTA
origin_url: >-
https://raw.githubusercontent.com/automotive-grade-linux/docs-sources/master/docs/security-blueprint/part-8/2-SOTA.md
---
<!-- WARNING: This file is generated by fetch_docs.js using /home/boron/Documents/AGL/docs-webtemplate/site/_data/tocs/architecture/master/security_blueprint-security-blueprint-book.yml -->
# Software Over The Air
Software updates in connected vehicles are a very useful feature, which can
deliver significant benefits. If not implemented with security in mind,
software updates can incur serious vulnerabilities. Any software update system
must ensure that not only are the software updates to devices done in a secure way,
but also that the repositories and servers hosting these updates are adequately
protected. As the process of updating software migrates from a Dealership update model
towards an **OTA** update model, securing these processes becomes a high priority.
**SOTA** is made possible by **AppFw** (See Platform part). It will be possible
to manage in a simple way the packets (i.g. Android like).
<!-- section-todo -->
Domain | Improvement
------------- | -----------------
Update-SOTA-1 | Part to complete.
<!-- end-section-todo -->
|
