Controls · Cybersecurity · Saudi Arabia
NCA ECC compliance: the 108 Essential Cybersecurity Controls explained
NCA ECC compliance means meeting the Essential Cybersecurity Controls set by Saudi Arabia's National Cybersecurity Authority. The current edition, ECC-2:2024, has 4 domains, 28 subdomains and 108 controls, and applies to government organisations, critical national infrastructure operators and the companies that serve them.
What you need to know about NCA ECC
Who must comply with NCA ECC?
Government bodies, critical national infrastructure, and the organisations that serve them.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does NCA ECC require?
NCA ECC requires in-scope organisations to govern cybersecurity through an independent function and approved policies, defend their systems with technical controls, build cybersecurity into business continuity, and manage third-party and cloud risk.
Cybersecurity governance
10 subdomains: strategy, function, policies, risk, audit, HR, training.
In QULDEX: Governance evidence mappedCybersecurity defence
15 subdomains: access, systems, network, data, crypto, logs, incidents.
In QULDEX: Controls mapped to ISO 27001Resilience
Cybersecurity in business continuity.
In QULDEX: BCP evidence reusedThird-party and cloud
Supplier and cloud hosting security.
In QULDEX: Vendor registerPeriodic review
Independent reviews and NCA assessments.
In QULDEX: Audit workspaceWhich NCA ECC subdomains matter most?
These 24 subdomains carry most of the work, grouped by ECC-2:2024 domain. Select any subdomain to see what it asks for, typical evidence and the matching ISO 27001 control.
Showing up to 6 per group. Search, filter, or open a group to see all 24.
Governance 10
1-1Cybersecurity strategyDefine, document and approve a cybersecurity strategy aligned with the organisation's objectives and national requirements.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Approved strategy
- Maps to
- ISO 27001 5.1
1-2Cybersecurity managementSet up a cybersecurity function, independent from IT, led by a full-time, qualified Saudi national.
In QULDEXThe function, its head and its reporting line are on record.
- Typical evidence
- Organisation chart, appointment
- Maps to
- ISO 27001 5.3
1-3Policies and proceduresDocument, approve and publish cybersecurity policies and procedures, and review them periodically.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Approved policies
- Maps to
- ISO 27001 A.5.1
1-4Roles and responsibilitiesDefine and approve cybersecurity roles and responsibilities across the organisation.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- RACI
- Maps to
- ISO 27001 A.5.2
1-5Risk managementAssess and treat cybersecurity risks, including before new projects and major changes.
In QULDEXThe risk register holds assessments and treatments.
- Typical evidence
- Risk register
- Maps to
- ISO 27001 6.1
1-6Cybersecurity in IT projectsInclude cybersecurity requirements in project and change management, including secure development.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Project security reviews
- Maps to
- ISO 27001 A.5.8
1-7Compliance with laws and regulationsComply with national cybersecurity legislation and regulations.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Compliance register
- Maps to
- ISO 27001 A.5.31
1-8Periodical review and auditReview the implementation of cybersecurity controls periodically, independently of the cybersecurity function.
In QULDEXReviews run in the audit workspace with findings into CAPA.
- Typical evidence
- Review reports
- Maps to
- ISO 27001 9.2
1-9Cybersecurity in human resourcesAddress cybersecurity before, during and after employment.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Screening, NDAs
- Maps to
- ISO 27001 A.6.1–A.6.5
1-10Awareness and trainingRun awareness programmes and specialised training.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Training records
- Maps to
- ISO 27001 A.6.3
Defence 11
2-1Asset managementKeep an accurate, up-to-date inventory of information and technology assets.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Asset inventory
- Maps to
- ISO 27001 A.5.9
2-2Identity and access managementControl logical access with least privilege, MFA for remote and privileged access, and periodic reviews.
In QULDEXAccess reviews run as recurring tasks.
- Typical evidence
- Access reviews
- Maps to
- ISO 27001 A.5.15–A.5.18
2-3Systems and processing facilities protectionProtect systems and devices with malware protection, patching, hardening and secure configuration.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Hardening baselines
- Maps to
- ISO 27001 A.8.7–A.8.9
2-5Network security managementSegregate and protect networks, including internet browsing, wireless and DNS.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Network diagrams
- Maps to
- ISO 27001 A.8.20–A.8.22
2-7Data and information protectionProtect data according to its classification and applicable law.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Classification policy
- Maps to
- ISO 27001 A.5.12
2-8CryptographyUse cryptographic solutions according to national cryptographic standards.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Crypto standard
- Maps to
- ISO 27001 A.8.24
2-9Backup and recovery managementBack up data and systems and test restoration periodically.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Restore tests
- Maps to
- ISO 27001 A.8.13
2-10Vulnerability managementDetect and remediate technical vulnerabilities on time.
In QULDEXFindings become CAPA items with due dates.
- Typical evidence
- Scan reports
- Maps to
- ISO 27001 A.8.8
2-11Penetration testingRun penetration tests periodically on external services and critical systems.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Pen test reports
2-12Event logs and monitoringCollect, analyse and monitor security event logs, with defined retention.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- SIEM evidence
- Maps to
- ISO 27001 A.8.15–A.8.16
2-13Incident and threat managementDetect, respond to and report cybersecurity incidents, and use threat intelligence.
In QULDEXIncidents run with timers and NCA reporting records.
- Typical evidence
- Incident reports
- Maps to
- ISO 27001 A.5.24–A.5.26
Resilience 1
3-1Resilience in business continuityInclude cybersecurity in business continuity management and test it.
In QULDEXContinuity evidence is reused from ISO 22301.
- Typical evidence
- BCP tests
- Maps to
- ISO 22301
Third party and cloud 2
4-1Third-party cybersecurityAddress cybersecurity in contracts and relationships with third parties, including outsourcing.
In QULDEXEach third party is assessed and linked to its services.
- Typical evidence
- Third-party assessments
- Maps to
- ISO 27001 A.5.19–A.5.22
4-2Cloud computing and hostingData residencyMeet cybersecurity requirements for cloud and hosting, including hosting data in the Kingdom where required.
In QULDEXQULDEX gives this subdomain an owner, evidence requests and a review date, and maps it to ISO 27001 so one programme serves both.
- Typical evidence
- Cloud assessments
- Maps to
- ISO 27017
Nothing matches that search.
Subdomain numbers follow ECC-2:2024. Summaries are QULDEX paraphrases; the NCA document is the authority.
How do you comply with NCA ECC?
Confirm you are in scope, set up an independent cybersecurity function, close the gaps against the 108 controls and evidence them for NCA. Most organisations need 6 to 12 months, less with ISO 27001 in place.
Confirm scope
Check whether you are a government body, CNI operator or a supplier to one.
Set up the cybersecurity function
Independent from IT, led by a qualified Saudi national, with an approved strategy.
Gap assessment against ECC-2:2024
Assess all 108 controls, reusing ISO 27001 evidence.
Close the gaps
Policies, technical controls, logging, testing and third-party clauses.
Self-assessment and NCA review
Submit the self-assessment and support NCA audits with evidence.
Keep it current
PeriodicIndependent reviewYearlyPolicy and risk reviewOn changeRe-assess risk
Durations are QULDEX planning ranges.
Which documents does NCA ECC need?
Assessors ask for these records.
| Document | Subdomain | Where it lives in QULDEX |
|---|---|---|
| Cybersecurity strategy | 1-1 | Policy library |
| Function charter and head appointment | 1-2 | Policy library |
| Policies and procedures | 1-3 | Policy library |
| Risk assessments | 1-5 | Risk register |
| Periodic review reports | 1-8 | Audit workspace |
| Training records | 1-10 | Evidence vault |
| Asset inventory | 2-1 | Risk register |
| Access reviews | 2-2 | Evidence vault |
| Vulnerability and pen test reports | 2-10, 2-11 | CAPA automation |
| Incident reports | 2-13 | CAPA automation |
| Third-party and cloud assessments | 4-1, 4-2 | Vendor register |
Subdomain numbers follow ECC-2:2024.
How long does NCA ECC take and what drives the effort?
Most organisations need 6 to 12 months. The cybersecurity function, logging and third-party contracts usually take longest.
Where the time goes
Bars show the upper end of each range on one scale (12 months = full width).
What changes the effort
- Existing ISO 27001: covers much of Domain 2
- Saudization of leadership: the function head must be a Saudi national
- Third parties: contracts need cybersecurity clauses
- Cloud use: adds data residency and cloud controls
- Other NCA sets: CCC, DCC or OTCC may apply too
How ready are you for NCA ECC?
Check these eight things first. Nothing you enter leaves this page.
How NCA ECC maps to ISO 27001, SAMA CSF and the Saudi PDPL
ISO 27001 covers most ECC controls; SAMA CSF applies on top for financial institutions; the PDPL governs personal data. One control set can serve all of them.
Saudi crosswalk
| NCA ECC-2:2024 | ISO 27001:2022 | SAMA CSF | Saudi PDPL | Shared evidence |
|---|---|---|---|---|
| 1-2 Function | 5.3 | 3.1.2 Organisation | — | Appointments |
| 1-5 Risk management | 6.1 | 3.2.1 | Art. 19 security | Risk register |
| 2-2 Access | A.5.15–A.5.18 | 3.3.5 | — | Access reviews |
| 2-7 Data protection | A.5.12 | 3.3.8 | Data handling | Classification |
| 2-12 Logs | A.8.15 | 3.3.14 | — | Logs |
| 2-13 Incidents | A.5.24–A.5.26 | 3.3.15 | Breach notice | Incident reports |
| 4-1 Third parties | A.5.19–A.5.22 | 3.4 | Processor contracts | Vendor register |
Indicative mapping for planning; SAMA CSF and PDPL references are approximate section labels. The full crosswalk is in the QULDEX control library.
How QULDEX runs NCA ECC from scoping to NCA review
QULDEX is NCA ECC compliance and audit management software built from EGV Group's audit delivery, used by in-scope organisations, their advisors and the auditors who review them. Pick your role to see who does what.
For government bodies, CNI operators and suppliers.
- ScopeConfirm scopeScope and status record
- GovernSet the functionStrategy and appointments recorded
- DefendClose control gaps108 controls mapped to evidence
- Third partiesAssess suppliersVendor register with clauses
- ReviewRun periodic reviewsReview schedule
- ReportAnswer NCAControlled evidence sharing
For cybersecurity consultants and internal audit.
- ScopeRun the gap assessmentA reusable ECC-2 gap template
- GovernAdvise leadershipBoard-ready reports
- DefendReview evidenceReview and approval states
- Third partiesCheck contractsStatus per supplier
- ReviewIndependent reviewFindings per subdomain
- ReportPrepare the packAn audit-ready pack
For independent reviewers and NCA assessments.
- ScopePlanScope in a standard format
- GovernReview governanceView-only access to approvals
- DefendSample evidenceView-only evidence with download control and an access log
- Third partiesTestSupplier evidence on request
- ReviewAssessFindings into CAPA
- ReportReportTraceable assessment record
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →NCA ECC questions people ask
What is NCA ECC?
The Essential Cybersecurity Controls issued by Saudi Arabia's National Cybersecurity Authority. The current edition, ECC-2:2024, sets 108 controls in 4 domains for government organisations, critical national infrastructure and their suppliers.
What changed in ECC-2:2024?
The 2024 edition reorganises the controls into 4 domains, 28 subdomains and 108 controls with 92 subcontrols, and updates requirements on areas such as third-party and cloud security. Industrial control systems are covered by the separate OTCC.
Who must comply with NCA ECC?
Government organisations, critical national infrastructure operators, and private companies that own, operate or host critical systems or provide services to them.
Does ISO 27001 certification cover NCA ECC?
Much of it, but ECC adds Saudi-specific requirements, such as a cybersecurity function led by a qualified Saudi national and national cryptography and data hosting rules.
How does NCA ECC relate to SAMA CSF?
Financial institutions regulated by SAMA follow the SAMA Cyber Security Framework; where they are also in NCA scope, both apply and most evidence overlaps.
Go deeper on NCA ECC
GCC compliance topic hub
NCA ECC, SAMA CSF, UAE IAS and Gulf data protection laws.
blog.quldex.comAudit evidence naming convention
A file-naming scheme reviewers can follow.
blog.quldex.comAudit sampling size for compliance
How many samples auditors look at.
blog.quldex.comMajor vs minor nonconformity, with examples
How auditors grade findings.
References
- National Cybersecurity Authority, Essential Cybersecurity Controls ECC-2:2024. nca.gov.sa
- NCA, Essential Cybersecurity Controls ECC-1:2018 (superseded). nca.gov.sa
- NCA Cloud Cybersecurity Controls (CCC) and Data Cybersecurity Controls (DCC). nca.gov.sa
- ISO/IEC 27001:2022. iso.org
Reviewed by
Page history
- : Page first built on ECC-2:2024: subdomain explorer, readiness check and Saudi crosswalk
Find your NCA ECC gaps before the next review
Answer a short readiness check and get a gap summary by domain. No sales call needed to see the result.