diff options
author | mudcam <v.nieutin@live.fr> | 2017-12-07 10:31:22 +0100 |
---|---|---|
committer | ronan [iot.bzh] <ronan.lemartret@iot.bzh> | 2017-12-07 12:52:16 +0100 |
commit | 981e9b9c4a40e248733d45cfedc6a512bdf95f5e (patch) | |
tree | 12526631368064d80c832d6bbf78b20af85c50f7 /security-blueprint/part-9 | |
parent | bc11e3eaceb629fbf5dee7ed7bfdf696839ddb12 (diff) |
Add proposal for new security blueprint
Diffstat (limited to 'security-blueprint/part-9')
-rw-r--r-- | security-blueprint/part-9/0_Abstract.md | 62 |
1 files changed, 62 insertions, 0 deletions
diff --git a/security-blueprint/part-9/0_Abstract.md b/security-blueprint/part-9/0_Abstract.md new file mode 100644 index 0000000..2dbc17b --- /dev/null +++ b/security-blueprint/part-9/0_Abstract.md @@ -0,0 +1,62 @@ +# 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). + +<!-- todo --> + +Domain | Improvement +----------------------- | ------------ +SecureDev-SecureBuild-1 | Add content. + +<!-- endtodo --> + +## App/Widget signatures + +<!-- todo --> + +Domain | Improvement +---------------------- | ------------ +SecureDev-Signatures-1 | Add content. + +<!-- endtodo --> + +## 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/). + +<!-- todo --> + +Domain | Improvement +--------------------- | ----------------------------------------------------- +SecureDev-CodeAudit-1 | Add CVE analyser. +SecureDev-CodeAudit-2 | [OSSTMM](http://www.isecom.org/mirror/OSSTMM.3.pdf). + +<!-- endtodo --> + +### 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). |