11 Nov 2026 By CISO Consulting team 29 views 5 min read

Board Questions on Cloud Migration Security and NCA

Directors often approve cloud business cases on cost and speed, then learn later who owned which control. These seven questions let a board test a proposal in one meeting and tell a sound answer from a reassuring one.

Board members around a table reviewing a cloud migration proposal on a presentation screen.
In this article
  1. 1. Who is responsible for each control, service by service?
  2. 2. Where will our data sit, and who has approved it?
  3. 3. Can we leave, and what would it cost to do so?
  4. 4. How quickly will we hear about an incident?
  5. 5. Who has checked this independently?
  6. 6. Is security built into the applications, or added afterwards?
  7. 7. What will it take to fix the gaps, and who funds it?
  8. How to read the answers
  9. What to fund and what to measure
  10. Where we can help

Cloud proposals reach the board with a clear story: lower cost, faster delivery, better resilience. What they often lack is a clear account of who is responsible for each security control once the workload moves. The seven board questions on cloud migration security and NCA below are designed to be put to management in a single meeting, and to help directors distinguish a sound answer from a merely reassuring one.

The regulator that matters most here is the National Cybersecurity Authority (NCA), whose Cloud Cybersecurity Controls set expectations for cloud service providers and for the organizations that use them. Sector regulators and data-protection obligations add to these. The board does not need to know the controls in detail. It needs to know that management does.

1. Who is responsible for each control, service by service?

Cloud providers secure their platform. The customer secures what it puts on it: configuration, identities, data, and often the applications. The split changes with each service model.

A sound answer is a written shared-responsibility matrix that names an owner on each side for every service in scope. A reassuring answer is "the provider is certified, so it is covered." Certification describes the provider's side only.

What to ask for: the matrix itself, with a named internal owner for every customer-side control.

2. Where will our data sit, and who has approved it?

Data location is a legal and regulatory question before it is a technical one. Directors should hear which data classes will move, in which locations they will be stored and processed, and which approvals are needed.

A sound answer lists data by classification, names the approvals sought or obtained, and confirms they were handled before migration began. A weak answer says residency will be "looked at during implementation." By then, data may already have moved.

3. Can we leave, and what would it cost to do so?

Exit rights are rarely discussed at approval and frequently regretted later. The board should ask how data and workloads would be retrieved, in what format, within what time, and at whose cost if the relationship ends or the provider fails.

Listen for specifics: contract terms on data return and deletion, a tested portability approach, and a view of how dependent the applications are on provider-specific services. If the answer is that exit is "unlikely to be needed," the question has not been answered.

4. How quickly will we hear about an incident?

Incidents at a provider can affect you before you know about them. Ask what the contract says about notification: who is told, how fast, in what detail, and whether logs and evidence will be available for investigation and for reporting to regulators.

Then ask the internal half: who receives the provider's notice, and does the incident response plan include the provider as a participant? A good answer references a rehearsed process. A reassuring answer references a clause nobody has tested.

5. Who has checked this independently?

Management's confidence is not assurance. The board should expect an independent assessment of the cloud environment against the NCA Cloud Cybersecurity Controls, and of the provider's own security model, before go-live and at intervals afterwards.

Ask who performed it, what they found, and what remains open. A sound answer includes findings and a plan. A report with no findings deserves a second look, not applause.

6. Is security built into the applications, or added afterwards?

A well-secured platform can still host a poorly built application. Ask how security is addressed in application design and delivery: whether threats are modelled before build, whether there is a secure development standard, and how configuration baselines are set and enforced.

The board is looking for evidence that security is part of the delivery process rather than a gate at the end that gets waived under schedule pressure.

7. What will it take to fix the gaps, and who funds it?

Every assessment finds gaps. The useful question is what happens next. Ask for a remediation roadmap with owners, priorities and dates, and confirm that the budget for it sits inside the business case rather than outside it.

A sound answer ties each gap to a funded action. A reassuring answer promises a "post-migration hardening phase" with no owner and no cost.

How to read the answers

Across all seven questions, the same pattern separates the two kinds of answer.

  • Sound answers are documented, name a person, and can be shown to the committee.
  • Reassuring answers rely on the provider's reputation, on certificates, or on intentions for later.
  • Sound answers describe what has been tested. Reassuring answers describe what is planned.

What to fund and what to measure

Fund the assessment, the responsibility matrix, the secure development practices and the remediation work as part of the migration, not as extras. Cutting them to protect the timeline moves the risk to a point where it is more expensive to fix.

For ongoing reporting, ask management for a short, regular set of measures:

  • Share of in-scope services with a completed responsibility matrix and named owners.
  • Open assessment findings, by severity, with dates for closure.
  • Data classes approved for each location, against data actually held there.
  • Date of the last tested exit and incident-notification exercise.

Trends in these measures tell a board more than a single assurance statement.

Where we can help

Our Cloud & Application Security service covers cloud security governance and assessment against the NCA Cloud Cybersecurity Controls, together with secure application practices. The work typically runs 4–8 weeks. Deliverables include a cloud security assessment report, a shared-responsibility matrix, a cloud security policy with baseline configuration standards, a secure development standard with threat models, and a remediation roadmap.

We define the shared-responsibility model for each service, and we address data residency and approvals before migration. We assess the major public cloud platforms and local cloud service providers, against the NCA controls and the provider's own security model.

If a cloud proposal is heading to your board or committee, these seven questions are a practical place to start, and we are glad to help management prepare answers the board can rely on.

Tags: Cloud security NCA Board governance Shared responsibility Cloud migration Data residency
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