Reading your executive summary

One of the two reports you receive is an executive summary — a plain-language account of the threats found, written to be read by anyone, not just a developer.

Use it to:

• Understand, in ordinary terms, what the risks are and what they could mean for your site and your users.
• Get a sense of how serious the findings are and where attention is most needed.
• Brief colleagues, management or clients who need to know the state of the site without wading through technical detail.

Think of the executive summary as the 'what and why', and the accompanying technical report as the 'how to fix'. Read the summary first to grasp the overall picture, then hand the technical report to whoever will carry out the fixes — or come back to us for a remediation quote if you would rather we did the work.