Applicability
Establish which authorities apply, for which data classes and which processing activities.
Done when: A written applicability statement exists per authority.
NDMO, PDPL, NCA, SAMA and SDAIA ethics folded into one control set with evidence per control.
The business problem
NDMO, PDPL, NCA and SAMA each trigger their own project, and the same evidence is gathered again and again.
What you hear inside the organisation
We just finished the NDMO review and now NCA wants the same.
Where exactly is our personal data?
Compliance lives in spreadsheets.
Who signs off this evidence?
Who it serves and what changes
Client teams and what they need
Compliance and risk
One control set for every regulator
Data office
Controls inside the data, not beside it
Cybersecurity
NCA controls tied to data assets
Internal audit
Evidence that is always current
The outcome you get
A worked example
The problem we saw
Each review was a separate project. Teams rebuilt the same evidence in spreadsheets, and nobody was sure where personal data sat.
How the framework solved it
We discovered and classified personal data, merged every regulator's requirements into one control set, and linked each control to live evidence.
The business result
The next review drew on the same evidence pack, owners knew their controls, and compliance stopped being a yearly scramble.
Illustrative example based on common client situations.
In short
Saudi Data Compliance Framework (SDCF): NDMO, PDPL, NCA, SAMA and SDAIA ethics folded into one control set with evidence per control.
Saudi organisations answer to several authorities that ask overlapping questions in different formats.
How it works
Regulations change; the control set is versioned so a new circular is a diff, not a restart.
Establish which authorities apply, for which data classes and which processing activities.
Done when: A written applicability statement exists per authority.
Merge overlapping requirements into one control per obligation, cited to each source.
Done when: The same duty is implemented twice in two languages of compliance.
Attach the artefact that proves each control, produced by a system rather than a statement.
Done when: Every control has an artefact with a date and a source system.
Score each control, rank the gaps by exposure, and assign an owner and a date.
Done when: Every high-exposure gap has a dated remediation owner.
Produce the attestation pack and re-run the control set on a fixed cycle.
Done when: The pack can be handed to a reviewer without preparation work.
Is it right for you?
A strong fit if
Probably not yet if
Free assessment
A working session with our senior team. We review what fits your situation, what does not, and where to start.
A focused conversation
We listen to your situation and goals.
Fit review
Which parts of this framework apply to you, and which do not.
A written view
Clear next steps, whether or not you work with us.
Go deeper
Open only the part you need: how it starts, what your team keeps, maturity levels, sector rules and the evidence a reviewer will ask for.
Saudi organisations answer to several authorities that ask overlapping questions in different formats. SDCF states each obligation once, maps it to every authority that asks for it, and names the evidence that satisfies all of them together.
Version
v1.0
Last reviewed
August 2026
Family
Saudi Data & AI Standards
How this was developed: Built from delivery practice on Saudi and international engagements, then reconciled clause by clause against the published standards below. Revised when a standard is updated or a gate proves unworkable in the field.
Unified control set
One control per obligation with citations to every authority that requires it.
Evidence index
A dated artefact per control, produced by the system that runs it.
Attestation pack
Reviewer-ready, versioned, and refreshed on a fixed cycle.
Banking & finance
SAMA expectations sit above the base set; outsourcing and cloud controls are examined first.
Establish which authorities apply, for which data classes and which processing activities.
Exit gate
A written applicability statement exists per authority.
Artefacts
Merge overlapping requirements into one control per obligation, cited to each source.
Exit gate
The same duty is implemented twice in two languages of compliance.
Artefacts
Attach the artefact that proves each control, produced by a system rather than a statement.
Exit gate
Every control has an artefact with a date and a source system.
Artefacts
Score each control, rank the gaps by exposure, and assign an owner and a date.
Exit gate
Every high-exposure gap has a dated remediation owner.
Artefacts
Produce the attestation pack and re-run the control set on a fixed cycle.
Exit gate
The pack can be handed to a reviewer without preparation work.
Artefacts
Parallel programmes produce contradictory evidence. Implement once, cite many.
A signed policy with no system artefact will not survive a review.
Evidence assembled in a panic is evidence of an unmanaged control.
A short readiness check against the obligations reviewers ask about first.
Most statements have no artefact behind them. Start with one domain and produce the evidence before widening scope.
Scoring is deterministic and runs entirely in your browser. Nothing is stored or sent.
NDMO data management and personal data protection standards
National Data Management Office specifications and domains.
Personal Data Protection Law (PDPL) and its implementing regulations
Lawful basis, subject rights, transfer and retention.
NCA Essential and Cloud Cybersecurity Controls
National Cybersecurity Authority control catalogues.
SAMA frameworks for cybersecurity and outsourcing
Supervisory expectations for financial institutions.
SDAIA AI Ethics Principles
Saudi Data & AI Authority, national principles for AI.
ISO/IEC 42001: AI management systems
International Organization for Standardization, management system requirements for AI.
Citations describe the parts of each standard the framework answers. Bilytica is not an accreditation or certification body.
In Saudi Arabia
This family exists because the Saudi control set, Arabic quality and the in-country deployment ruling are not add-ons to a global method. They decide whether a system is allowed to run at all.
SDAIA, PDPL
National AI ethics principles applied as testable controls.
Each principle becomes a check with a pass condition and a named reviewer.
Ethics review record per release, in Arabic.
Arabic quality standard
Saudi Arabic output has to be correct in register, terminology and numerals, in front of a customer.
Arabic evaluation sets built from Saudi content, scored before release.
Arabic quality score with the failing cases attached.
NCA ECC
Deployment location and network boundaries are a documented decision.
A deployment ruling per data class states what may leave Saudi Arabia and what may not.
Signed residency ruling referenced by the architecture record.
Where it runs
The default is in-country, in your environment. Any exception is written down with the data class, the reason and an expiry date.
Arabic, as it is spoken here
Arabic is the governing version of every artefact in this family, with English supplied alongside.
No. It prepares for it. The same evidence index answers the assessment without a separate exercise.
The control set is versioned. A new circular produces a change list against the previous version.
Yes, the AI-specific obligations are carried by the AI Assurance Framework, which reuses this control set as its Saudi layer.
Curated links across our Saudi hubs, sector pages and long-form blog research.