20 Nov 2026 By CISO Consulting team 14 views 5 min read

NCA CCC Responsibility Matrix: Provider or Tenant?

The NCA Cloud Cybersecurity Controls divide duties between the cloud provider and the tenant, and assessors ask tenants for evidence of their own half. This article shows how to build a per-control responsibility matrix, name the evidence for each side and prepare your team to defend it.

A compliance team around a table reviewing a printed control matrix beside a laptop showing a cloud dashboard.
In this article
  1. Why the split matters in an assessment
  2. Signs it is time to build the matrix
  3. Step 1: Define the scope
  4. Step 2: List the controls and assign ownership
  5. Step 3: Name the evidence each side supplies
  6. Step 4: Close the gaps
  7. Step 5: Review it as the environment changes
  8. What a good outcome looks like
  9. Training the team to defend it
  10. How the training is run
  11. Next step

Moving workloads to the cloud does not move accountability. The National Cybersecurity Authority (NCA) issues the Cloud Cybersecurity Controls (CCC), and they divide duties between the cloud service provider and the organization that uses the service, the tenant. An NCA CCC cloud cybersecurity controls responsibility matrix is the working document that records, control by control, who does what and what evidence each party can show. This article explains when you need one, how to build it and how to prepare your team to defend it.

Why the split matters in an assessment

A common assumption is that a provider with strong certifications covers the tenant's obligations. It does not. The provider answers for the controls it operates, such as the physical facility and the underlying platform. The tenant answers for what it configures and runs on top: identities, access rights, data classification, encryption key handling, logging, and the security of its own applications.

Assessors tend to ask the tenant for evidence of the tenant's half. A provider's attestation does not substitute for your access review records or your configuration baselines. Where the matrix is missing, teams often cannot say which side owns a control, and the discussion stalls.

Signs it is time to build the matrix

  • You are migrating workloads to a cloud provider and no one has mapped the controls to either party.
  • An NCA assessment or regulator review is approaching.
  • Different teams give different answers about who manages encryption keys, logging or backups.
  • Your evidence folders hold provider reports but little of your own configuration or review evidence.
  • You use several services, such as infrastructure, platform and software, and assume the split is identical across them.

Step 1: Define the scope

List each cloud service in use and its model: infrastructure, platform or software. The tenant's share grows as you move toward infrastructure and shrinks toward software, so each service needs its own column in the matrix. Note which services hold regulated or sensitive data, since these draw the closest attention.

Step 2: List the controls and assign ownership

Take the CCC control list by domain and assign each control one of three owners:

  1. Provider: the provider operates the control and you rely on it.
  2. Tenant: you operate the control entirely.
  3. Shared: both act, and each has a defined part.

Use the provider's documented responsibility statements and contract terms as the starting point, then confirm unclear items in writing. Avoid "shared" as a convenient label. If a control is shared, write down exactly what each side does.

Step 3: Name the evidence each side supplies

For every control, add two columns: the evidence the provider can supply and the evidence you must hold. Typical tenant evidence includes:

  • Access control lists and periodic access review records.
  • Configuration baselines and change records.
  • Log collection settings and alert handling records.
  • Data classification and encryption key management procedures.
  • Incident handling records that cover cloud events.
  • Backup and recovery test results.

Provider evidence usually takes the form of audit reports, certifications and contractual commitments. Record where each item is stored, who owns it and how often it is refreshed.

Step 4: Close the gaps

Rows where the tenant owns a control but holds no evidence are your gaps. Score them, assign an owner and a date, and track them like any other remediation item. Rows where you rely on the provider but cannot obtain evidence need a request to the provider, or a decision about whether the reliance is acceptable.

Step 5: Review it as the environment changes

The matrix is a living record. Review it when you adopt a new service, change a provider or alter how data flows. An out-of-date matrix is worse than none, because it gives false assurance.

What a good outcome looks like

A well-built matrix lets any team member answer three questions quickly: who owns this control, what proves it, and where is that proof. In an assessment, the lead can open the matrix, point to the tenant's rows and produce the evidence without searching. Gaps are already known and have owners and dates, so the conversation shifts from surprise to planned remediation.

Training the team to defend it

A matrix only helps if the people in the room can explain it. Assessors put questions to engineers, system owners and compliance staff, not only to the CISO. Each person should know the controls they own, the evidence that proves them and how to describe the provider's role without overstating it.

This is where training fits. Our SAMA & NCA Compliance Training covers what each domain asks for, what evidence proves it and how assessments run. The programme is built around the controls, the evidence and the auditor's questions, and it lists NCA CCC among its frameworks. Practical preparation includes rehearsing the questions an assessor is likely to ask of each role and agreeing consistent answers.

How the training is run

The engagement follows four steps.

  1. Scope: we agree the audience, level, language and dates.
  2. Prepare: we tailor examples and labs to your institution.
  3. Deliver: instructor-led sessions on site or online, with self-paced lessons where offered.
  4. Assess: quizzes or practical exercises, then certificates with CPE hours.

Sessions last from one to five days, on site or online. Learners receive a control-by-control guide and evidence checklist and a self-assessment workbook. The content includes a domain-by-domain walkthrough, the evidence an assessor expects for each control, self-assessment and maturity scoring, gap analysis and remediation planning, and preparation for regulator reviews and audits. Your team can use these materials to test and refine its own responsibility matrix during the programme.

Foundation level suits people new to the topic, Intermediate suits those who do the work, and Advanced suits leads and specialists. Levels can be mixed in one programme after a short skills check. On completion you receive a certificate with CPE hours and an evidence pack of attendance and results for your own audit.

Next step

If your cloud estate is growing and your team cannot yet say who owns each control, start with the matrix and then prepare the people who will defend it. To discuss a cohort or an on-site session for your staff, approach us about SAMA & NCA Compliance Training.

Tags: NCA CCC Cloud security GRC Shared responsibility Compliance training Saudi Arabia
Readiness self-check

How ready are you? Find out in two minutes

Answer a few questions for your framework. You get a score, your biggest gaps and — if you want it — a detailed assessment from our team.

Ready to talk about your compliance?

Tell us where you stand. We will show you the shortest path to what your regulator expects.

Regulatory updates in your inbox

SAMA, NCA and SDAIA changes and what they mean for your institution — once a month.

E-mails in

We confirm by e-mail; unsubscribe any time. Manage your subscription · Past issues

Schedule a Free Assessment