diff --git a/xml/source/snippets/offerte/en/methodology_code-audit.xml b/xml/source/snippets/offerte/en/methodology_code-audit.xml
index e86c7d1..18fe9ee 100644
--- a/xml/source/snippets/offerte/en/methodology_code-audit.xml
+++ b/xml/source/snippets/offerte/en/methodology_code-audit.xml
@@ -19,10 +19,10 @@
with the user and other systems. Having detailed documentation (manuals, flow charts, system
sequence diagrams, design documentation) at this stage is very helpful, as they aid the
understanding of the application
-
Comprehensive code reading
goals of the comprehensive code reading are:
- - to get an understanding of the whole code
- - identify adversary controlled inputs and trace their paths
- - identify issues
+ Comprehensive code reading
goals of the comprehensive code reading are:
+ - to get an understanding of the whole code
+ - identify adversary controlled inputs and trace their paths
+ - identify issues
Static analysis
Using the understanding we gained in the previous step, we will use static code analysis
to uncover any vulnerabilities. Static analysis means the specialist will analyze the code and
@@ -39,8 +39,11 @@
exploited by the specialist. This is usually done to confirm a vulnerability and as such
follows the result of the static analysis.
Fuzzing
-
Fuzz testing or Fuzzing is a software testing technique which in essence consists of finding implementation bugs using malformed/semi-malformed data injection in an automated fashion.
+
Fuzz testing or Fuzzing is a software testing technique which in essence consists of
+ finding implementation bugs using malformed/semi-malformed data injection in an automated
+ fashion.
Concolic analysis
-
If the specialist thinks it useful, additional concolic analysis may be performed on selected subsets of the code.
+
If the specialist thinks it useful, additional concolic analysis may be performed on
+ selected subsets of the code.