We e-mail the editable toolkit files to the address you gave, usually within 2 to 3 business days.
Cyber Security

ECC Toolkit: What to Look For in an NCA Essential Cybersecurity Controls Documentation Pack

ECC Toolkit: What to Look For in an NCA Essential Cybersecurity Controls Documentation Pack
In short

Looking for an ECC toolkit? Learn what an NCA Essential Cybersecurity Controls toolkit should contain, how to use it, and what to check before you buy.

In this article
  1. What an ECC toolkit is (and is not)
  2. Who needs to care about ECC
  3. What a good ECC toolkit should include
  4. How to use the toolkit step by step
  5. Mapping documents to evidence
  6. Checks before you rely on a toolkit
  7. Common mistakes
  8. Frequently asked questions

If you are searching for an "ECC toolkit", you are most likely working towards compliance with the Essential Cybersecurity Controls (ECC) issued by the National Cybersecurity Authority (NCA) of Saudi Arabia. The framework expects documented policies, standards, procedures and evidence. Writing all of that from scratch takes time, which is why many teams look for a structured documentation toolkit.

This article explains what an ECC toolkit should include, how to use it without creating paper compliance, and what to check before you rely on one. Always confirm requirements against the latest NCA publication, as the framework has been revised over time.

What an ECC toolkit is (and is not)#

An ECC toolkit is a set of editable documents and templates mapped to the ECC control requirements. It gives you a starting structure: policy wording, procedure outlines, registers, forms and a control-to-document map.

It is not a compliance certificate, an assessment, or a replacement for implementing controls. A policy that says you review privileged access quarterly is only useful if someone actually does it and keeps the records. A toolkit saves drafting time. It does not do the work of operating the controls.

Also note that ECC is a national framework with its own structure. It is not the same as ISO 27001, although the two overlap in many areas. Be wary of a pack that is simply an ISO 27001 set with the name changed.

Who needs to care about ECC#

ECC is aimed at government bodies in Saudi Arabia and at private sector organisations that own, operate or host critical national infrastructure. If you are a supplier or service provider to such organisations, you may also face ECC-aligned requirements through contracts. Check with your customer or the NCA to confirm exactly what applies to you.

What a good ECC toolkit should include#

ECC is organised into main domains, covering cybersecurity governance, defence, resilience, third-party and cloud computing security, and industrial control systems security. A useful toolkit follows that structure so you can trace each document back to a requirement.

Look for these components:

  • A control mapping or compliance matrix linking each ECC requirement to a document, owner and evidence source.
  • Governance documents such as a cybersecurity strategy, roles and responsibilities, risk management methodology, and a policy on cybersecurity in project management.
  • Defence documents covering asset management, identity and access management, system and network security, email protection, mobile device security, cryptography, backup, vulnerability management, penetration testing, event logging and monitoring, and incident management.
  • Resilience documents covering business continuity aspects of cybersecurity and disaster recovery.
  • Third-party and cloud documents, including supplier security requirements and cloud hosting controls.
  • Industrial control systems documents, if relevant to your environment.
  • Registers, forms and logs such as an asset register, risk register, access review record, incident log and training record.
  • Guidance notes explaining how to tailor each template.

How to use the toolkit step by step#

  1. Confirm applicability and scope. Decide which systems, sites and business units are in scope, and whether the ICS or cloud domains apply.
  2. Run a gap assessment first. Compare your current practices to the control matrix. Mark each requirement as in place, partly in place or missing. This prevents you from writing documents for controls you have not implemented.
  3. Assign owners. Every policy and procedure needs a named role responsible for it, not just a department.
  4. Tailor the templates. Replace generic wording with your actual tools, teams, frequencies and approval routes. Delete clauses you cannot honour.
  5. Approve and communicate. Get management approval, publish the documents, and make sure staff know which ones affect them.
  6. Operate and collect evidence. Run the processes and keep records: access reviews, patch reports, backup tests, incident tickets, training attendance.
  7. Review and improve. Schedule periodic reviews and update documents when systems, risks or the framework change.

Mapping documents to evidence#

Assessors and auditors generally look for two things: that a requirement is documented, and that it is being followed. Use a simple table to keep both visible.

AreaTypical documentTypical evidence
GovernanceCybersecurity policy, risk methodologyManagement approval, risk register, committee minutes
Access controlIdentity and access management policyAccess review records, joiner-mover-leaver tickets
OperationsVulnerability and patch procedureScan reports, patch records
MonitoringLogging and monitoring standardLog review records, alert tickets
ResilienceBackup and recovery procedureRestore test results
Third partiesSupplier security requirementsSupplier assessments, contract clauses

Checks before you rely on a toolkit#

  • Version alignment. Ask which version of the ECC the toolkit is based on and whether it has been updated for revisions.
  • Editable formats. You need to change the files, not just read them.
  • Coverage of all applicable domains. A pack that skips third-party, cloud or ICS requirements will leave gaps.
  • Practical guidance. Templates with no instructions tend to be left half-filled.
  • Language and terminology. Check whether wording suits your organisation and any language expectations from your regulator or customers.
  • Sample records. Examples of completed registers and logs make adoption easier.

The same evaluation logic applies to other frameworks. Our article on what an ISO 45001 toolkit should include covers how to judge a documentation pack in general. If your organisation also operates in the EU, the documents needed for NIS 2 implementation overlap with several ECC areas, such as risk management, incident handling and supply chain security.

Common mistakes#

  • Filling in templates without checking whether the control actually exists.
  • Leaving placeholder text or generic roles in approved documents.
  • Writing procedures nobody follows, then being unable to produce evidence.
  • Treating the toolkit as a one-off project instead of a maintained system.
  • Ignoring third-party and cloud requirements until late in the project.

Frequently asked questions#

Does an ECC toolkit make us compliant?#

No. A toolkit provides documentation templates and structure. Compliance depends on implementing the controls, operating them consistently and keeping evidence. The documents support that work but cannot replace it.

Can we use an ISO 27001 toolkit for ECC?#

Partly. Many topics overlap, such as risk management, access control and incident response, so existing ISO 27001 documents can be a useful base. But ECC has its own control structure and specific requirements, so you will need a mapping exercise and likely additional or adjusted documents.

Who should own the ECC documentation internally?#

Typically the cybersecurity or information security function coordinates it, with control owners in IT, HR, procurement, operations and legal maintaining the documents for their areas. Senior management must approve the policies and support the programme.

If you want help judging which documents your organisation needs and how to adapt them, you can contact the AdWiser team to discuss your requirements.

Share this guide

Need help with your next audit?

Our consultants can assess your gaps and guide you to certification.

Chat on WhatsApp