The NCA ECC third-party and cloud controls sit within Domain 4 of ECC-2:2024. They cover third-party cybersecurity, cloud computing and hosting security. Government entities and CNI-linked organisations must apply relevant requirements. Suppliers face contractual obligations. CCC-2:2024 extends these requirements through separate controls for Cloud Service Providers (CSPs) and Cloud Service Tenants (CSTs).
Organisations responsible for vendor contracts, cloud procurement, or compliance can strengthen their implementation through the NCA ECC Course (Saudi Arabia). It helps teams understand applicable requirements and translate them into practical controls.
What Are the NCA ECC Third-Party and Cloud Controls?
The NCA ECC third-party and cloud controls address cybersecurity risks arising from external suppliers and cloud services. They require organisations to define, approve, implement and periodically review relevant security requirements.
Domain 4 applies alongside other relevant ECC requirements. Organisations must therefore assess the complete control environment rather than treating supplier security separately.
Where Domain 4 Sits in ECC-2:2024

The National Cybersecurity Authority (NCA) publishes the Essential Cybersecurity Controls (ECC) to strengthen cybersecurity across covered Saudi entities.
ECC-2:2024 contains four main domains, 28 subdomains, 108 main controls, ls and 92 subcontrols. Domain 4, titled Third-Party and Cloud Computing Cybersecurity, contains two subdomains:
-
Third-Party Cybersecurity (4-1): addresses risks from suppliers, outsourced IT, cybersecurity outsourcing, and managed services.
-
Cloud Computing and Hosting Cybersecurity (4-2): addresses security requirements for cloud and hosting services.
Together, these subdomains contain eight main controls and seven subcontrols. Each addresses a specific part of supplier or cloud security.
The revised framework also changed how it treats industrial control systems. That domain moved to the Operational Technology Cybersecurity Controls (OTCC). See NCA ECC vs OTCC for the distinction.
Organisations comparing the previous and current frameworks can review what changed in ECC-2:2024 before updating their control registers.
Why the NCA Targets Supply Chain and Cloud Risk
External providers may access sensitive information, operate business systems or support essential services. Their weaknesses can therefore affect the contracting organisation.
For example, a managed service provider might hold privileged access to production systems. A cloud platform might store confidential records. Weak contractual terms could leave incident reporting, data return or security responsibilities unclear.
Domain 4 addresses these exposures through documented requirements, risk assessments, contractual obligations and periodic reviews.
Its purpose is practical: organisations must establish security expectations before engagement and maintain oversight throughout the service relationship.
Who Must Comply?
ECC applies to Saudi government entities, their affiliated companies and entities, including those operating outside the Kingdom. It also applies to private sector entities that own, operate or host Critical National Infrastructure (CNI).
Suppliers to covered organisations are reached through relevant contractual cybersecurity requirements. They should therefore review customer obligations before accepting service agreements.
For further scope guidance, see who must comply with NCA ECC. ECC is mandatory for government and CNI-linked entities; NCNICC-1:2025 now sets baseline controls for other private entities, so check the NCA's official document for how it applies to you.
The NCA assesses compliance through self-assessment, periodic reports from its compliance tool, and/or field audit visits.
Third-Party Cybersecurity Controls (ECC 4-1)
Subdomain 4-1 covers supplier cybersecurity across the contractual relationship, including IT outsourcing, cybersecurity outsourcing and managed services.
Organisations should link procurement with cybersecurity risk management. Contract approval alone does not ensure ongoing supplier security.
Contractual Cybersecurity Clauses
Control 4-1-1 requires third-party cybersecurity requirements to be identified, documented and approved.
Control 4-1-2 sets minimum contractual provisions for agreements that could affect organisational data or services:
-
Confidentiality and data removal: Control 4.1.2.1 requires non-disclosure clauses and secure data removal at service end.
-
Incident communication: Control 4.1.2.2 requires procedures for reporting cybersecurity incidents.
-
Compliance obligations: Control 4.1.2.3 requires suppliers to follow applicable organisational, legislative and regulatory requirements.
Procurement, legal and cybersecurity teams should review these terms together to ensure commercial and security obligations align.
Vendor Risk Assessment Before Onboarding
Control 1-5-3-3 supports third-party risk assessment during service planning.
Control 4-1-3 requires organisations to assess cybersecurity risks and confirm mitigation controls before signing relevant outsourcing or managed-service contracts. Reassess when legislative or regulatory requirements change.
A practical assessment should consider:
-
Supplier access to systems and information.
-
Data sensitivity and classification.
-
Operational importance and dependencies.
-
Incident communication and recovery arrangements.
-
Availability of mitigation controls.
These are practical considerations, not an NCA-prescribed questionnaire. Document risks, mitigations, and approval decisions.
Control 4-1-3 also requires cybersecurity managed service centres used for remote monitoring and operations to be fully located in Saudi Arabia. Verify this before contract signature and consider subcontractor access arrangements.
Continuous Monitoring and Audits
Control 4-1-4 requires periodic review of third-party cybersecurity requirements.
Review frequency should reflect service criticality, risk, and applicable requirements. Useful activities include:
-
Reviewing supplier compliance with contractual obligations.
-
Tracking incidents, findings, and corrective actions.
-
Reassessing material service or access changes.
-
Confirming mitigation controls remain available.
-
Updating assessments when regulations change.
These activities demonstrate ongoing oversight and support renewal, remediation, or termination decisions.
Access Control, Least Privilege, MFA and Offboarding
Supplier access should follow applicable access-management requirements. Control 2-2-3 supports MFA, least privilege, need-to-know access, privileged access management, and periodic access reviews.
Assign access according to approved responsibilities, monitor privileged accounts, and remove unnecessary permissions.
Domain 4 has no separate third-party offboarding control. Combine secure data removal under control 4.1.2.1 with applicable access-revocation requirements under Domain 2.
At termination, confirm that:
-
Access rights and credentials are revoked where appropriate.
-
Organisational data is securely removed as required.
-
Required information is returned in an agreed usable format.
-
Remaining obligations and closure evidence are documented.
Cloud Computing and Hosting Controls (ECC 4-2)
Subdomain 4-2 covers cloud and hosting cybersecurity for current and planned services, including SaaS, PaaS and IaaS.
Control 4-2-1 requires cloud security requirements to be identified, documented, and approved. Control 4-2-2 requires implementation, while control 4-2-4 requires periodic review.
Assess cloud services alongside ECC Domains 1–3 and subdomain 4-1. The ECC-2:2024 official document provides detailed control wording.
Shared Responsibility (CST vs CSP)

