Writing a small-business security action plan
Define the scope of a small-business security plan, record control gaps and assign owners, evidence and review dates for the work.

A security plan needs to connect business priorities with work someone can complete. A list of products doesn’t show which systems are covered, who responds to an alert or whether the business can recover.
Start with a manageable scope and record the gaps. Include leadership, the people running the work and IT so decisions about cost, access and disruption have an owner.
Define the systems and information in scope
List the accounts, devices, applications and locations the plan covers. Include outsourced services and the information staff share with clients and suppliers.
Describe the effect of losing access, exposing information or making an incorrect change. Identify work that must continue during an interruption.
Record exclusions and the reason for them. A vendor-controlled device still needs an owner and a decision about its dependencies, even when your team can’t change its configuration.
Use guidance as a starting point
The Cyber Centre’s baseline controls for small and medium organizations provide a Canadian reference for scoping security work. They aren’t a complete assessment of every business or a certificate of compliance.
Use the relevant controls to ask concrete questions about updates, device protection, sign-in, backups, staff training and response. Requirements from your sector, contracts and applicable law need separate review.
Our attack-path checklist helps connect a control with the situation it’s meant to address.
Record evidence and gaps
For each area, note the current arrangement, its coverage and the evidence checked. Buying a licence or installing an app doesn’t mean anyone has set it up or is watching its alerts.
Examples of useful evidence include a representative device’s update state, an account’s sign-in policy and a completed restore test. Note what the sample can’t show about the rest of the environment.
Treat unknown coverage as a question to resolve. Don’t turn an unverified answer into a completed action just because a supplier believes it’s included.
Prioritize the work with management
Rank gaps by the business effect, exposure, dependencies and practical effort. Identify urgent containment separately from work that needs a planned change.
Give each action an owner, target date and acceptance check. State required licences, staff time and supplier involvement. When management defers work, record the reason, temporary measures and next review date.
MFA, firewalls and device protection address different risks and still have limitations. No single product covers the whole plan.
Agree who handles incidents and recovery
Name the internal decision-maker and the technical contact. Confirm the support arrangement, escalation path and responsibilities with the provider.
Keep essential contact information available if email or the main business system fails. Practise an incident discussion and a recovery task with the relevant people.
Review completed work and remaining exceptions
Close an action only after its acceptance check. Keep the result with the plan and schedule a review after important business or system changes.
Cybersecurity planning can help define this work. The business still needs to decide its priorities and know which responsibilities stay with its staff and suppliers.


