the application. We could also find some spots where easy to find vulnerabilities
could be expected. However, looking at the source code was more effective,
especially when verifying that the \CMS{} \emph{passes} a requirement. Buggy code
-is easy to find. Bugless code is not.
+is easy to find. Bug-free code is not.
We have chosen to split the work by category of security requirements in
the OWASP Application Security Verification Standard. We set the goal to perform
% Initial approach
We were quickly set up and started to do each own parts of the audit by hand.
For each OWASP ASVS item specific to certain mechanisms (like login and input
-validation), we took the source code of the \CMS{} and follow the control
-flow to see if the application satisfies the security requirement. For more
+validation), we took the source code of the \CMS{} and followed the control
+flow to see if the application satisfied the security requirement. For more
general requirements, we could just look at the code that is responsible for
this requirement (like the \code{Response} class in the case of \HTTP{} security).
-When we had found that a requirement was not satisfied, we elaborate shortly
-and move on.
+When we had found that a requirement was not satisfied, we elaborated shortly
+and moved on.
This went well, because with five people the individual workload is just not
that big. Furthermore, finding vulnerabilities is a lot easier than verifying
When we finished the report, each of us reread the other parts to check
if things had been missed or reported incorrect. This may not have thorough, but
because in the end five pairs of eyes have read all verdicts, we trust that, in
-the end, we feel all verdicts are sufficiently checked.
+the end, all verdicts are sufficiently checked.
repositories / ssproject1617.git / blobdiff