NCA ECC vs ISO 27001
An information security management system can support ECC evidence, but the Saudi control requirements still need their own assessment.
NCA's ECC-2:2024 is a mandatory cybersecurity baseline for entities within its scope. ISO/IEC 27001:2022 defines an information security management system that can be certified. Their evidence overlaps, but an ISO certificate does not establish ECC compliance. Map the applicable ECC controls to the system and assess the remaining gaps.
Updated
A control baseline and a management system
ECC sets cybersecurity controls for entities within NCA's scope. ISO/IEC 27001 sets requirements for establishing and maintaining an information security management system, or ISMS. It uses a risk management process to protect information. These are different requirements to assess, even where the same record supports both.
For the buyer, the practical distinction is the question being answered. An ISO assessment examines conformity with the management system standard. An ECC review asks whether the applicable national controls have been implemented. Keep those questions separate in the assessment while sharing the documents and records that answer them.
Start with the written request. If it names both, create a requirement list that names both. If it names only one, establish whether the other applies independently before setting the scope. A supplier questionnaire is useful evidence of a customer's request, but it is not a substitute for assessing NCA applicability.
Who asks for each
ECC applies to Saudi government agencies and their affiliated companies and entities, and private entities owning, operating or hosting critical national infrastructure. Other organisations may encounter ECC requirements in a contract. ISO 27001 certification can provide assurance to customers; read the customer's clause to establish the requested scope.
NCA encourages other entities in the Kingdom to adopt ECC. Distinguish that encouragement from a direct obligation and from a contract condition. Record the reason for your assessment so the next reviewer can see why the controls were included.
For an ISO request, put the service and sites named by the customer beside your ISMS scope. Ask whether the information and activities behind the contract sit inside that boundary. Do the same exercise separately for ECC rather than assuming the certificate's scope defines the national control obligation.
The differences that change the work
The main differences are scope, how controls are selected and how conformity is demonstrated. ISO 27001 provides a management system and a Statement of Applicability. ECC requires compliance with every applicable control. One register can map the evidence, but it should retain the separate requirement and assessment result for each.
Use full control references in the mapping. A row labelled access control is too broad to show which requirement was checked, which evidence was sampled or what remains open.
| Point to compare | ECC-2:2024 / ISO/IEC 27001:2022 |
|---|---|
| Purpose | ECC: a national cybersecurity baseline. ISO 27001: an information security management system. |
| Scope | ECC: the entities and applicable controls defined by NCA. ISO 27001: the documented ISMS boundary and its activities. |
| Applicability | ECC: implement all applicable controls. ISO 27001: record control applicability and justification in the Statement of Applicability. |
| Assessment | ECC: NCA self-assessment, compliance-tool reporting and field audits. ISO 27001: management system assessment, with certification available. |
| Organisational structure | ECC 1-2-1: cybersecurity department independent of IT and communications. Check this explicitly alongside the ISMS roles. |
| Staffing | ECC 1-2-2: full-time, qualified Saudi cybersecurity professionals in cybersecurity positions. An ISO certificate does not evidence this staffing decision. |
| Shared evidence | Risk records, asset and access records, incident plans, continuity evidence and supplier assessments are starting points for mapping, not automatic equivalences. |
Reuse the record after checking it
The overlap includes risk management, assets, access, cryptography, monitoring, incidents, continuity and supplier security. Reuse evidence when it answers the actual requirement on both sides. A policy title alone does not show that the process ran or that the right assets and people were covered.
An access review is a useful example. Open the review record, check which systems it includes, who approved changes and whether actions closed. Link that record to the relevant requirements. If the ECC assessment includes a system outside the sampled set, the record does not close that gap just because it is called an access review.
Keep one evidence reference with separate assessment columns. Record the period and scope examined, who reviewed it and the unresolved work. This makes a shared file useful without turning a mapping exercise into an unsupported claim of conformity.
What an ISO-certified organisation still needs
An organisation holding ISO 27001 should assess ECC applicability and map every applicable ECC control to evidence. It should then address gaps in scope, implementation and organisational requirements. The independent cybersecurity department and Saudi staffing controls deserve explicit review because a policy document cannot establish that either exists.
Bring the scope statement, risk assessment and Statement of Applicability into the review. Add the evidence index and open corrective actions. These are useful inputs, but a certificate is not a completed ECC control register. Leave a control open where the evidence has not been examined.
Separate a missing record from a missing organisational decision. The first may need the process owner to retrieve evidence. The second may need management to change a reporting line or approve a role. Put the decision and responsible role into the gap register so it reaches the person who can act.
An ECC programme still needs the ISMS review
An ECC programme can supply security records for an ISO 27001 project. It still needs assessment against the management system requirements, including its scope, risk method, Statement of Applicability, internal audit and management review. An ECC control register is useful input; it is not the whole ISMS.
Check whether the existing risk process covers the intended ISMS boundary. Review who accepts risk, how treatment decisions are recorded and how changes are followed up. Reuse the approved process where it fits, and keep a clear record of any change needed for the new scope.
Then plan the internal audit against the standard and the actual operation. Carry its findings into corrective action and management review. The value of the existing ECC work is the evidence it provides, not a shortcut past reviewing the system that manages it.
Keep certification and ECC reporting distinct
ISO 27001 certification and NCA's ECC compliance mechanisms answer different requirements. NCA describes self-assessment, compliance-tool reports and field audits. The site's ECC guidance explains that there is no ECC certificate. Keep the assessment output and the recipient clear when you commission readiness work.
Ask for a control register showing the evidence examined and the gaps still open. A report that only says aligned gives the next reviewer little to check. A useful register shows the full reference, the evidence location and the reason for the assessment result.
A supplier receives an ECC clause
Consider an ISO-certified supplier receiving a contract clause naming ECC. We would first establish the requested activities and the basis for applicability, then compare them with the ISMS scope. This is an illustrative readiness review, not a completed engagement or a claim that every supplier is directly bound by ECC.
We would sample the existing risk register, access reviews and supplier assessments, mapping only the evidence that answers the relevant controls. A gap affecting reporting lines would go to management. A missing service or system in the evidence would go to its process owner.
The proposed outputs are an applicability note, a control mapping and a gap register with responsible roles. ITF Consult handles the management system; ITF Cyber supports the policies, control mapping and readiness evidence. The organisation can then see what it already has and what remains to be implemented.
What to bring to the review
Bring the request that triggered the comparison and the records you currently rely on. The first useful output is a scope comparison, followed by a mapped evidence index. Avoid starting with a new policy pack before checking what the existing system already does and what the requirement actually asks.
Use this short list to prepare the review. An unavailable document becomes a question to resolve, not a reason to assume the control is absent or present.
- The customer clause and the recorded basis for ECC applicability
- The ISMS scope and Statement of Applicability
- The risk assessment, treatment plan and evidence index
- The organisational chart and assigned cybersecurity roles
- The latest internal audit findings and management review actions
Questions before mapping the two
Does ISO 27001 certification satisfy ECC?
It provides a system and evidence to examine. ECC compliance still needs assessment against all applicable controls and the relevant scope.
Can we use the same policies?
Yes, where they answer both requirements and match how the organisation works. Keep the control references and evidence links so reviewers can check each obligation separately.
Can the Statement of Applicability exclude an ECC control?
An ISO control justification does not remove an applicable ECC requirement. Assess ECC applicability on its own basis and retain the reason for the decision.
Which should we start with?
Start with the obligation and the evidence you already hold. Where both apply, build the management system and ECC mapping together, with the remaining work assigned to responsible roles.
Is readiness a certificate?
Readiness work produces a reviewed scope, requirement mapping and gap register. ISO certification and NCA compliance assessment remain separate processes with their own evidence requirements.
Read next
NCA ECC readiness
Build the control register and evidence plan.
Read moreITF ConsultISO 27001 readiness
Scope, risk assessment and the management system records.
Read moreGuideNCA ECC-2:2024 explained
Read the control structure and the applicability boundary.
Read moreITF CyberPolicies and governance
Assign responsibilities and connect policies to working records.
Read morePart of one system
Every division keeps records to the same standard, so the second one you need works the way the first one did.
Map the requirement to evidence you can open
Bring the written request and your existing ISMS records so the review can identify the work still needed.