Responsibility

Trust needs
clear boundaries.

Security and service commitments become useful when their scope, owners and supporting evidence are clear.

Be specific about
what is protected.

Access

Identify who needs access, to which resources and for what purpose. Include changes to that access throughout the relationship.

Boundaries

Separate responsibilities for facilities, hardware, operating systems, applications and data. An agreement should make those boundaries visible.

Response

Define where an incident is reported, who takes responsibility and how the involved teams coordinate their response.

Recovery starts
with the business.

What needs to come back first? Which data can be recovered? Who confirms that the service is usable again? These questions shape a recovery plan before a failure occurs.

Backup arrangements, recovery objectives and the work required to restore service must refer to the particular environment. They should be reviewed when the application or operating model changes.

Read our recovery perspective

Ask for the evidence
that matters to your scope.

Which company provides the service?

The relevant operating business and contracting entity are identified in the proposed engagement. Group affiliation does not replace a clear service agreement.

How should certifications be assessed?

Check the named organisation, service, location, period and scope covered by the evidence. A supplier’s certification does not automatically apply to every company or service in the group.

Can a partner or investor request a closer review?

Use the contact form to identify the entity, relationship and information required. Document access and any confidentiality arrangements can then be agreed for that review.

Where should an existing service issue go?

Use the operating brand’s support channel so the team responsible for your environment can handle it. Group-level enquiries can be submitted here.

The next conversation

Make the scope clear.

Tell us which service, company or relationship you need to understand.

Request a discussion