Governance built for government entities in Saudi Arabia
Ministries, authorities, and agencies do not answer to one regulator. Govrly holds the NCA, SDAIA, NDMO, and DGA obligations in a single connected system — so one control, one owner, and one piece of evidence serve every authority that asks.
This page describes how we approach this work and how Govrly supports it. Where regulatory requirements are mentioned, confirm what applies to your organisation against the source documents published by the relevant authority.
What compliance applies to government entities in Saudi Arabia?
From the compliance programmes we build and run in Saudi Arabia: government entities in Saudi Arabia carry obligations from several authorities at once. The NCA sets cybersecurity requirements through the Essential Cybersecurity Controls (ECC-2:2024) and its specialised overlays. SDAIA enforces the Personal Data Protection Law. NDMO issues national data governance standards directed at government data. The DGA sets digital government policy. These stack rather than substitute.
This is the defining operational fact for a public-sector compliance team, and it is the reason spreadsheets stop working. A single access control decision sits inside an ECC requirement, an NDMO data-handling standard, and a PDPL safeguard simultaneously. Tracked separately, that control is documented three times, evidenced three times, and reported three times — and the three records drift apart within a quarter.
The obligations also reach beyond the entity itself. Affiliated companies fall within the ECC's scope whether they operate inside the Kingdom or outside it, which means a parent ministry needs visibility into entities that maintain their own systems, their own teams, and their own interpretation of the same requirement.
The obligation stack
Four authorities, overlapping scopes, separate reporting expectations. Which layers apply depends on the entity, its systems, and the data it holds.
The baseline. Four domains, 28 subdomains, and 108 main controls covering governance, defence, resilience, and third-party and cloud security. Every applicable control needs a named owner, an implementation state, and defensible evidence.
Depending on what the entity operates, the NCA's critical systems, cloud, data, and telework controls sit on top of the ECC. They add requirements rather than replacing the baseline — a distinction that gets lost in scoping more often than it should.
Actively enforced since the grace period ended in September 2024. Lawful basis per processing activity, records of processing, controller registration, rights requests within 30 days, and breach notification within 72 hours.
Operating under SDAIA, NDMO issues the standards for data governance, classification, and management at national level. Public entities carry the clearest exposure here, because these policies are directed at government data specifically.
Digital-service design must account for SDAIA privacy requirements and NCA cybersecurity requirements, with cloud adoption directed under the cloud-first policy. In our experience this means service design decisions carry compliance consequences from day one.
Health, education, energy, transport, and financial entities carry additional requirements from their own regulators on top of everything above.
Which overlays apply varies by entity, systems, and data classification. Confirm your applicable scope against the documents each authority has issued to your organisation rather than assuming a standard set.
Where public-sector compliance programs break
Not on understanding the requirements. On sustaining evidence for four authorities across departments that operate independently.
- 01/06The same control is documented four times
Once for the ECC assessment, once for the PDPL record, once for NDMO, once for the DGA service review. Four documents, four owners, four update cycles, and no single source of truth.
- 02/06Departments report in their own formats
IT, HR, legal, procurement, and facilities each hold part of the evidence. Assembling a submission means chasing five departments who each believe someone else owns the control.
- 03/06Affiliated entities are invisible until they are a finding
The parent ministry has no normalised view of posture across the entities it oversees, because each reports on its own schedule against its own interpretation.
- 04/06Cybersecurity Saudization is a control, not just an HR matter
Under ECC-2:2024, in-scope entities are expected to cybersecurity roles to be filled by qualified Saudi nationals. That is an evidenced requirement, and the records sit in HR while the control sits with the CISO.
- 05/06Incident notification depends on a path nobody has tested
Under the ECC, in-scope entities are expected to notifying the NCA, and the PDPL requires notifying SDAIA within 72 hours. Two obligations, potentially one incident, and often no rehearsed escalation route between the operational team and either.
- 06/06Assessment becomes an annual emergency
Evidence assembled in the weeks beforehand from systems that have since changed — describing a state of compliance that no longer exists on the day it is submitted.
How Govrly works for government entities
Controls, evidence, risks, vendors, assets, and privacy records are shared objects. Implement once, evidence once, satisfy every authority that asks.
An access control implemented once carries its ECC requirement, its NDMO data-handling standard, its PDPL safeguard, and its ISO 27001 Annex A control — from the same record, with the same owner and the same evidence.
Every control carries a named owner with a due date, whether that person sits in IT, HR, legal, procurement, or facilities. Nothing sits unassigned between assessment cycles.
Evidence is requested from an owner with context and a deadline, reviewed before it counts as control support, then linked to every requirement it satisfies across all four authorities.
A ministry monitors posture across affiliated entities through consolidated dashboards, while each entity keeps its own isolated users, controls, evidence, and audit records. Accountability stays where it belongs.
Incidents assessed against both the NCA notification requirement and the PDPL 72-hour window, with the decision reasoning preserved rather than reconstructed afterwards.
Coverage, implementation status, open risks, and overdue actions drawn from current records rather than rebuilt manually before each committee meeting.
Built for the people who carry the obligation
A defensible view of control implementation across every applicable NCA document, with the evidence behind each status and the gaps visible before an assessor finds them.
One system covering four authorities instead of four spreadsheets, with the overlap mapped so a single implementation effort is only done once.
Processing records, lawful bases, rights requests, and breach decisions held alongside the technical controls that actually protect the data.
Findings with root cause, corrective action, owner, and verification — closing only when verification completes, with the full trail preserved.
Compliance consequences visible at service-design time rather than discovered at review, in line with DGA expectations for privacy and security by design.
A current, honest picture of posture across the entity and its affiliates — the one thing that is hardest to obtain and most often asked for at short notice.
What makes the public sector different
Government compliance is not enterprise compliance with different logos on the framework documents.
| Dimension | Government entity | Typical private enterprise |
|---|---|---|
| Authorities | NCA, SDAIA, NDMO, DGA, plus sector regulator | Usually one or two |
| Baseline framework | NCA ECC-2:2024, mandatory | Often ISO 27001, voluntary |
| Scope reach | Extends to affiliated entities, inside and outside the Kingdom | Usually the legal entity itself |
| Staffing | Cybersecurity roles filled by qualified Saudi nationals | Market-determined |
| Data governance | NDMO standards directed at government data | Primarily PDPL |
| Service design | DGA policy, privacy and security by design | Commercially determined |
| Managed in Govrly | Yes | Yes |
Where to start
The sequence matters, because scoping decisions made early determine how much work gets duplicated later.
- 01/07Establish which authorities apply to you
The ECC baseline, which NCA overlays given your systems and data, PDPL scope, NDMO exposure, DGA obligations, and any sector regulator. Record the reasoning for each inclusion and exclusion.
- 02/07Define the entity boundary
Which affiliated entities, departments, systems, and e-services fall inside scope — and which authority each of them answers to.
- 03/07Map the overlap before implementing anything
The single largest saving available. Most controls carry requirements from more than one authority; identify those before building parallel programs.
- 04/07Assign ownership across departments
Each applicable control gets a named owner and a target date, regardless of which department they sit in. A department is not an owner.
- 05/07Close the documentation layer
Strategy, policies, standards, and procedures — approved, versioned, and traceable to the controls they support across every applicable framework.
- 06/07Rehearse the incident path
One incident may trigger both an NCA notification and a 72-hour PDPL notification. Test the escalation route before you need it.
- 07/07Operate continuously
Evidence produced by operations rather than assembled before submission, with posture snapshots preserving a defensible assessment history.
Government entities in Saudi Arabia — FAQs
The NCA Essential Cybersecurity Controls, currently ECC-2:2024, are the mandatory baseline for government entities, their affiliated companies, and critical national infrastructure. Depending on the entity's systems and data, additional NCA control documents covering critical systems, cloud, data, and telework may apply on top of that baseline.
Several at once. The NCA sets cybersecurity requirements, SDAIA enforces the Personal Data Protection Law, NDMO issues national data governance standards directed at government data, and the DGA sets digital government policy including cloud adoption. Sector regulators add further obligations for health, education, energy, transport, and financial entities.
Yes. The ECC applies to government entities in the Kingdom and to their affiliated companies and entities, whether those operate inside Saudi Arabia or outside it. This is why parent organisations need visibility into the compliance posture of entities that maintain their own systems and teams.
Yes. The Personal Data Protection Law applies to any organisation, public or private, processing the personal data of individuals in Saudi Arabia. Government entities carry the same core obligations as private organisations, including records of processing, lawful basis, rights requests within 30 days, and breach notification to SDAIA within 72 hours.
The NCA sets cybersecurity requirements — how systems and data are protected. NDMO, operating under SDAIA, issues the national standards for data governance, classification, and management. They address different questions about the same data, and a government entity typically needs to satisfy both.
Under ECC-2:2024, in-scope entities are expected to cybersecurity roles to be filled by qualified Saudi nationals. This is an evidenced requirement rather than an HR preference, and the supporting records need to be available at assessment.
Most organisations we work with take six to eighteen months to reach full implementation, depending on size, existing control maturity, and internal resourcing. Entities with an established ISO 27001 program generally move faster, because much of the required evidence already exists in a reusable form.
Yes. In Govrly, controls, measures, and evidence are shared objects, so one implementation effort and one piece of approved evidence can support overlapping requirements across every applicable authority — while each framework keeps its own scoping, scoring method, and reporting.
Through consolidated dashboards showing normalised posture, progress, risk, and open actions across entities, while each entity retains its own isolated users, controls, evidence, and audit records. The parent gains visibility without collapsing entity-level data separation or removing accountability from the entity.
Govrly runs on Google Cloud Platform with Cloudflare edge protection and multi-tenant isolation. For entities with specific data residency requirements, discuss your obligations with us directly — residency requirements for Saudi government data are directed by NDMO and SDAIA rather than by the ECC document itself.
Four authorities. One system of record.
See how a single control, owner, and evidence set can satisfy the NCA, SDAIA, NDMO, and DGA at the same time.
