fix markdown sec-blueprint

Signed-off-by: Ronan <ronan.lemartret@iot.bzh>

1 files changed, 32 insertions, 42 deletions

diff --git a/sec-blueprint/01-overview.md b/sec-blueprint/01-overview.md
index 9ee1670..c0134fb 100644
--- a/sec-blueprint/01-overview.md
+++ b/sec-blueprint/01-overview.md
@@ -16,34 +16,21 @@ layout: techdoc
 ## Introduction
 ### Abstract
 
+This document describes how it is possible to create reasonably secured connected cars using already available Open Source components.  
+The complexity attached to such project is clearly exposed for each step and may seem a quite heavy reading.  
+Fortunately ready made solutions are coming on the market (Open Source and Proprietary), enabling short cuts for many of us.
 
-This document describes how it is possible to create reasonably secured
-connected cars using already available Open Source components. The
-complexity attached to such project is clearly exposed for each step and
-may seem a quite heavy reading. Fortunately ready made solutions are
-coming on the market (Open Source and Proprietary), enabling short cuts
-for many of us.
-
-The documentation mostly focusses on the embedded side of the problem leaving the cloud
-components and manufacturing processes for further study.
+The documentation mostly focusses on the embedded side of the problem leaving the cloud components and manufacturing processes for further study.
 
 ### The risk is real
 
-Connected cars, to be accepted by users and keeping under control
-liability of the Automotive Industry will have to solve many issues
-ranging from physical, direct, and remote and indirect cloud attacks. A
-large section of unsolved technical security challenges, lies in car
-connectivity to user owned devices and well as to cloud.
-
-The Automotive Industry, by opposition to those operating in cloud and
-mobiles businesses, has little experience of security issues and no long
-return of experience. Proven solutions derived from the IT world are for
-most of them, inapplicable.
+Connected cars, to be accepted by users and keeping under control liability of the Automotive Industry will have to solve many issues ranging from physical, direct, and remote and indirect cloud attacks.  
+A large section of unsolved technical security challenges, lies in car connectivity to user owned devices and well as to cloud.  
+The Automotive Industry, by opposition to those operating in cloud and mobiles businesses, has little experience of security issues and no long return of experience.  
+Proven solutions derived from the IT world are for most of them, inapplicable.
 
-For many people the Cyber Security risk for the Automotive industry is
-still at best not understood and unfortunately more often, simply
-ignored. If the Fiat-Chrysler cyber car jacking has forced the industry
-to open their eyes, it is just a beginning.
+For many people the Cyber Security risk for the Automotive industry is still at best not understood and unfortunately more often, simply ignored.  
+If the Fiat-Chrysler cyber car jacking has forced the industry to open their eyes, it is just a beginning.
 
 -   24 Jul 2015 Hacking a radio in a car:  
     *"… the computer systems built into Fiat Chrysler cars: the flaw can
@@ -57,7 +44,7 @@ to open their eyes, it is just a beginning.
     ramsomware, or cyber terrorism using cars as weapon if nothing is
     done.  
 
-As malicious hackers or terrorists are smart and well organised, we know
+As malicious hackers or terrorists are smart and well organised, we know 
 that if we let them enter a system, even by a side door, they will work
 they way to the more juicy part of the system to monetise their work.
 
@@ -71,8 +58,8 @@ that tracking a mobile source will be more complex.
 ## Scope 
 Designing Connected cars without enabling a high level of security is
 not acceptable and will be soon a key market requirement for any
-respectable automotive company.
-AGL is aimaing at providing a reasonable level of security by default.
+respectable automotive company.  
+AGL is aimaing at providing a reasonable level of security by default.  
 The level of default security will evolve with the time and future releases to align with market expectations and needs.
 
 In order to converge on such an open question, we need to take
@@ -96,8 +83,8 @@ The assumptions selected are the following:
     run non attended.
 
 We can see that in such configuration, the base OS (kernel&middleware)
-represents a well guarded entry point for a malicious hacker. The
-combination of trusted boot, integrity enforcement and rootfs in ro,
+represents a well guarded entry point for a malicious hacker.  
+The combination of trusted boot, integrity enforcement and rootfs in ro,
 creates a set a garded walls to anyone, who would try to modify valid
 code on the product.
 
@@ -112,31 +99,34 @@ any compromised code.
 
 We will start by reducing the surface of attack by designing a product
 without open backdoors (e.g. cars drivers do not need a ssh connection
-nor tcpdump, so why to install the such development code on the image,
+nor tcpdump), so why to install the such development code on the image,
 and continue by reducing the capabilities which can be claimed by any
-code to the minimum required. This can be done by running the code with
-a non administrator’s user ID (non root) and by removing the unrequired
-capabilities and file access at code launch via Mandatory Access Control
-(MAC) and the Posix Capabilities.  
+code to the minimum required.  
+This can be done by running the code with a non administrator’s user ID 
+(non root) and by removing the unrequired capabilities and file access 
+at code launch via Mandatory Access Control (MAC) and the Posix Capabilities.  
 In the case of Smack, the general concept is to associate different
-label to specific code. As the MAC label cannot be changed by the
-process itself, it enables the security rules set to enforce the respect
-of the predefine code behaviour. Code with connects to the outside world
+label to specific code.  
+As the MAC label cannot be changed by theprocess itself, it enables the security rules set to enforce the respect
+of the predefine code behaviour.  
+Code with connects to the outside world
 by any mean, should first benefit of these special security
-configurations. The default policy should be good enough cover the
-security needs of most non connecting code.
+configurations.  
+The default policy should be good enough cover the security needs of most non connecting code.
 
 Once the surface of attack is reduced, you need to reduce possible
-damage when a malicious user will have found his way in. *Please
-remember that in security the question is not to know if someone will
+damage when a malicious user will have found his way in.  
+*Please remember that in security the question is not to know if someone will
 break in, but rather when, how you will detect it, and how to limit
 potential damages.*
 
 In this phase we will take care to limit options for a malicious user to
 move sideways and activate code that would help him to get more control
-over the system. We will pay a detailed attention to any code which can
+over the system.  
+We will pay a detailed attention to any code which can
 grant more privileges, change MAC label, create new user, install new
-Apps or update. Those types of code are normally called from a very
+Apps or update.  
+Those types of code are normally called from a very
 limited entry points in the system and once again the MAC system is your
 best friend when it comes to restrict activation from valid vector.