Added [in-progress] Developer Guides

[AGL/documentation.git] / docs / 2_Architecture_Guides / 2.2_Security_Blueprint / 9_Secure_development / 1.2.9.0_Abstract.md

diff --git a/docs/2_Architecture_Guides/2.2_Security_Blueprint/9_Secure_development/1.2.9.0_Abstract.md b/docs/2_Architecture_Guides/2.2_Security_Blueprint/9_Secure_development/1.2.9.0_Abstract.md
index ddc86a9..bfceefe 100644 (file)
--- a/docs/2_Architecture_Guides/2.2_Security_Blueprint/9_Secure_development/1.2.9.0_Abstract.md
+++ b/docs/2_Architecture_Guides/2.2_Security_Blueprint/9_Secure_development/1.2.9.0_Abstract.md
@@ -1,15 +1,11 @@
 ---
-edit_link: ''
 title: Introduction
-origin_url: >-
-  https://raw.githubusercontent.com/automotive-grade-linux/docs-sources/master/docs/security-blueprint/part-9/0_Abstract.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 -->
-
 # Part 9 - Secure development
 
-In order to save a lot of time in code auditing, developers must follow coding guidelines.
+In order to save a lot of time in code auditing, developers must follow coding
+guidelines.
 
 ## Secure build
 
@@ -18,7 +14,8 @@ In order to save a lot of time in code auditing, developers must follow coding g
 Tools like:
 
 - [Code optimisation](https://github.com/jduck/lk-reducer).
-- [Kernel Drivers test](https://github.com/ucsb-seclab/dr_checker) with [docs](https://www.usenix.org/system/files/conference/usenixsecurity17/sec17-machiry.pdf).
+- [Kernel Drivers test](https://github.com/ucsb-seclab/dr_checker) with
+  [docs](https://www.usenix.org/system/files/conference/usenixsecurity17/sec17-machiry.pdf).
 
 <!-- section-todo -->
 
@@ -56,16 +53,20 @@ SecureDev-CodeAudit-2 | [OSSTMM](http://www.isecom.org/mirror/OSSTMM.3.pdf).
 
 ### SATS
 
-- [RATS](https://github.com/andrew-d/rough-auditing-tool-for-security) (Maybe to old).
+- [RATS](https://github.com/andrew-d/rough-auditing-tool-for-security) (Maybe to
+  old).
 - [Flaw Finder](https://www.dwheeler.com/flawfinder/).
 
-- [wiki list](https://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis).
+- [wiki
+  list](https://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis).
 
-- [Mathematical approach](https://perso.univ-rennes1.fr/david.lubicz/planches/David_Pichardie.pdf).
+- [Mathematical
+  approach](https://perso.univ-rennes1.fr/david.lubicz/planches/David_Pichardie.pdf).
 
 It is necessary to verify that the application code does not use functions that
 are depreciated and recognized as unsecured or cause problems.
 
 ### DATS
 
-- [wiki list](https://en.wikipedia.org/wiki/Dynamic_program_analysis#Example_tools).
+- [wiki
+  list](https://en.wikipedia.org/wiki/Dynamic_program_analysis#Example_tools).