Cybersecurity

Privacy and compliance readiness

Laws, sector rules, contracts and insurers expect you to protect information and prove it. We close the technical gaps and prepare evidence, alongside your counsel; we do not give legal advice or certify compliance.

Who this service is for

A good fit if

  • You hold personal information and doubt your practices would survive a complaint or investigation.
  • You operate in or serve Quebec and must prepare for Law 25.
  • Ontario's PHIPA, another health privacy law, or OSFI B-13 or B-10 applies to you.
  • A client, insurer or auditor sent a questionnaire, or you are preparing for certification.

What is included

  • Map of laws, rules, contracts and frameworks, confirmed with counsel
  • Inventory of personal information: where it lives, access, retention
  • Gap review and ranked remediation plan with owners and effort
  • Breach response plan and the breach register regulators expect
  • Vendor and cloud contract review; privacy impact assessment support
  • Evidence packs and answers to client, insurer and auditor questionnaires

Requirements we commonly prepare for

Your counsel decides what applies and how to read it; auditors and certifiers decide whether you meet a standard. We turn their requirements into systems, procedures and evidence.

RequirementWhat it covers
PIPEDAFederal private-sector privacy law: ten principles, including accountability, safeguards and openness; breach reporting, notification and records.
Quebec Law 25A person responsible for personal information (by default the highest authority); incident reporting and register; privacy impact assessments, including before information leaves Quebec.
Alberta and BC PIPAProvincial private-sector laws; Alberta's requires breach notification.
PHIPA and similarHealth information custodians, their agents and service providers.
OSFI B-13, B-10Technology, cyber and third-party risk at federally regulated financial institutions and their vendors.
CASLEmail marketing consent, where in scope.
CyberSecure CanadaFederal certification for small and medium organizations, based on the Canadian Centre for Cyber Security's baseline controls; issued by accredited bodies.
SOC 2, ISO/IEC 27001For enterprise clients; from independent auditors and registrars.
Insurers, clientsQuestions on MFA, EDR, backups, email security, training; clauses on data location, breach notification, subcontractors.
General summaries, not legal advice. For AI questions in audits, insurance and due diligence, AI governance documents AI use, risks and controls (NIST AI RMF, ISO/IEC 42001).

Breach readiness

Early decisions are hard to undo, so the plan names who does each step; we rehearse it with you in a tabletop exercise.

  1. ContainStop the incident spreading.
  2. Assess harmIs there a real risk of significant harm?
  3. DecideReporting and notification, with your insurer and counsel.
  4. RecordKeep the breach record. See breach reporting.

Technical gaps? Security assessments measure controls in depth; cybersecurity closes them: EDR, email security, awareness training.

Delivery

How the work is delivered

  1. Scope the requirements

    Identify the laws, sector rules, contracts and frameworks likely to apply; confirm them with your counsel.

    Output: Requirements map.

  2. Understand your data

    Inventory what personal information you collect, why, where it lives, who sees it and for how long.

    Output: Data inventory and flow diagram.

  3. Review the gaps

    Compare your technical and organizational safeguards with the requirements, and rank gaps by risk.

    Output: Gap report and remediation plan.

  4. Close the gaps

    Update controls, procedures, contracts and training; build the breach plan and register.

    Output: Updated safeguards and breach plan.

  5. Prepare the evidence

    Assemble what an auditor, insurer or regulator would ask for, and rehearse a breach scenario.

    Output: Evidence pack and tabletop results.

Scope at a glance

Not included unless agreed

  • Legal advice, opinions, certification, attestation or audit reports
  • Filing breach reports or notifying individuals for you
  • Fixing technical findings, unless in scope or separately agreed

What we need from you

  • A named person accountable for privacy (often legally required)
  • Your counsel's input, policies, contracts, questionnaires and incident records
  • Time with whoever manages IT, HR, finance and client records

Before handover

  • Each requirement in scope traced to a control, owner and evidence
  • Open gaps listed with an owner and target date, not hidden
  • Breach plan rehearsed by its users; documents your staff can maintain

What affects the cost

  • Laws, rules and frameworks in scope
  • Amount and sensitivity of personal information
  • Systems, vendors and locations
  • Existing evidence, and whether remediation is included

No package prices: estimates in Canadian dollars from an agreed scope, taxes shown separately.

Questions buyers usually ask

What does PIPEDA require after a breach?

Organizations under PIPEDA generally must report breaches of security safeguards that create a real risk of significant harm to the Privacy Commissioner of Canada, notify affected individuals and keep a record of every breach. Quebec's Law 25 and Alberta's PIPA have their own rules.

Does storing data in a Canadian cloud region make us compliant?

Not on its own. A Canadian region (such as AWS Canada Central in Montréal or Azure Canada Central in Toronto) supports data residency; access controls, contracts, support access, backups and transfers matter too. We review the whole picture.

We are a small organization. Does this apply to us?

Generally yes. Privacy obligations apply regardless of size when you handle personal information in commercial activity, but the work scales down to a focused data inventory, a breach plan and a few well-run controls.

Has a client, insurer or regulator started asking questions?

Tell us what has been asked and what information you handle. We will reply to arrange a conversation about getting ready.