The agreed boundary
What was authorised, when it was tested and what was deliberately left out.
- Agreed scope and exclusions
- Test period and environments
- Named client contacts
Named assets, written authority, safe boundaries and findings that support a remediation decision.
We do not test systems outside the agreed scope, and a test does not certify that a system is secure.
No testing activity begins before written authorisation.
Written authorisation protects the client, its customers and the delivery team. It is required before any testing activity begins.
The final report is written for the people who have to act on it: technical owners, and the operating owners who decide what is fixed first.
What was authorised, when it was tested and what was deliberately left out.
Each finding explains why it matters, with evidence appropriate for the client audience.
Practical priorities, and a focused retest of the agreed fixes where it is included.
See the Trust Center for public control information. Security concerns about this website should be reported through security.txt.
Share the assets, the owner who can authorise the work and the constraints the test must respect. We agree the rules of engagement before any testing starts.
What to bring