THE R4 APPROACH

A test with
a clear way forward.

Review. Report. Resolve. Repeat. A straightforward process that connects security findings to the work your team needs to do.

HOW AN ENGAGEMENT WORKS

Clarity at
every stage.

The scope, deliverables, timing and retest arrangements are agreed before we start.

Plan an assessment
01

REVIEW

Agree the scope. Test the real risks.

We define the systems, user roles and testing window, then assess the agreed scope with a black-box or grey-box approach.

02

REPORT

Evidence your team can act on.

You receive prioritised findings, their business impact, reproduction steps and practical remediation guidance.

03

RESOLVE

Work through the fixes.

Your developers or IT team make the changes. We can help explain findings and retest the fixes included in the engagement.

04

REPEAT

Keep pace with what changes.

New features and infrastructure changes can introduce new risks. We discuss when another assessment would be useful.

PREPARING FOR THE TEST

What we’ll need
from you.

The systems and the question

Application URLs, API endpoints or infrastructure ranges, plus the risks or business decisions you need to understand.

The right access and permission

Authorisation to test, relevant accounts and documentation, and a safe way to exchange any sensitive access details.

The timing and operational contacts

Your deadline, preferred testing window, production constraints and the people to contact if something needs attention.

LET’S TALK SECURITY

Have a release on the horizon?

Allow time for testing and fixes. Share your target date when we discuss the scope.

Discuss an assessment