docs/1_Architecture_Guides/1.2_Security_Blueprint/9_Secure_development/1.2.9.0_Abstract.md

   1 ---
   2 edit_link: ''
   3 title: Introduction
   4 origin_url: >-
   5   https://raw.githubusercontent.com/automotive-grade-linux/docs-sources/master/docs/security-blueprint/part-9/0_Abstract.md
   6 ---
   7
   8 <!-- WARNING: This file is generated by fetch_docs.js using /home/boron/Documents/AGL/docs-webtemplate/site/_data/tocs/architecture/master/security_blueprint-security-blueprint-book.yml -->
   9
  10 # Part 9 - Secure development
  11
  12 In order to save a lot of time in code auditing, developers must follow coding guidelines.
  13
  14 ## Secure build
  15
  16 ### Kernel build
  17
  18 Tools like:
  19
  20 - [Code optimisation](https://github.com/jduck/lk-reducer).
  21 - [Kernel Drivers test](https://github.com/ucsb-seclab/dr_checker) with [docs](https://www.usenix.org/system/files/conference/usenixsecurity17/sec17-machiry.pdf).
  22
  23 <!-- section-todo -->
  24
  25 Domain                  | Improvement
  26 ----------------------- | ------------
  27 SecureDev-SecureBuild-1 | Add content.
  28
  29 <!-- end-section-todo -->
  30
  31 ## App/Widget signatures
  32
  33 <!-- section-todo -->
  34
  35 Domain                 | Improvement
  36 ---------------------- | ------------
  37 SecureDev-Signatures-1 | Add content.
  38
  39 <!-- end-section-todo -->
  40
  41 ## Code audit
  42
  43 These tools are used to check the correct implementation of functionalities and
  44 compliance with related good practices.
  45
  46 - [Continuous Code Quality](https://www.sonarqube.org/).
  47
  48 <!-- section-todo -->
  49
  50 Domain                | Improvement
  51 --------------------- | -----------------------------------------------------
  52 SecureDev-CodeAudit-1 | Add CVE analyser.
  53 SecureDev-CodeAudit-2 | [OSSTMM](http://www.isecom.org/mirror/OSSTMM.3.pdf).
  54
  55 <!-- end-section-todo -->
  56
  57 ### SATS
  58
  59 - [RATS](https://github.com/andrew-d/rough-auditing-tool-for-security) (Maybe to old).
  60 - [Flaw Finder](https://www.dwheeler.com/flawfinder/).
  61
  62 - [wiki list](https://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis).
  63
  64 - [Mathematical approach](https://perso.univ-rennes1.fr/david.lubicz/planches/David_Pichardie.pdf).
  65
  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.
  68
  69 ### DATS
  70
  71 - [wiki list](https://en.wikipedia.org/wiki/Dynamic_program_analysis#Example_tools).