5 # Part 9 - Secure development
7 In order to save a lot of time in code auditing, developers must follow coding
16 - [Code optimisation](https://github.com/jduck/lk-reducer).
17 - [Kernel Drivers test](https://github.com/ucsb-seclab/dr_checker) with
18 [docs](https://www.usenix.org/system/files/conference/usenixsecurity17/sec17-machiry.pdf).
23 ----------------------- | ------------
24 SecureDev-SecureBuild-1 | Add content.
26 <!-- end-section-todo -->
28 ## App/Widget signatures
33 ---------------------- | ------------
34 SecureDev-Signatures-1 | Add content.
36 <!-- end-section-todo -->
40 These tools are used to check the correct implementation of functionalities and
41 compliance with related good practices.
43 - [Continuous Code Quality](https://www.sonarqube.org/).
48 --------------------- | -----------------------------------------------------
49 SecureDev-CodeAudit-1 | Add CVE analyser.
50 SecureDev-CodeAudit-2 | [OSSTMM](http://www.isecom.org/mirror/OSSTMM.3.pdf).
52 <!-- end-section-todo -->
56 - [RATS](https://github.com/andrew-d/rough-auditing-tool-for-security) (Maybe to
58 - [Flaw Finder](https://www.dwheeler.com/flawfinder/).
61 list](https://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis).
64 approach](https://perso.univ-rennes1.fr/david.lubicz/planches/David_Pichardie.pdf).
66 It is necessary to verify that the application code does not use functions that
67 are depreciated and recognized as unsecured or cause problems.
72 list](https://en.wikipedia.org/wiki/Dynamic_program_analysis#Example_tools).