Saudi organizations that rely on public-cloud and SaaS platforms are watching the NCA cloud cybersecurity controls draft 2025 closely. The National Cybersecurity Authority has signaled expectations on where data sits, who holds encryption keys, how quickly incidents are reported and what rights a customer has to examine its provider. Most vendor standard agreements were written for a global customer base and do not address these points in the form a Saudi regulator is likely to expect.
This article is written for CISOs, legal counsel and procurement managers. It identifies four contract areas likely to need amendment, explains the compliance gap each one creates, and sets out a three-step sequence for negotiating changes while protecting your position if the vendor declines.
A note on status: the controls discussed here are in draft. Final wording, numbering and effective dates may differ, so treat this as a planning basis and confirm against the published NCA text before committing to contract language.
Why contracts, not only configurations, are the issue
Technical settings can be changed by your own team. Contract terms cannot. If a SaaS agreement allows the provider to move data to another region, hold keys on your behalf without your control, notify you of incidents "without undue delay," or limit audits to a summary report, then no configuration will close that gap. The obligation sits in the paper.
For organizations in critical sectors, or those holding personal data under the PDPL, the contract is also the evidence a regulator will ask to see.
The four clauses likely to become mandatory
1. Data residency
The draft direction is that data in scope for NCA controls should be hosted and processed in the Kingdom, with limits on transfer. Standard agreements typically reserve the provider's right to use sub-processors and move workloads between regions.
The gap: a general "region of choice" statement without a commitment covering backups, support access, telemetry and disaster-recovery copies. Data can leave the Kingdom through these routes even when primary storage stays local.
What to seek: a named hosting location, a prohibition on relocation without your written consent, and a list of sub-processors with notice of changes.
2. Encryption-key custody
Expectations around customer control of cryptographic keys are a recurring theme in cloud governance. Many SaaS platforms manage keys entirely on the provider side.
The gap: no right to hold, rotate or revoke keys, and no clarity on who can decrypt data during support or legal requests.
What to seek: customer-managed or customer-held key options, defined rotation and destruction procedures, and a statement of when provider staff may access decrypted data.
3. Incident-notification timelines
Regulated organizations have their own reporting duties to NCA, SAMA or the SDAIA under the PDPL, depending on sector. Your vendor's notice period must be shorter than your own obligation, or you cannot meet it.
The gap: vague wording such as "promptly" or a notice period that starts only when the vendor has completed its investigation.
What to seek: a fixed notification window measured from detection, a defined minimum content for the notice, a named contact channel, and a duty to provide updates and a post-incident report.
4. Audit and assurance rights
Customers need the ability to verify controls, not only to read a certificate.
The gap: audit clauses limited to a provider-issued report, with no right of inspection, no regulator access and no remedy for findings.
What to seek: the right to audit or commission an audit, access for the competent regulator, and a requirement that the provider remediate material findings within an agreed period.
The three-step negotiation sequence
Order matters. Teams that open with vendor demands before they understand their own exposure tend to negotiate the wrong points.
Step 1: Gap analysis
Inventory every cloud and SaaS contract, then rank them by data sensitivity, regulatory exposure and business criticality. For each, compare the existing terms against the four areas above and record:
- where data, backups and support access actually reside
- who holds and can use encryption keys
- the vendor's notification commitment against your own reporting duties
- the audit rights you hold today
The output is a short register showing which contracts have gaps, how serious each is, and which are renewing soonest. Renewal dates give you leverage, so use them.
Step 2: Vendor negotiation
Approach vendors with a specific amendment request tied to a regulatory driver, not a general complaint. Procurement, legal and security should speak with one voice.
- Separate must-have terms from preferred terms before the first conversation.
- Present the regulatory basis and the exact wording you need.
- Offer practical alternatives where the vendor cannot change its global terms, such as a Saudi-specific addendum or a dedicated regional tenant.
- Document every response, including refusals, with dates.
Refusals are information. A written refusal is the trigger for the third step and is also useful evidence of diligence.
Step 3: Fallback architecture
If a vendor will not amend, you need a design that reduces the risk without relying on its promises. Options depend on the service but commonly include:
- encrypting data with keys you control before it reaches the platform
- restricting the data types sent to the platform
- adding your own monitoring so you can detect incidents without waiting for vendor notice
- planning a migration path or an alternative provider for the affected workload
Where residual risk remains, record it formally, obtain risk acceptance at the right level, and set a review date.
Signs it is time to act
- You cannot say where backups and support access for key SaaS platforms are located.
- Vendor notice periods are longer than, or unclear against, your own reporting duties.
- Contracts renew before Q3 2025 and no one has reviewed them against the draft.
- The legal and security teams hold different views of who controls encryption keys.
What a good outcome looks like
By the time the final controls take effect, you should hold a current register of cloud contracts and their gaps, signed amendments for the highest-risk platforms, documented refusals with fallback measures for the rest, and board-level visibility of residual risk. That position lets you answer a regulator or an auditor with documents rather than assurances.
How we can help
Regulatory Updates — Stay ahead of SAMA, NCA, and PDPL regulatory changes with timely intelligence, impact analysis, and practical implementation guidance.
If you would like to understand how the NCA draft, and later the final text, affects your own cloud agreements, our Regulatory Updates service is the place to start.