Check your DPDP Readiness now!
Cybersecurity

NCA Cloud Cybersecurity Controls (CCC-2:2024): A Compliance Guide

Home

Compliance Hub

NCA Cloud Cybersecurity Controls (CCC-2:2024): A Compliance Guide

autoResilience

The Cloud Cybersecurity Controls (CCC) are the NCA's framework for securing cloud computing in Saudi Arabia. They extend the Essential Cybersecurity Controls (ECC) with cloud-specific requirements and apply to two groups: cloud service providers (CSPs) and cloud service tenants (CSTs), the organisations that use cloud services.

The current edition, CCC-2:2024, replaced CCC-1:2020. It was updated to reflect operational experience and alignment with ECC-2:2024, and follows the same four-domain structure. The NCA also publishes separate implementation guides for CSPs and CSTs.

Quick Answer

The Cloud Cybersecurity Controls (CCC) are the NCA's framework for securing cloud computing in Saudi Arabia. They extend the Essential Cybersecurity Controls (ECC) with cloud-specific requirements and apply to two groups: cloud service providers (CSPs) and cloud service tenants (CSTs), the organisations that use cloud services.

Key Takeaways
  • Establish cybersecurity governance, risk management and compliance for cloud services
  • Secure the cloud infrastructure, virtualisation and platforms, including segregation between tenants
  • Protect data and encryption keys, and manage identity, access and privileged accounts
  • Monitor, log and respond to incidents, and notify tenants as required
  • Meet hosting and data location expectations for the classification of data hosted

Overview

At a glance

ItemDetail
FrameworkCloud Cybersecurity Controls, CCC-2:2024
IssuerNational Cybersecurity Authority (NCA)
ReplacedCCC-1:2020
Relationship to ECCExtension: CCC applies in addition to ECC
TracksCloud service providers (CSPs) and cloud service tenants (CSTs)
GuidanceSeparate NCA implementation guides for CSPs and CSTs

What Is the NCA CCC?

CCC sets minimum cybersecurity requirements to reduce the risks of cloud computing for providers and their customers. Because it extends ECC, organisations implement ECC first and then add CCC requirements for their cloud services. Within the same domain structure, CSPs and CSTs each have their own set of controls, reflecting their different responsibilities.

Who Does It Apply To?

PopulationCCC role
Cloud service providers offering services to government entities and critical national infrastructure in Saudi ArabiaCSP controls
Government entities and CNI operators using cloud servicesCST controls
Other cloud usersEncouraged to adopt as good practice

Controls can differ by service model (IaaS, PaaS, SaaS) and by the sensitivity of the data and systems hosted.

Key Compliance Requirements

For cloud service providers

  • Establish cybersecurity governance, risk management and compliance for cloud services
  • Secure the cloud infrastructure, virtualisation and platforms, including segregation between tenants
  • Protect data and encryption keys, and manage identity, access and privileged accounts
  • Monitor, log and respond to incidents, and notify tenants as required
  • Meet hosting and data location expectations for the classification of data hosted
  • Support tenants with transparency, evidence and exit arrangements

For cloud service tenants

  • Classify data and choose cloud services that meet the required level
  • Define cybersecurity requirements in contracts with CSPs
  • Manage access, configuration and data protection on the tenant side
  • Monitor the provider's compliance and plan for continuity and exit

Key Areas Covered

DomainFocus
Cybersecurity GovernanceRoles, policies, risk, compliance for cloud services
Cybersecurity DefenceInfrastructure, access, data, encryption, monitoring
Cybersecurity ResilienceContinuity of cloud services
Third-Party CybersecuritySupply chain and outsourcing in cloud

Why It Matters

Saudi Vision 2030 is pushing government and enterprise workloads onto cloud. For providers, CCC alignment is effectively a prerequisite for serving government and critical-sector clients. For tenants, CCC turns cloud risk from a procurement question into a set of controls they must own.

The CSP and CST split is the key design point. Shared responsibility has to be written into contracts and evidenced on both sides, or gaps open between what the provider does and what the tenant assumes.

Penalties and Enforcement

The NCA monitors compliance with its controls through assessments and supervision, and cloud compliance is also enforced through government procurement and contractual requirements. Specific statutory penalties should be confirmed against current official texts.

  • National Cybersecurity Authority (NCA): the issuing authority
  • NCA Essential Cybersecurity Controls (ECC-2:2024): the baseline CCC extends
  • NCA Critical Systems Cybersecurity Controls (CSCC-1:2019): critical systems hosting
  • Saudi PDPL and SDAIA: personal data transfers and localisation
  • CST: cloud and ICT sector regulation

Frequently Asked Questions

What is the current version of the NCA CCC?

CCC-2:2024, which replaced CCC-1:2020.

Who must comply with the NCA CCC?

Cloud service providers serving government and critical infrastructure in Saudi Arabia, and government and critical-sector organisations that use cloud services.

How does CCC relate to ECC?

CCC is an extension of ECC. Organisations implement ECC and add CCC requirements for their cloud services.

What is the difference between CSP and CST controls?

CSP controls apply to providers of cloud services; CST controls apply to the organisations that use them. Each has its own control set within the same domains.

Does the NCA publish guidance on CCC?

Yes. It publishes separate implementation guides for CSPs and CSTs.

How autoResilience Supports CCC Compliance

CCC compliance depends on clear shared responsibility and ongoing evidence from both providers and tenants. autoResilience is an integrated Governance, Risk, Compliance and Resilience platform that helps organisations keep control libraries mapped to ECC and CCC, run cloud vendor assessments, manage contract requirements and track issues and corrective actions, with dashboards for the board. It supports cloud compliance programmes; it does not certify compliance.

See it in action

Get a 30-minute walkthrough of autoResilience with one of our experts β€” at no cost.

Book a Free Demo
autoResilience autoResilience autoResilience
πŸ‘‹ 30-Minute demo at Zero cost

Don't Wait for a Crisis

Start Today, Stay Secure Tomorrow!

Book a Demo
autoResilience