Revision of Architecture Guides
[AGL/documentation.git] / docs / 2_Architecture_Guides / 2_Security_Blueprint / 9_Secure_development.md
@@ -1,9 +1,7 @@
 ---
-title: Introduction
+title: Secure development
 ---
 
-# Part 9 - Secure development
-
 In order to save a lot of time in code auditing, developers must follow coding
 guidelines.
 
@@ -17,24 +15,16 @@ Tools like:
 - [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 -->
-
 Domain                  | Improvement
 ----------------------- | ------------
 SecureDev-SecureBuild-1 | Add content.
 
-<!-- end-section-todo -->
-
 ## App/Widget signatures
 
-<!-- section-todo -->
-
 Domain                 | Improvement
 ---------------------- | ------------
 SecureDev-Signatures-1 | Add content.
 
-<!-- end-section-todo -->
-
 ## Code audit
 
 These tools are used to check the correct implementation of functionalities and
@@ -42,15 +32,11 @@ compliance with related good practices.
 
 - [Continuous Code Quality](https://www.sonarqube.org/).
 
-<!-- section-todo -->
-
 Domain                | Improvement
 --------------------- | -----------------------------------------------------
 SecureDev-CodeAudit-1 | Add CVE analyser.
 SecureDev-CodeAudit-2 | [OSSTMM](http://www.isecom.org/mirror/OSSTMM.3.pdf).
 
-<!-- end-section-todo -->
-
 ### SATS
 
 - [RATS](https://github.com/andrew-d/rough-auditing-tool-for-security) (Maybe to
@@ -69,4 +55,4 @@ are depreciated and recognized as unsecured or cause problems.
 ### DATS
 
 - [wiki
-  list](https://en.wikipedia.org/wiki/Dynamic_program_analysis#Example_tools).
+  list](https://en.wikipedia.org/wiki/Dynamic_program_analysis#Example_tools).
\ No newline at end of file