A security strategy earns its place when it changes decisions before an incident forces them. If you are asking how to write a security strategy, start by rejecting the idea that the task is primarily about producing a polished document. The document matters, but it is only evidence of the thinking. The real test is whether people understand the risk, know their responsibilities and can act decisively when normal operations are disrupted.
Many strategies fail because they begin with standard headings, inherited policies or a list of security equipment. That approach can create an impressive file while leaving the organisation unclear about its actual exposure. A useful strategy starts with the operation, the people within it and the consequences of getting security wrong.
Start with the operational reality
Security is not separate from the business. It affects how a venue admits visitors, how a retailer manages peak trading, how a construction project controls changing access, or how a corporate office protects people and information without making work impossible. The strategy must reflect those realities.
Begin with a clear description of what the organisation is trying to protect. That will normally include people, operations, assets, information, reputation and the ability to recover. Do not treat every asset as equally critical. A short interruption to one system may be inconvenient; a failure at a key site, during a major event or at a busy public-facing location may have serious consequences.
This is where senior leaders need to be specific. What level of disruption is unacceptable? Which activities must continue? Who has authority to pause operations, close an area or change the security posture? If those answers are vague, the strategy will be vague too.
A distribution site, for example, may focus heavily on perimeter controls while overlooking the risk created by rushed contractor management during a busy period. A hospitality venue may have good CCTV coverage but no reliable process for staff to report concerning behaviour and escalate it. The weakness is not necessarily the system. It is the gap between the system and human action.
Build the strategy from credible risk assessment
A strategy should be grounded in current threat, vulnerability and risk assessment, not copied from a previous document. Threats change, sites change, staffing changes and organisational priorities move. A strategy based on assumptions from three years ago is often a historical record, not a plan.
Assessments need to consider what is plausible in the environment, where vulnerabilities exist and how existing controls perform in reality. That last point matters. A control recorded as present is not automatically effective. An access procedure that is routinely bypassed during deliveries is not a dependable control. A response plan that only one manager understands is not a response capability.
Avoid treating likelihood and impact scores as precise science. They are a way to support judgement, not replace it. A low-frequency event with severe consequences may still demand attention, particularly where public safety, critical operations or legal duties are involved. Conversely, a highly visible issue may receive too much investment because it is easy to explain, not because it creates the greatest risk.
Good assessment work draws out uncomfortable truths. It may show that the organisation has invested in technology but neglected supervision, training and maintenance. It may identify inconsistent standards between locations. It may reveal that out-of-hours arrangements depend on goodwill rather than defined accountability. Those findings are useful because they give the strategy something real to fix.
How to write a security strategy around decisions
The strongest strategies make choices. They do not simply describe risks and then promise to improve everything.
Set out the security objectives first. These should be practical outcomes, such as reducing unauthorised access, improving the identification and reporting of concerning behaviour, protecting critical operations during disruption, or strengthening the organisation’s ability to manage a serious incident. Objectives should be linked to business priorities and expressed in terms that leaders, managers and frontline staff can understand.
Then explain the approach the organisation will take. This normally covers governance, physical and technical measures, people and behaviour, incident management, assurance and recovery. The value is in showing how those elements work together.
A useful strategy answers five questions clearly:
- What risks require priority action and why?
- What standard of protection or readiness is required?
- Who owns each decision and each control?
- What resources, skills and investment are needed?
- How will the organisation know whether capability is improving?
That is more valuable than a long inventory of cameras, barriers, policies or training courses. Equipment may be part of the answer, but it is rarely the whole answer. Security technology can improve detection, delay and evidence. It cannot compensate for poor judgement, unclear escalation or an unprepared team.
Give people a role, not just a responsibility
Strategies often assign responsibility at a high level and stop there. “Security is everyone’s responsibility” sounds positive but usually means nobody knows what they are expected to do differently.
Be explicit about roles. Senior leaders set risk appetite, approve investment and provide visible backing when security decisions affect operations. Security managers translate the strategy into standards, plans and assurance activity. Operational managers make it work day to day. Frontline staff need to recognise what matters, report concerns and respond within their competence.
This is especially relevant to counter terrorism preparedness and the expectations associated with Martyn’s Law. Compliance activity alone will not create readiness. Organisations need people who can identify relevant concerns, communicate quickly, make proportionate decisions and work together under pressure. A completed course or an approved policy may support that aim. Neither proves it has been achieved.
Capability needs testing. Tabletop exercises, practical walkthroughs, supervisor discussions and structured evaluations show whether a process is understood and usable. They also expose the common gap between what a plan says and what people believe they should do. That is not a reason to avoid testing. It is precisely why testing is necessary.
Turn priorities into an achievable plan
A strategy without delivery arrangements is an aspiration. Include a programme of work that identifies priority actions, owners, dependencies, timescales and the resources required. Keep it realistic. Trying to address every weakness at once usually produces a long action tracker and little meaningful change.
Prioritise actions that reduce significant risk, close a clear capability gap or enable other improvements. Clarifying incident command arrangements may be more valuable than buying another technical system. Improving contractor induction and supervision may reduce multiple vulnerabilities at once. In other cases, capital investment is essential. It depends on the assessed risk and the operating environment.
The strategy should also distinguish between immediate controls and longer-term development. Some gaps can be addressed quickly through clearer procedures, better communication or stronger management oversight. Others require procurement, redesign, recruitment or a change in organisational culture. Presenting both as if they can be solved next month damages credibility.
Cost should be discussed honestly. Security expenditure competes with operational priorities, and leaders need a clear explanation of the consequence of delay. Do not rely on vague claims about best practice. Explain the risk being accepted, the likely effect on people or operations and the practical benefit expected from the proposed action.
Measure readiness, not document completion
The weakest performance measures count activity: policies reviewed, training completed, checks undertaken or equipment installed. These figures are easy to report but may say little about readiness.
Better measures examine whether controls work. Are access breaches identified and resolved? Are reported concerns handled within an agreed timeframe? Can managers account for their teams during an incident? Do exercises show that escalation routes are understood? Are repeat findings reducing, or simply being recorded again?
Use a combination of assurance activity and operational feedback. Audit has a place, but so do conversations with supervisors, observations at sites and lessons from incidents and near misses. A strategy must be reviewed when the operating context changes, not only because the calendar says it is due.
Mildot Group’s view is straightforward: a security strategy should make the organisation harder to disrupt and easier to lead when pressure rises. If the people responsible for delivery cannot explain the priorities, their role and the decisions they are authorised to make, the strategy is not finished. It is only written.
