Skip to main content
Authorised penetration testing

Authorised penetration testing.

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.

Rules of engagement

Agree the test before the test starts.

Written authorisation protects the client, its customers and the delivery team. It is required before any testing activity begins.

  1. 01Set written authorityConfirm the asset owner, authorised systems, environments, dates, test window and named contacts for urgent decisions.
  2. 02Record safe boundariesAgree exclusions, rate limits, data handling, credentials, notification paths and the activities that are not permitted.
  3. 03Review agreed targetsAssess the approved application, API or infrastructure surface using a method appropriate to the scope and operating constraints.
  4. 04Report and retestProvide prioritised findings and remediation guidance. A focused retest can confirm the agreed fixes where it is included in scope.
What you receive

Findings that support a remediation decision.

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.

01 · Scope

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
02 · Findings

Findings with a risk rationale

Each finding explains why it matters, with evidence appropriate for the client audience.

  • Prioritised findings
  • Risk rationale
  • Supporting evidence
03 · Remediation

Remediation and retest

Practical priorities, and a focused retest of the agreed fixes where it is included.

  • Remediation priorities
  • Focused retest option
  • Retest scope stated in the result
  • Written authorisation first.Testing begins only with written authority from the asset owner, inside agreed systems, windows and rules.
  • Inside the boundary.We do not test systems outside the agreed scope, and activities that are not permitted are recorded before work starts.
  • No certification claim.A test reports what was reviewed, in which scope, at that time. It is not a certificate.
  • Retest results are specific.Any retest result identifies only the remediation items reviewed within the retest scope.

See the Trust Center for public control information. Security concerns about this website should be reported through security.txt.

Start with authority

Discuss an authorised test.

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

  1. 01The assets in scopeApplications, APIs or infrastructure, and the environments they run in.
  2. 02The asset ownerThe person who can give written authorisation for the test.
  3. 03The constraintsTest windows, exclusions and anything testing must not touch.
WhatsApp us