Guide Cybersecurity

Building a Cybersecurity Roadmap: A Practical Guide for UK Organisations

Most breached organisations ran security the same way: reactively, in isolation, with no plan for when something went wrong. A cybersecurity roadmap maps where you are, where you need to be, and which controls close the gap, built around what would actually damage the business.

16 August 2026
Updated 19 November 2026
10 min read
Key takeaways
  • A cybersecurity roadmap protects business processes, not just assets. Start with what would break the business, then work backward to the systems, data, and controls that protect it.
  • The right sequence is: business context → asset inventory → threats and risk → current maturity → target state → gap analysis → prioritisation → phased plan → ownership and budget → testing → governance.
  • Maturity scoring across people, process, and technology gives you a more honest starting point than a binary in-place or not-in-place gap analysis.
  • Incident response belongs in the first 90 days. You need a response capability before you need a mature one.
  • Three roadmap horizons work well in practice, for example: Stabilise (0 to 90 days), Build foundations (3 to 12 months), Mature (12 to 24+ months). Urgent regulatory deadlines or critical exposures may need a compressed plan. Avoid committing to a 36-month plan. Threats, technology, and business priorities change too fast.
  • The roadmap's output is a table, not a strategy deck: priority, risk addressed, initiative, owner, dependency, target date, effort, and success measure for every initiative.

What a cybersecurity roadmap actually is

Many UK organisations treat cybersecurity as a product collection: antivirus here, a firewall there, a password policy because the IT provider asked. Each control exists in isolation. When a breach arrives, there is no prioritised list, no clear owner, and no plan.

A cybersecurity roadmap captures your current posture, defines the target state your risk profile and regulatory obligations require, and maps which controls close the gap, in order, with named owners and dates. It links to the risk register, carries a budget dimension, and refreshes on a fixed cadence. That makes it an investment plan, not a shopping list.

43%
of UK businesses reported a cyber breach or attack in the past 12 months (Cyber Security Breaches Survey 2026)
247
days: average time to identify and contain a breach globally, up for the first time in five years (IBM 2026)
$4.99M
global average cost of a data breach, up 12% year on year to a record high (IBM 2026)

The IBM figures are averages across breached organisations that took part in the study, in US dollars. They show the scale of the problem, but they are not the expected loss for any individual business, especially an SME.

Step 1: Understand the business

Security programmes that start with asset inventory or framework selection skip the most important question: what would actually damage this business? A vulnerability on a public-facing web server may be technically severe. A compromise of your identity platform may bring every business service to a halt simultaneously. Those are not equivalent risks, and a roadmap that treats them as such wastes budget on the wrong problems.

Before cataloguing assets, establish the business context your roadmap is designed to protect:

  • Critical services and processes: which operations, if disrupted, would cause material harm to customers, revenue, or regulatory standing
  • Crown-jewel systems and data: the systems and datasets whose compromise would represent the worst-case outcome: financial records, customer PII, intellectual property, operational technology
  • Maximum tolerable downtime: for each critical service, how long can the business function without it before consequences become serious
  • Regulatory obligations and risk appetite: sector-specific requirements (NIS2, DORA, FCA, NHS DSP Toolkit) and the organisation's stated tolerance for security risk
  • Key third-party dependencies: MSPs, SaaS providers, cloud platforms, and suppliers with privileged access or data-sharing relationships
  • Business priorities for the next 12 to 24 months: planned acquisitions, geographic expansion, new product launches, cloud migrations, or outsourcing that will materially change the attack surface

With that context in place, every control decision has a concrete business anchor, and the roadmap becomes something a board can evaluate and fund.

Step 2: Build your asset and dependency inventory

You cannot assess, prioritise, or protect assets you have not catalogued. A useful inventory covers four categories: hardware (every device connecting to your network or accessing business data, including employee-owned devices used for hybrid working); software and services (every application, cloud platform, and SaaS tool in active use, including shadow IT and third-party integrations); data (where sensitive data lives, who can reach it, and how it moves between systems); and people and third parties (users, contractors, vendors with system access, and managed service providers).

