- Three horizons work for most organisations, for example Stabilise (0 to 90 days), Build foundations (3 to 12 months) and Mature (12 to 24+ months). Compress them if a regulatory deadline or critical exposure demands it.
- Incident response belongs in the first 90 days: you need to know what to do when something goes wrong before the programme is mature.
- The roadmap is a table: every initiative has a named owner, a dependency, a target date, an effort estimate and a measurable success criterion.
- Untested controls are assumptions. Start by testing backup restores against the maximum tolerable downtime you set in step 1.
- Review progress quarterly, refresh the roadmap annually and report to the board in terms it can act on.
This guide covers steps 8 to 11 of building a cybersecurity roadmap, plus regulatory alignment. For what a roadmap is and steps 1 to 7, from business context to prioritisation, see our guide to building a cybersecurity roadmap.
Step 8: Build the phased roadmap
Three time horizons work for most organisations. Set a 24-month outer boundary with an annual reassessment. Beyond that, the forecast is too unreliable to plan against. The timeframes below are examples: if a regulatory deadline is close or you have a critical exposure, compress the phases and bring the urgent work forward.
Example roadmap
The roadmap is a table. Every initiative has a named owner, a dependency, a target date, an effort estimate, and a measurable success criterion. Without specific success criteria, progress tracking has nothing to measure against.
| Priority | Risk addressed | Initiative | Owner | Dependency | Target | Effort | Success measure |
|---|---|---|---|---|---|---|---|
| Phase 1 : Stabilise (0–90 days) | |||||||
| Critical | Compromised cloud accounts | Enforce phishing-resistant MFA; block legacy auth | IT / Security | Identity inventory | 30 days | M | 100% account coverage, legacy auth blocked |
| Critical | Ransomware / data loss | Immutable backup with quarterly restore test | IT | Backup assessment | 60 days | M | Restore test passed, RTO validated quarterly |
| High | Unpatched vulnerabilities | Automated vulnerability management | IT | Asset inventory | 90 days | M | ≥95% of systems within patch SLA |
| High | No response capability | Minimum viable IR plan + tabletop exercise | CISO / IT | None | 60 days | S | Plan documented, tabletop completed, roles assigned |
| High | Stale accounts (leavers) | Same-day account offboarding procedure | IT / HR | HR process alignment | 30 days | S | Zero active accounts for leavers within 48h |
| Phase 2 : Build foundations (3–12 months) | |||||||
| High | Unmanaged endpoints | Device management and compliance enforcement | IT | MDM procurement, MFA deployed | 6 months | L | 100% corporate devices enrolled and compliant |
| High | Supply chain compromise | Third-party risk assessment programme | Security / Procurement | Supplier inventory | 6 months | M | All critical suppliers assessed; contractual requirements in place |
| Medium | Phishing susceptibility | Security awareness + quarterly simulations | HR / Security | None | 6 months | M | Click rate <5% sustained over two consecutive quarters |
| Medium | Privilege abuse | Privileged access management (JIT / PIM) | IT | MFA deployed | 9 months | L | All admin roles use time-limited activation; no persistent privilege |
| Phase 3 : Mature (12–24+ months) | |||||||
| Medium | Holistic security gaps | ISO 27001 certification programme | CISO / Senior leadership | Mature controls, management system | 18+ months | XL | Stage 2 audit passed; certificate issued |
Step 9: Assign ownership and budget
Name an owner and a funded budget for each initiative. Each one also needs: an owner with the authority to deliver it; an estimated cost covering external spend and internal resource time; any skills or third-party support that must be procured; and a link back to the risk or compliance requirement it addresses.
For board reporting, frame the budget as an investment decision. Each initiative reduces a named risk by a quantifiable amount. The board is allocating a finite security budget across competing risks. If a critical risk stays unfunded, that should be an explicit board decision, not something they discover after a breach.
Insurers require specific controls as a condition of coverage: MFA, immutable backup, and incident notification procedures are the most common minimum requirements. Before finalising the roadmap, review your policy's conditions and exclusions. Controls required by the insurer belong in Phase 1 regardless of their risk ranking. A claim denied because a mandated control was absent is expensive; it also eliminates the budget argument against implementing it.
Step 10: Test and measure
Untested controls are assumptions. Unexercised recovery is an assumption.
Run backup restore testing first. A backup that has never been restored is not a recovery capability. Test against the maximum tolerable downtime from your Step 1 analysis. If recovery takes longer than the business can absorb, the backup architecture needs revision.
Incident response exercises (tabletop at minimum, full simulation as the programme matures) test the process and people dimensions technology cannot cover. Who makes the call to isolate a system? Who approves external communications? Who contacts the ICO? Run the exercise before those questions arise in a real incident.
Penetration testing tells you whether your technical controls hold against an adversary's approach. Scope it to your crown-jewel systems first.
Key metrics to track against the roadmap: MFA coverage (percentage of accounts enrolled), patch compliance rate (percentage within SLA), phishing simulation click rate trending quarterly, mean time to detect and respond to security incidents, and open critical vulnerabilities unresolved past SLA.
Step 11: Govern and refresh
Two mechanisms keep the roadmap live. Quarterly reviews track progress, flag slipping initiatives, and update the threat context. Annual refresh revisits the risk assessment, incorporates new threats, regulatory changes, and business changes such as acquisitions or new market entry, and reprioritises for the coming year. The outer horizon is reassessed against actual progress.
Board or senior leadership reporting converts security progress into terms a board can act on: risk posture trend, incidents in the period, critical control status, and what is funded versus what is not. Boards need to know whether risk is moving up or down, and what decision they are being asked to make.
Regulatory alignment
Build the roadmap around business risk, and the major frameworks become validation layers rather than separate projects.
Cyber Essentials maps to the Stabilise phase. Most organisations that complete the first-90-day quick wins can achieve Cyber Essentials certification within the same quarter. Specific government and MOD contracts require Cyber Essentials Plus. Verify your contract terms.
NIS2 Article 21 requires policies on risk analysis, incident handling, backup and recovery, supply chain security, network security, cryptography, access control, and multi-factor authentication. Every item is a roadmap initiative. NIS2 compliance follows from a programme that covers the required controls. It is not a parallel workstream.
ISO 27001 Clause 6.1.2 requires a risk treatment plan linking each identified risk to a treatment decision and a control. That plan is structurally identical to your roadmap. Build the roadmap correctly and you produce the ISO 27001 risk treatment plan as a direct output.
DORA requires financial entities to maintain an ICT risk management framework, conduct resilience testing, and manage third-party ICT risks. The roadmap structure maps to each obligation. Resilience testing and third-party risk assessment belong in the foundational phase for any entity in DORA scope.
A roadmap built around compliance requirements tends to address what auditors check, not what would most damage the business. Risk-based prioritisation produces a different order.
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