The Essential Cybersecurity Controls (ECC-1:2018), issued by Saudi Arabia's National Cybersecurity Authority, set a baseline of cybersecurity requirements for organisations in scope. Many of the controls ask for something to be defined, documented, approved, implemented and reviewed. Documentation is therefore a large part of the work.
This article explains which documents you need, how they map to the framework, and how to avoid common mistakes. Always check your final list against the current official NCA text and any sector-specific requirements that apply to you.
How ECC-1:2018 uses documentation#
The framework is organised into main domains: Cybersecurity Governance, Cybersecurity Defense, Cybersecurity Resilience, Third-Party and Cloud Computing Cybersecurity, and Industrial Control Systems Cybersecurity. The last one applies only where you operate such systems.
Across these domains, the expectations tend to fall into four kinds of document:
- Policies state management's intent and rules.
- Procedures and standards explain how the rules are carried out in practice.
- Plans and strategies set direction, such as the cybersecurity strategy or the incident response plan.
- Records and evidence prove the controls actually operate, such as logs, review minutes and test reports.
An assessor will usually look for all four. A polished policy with no records behind it is a weak position.
Governance documents#
Start here, because the rest depends on it. Governance covers the strategy, structure and management commitment behind your cybersecurity programme.
- Cybersecurity strategy, aligned with business objectives and relevant regulations, with a roadmap.
- Cybersecurity policy framework: a master policy plus topic policies, approved by the authorised official and communicated to staff.
- Roles and responsibilities document, including the cybersecurity function, its reporting line and a steering committee charter.
- Risk management methodology and risk register, with treatment decisions and owners.
- Cybersecurity requirements for projects, so security is considered in change and project work.
- Compliance and review records: a register of applicable laws and standards, plus periodic review and audit reports.
- HR security documents: screening, onboarding and exit steps, and confidentiality undertakings.
- Awareness and training plan, with attendance and completion records.
Cybersecurity defense documents#
This domain is the largest and the most technical. Most of it needs a policy and a procedure or standard, plus operational evidence.
- Asset management: an asset inventory and an acceptable use policy.
- Identity and access management: an access control policy, joiner-mover-leaver procedure, privileged access rules and access review records.
- System and processing facility protection: secure configuration standards, patch management procedure and patching records.
- Email protection and network security standards, covering segmentation, filtering and remote access.
- Mobile device security: a policy for managed and personal devices.
- Data and information protection: classification scheme, handling rules and retention requirements.
- Cryptography standard: approved algorithms, key management and where encryption is required.
- Backup and recovery procedure, with backup logs and restore test results.
- Vulnerability management and penetration testing: procedures, scan reports, test reports and remediation tracking.
- Logging and monitoring: a log management standard, monitoring use cases and review records.
- Incident and threat management: an incident response plan, escalation contacts, incident register and lessons-learned reports.
- Physical security policy and access records for sensitive areas.
- Web application security standard, including secure development expectations for internet-facing systems.
Resilience, third-party and cloud documents#
These domains cover continuity and your dependence on suppliers.
- Cybersecurity aspects of business continuity: continuity and disaster recovery plans with recovery objectives, and exercise reports that show the plans were tested.
- Third-party security policy and supplier assessment procedure.
- Contract security clauses: confidentiality, incident notification, and exit and data return terms.
- Cloud and hosting security requirements, covering how services are selected, approved and monitored.
- Industrial control systems: if relevant, a dedicated policy and standards for operational technology.
A simple document map#
| Document type | Examples | Evidence that proves it works |
|---|---|---|
| Strategy and plans | Cybersecurity strategy, incident response plan, continuity plan | Approval records, exercise reports |
| Policies | Access control, cryptography, third-party security | Approval signatures, communication records |
| Procedures and standards | Patching, backup, joiner-mover-leaver, secure configuration | Tickets, logs, review sign-offs |
| Registers | Asset inventory, risk register, incident register | Update history, owner reviews |
| Reports | Audit reports, penetration test reports, management reviews | Action trackers, closure evidence |
How to prepare the documents without creating shelfware#
- Map first, write second. List each ECC requirement that applies to you, then note which document and which record will satisfy it. This exposes gaps before you write anything.
- Write what you actually do. A procedure that describes an imaginary process will fail the first time someone asks to see evidence.
- Name owners and review cycles. Every document needs an approver, an owner and a review date. Use version control.
- Get formal approval. The framework places weight on management approval, so make sure the right authority signs off and that you can show it.
- Keep evidence in one place. A structured folder or GRC tool, organised by control domain, saves a great deal of time during assessments.
- Test the plans. Run a restore test, an incident exercise and an access review, and keep the outputs.
If you already run an ISO 27001 management system, you will have many of these documents in some form. Our article on what an ISO 27001 toolkit should include is a useful comparison. The same applies to the document list in our guide to Cyber Essentials implementation. Reuse what fits, but check each item against ECC wording, because the framework has its own requirements and terminology.
Frequently asked questions#
Do I need a separate document for every control?#
No. One well-structured policy or procedure can satisfy several related controls. What matters is that you can show where each requirement is addressed and that the document is approved and followed.
Are documents enough to show compliance with ECC-1:2018?#
No. Documents define what should happen, but assessors also look for evidence of implementation, such as logs, reports, tickets and review records. Technical controls must actually be in place.
How often should the documents be reviewed?#
Review them at planned intervals, and also after major changes, incidents or regulatory updates. Set the review cycle in each document and keep a record of every review, even when nothing changes.
If you would rather not draft every policy and procedure from scratch, the ECC-1-2018 Toolkit offers a ready-to-use documentation starting point that you can adapt to your organisation. For help with scoping or tailoring, you can contact the AdWiser team.
