Saudi cybersecurity regulations
The regulatory bodies and frameworks this tool assesses, with links to the official documents. Question banks paraphrase the official controls for self-assessment.
National Cybersecurity Authority (NCA)
The national authority for cybersecurity. It sets policies, frameworks and controls (ECC, NCNICC, CCC, DCC, CSCC, OTCC and others) and monitors compliance.
NCA ECC · NCA NCNICC · NCA CSCC · NCA CCC · NCA DCC · NCA OTCC · NCA TCC · NCA OSMACC · NCA NCS · nca.gov.sa ↗
Saudi Data & AI Authority (SDAIA)
The competent authority for the Personal Data Protection Law (PDPL). It handles breach notifications and enforcement, and publishes the Implementing Regulations and the Transfer Regulation.
Communications, Space & Technology Commission (CST)
Regulates telecom, ICT, space and postal services. It applies the Cybersecurity Regulatory Framework (CRF) to licensed service providers.
Saudi Central Bank (SAMA)
The central bank. It sets cybersecurity and business continuity requirements for banks, insurers, finance companies and payment providers.
Capital Market Authority (CMA)
Regulates the capital market. It sets cybersecurity requirements for capital market institutions.
Digital Government Authority (DGA)
Regulates digital government. It sets standards for government digital services.
Ministry of Health and health-sector authorities
Health-sector authorities set requirements for protecting health information.
National Cybersecurity Authority (NCA)
Essential Cybersecurity Controls
The national cybersecurity baseline. Mandatory for government entities (including their companies inside and outside the Kingdom) and for private entities that own, operate or host Critical National Infrastructure.
Applies to: Government entities, their affiliated companies, and CNI operators.
Domains assessed (108 questions)
- Approved cybersecurity strategy (1-1-1)
- Strategy action plan (1-1-2)
- Strategy review (1-1-3)
- Independent cybersecurity department (1-2-1)
- Qualified Saudi cybersecurity staff (1-2-2)
- Cybersecurity supervisory committee (1-2-3)
- Approved policies and procedures (1-3-1)
- Policy implementation (1-3-2)
- Technical security standards (1-3-3)
- Policy review and update (1-3-4)
- Governance structure and roles (1-4-1)
- Roles and responsibilities review (1-4-2)
- Risk management methodology (1-5-1)
- Risk management in practice (1-5-2)
- Risk assessment triggers (1-5-3 (1-5-3-1 – 1-5-3-4))
- Risk methodology review (1-5-4)
- Security in projects and change management (1-6-1)
- Pre-launch vulnerability and hardening checks (1-6-2 (1-6-2-1, 1-6-2-2))
- Secure software development (1-6-3 (1-6-3-1 – 1-6-3-5))
- Project security requirements review (1-6-4)
- International commitments (1-7-1)
- Periodic internal review (1-8-1)
- Independent audit (1-8-2)
- Audit results reporting (1-8-3)
- Personnel security requirements (1-9-1)
- Personnel requirements implemented (1-9-2)
- Contracts and screening (1-9-3 (1-9-3-1, 1-9-3-2))
- Security during employment (1-9-4 (1-9-4-1, 1-9-4-2))
- Access revocation on exit (1-9-5)
- Personnel requirements review (1-9-6)
- Approved awareness program (1-10-1)
- Awareness program delivered (1-10-2)
- Awareness topics (1-10-3 (1-10-3-1 – 1-10-3-4))
- Specialized training (1-10-4 (1-10-4-1 – 1-10-4-3))
- Awareness program review (1-10-5)
- Asset management requirements (2-1-1)
- Asset inventory in place (2-1-2)
- Acceptable use policy (2-1-3)
- Acceptable use enforced (2-1-4)
- Asset classification and labeling (2-1-5)
- Asset management review (2-1-6)
- IAM requirements (2-2-1)
- IAM implementation (2-2-2)
- Authentication, MFA and privileged access (2-2-3 (2-2-3-1 – 2-2-3-5))
- IAM review (2-2-4)
- System protection requirements (2-3-1)
- System protection implemented (2-3-2)
- Malware protection, media, patching and time sync (2-3-3 (2-3-3-1 – 2-3-3-4))
- System protection review (2-3-4)
- Email protection requirements (2-4-1)
- Email protection implemented (2-4-2)
- Filtering, MFA, archiving, APT and SPF/DKIM/DMARC (2-4-3 (2-4-3-1 – 2-4-3-5))
- Email protection review (2-4-4)
- Network security requirements (2-5-1)
- Network security implemented (2-5-2)
- Segmentation, browsing, wireless, IPS, DNS and DDoS (2-5-3 (2-5-3-1 – 2-5-3-9))
- Network security review (2-5-4)
- Mobile and BYOD requirements (2-6-1)
- Mobile and BYOD requirements implemented (2-6-2)
- Data separation, encryption and wipe (2-6-3 (2-6-3-1 – 2-6-3-4))
- Mobile and BYOD review (2-6-4)
- Data protection requirements (2-7-1)
- Data protected by classification (2-7-2)
- Data protection review (2-7-3)
- Cryptography requirements (2-8-1)
- Cryptography implemented (2-8-2)
- National Cryptographic Standards (2-8-3 (2-8-3-1 – 2-8-3-3))
- Cryptography review (2-8-4)
- Backup requirements (2-9-1)
- Backups in place (2-9-2)
- Backup scope, fast recovery and restore tests (2-9-3 (2-9-3-1 – 2-9-3-3))
- Backup review (2-9-4)
- Vulnerability management requirements (2-10-1)
- Vulnerability management implemented (2-10-2)
- Scanning, classification, remediation and patching (2-10-3 (2-10-3-1 – 2-10-3-5))
- Vulnerability management review (2-10-4)
- Penetration testing requirements (2-11-1)
- Penetration tests performed (2-11-2)
- Scope and frequency of testing (2-11-3 (2-11-3-1, 2-11-3-2))
- Penetration testing review (2-11-4)
- Logging and monitoring requirements (2-12-1)
- Logging and monitoring implemented (2-12-2)
- Critical logs, SIEM, continuous monitoring and retention (2-12-3 (2-12-3-1 – 2-12-3-5))
- Logging and monitoring review (2-12-4)
- Incident and threat management requirements (2-13-1)
- Incident management implemented (2-13-2)
- Response plans, NCA reporting and threat intelligence (2-13-3 (2-13-3-1 – 2-13-3-5))
- Incident management review (2-13-4)
- Physical security requirements (2-14-1)
- Physical security implemented (2-14-2)
- Critical areas, CCTV and secure disposal (2-14-3 (2-14-3-1 – 2-14-3-5))
- Physical security review (2-14-4)
- Web application security requirements (2-15-1)
- Web application security implemented (2-15-2)
- WAF, multi-tier architecture, HTTPS and authentication (2-15-3 (2-15-3-1 – 2-15-3-5))
- Web application security review (2-15-4)
- Cybersecurity in BCM requirements (3-1-1)
- Cybersecurity in BCM implemented (3-1-2)
- Continuity, incident response and DR plans (3-1-3 (3-1-3-1 – 3-1-3-3))
- Cybersecurity in BCM review (3-1-4)
- Third-party contract requirements (4-1-1)
- Security clauses in contracts (4-1-2 (4-1-2-1 – 4-1-2-3))
- Outsourcing and managed services (4-1-3 (4-1-3-1, 4-1-3-2))
- Third-party requirements review (4-1-4)
- Cloud and hosting requirements (4-2-1)
- Cloud and hosting requirements implemented (4-2-2)
- Data protection, return and tenant separation (4-2-3 (4-2-3-1, 4-2-3-2))
- Cloud and hosting review (4-2-4)
Non-CNI Private Sector Entities Cybersecurity Controls
Minimum cybersecurity requirements for private sector organizations that are not Critical National Infrastructure, derived from the ECC. Class A (large) entities apply all components; Class B (small and medium) entities apply the core defense controls.
Applies to: Private sector entities outside CNI that NCA circulates the controls to (Class A: large, Class B: SMEs).
Domains assessed (23 questions)
- Cybersecurity management (1-1-1 – 1-1-3)
- Policies and procedures (1-2-1 – 1-2-3)
- Risk management (1-3-1 – 1-3-3)
- Periodic review and audit (1-4-1, 1-4-2)
- Awareness and training (1-5-1 – 1-5-3)
- Asset management (2-1-1, 2-1-2)
- Identity and access management (2-2-1, 2-2-2)
- System and device protection (2-3-1, 2-3-2)
- Email protection (2-4-1, 2-4-2)
- Network security (2-5-1, 2-5-2)
- Mobile devices (2-6-1, 2-6-2)
- Data and information protection (2-7-1, 2-7-2)
- Cryptography (2-8-1, 2-8-2)
- Backup management (2-9-1, 2-9-2)
- Vulnerability management (2-10-1, 2-10-2)
- Penetration testing (2-11-1 – 2-11-3)
- Event logs and monitoring (2-12-1, 2-12-2)
- Incident and threat management (2-13-1, 2-13-2)
- Reporting incidents to NCA (2-13-1-2, 2-13-1-3)
- Physical security (2-14-1, 2-14-2)
- Web application protection (2-15-1 – 2-15-3)
- Third-party cybersecurity (3-1-1 – 3-1-3)
- Cloud and hosting cybersecurity (3-2-1 – 3-2-3)
Critical Systems Cybersecurity Controls
An extension of the ECC that sets additional minimum cybersecurity requirements for national critical systems, i.e. systems whose failure or compromise could harm the organization's services or cause national economic, financial, security or social impact.
Applies to: Organizations that own or operate systems identified as critical under the CSCC criteria: government organizations inside or outside the Kingdom (ministries, authorities, establishments, embassies), their subsidiaries and companies, and private sector organizations. Continuous ECC compliance is a prerequisite.
Domains assessed (32 questions)
- Strategy prioritizes critical systems (1-1-1)
- Critical systems risk management (1-2-1)
- Project and change management (1-3-1)
- Secure software development (1-3-2)
- Annual CSCC review (1-4-1)
- Independent CSCC review (1-4-2)
- Personnel for critical systems (1-5-1)
- Critical systems asset management (2-1-1)
- Critical systems access management (2-2-1)
- Quarterly access review (2-2-2)
- Critical systems and facilities protection (2-3-1)
- Critical systems network security (2-4-1)
- Mobile access to critical systems (2-5-1)
- Critical systems data protection (2-6-1)
- Critical systems encryption (2-7-1)
- Critical systems backup (2-8-1)
- Quarterly restore testing (2-8-2)
- Critical systems vulnerability remediation (2-9-1)
- Monthly vulnerability assessment (2-9-2)
- Penetration testing scope (2-10-1)
- Semi-annual penetration testing (2-10-2)
- Critical systems logging and monitoring (2-11-1)
- Log retention of 18 months (2-11-2)
- External web application security (2-12-1)
- Multi-tier web architecture (2-12-2)
- Internal application requirements defined (2-13-1)
- Internal application requirements implemented (2-13-2)
- Minimum internal application controls (2-13-3)
- Internal application requirements review (2-13-4)
- Disaster recovery for critical systems (3-1-1)
- Outsourcing and managed services (4-1-1)
- Hosting location of critical systems (4-2-1)
Cloud Cybersecurity Controls
Cloud-specific extension of the ECC that sets minimum cybersecurity requirements for Cloud Service Providers (CSPs) and Cloud Service Tenants (CSTs). Each control applies either to providers or to tenants, on top of the ECC.
Applies to: CSTs: government entities inside or outside the Kingdom and their companies, and private entities that own, operate or host CNI, that use or plan to use cloud services. CSPs: any provider serving those tenants. Both must also comply with the ECC.
Domains assessed (55 questions)
- Cloud roles and RACI (provider) (1-1-P-1)
- Cloud roles and RACI (tenant) (1-1-T-1)
- Cloud risk management (provider) (1-2-P-1)
- Cloud risk management (tenant) (1-2-T-1)
- Continuous regulatory compliance (provider) (1-3-P-1)
- Monitoring CSP compliance (1-3-T-1)
- Personnel before and during employment (1-4-P-1)
- Asset return on termination (1-4-P-2)
- Screening for sensitive cloud roles (1-4-T-1)
- Change management security requirements (1-5-P-1)
- Applying change management requirements (1-5-P-2)
- Secure and emergency changes (1-5-P-3)
- Change management review (1-5-P-4)
- Cloud asset inventory and owners (2-1-P-1)
- Inventory of cloud services (2-1-T-1)
- Provider identity and access management (2-2-P-1)
- Tenant cloud identity and access (2-2-T-1)
- Cloud platform protection and isolation (2-3-P-1)
- Verifying community cloud isolation (2-3-T-1)
- Cloud network security (2-4-P-1)
- Secure connection to the CSP (2-4-T-1)
- Provider end-user and mobile devices (2-5-P-1)
- Sanitizing devices with cloud access (2-5-T-1)
- Protection of tenant data (2-6-P-1)
- Cloud exit and data portability (2-6-T-1)
- Provider cryptography (2-7-P-1)
- Encrypting data to and from the cloud (2-7-T-1)
- Securing tenant and platform backups (2-8-P-1)
- Platform vulnerability management (2-9-P-1)
- Tenant cloud vulnerability management (2-9-T-1)
- Cloud platform penetration testing (2-10-P-1)
- Platform logging and SIEM monitoring (2-11-P-1)
- Tenant cloud logging and monitoring (2-11-T-1)
- Incident and threat management (2-12-P-1)
- Data center physical security (2-13-P-1)
- Web application transaction protection (2-14-P-1)
- Key management requirements (provider) (2-15-P-1)
- Applying key management (provider) (2-15-P-2)
- Key ownership, recovery and audit (provider) (2-15-P-3)
- Key management review (provider) (2-15-P-4)
- Key management requirements (tenant) (2-15-T-1)
- Applying key management (tenant) (2-15-T-2)
- Key ownership and recovery (tenant) (2-15-T-3)
- Key management review (tenant) (2-15-T-4)
- Secure development requirements (2-16-P-1)
- Applying secure development (2-16-P-2)
- Security across the development lifecycle (2-16-P-3)
- Secure development review (2-16-P-4)
- Storage media requirements (2-17-P-1)
- Applying storage media requirements (2-17-P-2)
- Media sanitization and control (2-17-P-3)
- Storage media review (2-17-P-4)
- Secure DR and security continuity (3-1-P-1)
- Cloud disaster recovery (tenant) (3-1-T-1)
- Supply chain and marketplace security (4-1-P-1)
Data Cybersecurity Controls
An extension of the ECC that sets the minimum cybersecurity requirements for protecting data throughout its lifecycle (create, store, share, use, dispose). Requirements scale with the data classification level: Public, Restricted, Secret and Top Secret.
Applies to: Government organizations (ministries, authorities, establishments and others) and their companies and entities, plus private sector organizations that own, operate or host Critical National Infrastructure; covers all physical and digital data. Continuous ECC compliance is a prerequisite.
Domains assessed (19 questions)
- Periodic internal DCC review (1-1-1)
- Independent DCC review and audit (1-1-2)
- Cybersecurity in human resources (1-2-1)
- Data protection awareness topics (1-3-1)
- Restricted data access privileges (2-1-1)
- Privileged access management for data (2-1-2)
- Periodic review of data privileges (2-1-3)
- Protection of systems handling data (2-2-1)
- Mobile devices and BYOD (2-3-1)
- Data and information protection (2-4-1)
- Cryptography by classification level (2-5-1)
- Secure data disposal (2-6-1)
- Review of secure disposal (2-6-2)
- Printer and copier security requirements (2-7-1)
- Printer and copier requirements implemented (2-7-2)
- Minimum printer and copier controls (2-7-3)
- Review of printer and copier controls (2-7-4)
- Third-party data protection (3-1-1)
- Consultancy on sensitive national projects (3-1-2)
Operational Technology Cybersecurity Controls
Extension of the ECC that sets minimum cybersecurity requirements for Industrial Control Systems (OT/ICS) in critical facilities. Controls apply according to the facility level (L1 high, L2 moderate, L3 low criticality) assigned with NCA's Facility Level Identification Tool.
Applies to: Government organizations and private entities owning, operating or hosting Critical National Infrastructure that own or operate ICS in critical facilities, inside or outside the Kingdom; ECC compliance is a prerequisite.
Domains assessed (47 questions)
- OT/ICS policies and procedures (1-1-1)
- OT/ICS technical standards (1-1-2)
- OT/ICS policy review (1-1-3)
- OT/ICS roles and responsibilities (1-2-1)
- OT/ICS risk management (1-3-1)
- Cybersecurity in ICS projects (1-4-1)
- ICS project security review (1-4-2)
- OT/ICS change management requirements (1-5-1)
- Change management implementation (1-5-2)
- Secure change practices (1-5-3)
- Change management review (1-5-4)
- Annual OTCC review (1-6-1)
- Independent OTCC review (1-6-2)
- OT personnel screening (1-7-1)
- OT HR security review (1-7-2)
- OT/ICS awareness (1-8-1)
- OT/ICS specialized training (1-8-2)
- OT/ICS asset inventory (2-1-1)
- OT asset management review (2-1-2)
- OT/ICS identity and access management (2-2-1)
- OT IAM review (2-2-2)
- OT system and facility protection (2-3-1)
- OT system protection review (2-3-2)
- OT/ICS network security (2-4-1)
- OT network security review (2-4-2)
- OT mobile device security (2-5-1)
- OT mobile device review (2-5-2)
- OT data and information protection (2-6-1)
- OT data protection review (2-6-2)
- OT cryptography (2-7-1)
- OT cryptography review (2-7-2)
- OT backup and recovery (2-8-1)
- OT backup review (2-8-2)
- OT vulnerability management (2-9-1)
- OT vulnerability management review (2-9-2)
- OT penetration testing (2-10-1)
- OT penetration testing review (2-10-2)
- OT event logs and monitoring (2-11-1)
- OT monitoring review (2-11-2)
- OT incident and threat management (2-12-1)
- OT incident management review (2-12-2)
- OT physical security (2-13-1)
- OT physical security review (2-13-2)
- OT business continuity and resilience (3-1-1)
- OT resilience review (3-1-2)
- OT third-party cybersecurity (4-1-1)
- OT third-party review (4-1-2)
Telework Cybersecurity Controls
Minimum cybersecurity requirements that let national organizations run telework (remote work) securely, issued as an extension of the ECC. Every in-scope organization that allows telework must apply all controls relevant to it.
Applies to: Government organizations (ministries, authorities, establishments and their companies) and private entities that own, operate or host Critical National Infrastructure, whenever they allow telework.
Domains assessed (21 questions)
- Telework cybersecurity policy (1-1-1)
- Telework risk management (1-2-1)
- Telework awareness (1-3-1)
- Telework technical training (1-3-2)
- Telework asset inventory (2-1-1)
- Telework access management (2-2-1)
- Telework access review (2-2-2)
- Telework systems protection (2-3-1)
- Telework network security (2-4-1)
- Mobile devices and BYOD (2-5-1)
- Telework data protection (2-6-1)
- Telework encryption (2-7-1)
- Telework backups (2-8-1)
- Telework backup restore tests (2-8-2)
- Telework vulnerability management (2-9-1)
- Telework penetration test scope (2-10-1)
- Telework penetration test frequency (2-10-2)
- Telework logging and monitoring (2-11-1)
- Telework log retention (2-11-2)
- Telework incident and threat management (2-12-1)
- Telework hosting location (3-1-1)
Organizations' Social Media Accounts Cybersecurity Controls
Minimum cybersecurity requirements for the secure use of official organizational social media accounts, reducing the risk of account takeover, misuse and impersonation. Issued as an extension of the ECC.
Applies to: Government organizations (ministries, authorities, establishments and their companies) and private entities that own, operate or host Critical National Infrastructure, when they use social media accounts.
Domains assessed (15 questions)
- Social media cybersecurity policy (1-1-1)
- Social media risk management (1-2-1)
- Social media account personnel (1-3-1)
- Social media awareness (1-4-1)
- Social media technical training (1-4-2)
- Social media account inventory (2-1-1)
- Social media identity and access (2-2-1)
- Social media access review (2-2-2)
- Social media systems protection (2-3-1)
- Social media mobile devices (2-4-1)
- No classified data on social media assets (2-5-1)
- Social media monitoring (2-6-1)
- Social media account recovery plan (2-7-1)
- Need assessment for social media services (3-1-1)
- Social media service provider requirements (3-1-2)
National Cryptographic Standards
The national minimum requirements for using cryptography to protect data, systems and networks for civilian and commercial purposes. It lists the accepted algorithms, key lengths, modes, protocols, certificate rules and key lifecycle management practices at two strength levels (MODERATE and ADVANCED). Other NCA controls, such as the ECC cryptography subdomain, require compliance with it.
Applies to: National entities that use cryptography to protect data (in use, at rest and in transit), systems and networks for civilian or commercial purposes; each entity selects the MODERATE or ADVANCED level according to data sensitivity or as mandated by other NCA regulations.
Domains assessed (38 questions)
- Cryptographic strength level selection (1.1, 1.2)
- Stream cipher algorithms (2.1.1)
- Block cipher algorithms (2.1.2)
- Asymmetric algorithms (2.2)
- Hash functions (2.3)
- Lightweight crypto algorithms (2.4)
- Block cipher modes of operation (3.1)
- Message authentication codes (3.2)
- Authenticated encryption (AEAD) (3.3)
- Key wrap functions (3.4)
- Key derivation functions (3.5)
- Key agreement and key transport (3.6.1, 3.6.2)
- Hybrid encryption schemes (3.7)
- Public key signatures (3.8)
- Protocols not listed in the standard (4 (introduction))
- IP Security (IPsec) (4.1)
- Transport Layer Security (TLS) (4.2)
- DNS Security (DNSSEC) (4.3)
- Secure Shell (SSH) (4.4)
- Bluetooth (4.5)
- Mobile networks (UMTS / LTE / 5G) (4.6)
- Wi-Fi Protected Access (WPA) (4.7)
- Kerberos protocol (4.8)
- Algorithms for certificates (5.1)
- Validity of certificates (5.2)
- Key protection and lifetime (6.1)
- Key generation (6.2 (Table 1: Key Generation))
- Key registration and certification (6.2 (Table 1: Key Registration/Certification))
- Key distribution and installation (6.2 (Table 1: Key Distribution and Installation))
- Key use (6.2 (Table 1: Key Use))
- Key storage and backup (6.2 (Table 1: Key Storage))
- Key revocation and validation (6.2 (Table 1: Key Revocation/Validation))
- Key archive (6.2 (Table 1: Key Archive))
- Key destruction (6.2 (Table 1: Key Destruction))
- Key accounting (6.2 (Table 1: Key Accounting))
- Pseudo random number generation (7.1)
- Post-quantum cryptography readiness (7.2)
- Side-channel attack protection (7.3)
Saudi Data & AI Authority (SDAIA)
Personal Data Protection Law
Protects the personal data of individuals in the Kingdom. Requires a legal basis and consent rules, privacy notices, data subject rights within 30 days, minimization, retention limits, processor controls, records of processing, DPO appointment and impact assessments where required, security measures, breach notification to SDAIA within 72 hours, and controls on transfers outside the Kingdom. Violations can reach SAR 5 million.
Applies to: Any entity processing personal data of individuals in the Kingdom, including entities outside the Kingdom that process data of residents; personal or family use is excluded.
Domains assessed (35 questions)
- Data Protection Officer (Art. 30(2); IR Art. 32; DPO Rules Art. 4–8)
- Privacy policy (Art. 12)
- Records of processing activities (Art. 31; IR Art. 33)
- Data protection impact assessments (Art. 22; IR Art. 25)
- Processor selection and contracts (Art. 8; IR Art. 17(1)–(2))
- Training and confidentiality (Art. 41)
- Processor oversight and sub-processing (IR Art. 17(3)–(5))
- National register of controllers (Art. 30(4)(c); IR Art. 34; Register Rules Art. 2–10)
- Cooperation with SDAIA and complaints (Art. 30(3), 34; IR Art. 37)
- Legal basis and consent (Art. 5(1), 6(1)–(3), 7; IR Art. 11, 14)
- Purpose limitation and minimization (Art. 11; IR Art. 19)
- Retention, destruction and anonymization (Art. 18; IR Art. 9)
- Marketing and communications (Art. 25, 26; IR Art. 28, 29)
- Sensitive and health data (Art. 23; IR Art. 26)
- Withdrawal of consent (Art. 5(2); IR Art. 12)
- Legitimate interest (Art. 6(4); IR Art. 16)
- Collection from other sources and new purposes (Art. 10; IR Art. 15, 18)
- Credit data (Art. 24; IR Art. 27)
- Children and persons lacking legal capacity (IR Art. 13)
- Scientific, research and statistical purposes (Art. 27; IR Art. 30)
- Photographing or copying official documents (Art. 28; IR Art. 31)
- Disclosure of personal data (Art. 15, 16; IR Art. 20, 21)
- Handling data subject requests (Art. 4, 21; IR Art. 3, 10)
- Notice at collection (right to be informed) (Art. 13; IR Art. 4)
- Right of access and copy (Art. 9; IR Art. 5, 6)
- Accuracy and correction (Art. 14, 17; IR Art. 7, 22)
- Destruction on request (IR Art. 8)
- Security measures (Art. 19; IR Art. 23(b))
- Encryption and access control (IR Art. 23(a))
- Breach notification within 72 hours (Art. 20; IR Art. 24)
- Breach detection (IR Art. 1(3))
- Cross-border transfer controls (Art. 29; Transfer Regulation Art. 2, 3)
- Data location and onward transfers (Transfer Regulation Art. 5)
- Appropriate safeguards for exempted transfers (Transfer Regulation Art. 4, 6)
- Transfer risk assessment (Transfer Regulation Art. 7)
Data Management and Personal Data Protection Standards
National standards for managing and governing government data and protecting personal data, organised in 15 domains from data governance to personal data protection. Entities audit their compliance at specification level every year and submit the report to NDMO in the third quarter; specifications are phased in by priority (P1 year 1, P2 year 2, P3 year 3).
Applies to: All public entities (government entities and their affiliates, and companies that run public utilities or national infrastructure or render related public services) and business partners handling government data.
Domains assessed (77 questions)
- Strategy and plan (DG.1 (DG.1.1 – DG.1.4))
- Policy and guidelines (DG.2 (DG.2.1 – DG.2.2))
- Data management training (DG.3 (DG.3.1))
- Data management organization (DG.4 (DG.4.1 – DG.4.11))
- Compliance audit framework (DG.5 (DG.5.1 – DG.5.3))
- Data lifecycle governance (DG.6 (DG.6.1 – DG.6.2))
- Data governance performance management (DG.7 (DG.7.1 – DG.7.2))
- Data governance artifacts (DG.8 (DG.8.1 – DG.8.3))
- Data catalog plan (MCM.1 (MCM.1.1 – MCM.1.3))
- Catalog access approval (MCM.2 (MCM.2.1 – MCM.2.2))
- Data catalog training and adoption (MCM.3 (MCM.3.1 – MCM.3.2))
- Metadata lifecycle management (MCM.4 (MCM.4.1 – MCM.4.7))
- Data catalog automation (MCM.5 (MCM.5.1 – MCM.5.4))
- Catalog and metadata KPIs (MCM.6 (MCM.6.1 – MCM.6.2))
- Data quality plan and assessment (DQ.1 (DQ.1.1 – DQ.1.3))
- Data quality operations (DQ.2 (DQ.2.1 – DQ.2.5))
- Data quality KPIs (DQ.3 (DQ.3.1 – DQ.3.2))
- Data quality in the lifecycle (DQ.4 (DQ.4.1 – DQ.4.3))
- Data operations plan (DO.1 (DO.1.1 – DO.1.4))
- Storage and retention policy (DO.2 (DO.2.1))
- Database operations (DO.3 (DO.3.1 – DO.3.5))
- Business continuity (DO.4 (DO.4.1 – DO.4.3))
- Storage KPIs (DO.5 (DO.5.1))
- Document and content plan (DCM.1 (DCM.1.1 – DCM.1.4))
- Document and content policy (DCM.2 (DCM.2.1))
- Document management training (DCM.3 (DCM.3.1))
- Document and content operations (DCM.4 (DCM.4.1 – DCM.4.5))
- Document management KPIs (DCM.5 (DCM.5.1))
- Data architecture plan (DAM.1 (DAM.1.1))
- Data architecture policy (DAM.2 (DAM.2.1))
- Data architecture framework (DAM.3 (DAM.3.1 – DAM.3.5))
- Data modelling definition (DAM.4 (DAM.4.1 – DAM.4.2))
- Architecture change and checkpoints (DAM.5 (DAM.5.1 – DAM.5.2))
- Data architecture KPIs (DAM.6 (DAM.6.1))
- Data architecture register (DAM.7 (DAM.7.1))
- Data integration plan (DSI.1 (DSI.1.1 – DSI.1.3))
- Data sharing training (DSI.2 (DSI.2.1))
- Integration solution lifecycle (DSI.3 (DSI.3.1 – DSI.3.4))
- Data processes (ETL/ELT) (DSI.4 (DSI.4.1 – DSI.4.2))
- Data sharing process (DSI.5 (DSI.5.1))
- Data sharing request channel (DSI.6 (DSI.6.1))
- Data sharing agreements (DSI.7 (DSI.7.1 – DSI.7.3))
- Data sharing KPIs (DSI.8 (DSI.8.1))
- Reference and master data plan (RMD.1 (RMD.1.1 – RMD.1.4))
- RMD architecture (RMD.2 (RMD.2.1 – RMD.2.5))
- RMD training (RMD.3 (RMD.3.1))
- RMD lifecycle management (RMD.4 (RMD.4.1 – RMD.4.4))
- RMD performance management (RMD.5 (RMD.5.1 – RMD.5.2))
- RMD artifacts (RMD.6 (RMD.6.1 – RMD.6.2))
- BI and analytics plan (BIA.1 (BIA.1.1 – BIA.1.4))
- BI and analytics training (BIA.2 (BIA.2.1 – BIA.2.2))
- Use case validation (BIA.3 (BIA.3.1 – BIA.3.2))
- BI and analytics KPIs (BIA.4 (BIA.4.1))
- BI and analytics register (BIA.5 (BIA.5.1))
- Data value realization plan (DVR.1 (DVR.1.1 – DVR.1.2))
- Data revenue generation process (DVR.2 (DVR.2.1 – DVR.2.4))
- DVR monitoring and maintenance (DVR.3 (DVR.3.1))
- DVR KPIs (DVR.4 (DVR.4.1))
- Open data plan (OD.1 (OD.1.1))
- Open data awareness (OD.2 (OD.2.1))
- Open data lifecycle (OD.3 (OD.3.1 – OD.3.6))
- Open data KPIs (OD.4 (OD.4.1))
- Open data register (OD.5 (OD.5.1))
- Freedom of information plan (FOI.1 (FOI.1.1))
- FOI awareness (FOI.2 (FOI.2.1))
- FOI request lifecycle (FOI.3 (FOI.3.1 – FOI.3.6))
- FOI register (FOI.4 (FOI.4.1))
- Data classification plan (DC.1 (DC.1.1 – DC.1.2))
- Classification handling controls (DC.2 (DC.2.1))
- Classification process (DC.3 (DC.3.1 – DC.3.5))
- Classification KPIs (DC.4 (DC.4.1))
- Data classification register (DC.5 (DC.5.1))
- Personal data protection plan (PDP.1 (PDP.1.1 – PDP.1.2))
- Personal data protection training (PDP.2 (PDP.2.1))
- Data breach (PDP.3 (PDP.3.1 – PDP.3.2))
- Personal data lifecycle (PDP.4 (PDP.4.1 – PDP.4.4))
- Personal data protection register (PDP.5 (PDP.5.1))
Communications, Space & Technology Commission (CST)
Cybersecurity Regulatory Framework for ICT Service Providers
Sector framework for service providers licensed or registered by CST. Non-CNI providers implement the CRF controls at the compliance level CST assigns (CL1–CL3); CNI providers follow NCA ECC and share compliance reports and incidents with CST.
Applies to: Telecom, internet, postal and ICT service providers licensed or registered by CST.
Domains assessed (32 questions)
- Cybersecurity strategy (Strategy)
- Cybersecurity function (Management)
- CRF compliance and CST reporting (Compliance)
- Cybersecurity audit (Audit)
- Staff awareness and training (Awareness & Training)
- Customer awareness (Customer Cybersecurity Awareness)
- Security in projects (Cybersecurity in Project Management)
- Security in HR (Cybersecurity in Human Resources)
- Asset discovery and inventory (Asset Discovery)
- Asset classification (Asset Classification)
- BYOD and acceptable use (BYOD · Acceptable Use)
- Maintenance and secure disposal (Asset Maintenance · Secure Disposal)
- Risk assessment (Risk Assessment)
- Risk treatment and monitoring (Risk Treatment & Monitoring)
- Cryptography (Cryptography)
- Change management (Change Management)
- Vulnerabilities and patching (Vulnerability Management · Patch Management)
- Network security (Network Security)
- Logging and monitoring (Logging & Monitoring)
- Identity and access (Identity & Access Management)
- Malware defense (Application Whitelisting · Malware Handling)
- Incident management (Incident Management)
- Information protection (Information Protection)
- Backup and recovery (Backup & Recovery)
- Secure configuration (Configuration Management & Hardening)
- Secure development (Secure Software Development)
- Email and browser protection (Email & Web Browser Protection)
- Penetration testing (Penetration Testing)
- Physical asset protection (Protection of Physical Information Assets)
- Physical access (Physical Access Management)
- Cloud services security (Cloud Services)
- Outsourcing security (Outsourcing Services)
Cloud Computing Services Provisioning Regulations (formerly Cloud Computing Regulatory Framework)
CST rules for cloud computing services in the Kingdom: CSP registration with CST, subscriber data classification and location, breach notification, subscriber data protection, unlawful content, minimum contract terms, liability, quality and continuity. It replaced the Cloud Computing Regulatory Framework v3 and applies together with the Guide for Cloud Computing Service Providers v5.
Applies to: Cloud service providers serving subscribers resident or addressed in the Kingdom, and any CSP processing or storing subscriber content in Saudi data centers; CSPs controlling a data center or core cloud infrastructure in the Kingdom must register with CST. Cloud subscribers must classify their data, keep government data in the Kingdom with registered CSPs, and comply with NCA, NDMO and SAIP rules.
Domains assessed (41 questions)
- Applicability determination (3-1-1 – 3-1-4)
- Registration before operating (3-2-1)
- Registration file and renewal (3-2-2; Guide 3-1 (1–8), 3-2 (11–13), 3-3)
- Category technical standards (Guide 3-2 (9); 3-8-3)
- NCA controls compliance (Guide 3-2 (10))
- Qualifying category registration (3-2-3; Qualifying Category Guide)
- Subscriber data classification (3-3-1, 3-3-4)
- Sector outsourcing rules (3-3-2)
- Exclusion of commercial data (3-3-3)
- Notifying the registration category (3-3-5)
- Government data stays in the Kingdom (3-3-6)
- Registered CSP for shared government data (3-3-7)
- Consent for data outside the Kingdom (3-3-8)
- Breach notification (3-3-9)
- Insurance coverage disclosure (3-3-10)
- No disclosure of subscriber data (3-4-1; 3-4-2-1)
- Purpose limitation and access powers (3-4-2-2)
- Lawful exceptions and consent (3-4-3)
- Subscriber data rights (3-4-4, 3-4-5)
- Stricter data protection rules (3-4-6)
- Removing content on official request (3-5-1 – 3-5-4)
- Voluntary removal and subscriber notice (3-5-5, 3-5-8)
- Reporting unlawful content (3-5-6)
- Complaints and cooperation (3-5-7, 3-5-9)
- Software licenses for subscribers (3-5-10)
- Pre-contract transparency (3-6-1, 3-6-2)
- Minimum contract content (3-6-3)
- Customer care and disputes (3-6-4, 3-6-5)
- Data return at termination (3-6-6)
- Liability for agents and subcontractors (3-7-1)
- No unfair liability exclusions (3-7-2, 3-7-3)
- Customer evidence and liability limits (3-7-4, 3-7-5)
- SLA and certification transparency (3-8-1)
- Continuity and risk summaries (3-8-2)
- Content filtering exclusion (3-9-1, 3-9-2)
- Reports and information to CST (3-10-1, 3-10-2)
- Cooperation with CST inspections (3-10-3)
- Tracking CST guidance and decisions (3-10-4, 3-10-5)
- Compliance with national authorities (3-11-1)
- Conflicting foreign laws and requests (3-11-2)
- Service continuity management (3-11-3)
Saudi Central Bank (SAMA)
SAMA Cyber Security Framework
Principle-based cyber security framework of the Saudi Central Bank that sets the cyber security controls and maturity model for financial institutions regulated by SAMA. Member Organizations must operate at maturity level 3 or higher (level 4 for banks).
Applies to: All Member Organizations regulated by SAMA: banks, insurance and/or reinsurance companies, financing companies and credit bureaus operating in Saudi Arabia, and the financial market infrastructure; the Rulebook also applies it to payment systems and payment service providers and regulatory sandbox participants. All subdomains apply to banks; non-bank institutions are exempt from 3.2.3, 3.3.12 and 3.3.13 (with conditions).
Domains assessed (40 questions)
- Cyber security committee (3.1.1 (1–4))
- Independent cyber security function and CISO (3.1.1 (5–10))
- Cyber security strategy (3.1.2 (1–3))
- Cyber security policy (3.1.3 (1–4))
- Cyber security roles and responsibilities (3.1.4 (1–6))
- Cyber security in project management (3.1.5 (1–2))
- Cyber security awareness (3.1.6 (1–7))
- Cyber security training (3.1.7 (1–2))
- Cyber security risk management (3.2.1 (1–11))
- Risk identification and analysis (3.2.1.1 (1–3); 3.2.1.2 (1–2))
- Cyber security risk response (3.2.1.3 (1–7))
- Cyber risk monitoring and review (3.2.1.4 (1–2))
- Regulatory compliance (3.2.2 (1))
- Compliance with industry standards (3.2.3 (1))
- Cyber security review (3.2.4 (1–5))
- Cyber security audits (3.2.5 (1–2))
- Human resources (3.3.1 (1–3))
- Physical security (3.3.2 (1–3))
- Asset management (3.3.3 (1–3))
- Cyber security architecture (3.3.4 (1–3))
- Identity and access management (3.3.5 (1–3, 4.a–4.d))
- MFA and privileged access (3.3.5 (4.e–4.f))
- Application security (3.3.6 (1–5))
- Change management (3.3.7 (1–4))
- Infrastructure security (3.3.8 (1–5, 6.a–6.g, 6.i–6.j))
- DDoS protection (3.3.8 (6.h))
- Cryptography (3.3.9 (1–4))
- Bring your own device (BYOD) (3.3.10 (1–4))
- Secure disposal of information assets (3.3.11 (1–6))
- Payment systems (3.3.12 (1–2))
- Electronic banking services (3.3.13 (1–3, 4.a–4.b))
- ATM, POS and SMS notifications (3.3.13 (4.c–4.d))
- Cyber security event management (3.3.14 (1–4))
- Cyber security incident management (3.3.15 (1–4))
- Incident reporting to SAMA (3.3.15 (5–7))
- Threat management (3.3.16 (1–3))
- Vulnerability management (3.3.17 (1–3))
- Contract and vendor management (3.4.1 (1–6))
- Outsourcing (3.4.2 (1–3))
- Cloud computing (3.4.3 (1–4))
SAMA Business Continuity Management Framework
Saudi Central Bank requirements for initiating, implementing, maintaining, monitoring and improving business continuity and IT disaster recovery, based on ISO 22301, ISO 27001, BCI and DRII practices. Member Organizations must integrate the requirements formally into their BCM program.
Applies to: All organizations affiliated with SAMA (Member Organizations), all banks operating in Saudi Arabia, banking subsidiaries of Saudi banks and subsidiaries of foreign banks in Saudi Arabia; the SAMA Rulebook lists its scope as the banking sector, finance sector, payment systems and payment service providers, and credit bureaus. It covers the full scope of the organization, including subsidiaries, staff, subcontractors, third parties and customers.
Domains assessed (19 questions)
- BCM governance and committee (2.1 (1–5))
- BCM function and manager (2.1 (6–9))
- BCM strategy (2.2 (1–2))
- Business continuity policy (2.3 (1–5))
- Business impact analysis (2.4 (1, 3, 4, 6, 9))
- Business continuity risk assessment (2.4 (2, 5, 7, 8))
- Business continuity plan (2.5 (1–5))
- Alternate workspace and provider continuity (2.5 (6–8, 10))
- IT disaster recovery plan and DR site (2.6 (1–4, 8–10))
- Backup, offsite storage and DR contracts (2.6 (5–7))
- Cyber resilience (2.7 (1–2))
- Crisis management plan (2.8 (1–4))
- BCP testing (2.9.1 (1–4))
- DRP testing (2.9.2 (1–4))
- Executed tests and results (2.9.3 (1–4))
- Awareness and training (2.10 (1–3))
- Communication with SAMA (2.11 (1–5))
- Periodic document review (2.12 (1–2))
- BCM assurance (2.13 (1–3))
Capital Market Authority (CMA)
Cybersecurity Guidelines for Capital Market Institutions
CMA cybersecurity controls for capital market institutions supervised by the Capital Market Authority, built on NCA controls, the SAMA framework, NIST and ISO. Implementation is subject to periodic self-assessment, review and audit under a mechanism set by CMA.
Applies to: All capital market institutions licensed and supervised by CMA (e.g. Authorised Persons); CMA may apply the guidelines to any entity under its supervision. NCA ECC also applies and is mandatory for institutions that fall within the ECC scope.
Domains assessed (60 questions)
- Independent cybersecurity department (4.1.1 (1–2))
- Cybersecurity budget and roles review (4.1.1 (3–4))
- Cybersecurity committee (4.1.1 (5–8))
- Board responsibilities (4.1.1 (9))
- Head of Cybersecurity duties (4.1.1 (10))
- Internal audit and staff responsibility (4.1.1 (11–12))
- Data governance program (4.1.2 (1–3))
- Data classification and privacy (4.1.2 (4–5))
- Sensitive data control and measurement (4.1.2 (6–7))
- Data governance workflows (4.1.2 (8–9))
- Cybersecurity strategy (4.1.3 (1–3))
- Cybersecurity policies and standards (4.1.3 (4–7))
- Cybersecurity awareness program (4.1.4 (1–4))
- Program evaluation and specialist training (4.1.4 (5–6))
- Human resources cybersecurity (4.1.5 (1–3))
- Risk management methodology (4.2.1 (1–5))
- Risk assessment triggers (4.2.1 (6))
- Risk register and treatment (4.2.1 (7–9))
- Periodic cybersecurity review (4.2.2 (1–2))
- Independent cybersecurity audit (4.2.2 (3–4))
- Cybersecurity architecture (4.3.1 (1–2))
- Infrastructure security controls (4.3.2 (1–3))
- Email security (4.3.2 (4))
- Core infrastructure protections (4.3.2 (5))
- Secure change management (4.3.3 (1–2))
- Cybersecurity in project management (4.3.3 (3–5))
- Vulnerabilities and hardening in changes (4.3.3 (6))
- Access management policy (4.3.4 (1–2))
- Access control and privileged access (4.3.4 (3))
- Asset inventory and classification (4.3.5 (1–2))
- Acceptable use policy (4.3.5 (3))
- Secure disposal standards (4.3.6 (1–4))
- Disposal execution and third parties (4.3.6 (5–7))
- Incident management process (4.3.7 (1–4))
- Reporting incidents to CMA (4.3.7 (5–7))
- Security event log management (4.3.8 (1–6))
- Security operations center (4.3.8 (7))
- Major incident crisis handling (4.3.8 (8))
- Threat intelligence management (4.3.9 (1–3))
- Application security controls and SDLC (4.3.10 (1–4))
- Application security measures (4.3.10 (5))
- Encryption standards (4.3.11 (1–4))
- Vulnerability management (4.3.12 (1–3))
- E-trading security controls (4.3.13 (1–3))
- E-trading customer protection (4.3.13 (4))
- Physical security controls (4.3.14 (1, 2, 6))
- Power, fire and disaster protection (4.3.14 (3–5))
- Business continuity policy (4.3.15 (1–3))
- BIA and continuity strategy (4.3.15 (4–6))
- Crisis team and continuity plan (4.3.15 (7–8))
- BCP and DR testing (4.3.15 (9))
- Continuity training (4.3.15 (10–11))
- BYOD security (4.3.16 (1–4))
- Supplier cybersecurity controls (4.4.1 (1–3))
- Security in contracts (4.4.1 (4–5))
- Supplier SLA security reporting (4.4.1 (6))
- Outsourcing security controls (4.4.2 (1–3))
- Outsourcing compliance and SOC location (4.4.2 (4–5))
- Cloud computing policy (4.4.3 (1–3))
- Cloud service approval and terms (4.4.3 (4))
Digital Government Authority (DGA)
Digital Government Controls and Standards (IT Governance, Risk & Business Continuity, Digital Transformation)
Mandatory DGA controls for IT governance and for risk management and business continuity in digital government, plus the security-, hosting- and resilience-related Digital Transformation Basic Standards measured in the annual Qiyas assessment. DGA measures compliance; cybersecurity controls are left to NCA and data and privacy to SDAIA/NDMO.
Applies to: All government entities and operating entities that provide digital government services and products, regardless of type, size or nature (applied in proportion to their environment, complexity and locations).
Domains assessed (49 questions)
- Operations management (5-108-01 – 5-108-05 (7.1.1))
- IT policies and procedures (5-108-06 – 5-108-08 (7.1.2))
- Roles and responsibilities (5-108-09 (7.1.3))
- IT risk management (5-108-10 – 5-108-19 (7.1.4))
- IT capabilities and competencies (5-108-20 – 5-108-23 (7.1.5))
- IT strategy and technical architecture (5-108-24 – 5-108-29 (7.2.1 – 7.2.2))
- Service levels and outsourcing (5-108-30 – 5-108-39 (7.2.3))
- Systems and applications procurement (5-108-40 – 5-108-44 (7.3.1))
- Configuration management (5-108-45 – 5-108-47 (7.3.2))
- Change management (5-108-48 – 5-108-56 (7.3.3))
- Systems development (5-108-57 – 5-108-66 (7.3.4))
- Digital assets and data centers (5-108-67 – 5-108-75 (7.3.5))
- IT project management (5-108-76 – 5-108-79 (7.3.6))
- Service availability and capacity (5-108-80 – 5-108-84 (7.3.7))
- Backup service management (5-108-85 – 5-108-90 (7.4.1))
- Reliability and interconnection (5-108-91 – 5-108-93 (7.4.2))
- Network infrastructure (5-108-94 – 5-108-96 (7.4.3))
- Virtualization software (5-108-97 – 5-108-100 (7.4.4))
- Batch data processing (5-108-101 – 5-108-105 (7.4.5))
- Performance management (5-108-106 – 5-108-109 (7.5.1))
- IT internal audit and compliance (5-108-110 – 5-108-120 (7.5.2 – 7.5.3))
- Risk management governance (05-107-01 – 05-107-04 (7.1.1); DTS 5.9.1)
- Risk management strategy (05-107-05 – 05-107-07 (7.1.2))
- Risk framework and procedures (05-107-08 – 05-107-14 (7.1.3))
- Risk appetite and tolerance (05-107-15 (7.1.4))
- Risk assessment and treatment (05-107-16 – 05-107-24 (7.2.1 – 7.2.2); DTS 5.9.2)
- Risk review and reporting (05-107-25 – 05-107-27 (7.2.3); DTS 5.9.3)
- Risk training and awareness (05-107-28 – 05-107-31 (7.3.1); DTS 5.9.4)
- Risk management improvement (05-107-32 – 05-107-37 (7.3.2); DTS 5.9.5)
- Business continuity system (05-107-38 – 05-107-44 (8.1.1); DTS 5.10.1)
- Business continuity training (05-107-45 – 05-107-48 (8.1.2); DTS 5.10.2)
- Business impact analysis (05-107-49 – 05-107-64 (8.2.1); DTS 5.10.3)
- Business continuity strategies (05-107-65 – 05-107-68 (8.2.2); DTS 5.10.4)
- Business continuity plans (05-107-69 – 05-107-70 (8.2.3); DTS 5.10.5)
- ICT disaster recovery (05-107-71 – 05-107-75, 05-107-78 – 05-107-81 (8.2.4); DTS 5.10.5)
- Outage reporting to DGA (05-107-76 – 05-107-77 (8.2.4))
- Incident response plans (05-107-82 – 05-107-85 (8.2.5))
- Continuity exercises and tests (05-107-86 – 05-107-89 (8.3.1); DTS 5.10.6)
- BC documentation and improvement (05-107-90 – 05-107-92 (8.4.1); DTS 5.10.7)
- Government email (DTS 5.11.5 (req. 2–3))
- IT service management framework (DTS 5.12.1)
- IT service management operations and hosting (DTS 5.12.2 – 5.12.3)
- Cloud unit and adoption plan (DTS 5.13.1 – 5.13.2)
- Cloud environment operation (DTS 5.13.3)
- National single sign-on and shared services (DTS 5.14.2)
- Digital trust services (DTS 5.14.4)
- Platforms and government domains (DTS 5.15.1, 5.15.3)
- Website reliability and security (DTS 5.21.1)
- Privacy notice and terms of use (DTS 5.22.1 (req. 1))
Ministry of Health and health-sector authorities
Saudi Health Information Exchange Policies (IS0303)
Privacy and security policies of the Saudi Health Information Exchange (SeHE): nine policies on purpose of use, information security, patient rights, identity management, authentication, consent and access control, audit, breach notification and secondary use of personal health information. Some technical values are dated (e.g. 3DES, TLS 1.0, ISO 27799:2008) and should be read together with current NCA controls.
Applies to: Participating Healthcare Subscribers (healthcare organizations connected to the SeHE), their business associates and subcontractors, and SeHE system service providers, for all personal health information provided to or retrieved from the exchange.
Domains assessed (50 questions)
- Permitted purposes of use (§3.3.1 – §3.3.2; §5.3(14))
- Prohibited uses (§3.3.3)
- Minimum security protections (§4.3(1))
- Security management framework (§4.3(2), §4.3(4))
- Data integrity and retention (§4.3(3), §4.3(6))
- Contingency and disaster recovery (§4.3(5), §4.3(12))
- Encryption of communications (§4.3(7))
- Intrusion detection (§4.3(8))
- Privacy and confidentiality training (§4.3(9))
- Privacy and security officer (§4.3(10))
- Personnel sanction policy (§4.3(11))
- Patient access to health information (§5.3(1))
- Protection and disclosure limits (§5.3(6), §5.3(14))
- Breach complaints by patients (§5.3(8))
- Report of electronic disclosures (§5.3(9))
- Opt-out requests (§5.3(10) – §5.3(13))
- Patient information and special notice (§5.3(2) – §5.3(4))
- Organization system certificates (§6.3(1), §6.3(3))
- User identity proofing (§6.3(2), §6.3(5.1) – §6.3(5.2))
- Role-specific proofing (§6.3(5.2.1) – §6.3(5.2.6))
- Organization node proofing (§6.3(6))
- Credential agreements (§6.3(7), §6.3(10))
- Account revocation and updates (§6.3(8) – §6.3(9))
- Compromised credentials (§6.3(11))
- Emergency (break-glass) access (§7.3(1))
- Automatic logoff (§7.3(2))
- Node authentication (§7.3(3))
- Multi-factor authentication (§7.3(4) – §7.3(5))
- Unique identification (§7.3(6.3) – §7.3(6.4), §7.3(7))
- Credential verification (§7.3(8) – §7.3(9))
- Access control testing (§8.3(1))
- Consent verification (§8.3(2) – §8.3(3), §8.3(8))
- Information flows and local policies (§8.3(4) – §8.3(5))
- Opted-out patients (§8.3(6) – §8.3(7), §8.3(14))
- Sensitive health information (§8.3(9) – §8.3(13))
- Role-based access (§8.3(15))
- Portal agreements and compliance policies (§8.3(16), §8.3(18))
- Audit recording of PHI activity (§9.3(1) – §9.3(3))
- Logon and disclosure audit content (§9.3(4) – §9.3(5))
- Log generation and review (§9.3(6) – §9.3(8))
- Audit inquiries and external auditors (§9.3(9) – §9.3(10))
- Time synchronization (§9.3(13))
- Protection of audit logs (§9.3(14) – §9.3(15))
- Suspicious activity investigation (§10.3.1)
- Reportable event notification (§10.3.2)
- Breach mitigation cooperation (§10.3.3(3.3), §10.3.3(4))
- Breach notification to individuals (§10.3.4(2) – §10.3.4(5))
- Ethics approval for secondary use (§11.3(1) – §11.3(2.3))
- Data use agreements (§11.3(2.6))
- De-identified data release (§11.3(3))
Penalties
Maximum penalties under the Personal Data Protection Law and the Anti-Cyber Crime Law (Royal Decree M/17, 1428H). This is for information only, not legal advice.
| Law | Violation | Imprisonment | Fine |
|---|---|---|---|
| PDPL Art. 35(1) | Disclosing or publishing sensitive personal data in violation of the law, with intent to harm the data subject or for personal benefit | Up to 2 years | Up to SAR 3,000,000 Either or both; the court may double the fine for repeat offences. |
| PDPL Art. 36(1) | Any other violation of the PDPL or its regulations (e.g. no legal basis, missing security measures, late breach notification, unlawful transfers) | — | Warning or up to SAR 5,000,000 Imposed by an SDAIA committee; may be doubled for repeat violations. |
| Anti-Cyber Crime Law Art. 3 | Unlawful interception, unauthorized access to threaten or blackmail, defacing websites, invading privacy through devices, defamation via IT | Up to 1 year | Up to SAR 500,000 Either or both. |
| Anti-Cyber Crime Law Art. 4 | Fraud through IT, unauthorized access to bank, credit or securities data | Up to 3 years | Up to SAR 2,000,000 Either or both. |
| Anti-Cyber Crime Law Art. 5 | Unauthorized access to delete, leak, destroy or alter private data; disrupting networks or services (e.g. denial of service) | Up to 4 years | Up to SAR 3,000,000 Either or both. |
| Anti-Cyber Crime Law Art. 6 | Producing or distributing content harmful to public order, religious values, public morals or privacy | Up to 5 years | Up to SAR 3,000,000 Either or both. |
| Anti-Cyber Crime Law Art. 7 | Supporting terrorist organizations online; unauthorized access to data affecting state security or the national economy | Up to 10 years | Up to SAR 5,000,000 Either or both. |
Key obligations and timelines
Incident and breach reporting
- ECC-2:2024 (2-13-3-3/4) and NCNICC (2-13-1-2/3): report cybersecurity incidents to NCA and share threat intelligence and IoCs. The reporting channel is the NCA Haseen portal.
- PDPL Art. 20 and Implementing Regulation Art. 24: notify SDAIA within 72 hours of becoming aware of a personal data breach, and notify affected individuals when harm is likely.
- CST CRF: CNI service providers report incidents to NCA immediately and notify CST.
Useful official links
- NCA – Essential Cybersecurity Controls (ECC-2:2024)
- NCA – NCNICC-1:2025 (Arabic)
- NCA – Report an incident · Haseen portal
- CST – Cybersecurity Regulatory Framework
- Bureau of Experts – Personal Data Protection Law
- Bureau of Experts – Anti-Cyber Crime Law
- SDAIA – Data governance platform (PDPL regulations)