Simplified doc-site generation

[AGL/documentation.git] / docs / 1_Architecture_Guides / 1.2_Security_Blueprint / 8_Update_(Over_The_Air) / 1.2.8.2_Software_Over_The_Air.md

diff --git a/docs/1_Architecture_Guides/1.2_Security_Blueprint/8_Update_(Over_The_Air)/1.2.8.2_Software_Over_The_Air.md b/docs/1_Architecture_Guides/1.2_Security_Blueprint/8_Update_(Over_The_Air)/1.2.8.2_Software_Over_The_Air.md
new file mode 100644 (file)
index 0000000..8004f52
--- /dev/null
+++ b/docs/1_Architecture_Guides/1.2_Security_Blueprint/8_Update_(Over_The_Air)/1.2.8.2_Software_Over_The_Air.md
@@ -0,0 +1,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 -->