How an assessment runs
Every engagement follows the same four steps: agree the scope in writing, test under controlled conditions, report the evidence clearly, then support your team through the fixes and the retest.
Scope and written authorisation
We agree what may be tested: targets, exclusions, timing, escalation contacts, data handling, and stop conditions.
You authorise the work in writing before anything is touched, so every action stays inside agreed boundaries.
Controlled testing
Testing follows realistic attack paths, but we avoid destructive proof when safer evidence answers the same question.
Risk is separated from low-impact noise as the work happens, and the escalation contacts stay available for the whole test window.
Evidence and reporting
Material findings are written to reproduce and close: impact, proof, affected assets, reproduction steps, and a retest condition.
Critical and high findings are verified rather than closed by a ticket status change.
Fix path and retest
Your technical team gets a clear order of work instead of raw scanner output, so the highest-risk items are closed first.
Once fixes are in place we retest against the condition set in the report, and closure means the route is actually blocked.
Ready to scope an assessment?
Tell us what needs to be tested, when you need it by, and what the report has to support.