What Is NCNICC?

NCNICC-1:2025, the Non-CNI Private Sector Entities Cybersecurity Controls, sets the National Cybersecurity Authority's minimum cybersecurity requirements for small, medium and large private companies in Saudi Arabia that are not classified as critical national infrastructure.

Issued on 28 December 2025, the controls were developed on the basis of the Essential Cybersecurity Controls (ECC) to provide a version better suited to these companies. In practice, this brings a defined NCA baseline to a part of the economy that ECC, which targets government entities and critical infrastructure, was not written for.

0
Main Components
0
Subcomponents
0
Main Controls

The figures above are the full set that applies to large entities. Small and medium entities have a shorter mandatory list of 26 main controls. The Arabic text published by the NCA is the authoritative version, so use it as your final reference when you interpret any control.

Who Must Comply?

Two questions decide your position: which size category you fall into, and whether the NCA has notified your entity. The controls are mandatory for private entities notified by the Authority, and the NCA can require additional controls from an entity whenever it sees the need.

Entity Definition Position
Category A: Large More than 250 full-time employees, or more than SAR 200 million in annual revenue 65 controls if notified
Category B: Small & Medium 6 to 249 full-time employees, or SAR 3 million to SAR 200 million in annual revenue 26 controls if notified
Other private entities in the Kingdom Entities outside the controls' scope, including those not notified Best practice
Micro entities Excluded from the definition of an in-scope entity Out of scope
Government & critical infrastructure Covered by ECC and other NCA frameworks, not NCNICC ECC instead

Even if you have not been notified, the text says entities outside its scope bear the responsibility of benefiting from the controls as appropriate. Treating them as your baseline now also leaves you ready if a notification arrives.

The 3 Main Components

The controls are grouped into three main components with 22 subcomponents between them. Most subcomponents follow the same pattern: define and approve the requirements, implement them, then review them periodically.

01
Cybersecurity Governance
Five subcomponents: cybersecurity management, policies and procedures, risk management, periodic review and audit, and awareness and training.
5 Subcomponents
02
Cybersecurity Defense
Fifteen subcomponents, from asset and access management to email, networks, data, backups, vulnerabilities, penetration testing, monitoring, incidents and web applications.
15 Subcomponents
03
Third-Party & Cloud
Two subcomponents: security terms in third-party contracts, and requirements for cloud computing and hosting services.
2 Subcomponents

The biggest difference between the categories is governance. Category B's mandatory controls all sit in Cybersecurity Defense, while governance, penetration testing, web application security and third-party controls are recommended for Category B. Key examples:

Requirement Category A Category B
Cybersecurity function independent of IT Mandatory Recommended
Full-time, qualified Saudi nationals leading the function Mandatory Recommended
Independent review and audit of controls Mandatory Recommended
Multi-factor authentication for remote access Mandatory Mandatory
Email domain documented through Haseen with SPF, DKIM and DMARC Mandatory Mandatory
Periodic backups and restore testing Mandatory Mandatory
Notifying the NCA of cybersecurity incidents Mandatory Mandatory
Managed SOC from an NCA-licensed provider Mandatory Recommended
Penetration testing of internet-facing services Mandatory Recommended

How to Achieve Compliance

The published text does not set a fixed compliance deadline or grace period. It requires permanent and continuous compliance from entities in scope, so we suggest working through the following order:

7-Step Compliance Roadmap
01
Confirm Your Scope & Category
Check for any NCA notification, then work out your category from your headcount and annual revenue. Confirm that you are not already subject to ECC as critical infrastructure.
Output: scope statement
02
Run a Gap Assessment
Measure current practice against each applicable control, using the Arabic text as the reference. Record each result with supporting evidence, and note recommended controls separately.
Output: gap register
03
Establish Governance
Category A entities must set up a cybersecurity function that reports to the head of the entity and is independent of IT, with approved policies and a risk methodology. Category B entities should adopt what is proportionate, even though it is recommended.
Output: approved policies
04
Close the Defense Gaps
Prioritise the controls shared by both categories: asset inventory, MFA for remote access, malware protection, hardened configurations, email authentication, encryption, backups, patching, logging and physical security.
Output: remediation plan
05
Prepare for Incidents
Define how you will detect, escalate and report incidents, including how you notify the NCA. Large entities also need incident response plans for scenarios such as data breaches and ransomware, plus a licensed managed SOC.
Output: incident procedure
06
Secure Suppliers & Cloud
Add confidentiality and incident communication terms to third-party contracts. Before moving data to the cloud, classify it, and make sure it will be returned in a usable format when the service ends.
Output: updated contracts
07
Test, Audit & Keep Reviewing
Validate your controls with vulnerability scans, penetration tests and a review by a party independent of the cybersecurity function. Then keep the evidence current through periodic reviews.
Ongoing

The Cost of Non-Compliance

Beyond the immediate exposure to attacks, falling short of these controls can create regulatory and commercial consequences.

⚠️

Regulatory Exposure: The NCA assesses compliance by the mechanism it considers appropriate and can require additional controls. Penalties are not set out in NCNICC itself but fall under the NCA's wider statutory framework, so ask your legal adviser how it applies to your entity.

There is also an overlap with the Personal Data Protection Law. If you suffer a personal data breach, the safeguards you had in place will matter, and legal commentary suggests that aligning with NCNICC, including its recommended controls, can help you show due diligence.

How CyberOps Can Help

CyberOps can help you turn NCNICC from a long control list into a manageable plan. We start by confirming your category and running a gap assessment against the controls that apply to you.

From there, our services cover risk assessments, GRC and policy support, vulnerability assessments, penetration testing and security awareness, so you can act on the gaps and keep your evidence ready.

Ready to Prepare for NCNICC?

Book a free consultation with our GRC specialists and get a high-level compliance readiness assessment within 48 hours.

Get in Touch