- A strategy sets the security outcomes the organisation wants, how much risk leadership will accept and where investment goes. A roadmap turns those decisions into initiatives with owners, resources and deadlines. You need both.
- Strategy is business-led and technically informed. Leadership stays accountable for the risk decisions in it; the CISO or security lead usually coordinates and maintains it.
- Risk appetite is the broad direction. Risk tolerance turns it into measurable limits, such as the maximum acceptable outage for a specific service.
- Build the strategy on the risks that matter most, but treat serious risks you already know about without waiting for a complete risk assessment.
- A practical strategy covers business context, risk appetite and tolerance, current and target posture, objectives, guiding principles, governance and funding, and measurement.
Strategy versus roadmap: what each one decides
Many organisations that ask for a cybersecurity strategy want a roadmap: a prioritised list of things to fix. A roadmap is useful, but it answers a different question.
A strategy is a business direction document, grounded in the organisation's risks and technology needs. It sets the security outcomes the organisation wants to achieve, the level of risk it is prepared to accept and its investment priorities. It can include technical content, such as architecture principles or the capabilities the organisation needs to build. What sets it apart from a roadmap is the level of decision it records.
A roadmap turns those decisions into initiatives, owners, resources and deadlines, and tracks progress. The security or IT team usually runs it day to day.
A roadmap without a strategy is a collection of good ideas competing for budget with no basis for choosing between them. A strategy without a roadmap describes where you want to be and leaves you there.
Who owns and approves the strategy
The strategy should be approved by the board or by whichever governing body holds that authority, depending on your organisation's structure and regulatory obligations. The CISO or security lead can coordinate its preparation and delivery, but decisions on risk appetite, priorities and investment stay with leadership. NIST CSF 2.0 frames this as leadership being responsible and accountable for cybersecurity risk (GV.RR-01).
Some regulated firms face more specific rules. Under the FCA and PRA operational resilience rules, in-scope UK financial firms identify their important business services and set impact tolerances for disruption. In the EU, DORA (Article 5) gives the management body of an in-scope financial entity overall responsibility for setting and approving its digital operational resilience strategy.
Ground it in risk, without waiting for perfection
A strategy written without understanding business risks and technology dependencies is unlikely to work. The risk assessment tells you what assets you have, what threatens them, what weaknesses exist in your defences and what impact an incident could have.
Strategy and assessment feed each other. Business objectives and critical services shape the assessment; its findings set strategic priorities; leadership's risk appetite decides how those risks are treated; and later assessments can change the strategy. You can develop and refine the assessment in parallel with strategic planning. Deal with serious risks you already know about, such as an internet-facing remote access service without MFA, as urgently as they need, without waiting for the whole process to finish.
Once you have an assessment, make the strategy traceable to it: each strategic objective should map back to a risk category the assessment identified.
Risk appetite expresses the organisation's general position on the risks it is willing to take on. Risk tolerance turns that position into more specific limits, such as maximum acceptable downtime, financial exposure or levels of privileged access. The responsible leaders should approve those limits and use them to prioritise investment. NIST CSF 2.0 covers both under GV.RM-02.
| Concept | Illustrative statement |
|---|---|
| Risk appetite | We have a low appetite for disruption to customer-facing critical services. |
| Risk tolerance | The approved recovery objective for a specific critical service is no more than four hours, based on its business impact assessment. |
| Operational measure | Recovery tests show whether that objective can be met in practice. |
These are illustrative management decisions, not thresholds set by NIST.
What a cybersecurity strategy contains
Four components sit at the core of a strategy: risk appetite, objectives, guiding principles and measurement. Three more give it the context that explains why those decisions were made. A smaller business can cover all seven in a short, management-approved plan instead of a long formal document.
1. Business context and critical services
Identify the operations, customers and dependencies the strategy has to protect, and the legal and contractual obligations that apply, such as UK GDPR, sector regulation and customer contracts.
2. Risk appetite and tolerance
Define which risks the organisation will accept, which it will not, and where the limits are. Break it down by risk category: financial loss, data exposure, operational disruption, reputational damage, regulatory consequence. Then translate each category into tolerances specific enough to guide a real decision.
Some sectors have explicit requirements. UK firms within the FCA and PRA operational resilience rules set impact tolerances for their important business services. Under DORA, an EU financial entity's strategy has to establish its ICT risk tolerance level and analyse impact tolerances for ICT disruptions (Article 6(8)), in line with its risk appetite. The values depend on the firm and the services it provides; no rule sets one number for everyone.
3. Current and target security posture
Describe where the organisation is today and where it needs to be, so the improvement is explicit and measurable. NIST CSF 2.0 Organizational Profiles are one way to do this: a Current Profile, a Target Profile and a prioritised plan to close the gaps between them.
4. Strategic objectives
Objectives are the outcomes the strategy is designed to achieve, stated in terms the business can evaluate. Some examples:
- Instead of "improve patch management": treat vulnerabilities on deadlines set by criticality, exposure and active exploitation. For example, 95% of critical vulnerabilities treated or mitigated within the deadline in the vulnerability management policy, with immediate escalation of actively exploited flaws.
- Instead of "train staff": improve how people spot and report phishing, measured by the reporting rate for suspicious messages and how performance changes in controlled exercises.
- Instead of "certify all suppliers": reduce exposure to incidents that start at third parties, with minimum security requirements, risk assessment and ongoing monitoring for critical suppliers, proportionate to their access, the data they handle and the importance of their services.
The 95% is an illustrative target your organisation would set, not a recognised benchmark. A handful of objectives is usually easier to fund and track than a long list; how many you need depends on maturity, size and complexity. Each one should be tied to a risk category from the assessment, measurable with a metric that exists or can be created, achievable within your budget and headcount, and approved by leadership, not just the security function.
5. Guiding principles
Principles are the rules that govern security decisions in the gaps between explicit policies. Examples of useful principles: least privilege (users get the minimum access needed, by default); security by design (new products include security review before build, not after); third-party assurance (suppliers with access to our systems meet minimum requirements, proportionate to that access, before onboarding).
Principles have to work in practice, including when the organisation is under pressure. One that would be dropped at the first deadline does not belong in the strategy.
6. Governance, funding and responsibility
Record who makes decisions, who pays and who reports progress. Validate resource assumptions before the strategy goes for approval: a strategy that depends on budget or headcount nobody has agreed will not be executed.
7. Measurement
Define the metrics that show progress against each objective, who collects them and how often. Keep business outcomes apart from activity counts: "percentage of critical services with tested recovery" tells leadership more than "number of backup jobs run".
Metrics worth reporting to leadership: time to detect and respond to incidents; coverage of critical controls (MFA, patching, logging); percentage of high-risk vulnerabilities remediated within the agreed deadline; movement in the risk register over time.
How to build your strategy in seven steps
| Step | Activity | Deliverable |
|---|---|---|
| 1 | Understand business objectives and critical services | Overview of critical services and their dependencies |
| 2 | Assess material risks, existing controls and obligations | Current-state risk assessment |
| 3 | Agree risk appetite and measurable tolerances | Approved risk limits |
| 4 | Define a small number of strategic outcomes | Prioritised strategic objectives |
| 5 | Set governance, principles and responsibilities | Ownership and decision framework |
| 6 | Define indicators, funding and target capabilities | Approved strategy |
| 7 | Turn the gaps into a funded implementation roadmap | Prioritised actions with owners and deadlines |
In practice the steps overlap: you will revisit the risk assessment as objectives take shape. For step 7, see our guide to building a cybersecurity roadmap.
Worked example: recovering critical services
| Element | Example |
|---|---|
| Business problem | The organisation relies on several critical services but has not shown it can restore them within acceptable downtime. |
| Strategic outcome | Demonstrable recovery capability for all business-critical services within 18 months. |
| Management metric | Percentage of critical services with approved recovery objectives and successfully tested recovery arrangements. |
| Roadmap initiatives | Business impact assessment, service dependency mapping, backup improvements, restore exercises and supplier recovery testing. |
The example is illustrative. It ties the strategy to a business risk instead of a list of security purchases.
How strategy and roadmap work together
| Strategy | Roadmap |
|---|---|
| Why and what | How and when |
| Medium-term horizon, often two to three years, reviewed periodically | Shorter-term initiatives, tracked frequently |
| Primary audience: board and senior leadership | Security, IT and delivery teams |
| A small number of strategic objectives | Initiatives prioritised by capacity and risk |
| Guided by risk appetite and tolerance | Guided by the strategic objectives |
| Formally refreshed, often annually or after major change | Updated as initiatives progress |
The number of objectives and initiatives depends on the organisation's maturity, size and complexity. A small company might work with three objectives and six initiatives; a large group might run several programmes with dozens of workstreams.
Common strategy mistakes
Mistaking a framework for a strategy. Adopting ISO 27001 or Cyber Essentials is an implementation decision. "We will achieve ISO 27001 certification" is a roadmap milestone. "We will reduce our exposure to incidents that start at critical suppliers" is a strategic objective.
Writing a strategy for the auditor, not the business. A strategy written only to tick a compliance box will not get the priority it needs in budget decisions when it competes with revenue-generating work.
Setting goals without checking budget. A strategy that requires a 40% increase in security headcount that nobody has approved will not be executed. Validate resource assumptions before the strategy goes for approval.
No accountability. Every strategic objective needs a clearly named owner, with the authority to act and the support of the teams involved.
How long a strategy lasts and how often to review it
Many organisations work to a medium-term horizon, often two to three years, but no standard fixes the length. It helps to separate four rhythms:
- Leadership oversight of material risk and performance, on an agreed recurring schedule
- Roadmap and remediation reporting, monthly or more often where needed
- Extraordinary escalation after a major incident, a regulatory change or a material increase in risk
- Formal strategic refresh, often annually or after a major change such as a merger or a move into a new sector
At each refresh, check whether the risk appetite and tolerances still fit. If the organisation has grown, changed sector or taken on new regulatory obligations, they need to keep pace.
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