ISO 27001 Scope for Data Centres in UAE, Malaysia, KSA, GCC and Worldwide — Colocation, Managed Services and Tenant Responsibilities
A customer asks whether its servers are covered by your data centre’s ISO 27001 certificate. Your team manages the building, power, cooling and physical access. The customer controls its operating systems and applications. Another supplier handles backups.
A useful answer starts with the certified organisation, services and locations. It then explains the responsibilities connecting the parties.
This guide helps data-centre operators prepare an ISO 27001 scope for colocation, managed hosting and related services. It includes illustrative scope statements and a responsibility matrix for discussion before certification or a scope review.
Start With the Operator’s Services and Management System
ISO/IEC 27001 concerns an information security management system, or ISMS. For a data centre, scope definition needs to reflect the activities being managed and the information-security risks associated with them. ISO/IEC 27001 overview
Prepare a service inventory before drafting the scope wording.
-
Colocation space, racks or private cages.
-
Physical access and visitor management.
-
Power, cooling and environmental monitoring.
-
Cross-connect or network services actually provided.
-
Remote-hands services.
-
Managed servers, operating systems or backup services where contracted.
-
Supporting operations, security monitoring and customer administration.
Record which legal entity delivers each service, the locations involved and the relevant external providers.
A tenant’s environment connects to the operator’s services through identified interfaces. A tenant pursuing certification defines its own ISMS scope and assesses its responsibilities.
Distinguish Colocation From Managed Services
A colocation arrangement may give the customer control of its equipment and workloads while the operator manages the facility services described in the contract.
Managed services introduce additional activities. These could include server administration, patching, backup operation or security monitoring. The scope review should establish which of those activities the operator actually performs.
For each service, ask three questions.
-
What does our organisation deliver?
-
What does another party deliver or control?
-
What information, access or decisions pass between us?
Record the answers against the actual service agreement. ISO/IEC 27017 provides cloud-specific guidance on allocating responsibilities between providers and customers. Use that guidance where cloud services form part of the arrangement. ISO/IEC 27017 overview
For broader cloud-control guidance, refer to the existing SCS article. Cloud security and responsibilities in UAE
Map the Dependencies Around Your Scope
Ownership of a building, system or asset is useful information, but the scope review also needs to examine who operates it and how the service depends on it.
A landlord may maintain part of the building. An external contractor may service the UPS. A regional team may administer the access-control system from another country.
Identify the interfaces, responsible contacts and evidence available for review. ISO’s auditing-practices note recognises that an organisation can rely on processes performed by external suppliers or other parts of a larger organisation. Those relationships need appropriate treatment within the ISMS. ISO auditing-practices note
Include supporting functions such as procurement, human resources, IT administration and incident coordination where they affect the scoped operation.
Sample ISO 27001 Scope Statements for Data Centres
The statements below are illustrative drafts. Adapt the entity, services, facilities and supporting functions to the actual operation. The certification body reviews the proposed certification scope and documentation.
Example 1 — Colocation and Remote Hands
“The management of information security supporting the provision of colocation and remote-hands services at [named facility and address], including facilities operations, physical access management, customer service and the management of relevant external providers.”
Use this example to identify the services the operator performs. Keep the underlying service inventory available to explain what remote hands includes.
Example 2 — Colocation With Managed Hosting
“The management of information security supporting colocation and managed hosting services provided by [legal entity] at [named facilities], including facilities operations, contracted server administration, backup operations, service monitoring and supporting management functions.”
Retain the service descriptions and contracts showing which administration and backup activities are included.
Example 3 — UAE and Malaysia Operations With Central Support
“The management of information security supporting colocation and [specified managed services] delivered by [identified entity or entities] at [listed UAE and Malaysia facilities], including central operations coordination, security monitoring and relevant supporting functions.”
Prepare a site schedule and organisation chart alongside this wording. They should explain management authority, shared functions and differences between the facilities.
Example Operator–Tenant Responsibility Matrix
This is an illustrative allocation worksheet. Confirm the actual responsibilities in the service agreements, risk assessment and operating procedures. Each activity needs an accountable owner and a clear handover.
| Activity | Example colocation operator responsibility | Example tenant responsibility | If a managed service is added |
|---|---|---|---|
| Facility access | Operate agreed entry and visitor controls | Authorise its personnel and report access changes | Define any delegated approval arrangements |
| Rack or cage access | Maintain the agreed access mechanism and records | Maintain its approved access list | Identify who controls provider access |
| Power and cooling | Deliver and monitor contracted facility services | Communicate relevant equipment and load information | Record dependencies affecting the managed service |
| Network boundary | Identify operator-provided connections and demarcation points | Manage tenant-controlled network equipment | Specify routing, firewall and administration duties |
| Operating-system access | Protect operator-controlled systems | Administer tenant-controlled systems | Identify systems administered by the provider |
| Monitoring | Monitor agreed facility and operator-system events | Monitor its workloads and applications | Define additional monitoring and escalation coverage |
| Backup | Maintain relevant operator records and configurations | Arrange protection of its workloads | Specify backup scope, retention and recovery responsibilities |
| Incident coordination | Assess and communicate incidents affecting its services | Assess effects on its business and systems | Agree notification contacts and escalation responsibilities |
| Equipment removal | Apply agreed release and access procedures | Authorise collection and manage its equipment | Define any contracted data-handling or disposal tasks |
Review the matrix with facilities, operations, security, customer-service and relevant tenant representatives. Keep evidence of unresolved questions and the decisions made.
ISO 27001 Data Centre Scope in UAE
For a UAE operation, identify the licensed entity, named facilities and services proposed for certification.
A Dubai colocation facility may receive central support from another office, while an Abu Dhabi location has a different managed-service offering. The scope pack should show those differences.
-
List the facilities and supporting teams involved.
-
Distinguish existing services from proposed additions.
-
Record relevant customer conditions concerning location and service coverage.
The existing SCS service page provides the broader certification enquiry route. Data-centre and cloud-provider certification services · ISO 27001 guidance for UAE
ISO 27001 Data Centre Scope in Malaysia
For a Malaysian operation, map each facility and the services delivered there before deciding how the scope should be described.
For example, a Johor colocation facility may receive administration or security support from a team in Kuala Lumpur. Record the team’s authority, system access and responsibilities within the proposed arrangement.
-
Identify facilities, entities and central support locations.
-
Describe differences between colocation and managed-service contracts.
-
Confirm responsibility for outsourced maintenance and remote administration.
Use the actual operating structure when requesting a scope review. ISO 27001 guidance for Malaysia
ISO 27001 Data Centre Scope in Saudi Arabia
A Saudi data-centre operator should identify the named facilities and the teams controlling operations, access and customer services.
If a regional operations team supports facilities in other countries, show the connection in the organisation chart and responsibility matrix. Record any customer condition that affects the proposed site or service coverage. ISO 27001 guidance for Saudi Arabia
ISO 27001 Data Centre Scope in Other GCC Countries
For a GCC group, prepare one service-and-site register. Give each facility a country, legal entity, service description and operational owner.
Oman
Describe the services delivered at each Omani facility and the external providers supporting them. Identify any customer systems administered by a separate managed-service team. ISO 27001 guidance for Oman
Qatar
Show the interfaces between facility operations, customer equipment and network providers. Keep the service descriptions available when discussing the proposed scope. ISO 27001 guidance for Qatar
Kuwait
If facilities offer different services, record those differences by site. A shared group name should be supported by a clear description of management and operational responsibilities. ISO 27001 guidance for Kuwait
Bahrain
Identify responsibility for contracted services, shared infrastructure and remote support. Keep customer approval and incident-contact arrangements aligned with those responsibilities. ISO 27001 guidance for Bahrain
ISO 27001 Data Centre Scope in Canada
A Canadian operator should distinguish the facilities covered by the proposed arrangement and the services delivered at each.
Where customers or support teams operate across the US border or elsewhere, describe the relevant access, information flows and operational decisions. Confirm the site and service coverage stated in customer-facing certification documents. ISO 27001 guidance for Canada
ISO 27001 Data Centre Scope in Singapore
For a Singapore business coordinating regional facilities, identify the functions performed centrally and those delivered locally.
Explain who authorises access, administers operator systems and coordinates incidents. Where a Singapore team supports UAE or Malaysian facilities, show that relationship in the scope pack. ISO 27001 guidance for Singapore
ISO 27001 Data Centre Scope in India
An Indian operation should map its facilities, central support teams and contracted services. Where an operations or security team supports overseas locations, identify its authority and the systems it accesses.
Keep the scope proposal consistent with the service catalogue and supporting organisation chart. ISO 27001 guidance for India
ISO 27001 Data Centre Scope in the United Kingdom
A UK organisation should identify the entity operating the service, the named facilities and any regional support functions.
If the service uses third-party colocation, document the hosting relationship and the responsibilities retained by the organisation seeking certification. SCS United Kingdom contact information
ISO 27001 Data Centre Scope in the United States
Define a data centre’s ISO 27001 scope using illustrative scope statements, an operator–tenant responsibility matrix and practical guidance for UAE, Malaysia and worldwide operations.
SCS United States contact information
ISO 27001 Scope for Worldwide Data-Centre Operations
Define a data centre’s ISO 27001 scope using illustrative scope statements, an operator–tenant responsibility matrix and practical guidance for UAE, Malaysia and worldwide operations.
SCS international offices and enquiries
Prepare the Scope Review Pack
Bring together the following records.
-
Proposed scope statement and named legal entities.
-
Facility and support-location schedule.
-
Service catalogue and representative agreements.
-
Responsibility matrix with unresolved items identified.
-
Diagram showing operational and supplier interfaces.
-
Relevant risk assessment and control-applicability decisions.
-
Current certificate, where certification already exists.
The scope defines the ISMS boundary. The Statement of Applicability records necessary control decisions within the organisation’s approach. Keep the two consistent as services and responsibilities change. ISO auditing-practices note on the Statement of Applicability
For broader assessment preparation, use the existing evidence guide. SCS ISO 27001 audit evidence guide
Discuss Your Data Centre’s ISO 27001 Scope With SCS
Send SCS your proposed services, legal entity, facility locations and responsibility matrix. Identify whether you provide colocation, managed services or a combination.
For UAE and Malaysia operations, include the central support functions and cross-country interfaces. If a certificate already exists, attach it and explain the intended change.
SCS can review the enquiry and discuss the applicable certification arrangements for the proposed scope.
Need ISO 27001 Certification for Your Business?
Speak with our certification specialists to understand certification requirements, audit process, implementation timelines and accredited certification services.
Frequently Asked Questions
These examples require adaptation to the actual organisation and service agreements. ISO/IEC 27001 overview · ISO/IEC 27017 cloud-security guidance