The shared responsibility model divides security duties between the customer and cloud provider, depending on the service model and applicable controls.
A Cloud Service Provider (CSP) supplies cloud services; a Cloud Service Tenant (CST) uses them. A provider may manage infrastructure, while the customer manages permissions, data classification, io,n and configuration.
Document responsibilities before approving a cloud service. A responsibility matrix can cover:
|
Security area |
Questions to resolve |
|
Identity and access |
Who manages privileged accounts and MFA? |
|
Data protection |
Who classifies, encrypts and authorises access to data? |
|
Incident response |
Who detects incidents, reports them and coordinates response? |
|
Vulnerability management |
Who identifies, fixes and verifies vulnerabilities? |
|
Service termination |
Who exports data and confirms secure disposal? |
This matrix supports implementation but does not replace formal ECC and CCC controls.
Data Classification and Localisation (SDAIA/NDMO)
Control 4-2-3-1 requires providers to protect data according to classification and return it in a usable format at service end.
Classify data before selecting a hosting platform, then confirm the provider can meet the resulting requirements.
ECC-2:2024 removed the previous in-Kingdom hosting and storage requirement, directing entities to the National Data Management Office (NDMO) at SDAIA for localisation requirements. The SDAIA/NDMO data classification policy is a relevant reference, but verify the URL and applicable policy version before publication.
Coordinate localisation decisions with SDAIA/NDMO and consider other applicable Saudi regulations. Separately, the Communications, Space and Technology Commission (CST) regulates cloud service provision through its Cloud Computing Services Provisioning Regulations, including requirements for Saudi public-sector data and in-Kingdom storage, subject to legal exceptions.
Before approving a cloud service, confirm the data category, permitted hosting arrangements, and legal obligations.
Encryption at Rest and in Transit
Control 2-8-3-3 requires encryption in transit and at rest according to data classification. Control 2-8-3 also refers to the NCA National Cryptographic Standards.
Confirm how encryption applies to cloud workloads and data transfers, and clarify responsibility for encryption keys and access.
Practical review questions include:
-
Is sensitive data encrypted at rest and in transit?
-
Are encryption methods aligned with applicable NCA standards?
-
Who controls, retrieves, and manages encryption keys?
-
Are encryption settings reviewed when services or data classifications change?
Generic provider assurances are not enough to establish control implementation.
Tenant Separation and Data Return at Exit
Control 4-2-3-2 requires separation between the organisation’s environment and other customers’ environments, with particular attention to virtual servers.
Confirm the provider implements suitable tenant separation and protects data from unauthorised cross-tenant access.
Under control 4-2-3-1, providers must return organisational data in a usable format at service end. The exit plan should define format, transfer method, responsibilities and completion checks, aligning with contractual data removal under control 4-1-2-1 where applicable.
These arrangements reduce the risk of losing business information when changing providers and demonstrate that cloud exit requirements have been addressed.
Organisations preparing these controls can strengthen practical understanding through the NCA ECC Course (Saudi Arabia), supporting teams reviewing cloud requirements, supplier obligations and implementation evidence.
How CCC-2:2024 Builds on ECC for Cloud
The NCA Cloud Cybersecurity Controls (CCC-2:2024) extend ECC requirements specifically for cloud computing. They address both CSPs and CSTs.
The official CCC-2:2024 document sets out the applicable control requirements. Covered organisations should assess CCC alongside ECC rather than treating the two frameworks as alternatives.
CSP vs CST Control Sets
CCC-2:2024 contains four main domains and 24 subdomains. It separates requirements into provider and tenant control sets.
|
Control set |
Main controls |
Subcontrols |
|
CSP |
37 |
94 |
|
CST |
18 |
26 |
CSP controls address provider-side responsibilities. CST controls address customer-side responsibilities.
For example, CST control 1-3-T-1-1 addresses continuous compliance monitoring of a CSP against relevant laws and contractual clauses. CST control 2-6-T-1-1 addresses an exit strategy for secure data disposal.
Other tenant examples include MFA for privileged cloud users under 2-2-T-1-4 and a cloud service inventory under 2-1-T-1-1.
Provider examples include tenant data separation under 2-3-P-1-2. Control 2-12-P-1-6 addresses real-time incident reporting to the CST.
These examples show why the shared responsibility model needs documented ownership. A provider's obligations do not automatically discharge the tenant's obligations.
The CCC implementation guide for CSPs can help providers interpret and implement their applicable controls.
The 2024 Data Localisation Update
CCC-2:2024 was updated to reflect changes related to data localisation requirements. The NCA's change log records the deletion of specific localisation subcontrols.
The NCA states that localisation requirements are transferred to SDAIA/NDMO. Organisations should therefore consult the applicable data governance requirements before making hosting decisions.
This change does not mean localisation no longer matters. It means organisations must identify the relevant requirements from the appropriate regulatory sources.
Cloud tenants should also assess classification-based controls and any other applicable legal restrictions. Their decisions should reflect the data involved and the organisation's regulatory position.

