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

NCA CCC Cloud Security Training Checklist by Role

One generic cloud course rarely serves architects, engineers and auditors alike. This checklist maps NCA CCC topics to each role so you can set learning objectives and verify them the same day.

A small group of cloud and security professionals reviewing a checklist on a screen in a bright training room.
In this article
  1. How to use this checklist
  2. Group 1: Common ground for every role
  3. Group 2: Architects
  4. Group 3: Engineers
  5. Group 4: Compliance, risk and audit teams
  6. Group 5: Cloud leads and CISOs
  7. Turning the checklist into a plan
  8. How CISO Consulting can help

A single cloud course seldom fits everyone on a cloud programme. Architects decide where workloads sit, engineers configure them, and compliance teams must prove the result to an assessor. This NCA CCC cloud security training checklist maps the main topics of the National Cybersecurity Authority's Cloud Cybersecurity Controls (CCC) to each role, so you can set learning objectives and check them the same day.

Use it as a working document. For each item, ask the role owner to explain the point in their own words or show it in your environment. If they cannot, that is your learning objective.

How to use this checklist

  1. Pick the roles in scope: architects, engineers, compliance and audit staff, and any cloud leads.
  2. Walk through the common items first, then the role-specific groups.
  3. Mark each item as confident, partial or gap.
  4. Turn every partial or gap into a stated learning objective with a date.

Group 1: Common ground for every role

  1. Shared responsibility. Everyone should be able to say which controls the provider operates and which stay with your organization. Why it matters: most cloud failures come from assuming the provider handles something it does not.
  2. Where NCA CCC applies. Know which of your services are cloud services in scope and how CCC relates to the NCA Essential Cybersecurity Controls (ECC). Why it matters: scope errors lead to missing controls or wasted effort.
  3. Hosting location and data residency. Staff should know where data and backups may be hosted under NCA requirements. Why it matters: location is a design decision that is costly to reverse.
  4. Data classification. Each person should know how classification drives the choice of cloud service and protection. Why it matters: the right control depends on the data, not the platform.
  5. Escalation. Everyone should know how to report a cloud incident or suspected misconfiguration. Why it matters: early reports shorten exposure.

Same-day check: ask three people from different roles to name one control the provider owns and one your team owns. Matching answers show a shared model.

Group 2: Architects

Architects need the ability to design to the controls before anything is built.

  1. Landing zone and segmentation design. They should be able to explain how accounts, networks and environments are separated. Why it matters: structure is hard to fix once workloads depend on it.
  2. Hosting and residency decisions. They should choose regions and services with residency requirements in mind. Why it matters: a wrong region can breach requirements on day one.
  3. Identity architecture. They should design federation, role models and privileged access paths. Why it matters: identity is the main perimeter in cloud.
  4. Key management design. They should decide who holds keys, where, and how they rotate. Why it matters: key ownership defines real control over data.
  5. Third-party and provider assessment. They should know what to ask a cloud provider before selection. Why it matters: assurance starts before contract signature.
  6. Resilience and exit. They should plan for outage, recovery and migration away from a provider. Why it matters: dependency risk is easy to overlook.

Same-day check: ask an architect to sketch one planned workload and mark residency, identity and key decisions on it.

Group 3: Engineers

Engineers turn design into configuration, so their learning should be hands-on.

  1. Identity and access in practice. Least privilege, multi-factor authentication, and removal of unused access. Why it matters: excess permissions are a common route to compromise.
  2. Key and secrets handling. Rotation, storage and access to keys and secrets. Why it matters: exposed secrets bypass other controls.
  3. Secure network configuration. Security groups, private connectivity and exposure of management interfaces. Why it matters: one open rule can undo a sound design.
  4. Workload hardening. Images, containers, patching and configuration baselines. Why it matters: workloads drift without a baseline.
  5. Encryption in transit and at rest. Enabling and verifying it for each data store. Why it matters: it must be confirmed, not assumed.
  6. Logging and monitoring. What to log, where logs go and who reviews them. Why it matters: you cannot investigate what was never recorded.
  7. Cloud incident response. Containment steps specific to cloud resources. Why it matters: on-premises playbooks often do not translate.

Same-day check: ask an engineer to show one storage resource and demonstrate its access rules, encryption and logging.

Group 4: Compliance, risk and audit teams

These readers do not need to configure services, but they must understand them well enough to test and evidence them.

  1. Reading the control set. Map CCC requirements to your own policies and to ECC. Why it matters: duplicated or missing mappings slow every assessment.
  2. Evidence expectations. Know what proof each control needs, such as configuration exports, access reviews and logs. Why it matters: a control without evidence is treated as not implemented.
  3. Provider assurance. Know how to use provider reports and where they stop. Why it matters: provider attestations do not cover your side of shared responsibility.
  4. Asking technical questions. Be able to challenge an engineer on identity, encryption and logging. Why it matters: assurance depends on informed questions.
  5. Residency verification. Know how to confirm where data actually sits. Why it matters: policy statements are not proof.
  6. Exceptions and risk acceptance. Record deviations with owner, reason and expiry. Why it matters: unmanaged exceptions become permanent gaps.

Same-day check: pick one CCC requirement and ask compliance to name the evidence, its owner and where it is stored.

Group 5: Cloud leads and CISOs

  1. Decision rights. Be clear on who approves new cloud services and regions. Why it matters: unapproved services create shadow risk.
  2. Skills gaps by role. Record which groups above are weak. Why it matters: it lets you spend training effort where it counts.
  3. Level selection. Match foundation, intermediate and advanced content to people's actual work. Why it matters: mixed levels in one room waste time for everyone.
  4. Follow-up. Set a review date to confirm the learning shows up in configuration. Why it matters: training is only useful if practice changes.

Turning the checklist into a plan

Count the gaps by role and group. Cluster them into sessions: a short common session on shared responsibility and residency, then separate technical tracks for architects and engineers, and an evidence-focused track for compliance. Set an objective for each cluster in the form "after training, the engineer can show X" and keep the same-day check as your first assessment.

How CISO Consulting can help

Our Cloud Security Training is built for architects, engineers and compliance teams, and covers shared responsibility, identity, data protection and the NCA cloud controls. Delivery follows four steps: scope the audience, level, language and dates; tailor examples and labs to your institution; deliver instructor-led sessions on site or online; then assess with quizzes or practical exercises. Training runs from one to five days, on site or online.

Content includes shared responsibility and data residency requirements, identity, access and key management, secure network and workload configuration, logging, monitoring and cloud incident response, and mapping cloud controls to NCA CCC. You receive course materials and lab exercises, a cloud configuration review checklist, certificates with CPE hours, and a skills gap summary for your cloud team.

Levels can be mixed in one programme after a short skills check. Contact us to discuss your audience and plan the programme.

Tags: NCA CCC cloud security security training shared responsibility data residency GRC
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