How to use this report

Getting the most out of this report

• In order to present the issues correctly, we highlight the issues as we have seen them.

• We have also provided practical recommendations (at code level where possible) which need to be interpreted by the development team.

• As such the ‘findings’ section of the report is aimed primarily at the development team as they will be responsible for fixing the issues. We recommend that your lead developer reads this report and is actively involved in the project.

• The summary and next steps are written to guide the management and product owners to get an understanding of the situation and to recommend what to do next.

• Issues are split into “Resolved” and “Unresolved”. “Unresolved” issues are issues that still persist from the original audit.