summaryrefslogtreecommitdiffstats
path: root/security-blueprint/part-9
diff options
context:
space:
mode:
authorStephane Desneux <stephane.desneux@iot.bzh>2018-10-16 13:10:46 +0200
committerStephane Desneux <stephane.desneux@iot.bzh>2018-10-16 13:13:14 +0200
commit0eba225fb27ec0b87bfa80361314fec5ab901caa (patch)
tree02baf13e25b4d8989dc25051ff7ce3256ffb7bbd /security-blueprint/part-9
parent536b42be464af2f29fc5061489821c8903a6690a (diff)
Import from docs-agl/docs
Change-Id: Id524561d87410e5463cddd123b30eb63d75b62bd Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
Diffstat (limited to 'security-blueprint/part-9')
-rw-r--r--security-blueprint/part-9/0_Abstract.md62
1 files changed, 0 insertions, 62 deletions
diff --git a/security-blueprint/part-9/0_Abstract.md b/security-blueprint/part-9/0_Abstract.md
deleted file mode 100644
index 25d3f35..0000000
--- a/security-blueprint/part-9/0_Abstract.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Part 9 - 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).
-
-<!-- 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
-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 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).