Skip to main content
Cybersecurity & DevSecOps

Protect the system through the way it operates.

Architecture, authorised testing and delivery controls grounded in the users, data and decisions inside the agreed scope.

The starting point is the system, its users, its data and the decision that needs protection.

Service directory

Security work with clear boundaries.

Choose the work closest to the decision in front of you. We agree the assets, people, data and release constraints before an engagement starts.

01 · Design

Security architecture

Review the system boundary, critical paths and priority controls before a platform or programme changes.

  • System boundary and critical paths
  • Priority controls
  • Prioritised findings
02 · Access

Zero Trust architecture

Shape practical identity, access and service boundaries for people, devices and connected systems.

  • Identity and roles
  • Devices and entry points
  • Service and data boundaries
03 · Test

Penetration testing

Run authorised testing with agreed rules, clear findings and an available retest after remediation.

  • Written authorisation
  • Rules of engagement
  • Report and retest
04 · Deliver

DevSecOps

Bring security checks, exception handling and release evidence into the way software is delivered.

  • Threat modelling and design review
  • Code, dependency and container controls
  • SBOMs, exceptions and metrics
Before work begins

The review starts with accountable scope.

Security work is not a promise that a system is risk-free. It is a defined review of agreed systems and controls, carried out with named client owners.

  1. 01Agree the boundaryIdentify the systems, environments, interfaces and business processes in scope. Record exclusions, testing windows and emergency contacts.
  2. 02Set access and data rulesAgree authorised access, data handling, evidence storage and the client contacts who can make decisions during the work.
  3. 03Review and prioritiseShare findings in a form technical and operating owners can use, separating immediate actions from design changes.
  4. 04Close the loopRecord the agreed remediation path, ownership and review date. Where testing is included, agree whether a focused retest is required.
  • No certification claim.An engagement reports what was reviewed, in which scope, at that time. It does not certify that a system is secure.
  • Authorisation first.Testing begins only with written authority from the asset owner, inside agreed systems, windows and rules.
  • Named owners decide.Client owners hold policy, risk acceptance and remediation authority throughout the engagement.
  • Evidence is handled carefully.Access, data handling, evidence storage and retention are agreed before work starts.

Every engagement is shaped around an agreed scope and a named set of delivery responsibilities. The final material may include an architecture or control review, prioritised findings, remediation guidance, a delivery plan and retest results where a retest is in scope. Read our Trust Center for the public overview of our delivery, privacy and AI controls. To report a website security concern, use the contact in security.txt.

Start with the scope

Discuss a security review.

Share the system, scope and assurance questions your team needs to resolve. We agree the boundary, rules and named owners before any security work begins.

What to bring

  1. 01The system in scopeWhat it does, who uses it and which data it holds.
  2. 02The assurance questionWhat a customer, board, auditor or regulator is asking you to show.
  3. 03The constraintsEnvironments, release windows and anything testing must not touch.
WhatsApp us