Skip to main content

Guide

ISO 27001 for cloud and hosting providers: Protect the service traceably

ISMS for cloud and hosting providers: test responsibility boundaries, shared infrastructure and recovery using a specific service.

ISO 27001 for cloud and hosting providers: Protect the service traceably
Julian Köhn
|Read time: 3 minutes

A hosting provider can control its infrastructure without controlling every customer configuration. A useful ISMS explains this boundary clearly. Otherwise a certificate can imply more than the service scope actually assessed supports.

Use the responsibility table to define your service. Then test complete recovery and shared administration services supporting several customer services.

Describe the service, beyond the data centre

Define which services belong to scope: infrastructure, platform, operating system management, backup or support. Include outsourced services. ISO/IEC 27001 concerns the management system; the specific scope remains decisive.

Describe responsibility allocation so a customer can act on it. “Shared responsibility” is insufficient as a heading. Who configures access, who checks backups and who responds to misconfiguration?

Make shared dependencies visible

Identities, network control and management interfaces can affect many customer services at once. Assessing only individual virtual machines overlooks this concentration.

Trace the path from the customer service to central components. Who has privileged access? Which providers support operations? Our access control policy guide provides a practical starting point.

Connect recovery with the customer-facing claim

Fictional example: A database restores successfully, but the application remains disrupted because an external key or configuration is missing. Technical backup success does not yet answer the service recovery question.

Test a complete workflow. Record scope, data state, time needed and unresolved limitations. Evidence must support the statement you make to customers.

Record responsibility for each service

A blanket “the customer is responsible” is as unhelpful as an unlimited security promise. Record allocation for the service actually sold.

ServiceExample responsibility to clarify
Virtual infrastructureWho patches the guest operating system?
Managed databaseWho checks recovery and business data consistency?
Backup serviceWho defines scope, retention and restoration testing?
Support accessWho approves privileged access and its termination?

Answers differ by contract and operating model. Use the table as a questionnaire, rather than a prescribed allocation.

A shared control plane can undermine redundancy

Several hosts or locations offer little protection if the same inadequately protected administrative access can affect both. Treat central identities, key management and management interfaces as dependencies in their own right.

Kopexa’s information assets and asset graph help structure these relationships. A service-process BIA supports prioritisation. Testing should reveal which measure treats a central dependency and which evidence supports implementation.

This creates a more precise answer for customers: describe the assessed scope and suitable safeguards rather than saying generally that “our cloud is secure”. Customers can assess whether the statement applies to their purchased service.

Feed changes back into security work

A new subcontractor, changed platform component or different support access can affect assessments. Define a risk review trigger, rather than waiting only for the next annual date.

Suitable evidence can be reused for recurring customer assessments. Always check the period, service scope and permitted disclosure.

Test the connection in the product

Kopexa connects information assets and asset dependencies with risks, measures and evidence. Choose one service and follow a change through to reassessment. This shows whether your ISMS accompanies operations and bases certification preparation on dependable information.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

Does an ISO 27001 certificate automatically cover every customer configuration?

No. Scope and responsibility allocation determine coverage. Customers remain responsible for tasks assigned to them.

Sources

  1. ISO/IEC 27001 — ISO [Accessed ]