How to read a test report
What a report should contain and how to tell whether it is useful.
home / resources
resources
Practical material written for people who have to decide, buy or read a security test.
what they are for
A penetration test is only useful if whoever commissions it knows what to ask for and how to read the result. These guides explain what a good report looks like, which checks to run before starting and how to write the authorised scope.
They are written for IT managers, software houses, compliance consultants and DPOs: anyone who has to decide on, buy or present a test to a client, an auditor or a tender.
What a report should contain and how to tell whether it is useful.
Ten checks to do before ordering a test.
Domain, roles, time window and prohibitions, written well.