NIS2
Identify your national implementation and prepare governance, security controls and incident reporting.
Essential Cybersecurity Controls (ECC 2:2024)
Map the NCA baseline to your organization and make each control testable.
Saudi organizations in the official scope, including relevant government entities and private organizations that own, operate or host critical national infrastructure.
A defensible control matrix, evidence of operating controls and a remediation plan for scoped gaps.
Check separate NCA controls for cloud, operational technology, data and other specialized environments where applicable.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
Saudi NCA Essential Cybersecurity Controls kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Confirm entity scope and control versions · CISO + local compliance [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
A Saudi critical infrastructure operator separates business IT from an industrial control environment. It documents shared identity and incident escalation, then maps specialized operational controls where they apply.
Check how personal data collection, transfer and breach response interact with cybersecurity duties.
Checklist, instructions and 9 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Confirm entity scope and control versions | CISO + local compliance | Before assessment | Set a start date | Applicability matrix; System inventory | Open |
| Assign controls and evidence by domain | Control owners + risk team | Before readiness review | Set a start date | Control matrix; Responsibility matrix; Evidence index | Open |
| Test control operation and resolve gaps | Security testing + internal assurance | On assessment and after major changes | Set a start date | Test reports; Corrective-action register | Open |
| Maintain assessment and response records | CISO + management | At reviews and reportable events | Set a start date | Periodic reports; Incident procedure | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Map legal entities and service boundaries. Check current ECC scope and any parallel NCA or sector-specific obligations.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Fictional details. Use the same fields with evidence from your work.
Each item has one accountable owner. The source and as-of date let a reviewer trace it back.
Share the reviewed inventory with the people building the control, privacy or testing scope.
Convert the official controls into operating tasks. Map security governance, protection, resilience and third-party responsibilities to evidence.
Fictional details. Use the same fields with evidence from your work.
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Sample actual configurations and processes. Document findings, approved exceptions, corrective dates and validation.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Keep status and evidence current, use the applicable authority notifications and review changes in scope or required control sets.
Fictional details. Use the same fields with evidence from your work.
The period, evidence and required metrics are complete and the reviewer can follow up on open items.
Send the approved report to the required recipient and give ongoing actions to service owners.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.