NCA ECC vs SAMA CSF: Which Applies to Your App?
Who NCA's Essential Cybersecurity Controls and SAMA's Cyber Security Framework cover, where they overlap, and how to build one control matrix for both.
SAMA's Cyber Security Framework applies if your organization is regulated by the Saudi Central Bank, or if you build and operate software for an organization that is. NCA's Essential Cybersecurity Controls apply if you are a Saudi government entity, a company owned by one, or a private operator of critical national infrastructure, and they reach the vendors serving those organizations through contracts. A SAMA-licensed fintech answers to the CSF. A ministry portal answers to the ECC. A large bank can answer to both, and so can a software vendor whose clients span finance and government. Saudi Arabia's Personal Data Protection Law applies on top of either whenever personal data is processed. The two frameworks ask engineers to build many of the same controls, so the efficient approach is one control matrix mapped to every framework in scope, not two compliance projects run in parallel. This post covers who each framework reaches, where they overlap, and the questions to settle before any SAMA compliant software development or ECC work starts. We are engineers, not legal counsel, so confirm scope with your compliance team in writing.
SAMA CSF: Who It Covers and What It Asks
SAMA issued its Cyber Security Framework in 2017 for its member organizations, which the framework lists as banks, insurance and reinsurance companies, finance companies, credit bureaus and financial market infrastructure. A fintech holding any SAMA license should assume the framework applies until its compliance counsel says otherwise. The CSF is organized into four domains: cyber security leadership and governance, risk management and compliance, operations and technology, and third-party cyber security. It is assessed as maturity rather than as a pass or fail checklist, on a scale from 0 to 5, and member organizations are expected to reach at least level 3, where controls are defined, approved and implemented in a structured, formal way. For software teams, that level matters more than it sounds: a control that exists but isn't documented, owned and consistently applied does not reach level 3. The third-party domain is how the CSF reaches vendors. A bank that contracts you will flow its obligations into your contract and its security questionnaire, and its assessors may ask for your evidence as well as its own. Our SAMA compliance checklist covers the controls that most often catch app teams.
NCA ECC: Who It Covers and What It Asks
The National Cybersecurity Authority published the Essential Cybersecurity Controls in 2018 and released a revised edition in 2024. They apply to government organizations in the Kingdom, including ministries, authorities and the companies they own, and to private sector organizations that own, operate or host critical national infrastructure. The ECC is organized into five main domains: cybersecurity governance, cybersecurity defense, cybersecurity resilience, third-party and cloud computing cybersecurity, and industrial control systems cybersecurity. Where SAMA grades maturity, the ECC is closer to compliance against specific numbered controls. It is also a baseline rather than the whole picture. NCA publishes further control sets on top of it, including cloud cybersecurity controls for cloud providers and their tenants, and controls for systems an entity classifies as critical, and a government client may hold you to those as well. One ECC requirement shapes architecture early: its cloud controls expect the organization's data to be hosted and stored inside the Kingdom. If a vendor's default stack ships logs, backups or analytics events to a region abroad, that has to change before the first environment is built, not after the first assessment.
Where They Overlap, and Where They Differ
The overlap is large. Both frameworks expect a named owner for cybersecurity, an asset inventory, risk assessments, identity and access management with least privilege and controlled privileged access, logging and monitoring, vulnerability management and penetration testing, incident response, business continuity, and third-party risk management. An engineer implementing multi-factor authentication for administrators, append-only audit logs or managed key rotation is satisfying controls in both frameworks at once. The differences lie in scope, assessment style and emphasis. SAMA's audience is the financial sector, and the CSF sits alongside other SAMA requirements for regulated entities, such as business continuity, which your client's compliance team will apply together. The ECC reaches across government and critical infrastructure, includes an industrial control systems domain that most app teams never touch, and connects to the further NCA control sets described above. SAMA asks how mature each control is; the ECC asks whether each control is in place. In our experience, a system built with SAMA level 3 discipline already carries most of the engineering an ECC assessment looks for, and the remaining work tends to be mapping and documentation against the ECC's own control wording.
The PDPL Sits on Top of Both
Saudi Arabia's Personal Data Protection Law, supervised by the Saudi Data and Artificial Intelligence Authority, has been fully enforceable since September 2024. It applies to personal data in every sector, so a SAMA-regulated app and an ECC-scoped government portal both carry it. For engineering, the PDPL means a documented lawful basis for each kind of processing, support for data subject rights such as access and correction, a breach notification process, and restrictions on transferring personal data outside the Kingdom. That last point matters for any offshore team, including ours in Lahore. The pattern that works is to keep production personal data in-Kingdom, give engineers outside it masked or synthetic data for development and testing, and route any production access through a logged, approved session on in-Kingdom infrastructure. Designed this way from the start, the transfer question rarely comes up. Retrofitted later, every pipeline, backup job and support tool has to be checked for where its data goes.
One Control Matrix, Mapped to Each Framework
Running SAMA and ECC as separate projects produces two sets of documents describing the same firewall. Build one control matrix instead. Each row is a control as your system implements it, for example 'administrative access requires multi-factor authentication and is logged to append-only storage'. The columns record the framework references it satisfies (the CSF section, the ECC control number, the PDPL article where relevant), the owner, where the evidence comes from, and when it was last tested. Generate that evidence from the systems themselves: access reviews exported from the identity provider, deployment approvals recorded by the pipeline, key rotation logs from the key management service. When an assessor asks for proof, you query a system instead of assembling screenshots the night before. Our cybersecurity and compliance engagements for GCC clients build this matrix during design, so every sprint that touches authentication or data storage references the controls it satisfies.
Questions to Settle Before Architecture
- Is the client SAMA-licensed, government-owned, or a designated operator of critical national infrastructure? Get the answer from its compliance team in writing
- Which edition of the ECC does the contract reference, the 2018 controls or the 2024 revision?
- Which data sets contain personal data, and how does the client's data classification policy label each one?
- Which cloud provider and region will host each data set, and is that provider accepted for the classification?
- Will anyone outside the Kingdom touch production data? If so, through what controlled, logged path?
- Which additional NCA control sets, such as the cloud controls, does the client expect you to meet?
- Who on the client side signs off the control matrix, and how often is it reviewed?
Have a project that needs this kind of thinking applied to it?