aboutsummaryrefslogtreecommitdiffstats
path: root/site/_posts/_2016-06-27-security-white-paper.md
diff options
context:
space:
mode:
Diffstat (limited to 'site/_posts/_2016-06-27-security-white-paper.md')
-rw-r--r--site/_posts/_2016-06-27-security-white-paper.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/site/_posts/_2016-06-27-security-white-paper.md b/site/_posts/_2016-06-27-security-white-paper.md
new file mode 100644
index 0000000..dcf9780
--- /dev/null
+++ b/site/_posts/_2016-06-27-security-white-paper.md
@@ -0,0 +1,18 @@
+---
+layout: post
+author:
+ name: Fulup Ar Foll
+ url: http://iot.bzh
+title: "Security White Paper"
+date: 2016-01-10 12:45:04
+categories: blog
+tags: security
+---
+
+Cars are expensive pieces of equipment, yet they represent a huge mass market.
+Adding Internet connectivity to previous elements generates perfect conditions for the growth of a viable business model on attacking “Connected Cars”. It is already well understood that cars will be connected and connected cars will be attacked. While it's still too early to predict with certainty how “Connected Cars” will be impacted by security flaws, making the assumption that a car should be at least as secure as a TV, a set-top-box or a smart phone should make sense to everyone.
+This white paper focuses on how Linux best practices security mechanisms
+that could be used today and within the next couple of years to make connected cars safer and more secure.
+<!--more-->
+Download in PDF [here](http://iot.bzh/download/public/2016/security/Linux-Automotive-Security-v10.pdf)
+