ECC vs CCC at a Glance
|
Topic |
ECC-2:2024 |
CCC-2:2024 |
|
Purpose |
Baseline cybersecurity requirements |
Cloud-specific extension to ECC |
|
Who it covers |
Government and CNI-linked entities within scope |
Relevant CSTs and CSPs under the CCC scope |
|
Structure |
Four domains, 28 subdomains |
Four domains, 24 subdomains |
|
Shared responsibility |
Addresses entity and third-party obligations |
Separates provider and tenant controls |
|
Data localisation |
Refers entities to SDAIA/NDMO for applicable requirements |
Updated to reflect localisation changes |
|
Data classification levels |
Protects data according to applicable classification requirements |
Applies controls according to classification levels 1 to 4, with some controls optional at level 4 |
|
Third-party security |
Subdomain 4-1 |
Cloud-specific provider and tenant obligations |
|
Cloud exit |
Requires usable data return and relevant secure removal provisions |
Includes cloud exit strategy and data disposal requirements |
CSTs in scope must comply with both ECC and CCC. CSPs must also comply with both when covered, even if they fall outside ECC's own scope.
Organisations should check the applicable scope and control identifiers before building their compliance register.
Third-Party and Cloud Controls Checklist (ECC Implementation Guide)
Use this NCA ECC implementation guide checklist to organise practical implementation activities. It is a working aid, not an official NCA checklist or prescribed audit evidence list.
Before you onboard a vendor
-
Assess third-party risks when planning the service. Record findings and proposed mitigations. (Control 1-5-3-3)
-
For IT or cybersecurity outsourcing and managed services, assess cybersecurity risks before contract signature. Confirm mitigation controls are available. (Control 4-1-3)
-
Identify applicable cybersecurity requirements and obtain approval before engagement. (Control 4-1-1)
-
Classify relevant data and assess cloud requirements before choosing a hosting platform. (Controls 4-2-1 and 4-2-3-1)
Contract
-
Document and approve cybersecurity requirements in third-party agreements. (Control 4-1-1)
-
Include non-disclosure clauses and secure data removal at service end. (Control 4-1-2-1)
-
Define procedures for communicating cybersecurity incidents. (Control 4-1-2-2)
-
Require relevant organisational security policies and applicable legal requirements to be followed. (Control 4-1-2-3)
-
Confirm remote-access managed service centres used for monitoring and operations are fully located in Saudi Arabia. (Control 4-1-3-2)
While the service runs
-
Implement approved cloud and hosting security requirements. (Control 4-2-2)
-
Confirm providers protect data according to classification and separate tenant environments. (Controls 4-2-3-1 and 4-2-3-2)
-
Review supplier cybersecurity requirements periodically. Update assessments when relevant regulatory requirements change. (Controls 4-1-4 and 4-1-3-1)
-
Apply relevant access controls, including MFA, least privilege, and periodic access reviews. (Control 2-2-3)
At exit
-
Confirm organisational data is securely removed under applicable contractual requirements. (Control 4-1-2-1)
-
Verify cloud data is returned in a usable format. (Control 4-2-3-1)
-
Revoke unnecessary supplier access under applicable access-management controls. (Domain 2)
For supporting implementation material, consult the NCA's ECC implementation guide. Organisations can use the guide alongside their control register and risk assessments.
How Auditors Assess These Controls (NCA Audit)

The NCA does not publish a universal evidence list for these controls. However, a practical assessment can organise supporting material into three categories.
|
Evidence category |
Examples of supporting material |
|
Policy and approval |
Approved security requirements, supplier policies and cloud approvals |
|
Evidence of operation |
Risk assessments, signed contracts, access reviews and incident procedures |
|
Evidence of review |
Periodic review records, remediation tracking and updated assessments |
These categories are a practitioner framework, not an NCA-mandated evidence list. They align with the ECC pattern of requirements being identified, documented and approved, implemented, and periodically reviewed.
Auditors may examine whether the organisation can demonstrate that controls operate in practice. A signed policy alone may not show how responsibilities are managed.
Organisations can use the NCA's official implementation guidance to support this work. An internal NCA checklist should distinguish mandatory control wording from recommended evidence and local procedures.


