- Market
- Saudi Arabia
- Written for
- CTO, CISO
- Decision
- Prepare a cloud service to carry Saudi-regulated workloads and answer customers' control questions
Cybersecurity credentials
NCA ECC
ECC compliance expertise
NCA registration
Registered cybersecurity service provider

ISO/IEC 27001
ISO/IEC 27001 certified
The split
Where the NCA's cloud controls place the line between provider and customer
The Authority's cloud control set addresses both sides of the service. Reading it as a provider means knowing, per layer, which controls are yours to run and which your customer will run on top of you — because your customers' assessors read it the same way.
| Stage | 01Facility and infrastructure | 02Platform and tenancy | 03Customer workload | 04Assurance |
|---|---|---|---|---|
| Moment | The physical sites, hardware and networks the service runs on. | The virtualisation, isolation and shared services between tenants. | The systems, identities and data the customer builds and operates. | The proof each side can produce that its half operates. |
| The provider carries | Physical security, hardware lifecycle, network infrastructure. | Tenant isolation, hypervisor security, platform hardening and patching. | The service interfaces and defaults the customer builds on. | Documentation and evidence of the provider-side controls. |
| The customer carries | Nothing directly — but it must satisfy itself the provider does. | Its tenancy configuration and the boundaries of what it deploys. | Identity, data classification, workload hardening, logging of its own systems. | Evidence of its own half — which is where your pack is cited. |
01
Facility and infrastructure
The physical sites, hardware and networks the service runs on.
- The provider carries
- Physical security, hardware lifecycle, network infrastructure.
- The customer carries
- Nothing directly — but it must satisfy itself the provider does.
02
Platform and tenancy
The virtualisation, isolation and shared services between tenants.
- The provider carries
- Tenant isolation, hypervisor security, platform hardening and patching.
- The customer carries
- Its tenancy configuration and the boundaries of what it deploys.
03
Customer workload
The systems, identities and data the customer builds and operates.
- The provider carries
- The service interfaces and defaults the customer builds on.
- The customer carries
- Identity, data classification, workload hardening, logging of its own systems.
04
Assurance
The proof each side can produce that its half operates.
- The provider carries
- Documentation and evidence of the provider-side controls.
- The customer carries
- Evidence of its own half — which is where your pack is cited.
A customer cannot close its own assessment without an account of your half. That is why the questionnaires arrive, and why one prepared answer beats fifty improvised ones.
The commercial reality
Why a regulated customer's assessment reaches into your platform
When a bank, a government entity or any organisation under the Authority's frameworks moves a workload onto your service, its obligations do not shrink to the part it still runs. Its assessor will ask how the underlying platform is secured, and the customer has only two possible answers: your documented, evidenced controls, or a shrug. Customers who foresee the shrug choose another provider — usually without telling you why.
This is the sense in which the cloud control set is commercial rather than merely regulatory for a provider. Nobody may ever assess you directly, and it will still decide which deals you can win, because every regulated prospect must account for you inside its own compliance file. Your control story is part of your product, priced into it whether you wrote it or not.
The efficient response is to treat customer assurance as a product surface: one written account of your half of the split per service, evidence generated by operating the platform rather than assembled per request, and a way to keep both current as the platform changes. The questionnaires do not stop arriving — they start taking hours instead of quarters.
The control story
Building a provider control story a customer's assessor can cite
The deliverable is not a certificate — it is a written, evidenced account of your half of the split that survives being read by a sceptical third party.
Read the cloud control set against your services
Each published control is placed on your side of the line, the customer's, or shared — per service, because an infrastructure offering and a managed platform split differently. The output is your responsibility matrix, in the Authority's vocabulary. A responsibility matrix per service, in the published controls' terms.
Implement and close the provider-side controls
Tenancy isolation, platform hardening, identity for your own operators, logging of the platform itself — engineered with your teams inside your change process, so the build produces its own records. Provider-side controls operating, with change records behind them.
Write the customer-facing account
The matrix and the controls become a document a prospect's security team can read without a meeting: what you carry, how it is evidenced, where their responsibility begins. Written once, versioned, and consistent across every deal. One assurance document that answers the recurring questionnaire.
Keep the story current as the platform moves
A control story dated last year raises more questions than it answers. Review triggers are wired to platform changes — a new region, a new service tier, a re-architecture — so the document ages with the platform, not against it. A living account, versioned with the platform it describes.
Our role
What we build with a cloud provider and what stays with the Authority
- 01
The reading
We work through the published cloud control set with your architects and map it to your actual services — because a split copied from a hyperscaler's whitepaper describes their platform, not yours.
- 02
The engineering
Provider-side controls are implemented hands-on with your platform teams, inside your environments and change process, so the capability and its records both stay with you when we leave.
- 03
The assurance surface
We draft the customer-facing account and the evidence index behind it, and install the review triggers that keep both current — so sales stops borrowing engineers to answer security questionnaires.
Whether your service satisfies the framework, and what any given customer must still do on top of it, are determinations that belong to the Authority's process and to each customer's own assessment — what we leave is a platform, a written split and evidence built to be read by both.
The National Cybersecurity Authority publishes the Cloud Cybersecurity Controls on its regulatory-documents pages. Work from the published text, and take applicability questions to the Authority rather than to any provider or consultancy — including us. Source
Common questions
What buyers ask
We are a Saudi cloud provider. Do the NCA cloud controls bind us or our customers?+
Read the published set and you will find it addresses the relationship, not one party: some controls describe what the provider side of the service must do, others what the customer must do on top of it, and several describe the split itself. Which obligations formally attach to your organisation is a question for the Authority and your own advisers against your specific situation. Commercially, though, the answer is simpler: your regulated customers must account for your half either way, so the provider-side controls are yours to run and to prove regardless of who is being assessed.
Our customers keep sending cloud security questionnaires. Can one prepared pack answer them all?+
Most of every questionnaire, yes — because the questions converge on the same underlying facts: how tenants are isolated, how the platform is patched, who among your staff can touch customer environments, what is logged and what a customer can obtain of it. A written account of your responsibility split with an evidence index behind it answers that recurring core in hours. What it does not remove is the tail each customer adds for its own regulator or its own risk appetite; the pack turns those from a full engagement into a short delta, which is the realistic best case.
We resell a hyperscaler's platform under our brand. Whose controls answer for the infrastructure?+
Both, in a chain — and your customers will read the whole chain. The hyperscaler documents its layers; you answer for everything you add on top: your management plane, your operators' access, your provisioning, your support processes, your tenancy design. The mistake resellers make is pointing at the upstream provider's published material as if it covered that middle layer. It does not, and a customer's assessor will notice the gap precisely because the upstream half is so well documented. Your control story is the part only you can write, and it is the part regulated customers actually need from you.
In this cluster
Next step
Prepare the provider control story
A provider whose responsibility split is written per service, whose controls are implemented behind it, and whose evidence answers the next customer questionnaire on day one.
Prepare the provider control story
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly
