A security strategy has value when it helps a business decide what to do next. For a growing organisation, that usually means connecting the risks to its important services with a manageable programme of improvements, clear responsibilities and evidence that something has actually changed.

The approach needs to suit the size and resources of the business. A small team is unlikely to need the same operating model as a large enterprise. However, a simpler arrangement still has to answer some basic questions. Who approves access? Who deals with an unresolved supplier issue? Who decides what happens when a control fails?

Establish the starting position

I would start with essential services and whatever evidence already exists. Which protections are in place? What do they cover? How is their operation checked? Contracts, access reviews, software update reports and restoration records might provide useful answers. Where they don't, the honest position is that more information is needed.

The NCSC Cyber Action Toolkit gives smaller organisations a practical way to begin [S4]. Cyber Essentials provides a recognised baseline across five technical areas: firewalls, secure configuration, security update management, user access control and malware protection [S5]. These are useful foundations; a business does not need to invent a standard from scratch.

But the limits matter. A control assessment or certificate relates to a defined scope. It should not be treated as proof that the organisation has resolved every supplier dependency, established business continuity arrangements or tested the decisions required in a serious incident.

A lengthy technical assessment can be useful, but it does not automatically tell leadership what should happen first. I would put the findings alongside the services they affect and distinguish a confirmed weakness from a gap in evidence. For example, knowing that backups exist but having no representative recovery test does not prove either success or failure. It creates a discovery action with an owner and an expected result. This avoids two equally unhelpful responses: treating uncertainty as reassurance or turning every unknown into an emergency. A strategy is credible when its starting assumptions are visible.

Address the foundations in the context of the business

Access is a sensible early priority. Legitimate accounts can become routes into essential services, so the business should know who has access, how that access is authorised and what happens when a person changes role or leaves. Appropriate multifactor authentication deserves particular attention, especially for privileged accounts. It improves protection without removing every possibility of compromise [S6].

The same practical ownership is needed for supported software, secure configuration and timely updates. Can the organisation identify devices or applications that are unmanaged or no longer supported? If an exception is unavoidable, who accepts it and when will that decision be reviewed? An exception without an owner or end date can become a permanent weakness almost unnoticed.

Recovery needs equal attention. It matters which information is backed up, who can administer the backup service and whether a representative restoration has worked. A successful backup job is one component of recovery, not the complete answer. People, credentials, dependencies and the ability to use the restored information must also be considered [S7].

The baseline needs to reflect how the organisation actually operates today. New cloud platforms, contractors and acquired teams can fall outside the arrangements assumed when a control was designed. An account review is only meaningful if the relevant population is known, and a monitoring product is only useful if someone can deal with its findings. The strategy should identify who will operate each improvement once the initial project finishes. A straightforward, evidenced process may be more sustainable for a small team than a more sophisticated product without the people or capacity to manage it.

Build the first 90 days around decisions

I would divide the initial work into three practical periods, without treating the timetable as a rule that overrides urgent action.

First month. Agree which services are in scope, identify the most significant unknowns and address urgent exposures with appropriate specialist support. Nominate business owners and clarify where the supplier's responsibility begins and ends. A serious weakness should not wait for a lengthy review exercise to finish.

Second month. Deliver a small number of worthwhile improvements and agree what evidence will show that each is complete. For an access review, that might mean a reconciled account list, resolved exceptions and proof that permissions can be removed. For resilience, it might mean an agreed restoration exercise and a recorded result for an essential service.

Third month. Test what has been put in place. A leadership incident discussion and a representative restoration check can reveal limitations that weren't visible on paper. Review the results, amend the assumptions and decide what comes next. The end of a 90-day programme is a point of review, not a declaration that security is finished.

An active incident, major exposure or sector-specific obligation may require a much faster response. The sequence is intended to organise work where time and resources are limited.

For the opening review, I would keep a compact decision record: the service involved, the issue or unknown, its business consequence, the accountable owner and the evidence needed to resolve it. The technical details can sit behind those fields. Later reviews should be allowed to change the programme. A restoration exercise might reveal an unexpected shared dependency; an access review might show that the scope was incomplete. The right response is to revise priorities and explain why, not to preserve a timetable for the sake of a positive progress report.

Make trade-offs explicit

Imagine a smaller business with limited capacity to improve device management and a fragile recovery process at the same time. Which comes first? The answer depends on the systems exposed, the consequences of failure and what can realistically be achieved. A numerical risk score cannot make that judgement on its own.

Leadership should record the reasoning, dependencies and exposure that will remain. If an improvement is postponed, agree any temporary safeguards and the circumstances that would bring the work forward. A decision that is written down can be reviewed when the business changes.

Choices will seldom be as simple as selecting the highest numerical score. A broad technical improvement may offer significant coverage, while a limited process change could remove an immediate approval gap affecting one essential service. Compare their expected effect, ongoing operating burden, dependencies and the exposure left behind. Some proposed work may be reduced, replaced or deferred once more evidence is available. Those decisions should have named owners, reasons and review dates. Deciding not to purchase something can be a positive strategic choice when the evidence supports it, rather than a failure to invest.

Sources and further reading

[S4] NCSC. Cyber Action Toolkit. Read original guidance

[S5] NCSC. Cyber Essentials overview. Read original guidance

[S6] NCSC. 10 Steps to Cyber Security Identity and access management. Read original guidance

[S7] NCSC. Ransomware resistant backups. Read original guidance

The source collection records these references as checked on 28 October 2026. Source attribution does not imply endorsement.

Scenarios are illustrative, not client case studies. This article provides general business guidance, not a security audit, certification or substitute for sector-specific technical, legal or contractual advice.