Methodology
How an assessment runs.
Five phases, the same for every engagement. Each one has a clear output, and nothing moves forward until the one before it is agreed.
- Phase 01
Scope & authorise
Before any testing, we agree in writing exactly what will be tested, when, how deeply, and by whom, and the owner of the systems signs to authorise it.
What happens
- An initial call to understand your systems, your concerns and why you want the assessment now.
- Agreement on the systems, environments, user roles and addresses in scope, and anything explicitly excluded.
- Agreement on testing windows, contacts for urgent issues and the limits we will work within on production.
- Confirmation that the person signing has the authority to permit testing, including for systems hosted by third parties.
You receive
- A written scope document.
- A signed authorisation from the system owner.
- A quote and an agreed timeline.
We need from you
- A description of the systems you want tested and the people who can answer questions about them.
- Signed authorisation from someone entitled to give it.
- Your NDA, if you would like us to sign one before scoping.
- Phase 02
Discover
We build an accurate picture of what is in scope: the hosts, applications, endpoints, user roles and data flows that make up your attack surface.
What happens
- Identifying the hosts and services reachable within the authorised ranges.
- Working through applications to map pages, functions, API endpoints and user roles.
- Reviewing documentation, API specifications or cloud account structure that you provide.
- Checking our picture against yours and raising anything that looks out of scope or unexpected.
You receive
- A confirmed list of the assets and functions to be tested.
- Early notice of anything significant we notice during discovery.
We need from you
- Test accounts for each role in scope, and access to the agreed environment.
- Any documentation that helps, such as API specifications or architecture notes.
- Phase 03
Test
Automated scanning and manual testing are carried out within the agreed scope, with every finding verified by hand before it is reported.
What happens
- Automated scanning to cover known vulnerability patterns quickly and consistently.
- Manual testing of access control, business logic, sessions and input handling, guided by the OWASP testing guides.
- Verification of each potential finding to remove false positives.
- Immediate contact with your named person if we find something critical or see any sign of service impact.
You receive
- Urgent notification of any critical finding, without waiting for the report.
- Verified findings with supporting evidence, ready for reporting.
We need from you
- A contact who can be reached during testing windows.
- Notice of any planned changes or deployments that could affect testing.
- Phase 04
Report
Findings are written up for two audiences, leadership and developers, rated by severity and likelihood, and walked through with your team.
What happens
- Writing an executive summary of overall exposure and the most important issues.
- Documenting each finding with its severity, evidence, steps to reproduce and specific fix guidance.
- Rating findings using CVSS where it applies, adjusted for likelihood and business impact in your context.
- A walkthrough call to explain findings and agree a fixing order.
You receive
- The full assessment report.
- A walkthrough call with your team.
- An agreed list of priorities for fixing.
We need from you
- The people who will make fixes, available for the walkthrough call.
- The names of everyone who should receive the report.
- Phase 05
Fix & verify
Your team makes the fixes, with our guidance where needed, and we retest each one and confirm in writing whether it is closed.
What happens
- Answering questions from your developers as they work through the fixes.
- Retesting each fixed issue using the same method that found it.
- Recording the status of every retested finding: closed, partly closed or still open.
- Deleting engagement data on request once the work is complete.
You receive
- A retest report confirming the status of each fixed finding.
- Written confirmation that can be shared with customers or auditors if you choose.
We need from you
- Notice when fixes are deployed and ready for retesting.
- Continued authorisation for the retest, covered by the original scope or an update to it.
Principles
How we work at every stage
Written authorisation first
No system is tested without a signed scope and authorisation from its owner. If we are unsure whether something is covered, we ask and wait.
Safety on live systems
We agree limits and windows for production, avoid destructive techniques, and stop and call you if anything looks at risk.
Verified, not just scanned
Every finding in a report has been checked by a person. Scanner output on its own is not a finding.
Written for the people who fix
Reports explain what to change and why, in terms your developers and administrators can act on directly.
Confidential by default
Findings go only to the people you name, and engagement data is deleted on request when the work ends.
Know where you stand
Tell us what you want tested. We will reply with a proposed scope, the authorisation we need, and a quote.
