Fixing the index numbering

Fixing the index numbering for all documentation

Bug-AGL: [SPEC-4470]
Signed-off-by: Vinod Ahuja <vahuja@unomaha.edu>
Change-Id: I96b482a3ab598f0739c692e301de66c0553ba0e4
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/28118
Reviewed-by: Walt Miner <wminer@linuxfoundation.org>
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Tested-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>

1 files changed, 58 insertions, 0 deletions

diff --git a/docs/3_Architecture_Guides/2_Security_Blueprint/A_Secure_development.md b/docs/3_Architecture_Guides/2_Security_Blueprint/A_Secure_development.md
new file mode 100644
index 0000000..9cbe3b4
--- /dev/null
+++ b/docs/3_Architecture_Guides/2_Security_Blueprint/A_Secure_development.md
@@ -0,0 +1,58 @@
+---
+title: Secure development
+---
+
+In order to save a lot of time in code auditing, developers must follow coding
+guidelines.
+
+## Secure build
+
+### Kernel build
+
+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).
+
+Domain                  | Improvement
+----------------------- | ------------
+SecureDev-SecureBuild-1 | Add content.
+
+## App/Widget signatures
+
+Domain                 | Improvement
+---------------------- | ------------
+SecureDev-Signatures-1 | Add content.
+
+## Code audit
+
+These tools are used to check the correct implementation of functionalities and
+compliance with related good practices.
+
+- [Continuous Code Quality](https://www.sonarqube.org/).
+
+Domain                | Improvement
+--------------------- | -----------------------------------------------------
+SecureDev-CodeAudit-1 | Add CVE analyser.
+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).
+- [Flaw Finder](https://www.dwheeler.com/flawfinder/).
+
+- [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).
+
+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).
\ No newline at end of file