Most organisations find sensitive data in more places than expected: email archives, unmanaged OneDrive folders, shared drives with no access review since deployment, spreadsheets used as improvised databases. Start with what you can catalogue now. Prioritise accuracy and maintenance over completeness, and map everything back to the critical business services identified in Step 1.

Step 3: Identify threats and assess risk

The attacks targeting UK organisations in 2025 and 2026 follow familiar patterns: ransomware encrypting systems and demanding payment; business email compromise diverting payments or extracting data; credential theft through phishing and password-spray attacks against cloud accounts; and supply chain compromise reaching you through a trusted software provider or managed service. Your risk assessment focuses on these patterns applied to your specific assets and business context.

Crown jewels and business impact

For each critical business service identified in Step 1, map the specific assets that service depends on. Then ask: what is the business consequence if that asset is compromised or made unavailable? The answer drives prioritisation more reliably than a generic severity score.

A useful crown-jewels analysis records, for each critical service: the systems required to operate it, the data required to operate it, the internal people required, external supplier dependencies, recovery time requirements, and the specific consequences of a compromise or prolonged outage. That analysis makes the risk register defensible at board level, because every risk has a business consequence attached.

Risk scoring

For each asset or service, score likelihood of a successful attack (1 to 5) and impact to the business if it succeeds (1 to 5). Multiply them. The score is a prioritisation aid, not a quantified estimate of financial loss. Controls that reduce the score of high-likelihood, high-impact risks give the greatest estimated risk reduction relative to their cost and dependencies.

Step 4: Assess your current maturity

A binary gap analysis ("in place" or "not in place") misrepresents most organisations' actual security position. A control that exists but is inconsistently applied, untested, or undocumented is not the same as one that works reliably. Maturity scoring exposes the difference.

Score each security domain on a five-point scale: 0 = not implemented, 1 = ad hoc (exists informally or in isolated pockets), 2 = defined (documented and consistently applied), 3 = managed (monitored with metrics), 4 = measured (quantitatively understood with feedback loops), 5 = optimised (continuously improved based on evidence).

Assess across three dimensions: people, process, and technology. Use domains relevant to your organisation:

👥
People
Roles and responsibilities (who owns security decisions), security awareness and training programme, phishing resilience, executive accountability for security outcomes, and a named internal owner for the roadmap. Most organisations score poorly on accountability: controls exist but nobody owns them.
📋
Process
Security policies, risk management process, incident response procedures, vulnerability management cadence, supplier security requirements, change management controls, and business continuity planning. Process is where most organisations underinvest. The tools exist; the policies and procedures to operate them often do not.
💻
Technology
Identity and access management, endpoint protection, email security, network security and segmentation, centralised logging and monitoring, backup and recovery, and vulnerability scanning. Organisations tend to over-invest in technology and under-invest in the processes to operate it. A tool deployed without a defined owner, review cadence, or response procedure adds noise, not protection.

Score these domains honestly; the result is your current-state baseline. The gap between that baseline and your target (Step 5) generates the initiative list. Treat any domain scored at 0 or 1 as a priority regardless of risk-matrix position. Ad-hoc controls are not controls.

Step 5: Define your target state

Choose a recognised framework as your target anchor. Three apply most commonly in the UK:

🛡️
Cyber Essentials
The NCSC's baseline standard covering five technical control areas: firewalls, secure configuration, user access control, malware protection, and patch management. A practical starting point for most organisations, and required for many UK government and public sector contracts. Cyber Essentials Plus adds independent technical verification of those controls and is specifically required by some government and Ministry of Defence contracts. The exact requirement varies by contract. Always check the specific procurement terms. Certification timelines for Cyber Essentials are typically measured in weeks.
📋
ISO 27001:2022
The international standard for information security management systems, covering 93 controls across four domains. It requires establishing, operating, and continually improving a management system that addresses your full risk landscape. Appropriate for organisations with significant regulatory obligations, enterprise customer security requirements, or a programme mature enough to sustain the ongoing management system commitment. Certification timelines vary substantially depending on organisational size, scope, existing controls, and management-system maturity.
🗺️
NIST Cybersecurity Framework 2.0
A maturity framework that organises controls across six functions: Govern, Identify, Protect, Detect, Respond, and Recover. Well suited to internal roadmap planning because it covers the full security lifecycle. Many organisations use NIST CSF to structure their programme and pursue Cyber Essentials or ISO 27001 for external validation.

