Five inputs to your next security plan
Turn AI use, cryptography changes, public exposure, ransomware readiness and insurance questions into specific decisions for your next business security plan.

A security plan needs to account for changing tools and business dependencies. It also needs to keep routine work funded: updates, access reviews, recovery tests and incident preparation.
Use these five subjects as inputs to the next planning discussion. For each, record what has changed in your business, the evidence available and the decision needed. Industry forecasts describe other businesses, so base each decision on your own systems and records.
1. AI use and decision authority
List the AI applications the business uses, the information sources they connect to and any actions they can take. Identify the person accountable for accepting outputs and signing off changes.
Check whether proposed uses need access your business hasn’t granted. Include features a supplier has added to an existing subscription, as well as tools staff signed up for themselves.
Choose one review or pilot with a clear acceptance test. The AI application access guide covers data flows and permissions. Use its findings to decide whether the next step is configuration, training or a different design.
2. Cryptography and supplier roadmaps
Post-quantum cryptography addresses the future threat of a quantum computer capable of breaking vulnerable public-key cryptography. Don’t assume that all encryption is already broken or replace algorithms without a supported migration plan.
The Cyber Centre’s Government of Canada migration roadmap recommends inventory, planning and coordinated implementation. Its departmental milestones aren’t a blanket deadline for every Canadian business.
Ask important software, cloud and hardware providers about their supported roadmap. Identify information that needs protection for many years and systems that are difficult to replace. Bring those dependencies into lifecycle planning and test compatibility before making a change.
3. Public exposure and service disruption
Review the services people outside your organization depend on: the website, client access, email and published contact channels. Ask who controls them and how the business handles an unavailable or altered service.
For a public campaign or contentious event, discuss whether exposure and support needs change. Avoid predicting that a particular group will target the business without evidence.
Check domain and administrator access, provider escalation routes and an alternative way to contact clients. Run a tabletop exercise to practise decisions without sending attack traffic at a live service.
4. Ransomware recovery and incident responsibilities
Bring recent backup and recovery evidence to the meeting. Identify essential records, missing dependencies and what must happen before restored systems return to service.
The Cyber Centre’s baseline controls cover incident planning, updates, access and tested backups. Use them to find gaps in everyday operations as well as longer-term projects.
Include the possibility of stolen information. A restore doesn’t settle privacy obligations or communications with affected people. Assign an incident coordinator and confirm access to the advice and providers the plan relies on.
5. Insurance terms and control evidence
Before renewal, have the business owner and broker review the policy wording, application questions and incident contact procedure. Don’t assume that every cyber policy provides the same recovery services or covers the same losses.
Ask IT for evidence supporting each answer about controls. Record uncertainty and resolve it with the broker or insurer before signing. Keep the renewal evidence guide with the application records.
An insurer’s requirements may change your priorities. Buying cover won’t tell you whether the controls work.
Put decisions into the operating plan
Give each action you agree on an owner, budget and acceptance check. Separate urgent corrections from changes that need supplier coordination or a renewal decision.
Keep unresolved dependencies visible. At the next review, compare the expected result with evidence from the completed work and adjust the plan.


