Every NCA ECC assessment ends the same way: a long list of gaps, each with a control reference and a rating. That list is evidence, not a plan. A board cannot approve a spreadsheet of 80 findings, and a finance committee cannot fund it. What they can decide on is an NCA ECC cybersecurity roadmap budget: a small number of initiatives, each with a cost, an owner, a timeline and a stated effect on risk.
This article sets out how to get from one to the other.
What the framework asks of you
The National Cybersecurity Authority issues the Essential Cybersecurity Controls (ECC) as the baseline for government bodies and the critical national infrastructure operators it covers. The controls are organized into domains including governance, cybersecurity defense, resilience, third-party and cloud security, and industrial control systems. Compliance is not a one-time certificate. Organizations are expected to implement, document, measure and keep improving the controls, and to be able to show evidence.
For a CISO, this means the roadmap has to do two jobs. It must close the gaps against ECC, and it must show the organization can sustain the controls afterwards, with people, process and tooling that are funded beyond year one.
Where the usual gaps sit
Gap lists tend to cluster, and the clusters are what make grouping possible. Common areas include:
- Governance artefacts that exist on paper but are not approved, owned or reviewed on a schedule.
- Asset inventories and classification that are incomplete, which weakens almost every other control.
- Identity and privileged access practices, including multi-factor authentication coverage and access reviews.
- Logging, monitoring and incident response that are partly in place but not tested end to end.
- Backup and recovery arrangements that have not been exercised.
- Third-party and cloud oversight that depends on contract terms nobody has checked.
- Awareness and role-based training without records that stand up to audit.
Several of these are not technology purchases at all. That matters for costing, because a gap closed by a policy and a review cycle has a very different cost profile from one closed by a platform.
Step 1: Group gaps into initiatives
Start by tagging each gap with the root cause, not the control number. Typical root causes are missing ownership, missing capability, missing tooling, missing evidence and missing integration. Gaps that share a root cause usually share a fix.
Then form initiatives of a size someone can own. A workable initiative has:
- A clear outcome stated in business terms, such as "privileged access is controlled and reviewed across critical systems".
- A list of the ECC gaps it closes.
- A single accountable owner, usually outside the security team for anything touching IT operations or HR.
- A defined end point, so it can be finished and handed to run.
Aim for roughly eight to fifteen initiatives. Fewer hides detail; more recreates the gap list.
Step 2: Estimate cost and effort
Cost each initiative in three parts, so the board sees what continues after the project ends:
- One-time cost: design, implementation, external support, licences purchased up front.
- Recurring cost: subscriptions, managed services, additional headcount, annual testing and audit.
- Internal effort: time from IT, legal, HR and business units, which is rarely budgeted but often the real constraint.
Use ranges rather than single figures where scope is uncertain, and state the assumptions behind each. Mark confidence as low, medium or high. Early estimates for a tool-heavy initiative should be wide until a vendor-neutral requirement has been written. Do not hide contingency inside line items; show it separately so it can be challenged.
Step 3: Sequence by risk reduction and dependency
Two questions drive the order. Which initiatives reduce the most risk for the least delay? And which ones must exist before others can work?
Dependencies are usually clear once written down. Asset inventory and classification come before data-centric controls and meaningful monitoring. Governance and ownership come before tooling, otherwise tools are bought and not operated. Identity foundations come before extending access controls to cloud and third parties.
A sensible three-year shape looks like this:
- Phase 1 (first 6 to 12 months): foundations and exposure. Governance, asset visibility, privileged access, critical logging, and any gap with a regulatory deadline or a clear threat link.
- Phase 2 (year two): build capability. Detection and response maturity, resilience testing, third-party and cloud assurance, and integration of the tools bought in phase 1.
- Phase 3 (year three): sustain and optimize. Measurement, automation, assurance cycles and the refresh of the strategy itself.
Test the order against your risk appetite and current threat picture. If the sector is being targeted by a specific type of attack, a related control may justifiably move forward even when the dependency chain would normally place it later.
Step 4: Present trade-offs, not just a total
Boards approve more readily when they can see choices. For each phase, show:
- What the funding buys, and the risk it reduces.
- What happens if the initiative is deferred a year, including any regulatory exposure.
- Options at different spend levels, for example a baseline, a recommended and an accelerated scenario.
- The people and organizational changes the plan assumes.
This turns the discussion from "is this too expensive" into "which risks are we choosing to carry, and for how long". A deferral that is recorded with an owner and a review date is a governance decision. A deferral nobody notices is a finding in the next audit.
Step 5: Attach measures and a review rhythm
A budget without measures cannot be defended in year two. Define a short set of KPIs for delivery, such as initiatives on schedule and controls with current evidence, and KRIs that show exposure, such as unmanaged privileged accounts or overdue critical remediations. Review the roadmap lightly each year and refresh it fully every three years, or sooner after a major change in the business or the regulatory landscape.
How we support this work
Our Cybersecurity Strategy & Roadmap service is built for this problem. We translate your business priorities, regulatory obligations and threat landscape into a costed, prioritized cybersecurity strategy and multi-year roadmap. The work is a project of 6–10 weeks and follows four stages: understand, assess, design and approve.
In the understand stage we hold interviews with leadership and review the business plan, risk appetite and regulatory position. In the assess stage we build a maturity baseline against the applicable frameworks and the current threat picture. NCA ECC and SAMA CSF are both covered by the service. In the design stage we set objectives, initiatives, sequencing and investment, and test them with stakeholders. In the approve stage we present a board-ready strategy, roadmap and measures, and adjust them for approval.
The deliverables are a cybersecurity strategy document, a three-year roadmap with budget estimates, a target operating model, a board presentation pack and a KPI and KRI dashboard definition. Regulatory obligations that apply to you are built into the objectives and the roadmap, so compliance and security move together.
Where an organization needs ongoing leadership to carry the plan forward, our vCISO Services provide experienced security leadership without a full-time hire.
Next step
If you hold an ECC gap list and need a plan your board can decide on, start by grouping the gaps by root cause and drafting initiative owners. If you would like support turning that into a costed three-year roadmap, speak to us about Cybersecurity Strategy & Roadmap.