Build the roadmap around business risk. Use frameworks and regulations to define control requirements and validate that your programme covers what matters.

Step 6: Perform the gap analysis

With a maturity baseline (Step 4) and a target framework (Step 5), compare your current maturity against your target for each control area. Record current score, target score, and the initiatives that close the gap. A gap analysis is only useful if specific enough to act on: "MFA is not enforced on shared service accounts" is actionable; "access control needs improvement" is not.

The gap list feeds into prioritisation. Every initiative on it has a parent risk from the register and a parent control requirement from the framework. That traceability makes the roadmap defensible when someone asks why a particular project is funded and another is not.

Need this done for you?

Our cybersecurity assessment covers Steps 1 through 6 for your organisation: asset and dependency mapping, threat and risk profiling, maturity scoring across people, process, and technology, compliance gap analysis, and a prioritised roadmap. Three to ten working days, starting with a free 30-minute scoping call.

Step 7: Prioritise

Risk-based prioritisation outperforms compliance-first. Compliance-first asks what the auditor flagged. Risk-based asks what reduces the most real risk for the least effort.

Rank initiatives on two axes: the risk reduction they deliver, and the effort required. High-reduction, low-effort initiatives go first. Low-reduction, high-effort initiatives go last or are deferred. Regulatory deadlines add a third constraint: an NIS2 obligation with a hard deadline may warrant scheduling ahead of a higher-risk initiative that has no external date.

A roadmap is closer to a dependency graph than a ranked list. Some controls cannot be implemented until others are in place. Consider the chain: asset inventory enables identity and device visibility; that enables MFA and Conditional Access; that enables privileged access management; that enables Zero Trust. Similarly, backup inventory precedes backup architecture, which precedes immutable storage, which precedes restore testing, which precedes recovery exercises. Build the prioritisation to respect those dependencies.

With a prioritised list in hand, the next job is turning it into a plan. Our companion guide, Delivering your cybersecurity roadmap: phased plan, ownership and governance, covers steps 8 to 11: the phased roadmap with a worked example table, ownership and budget, testing and measurement, governance, and how the roadmap aligns with regulation.

Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Common questions

What is the difference between a cybersecurity roadmap and a security policy?

A security policy defines what your organisation requires of its people, systems, and processes: an acceptable use policy, a password policy, a remote working policy. The roadmap defines how the organisation invests its security effort over the next 12 to 24 months. It translates the risk register into a sequenced programme of controls with owners, timelines, and success criteria. Both are needed; they serve different purposes.

How long does it take to build a cybersecurity roadmap?

A basic roadmap covering current state assessment, risk scoring, gap analysis, and a prioritised 12-month initiative list takes three to five working days with the right stakeholders engaged. A more comprehensive programme including a full ISO 27001 gap analysis, maturity assessment across people/process/technology domains, and a multi-year plan takes two to four weeks. A roadmap built on incomplete data will be optimised for the wrong risks. The time invested in a thorough assessment pays back in more defensible prioritisation.

Which security framework should our cybersecurity roadmap be based on?

For most UK businesses, Cyber Essentials is the practical starting point. It covers the five technical controls that prevent the majority of opportunistic attacks and is achievable in weeks. Some government and MOD contracts require Cyber Essentials Plus. Verify your contract terms. For organisations with regulatory obligations under NIS2 or DORA, or with enterprise customer security requirements, ISO 27001 is the appropriate target. NIST CSF 2.0 works well as an internal planning scaffold regardless of which certification you pursue. Let business risk set the priorities; use frameworks to validate that your programme covers what is required.

Security Roadmap Assessment

Find out where your security programme stands

We run the gap analysis, build the prioritised roadmap, and give you a clear plan for the next 12 months, with no tooling you do not need.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.