Colour theme
Book a consultation

Managing communication after a data breach

Coordinate evidence, decisions and clear updates after a suspected data breach, with Canadian notification assessment and a verified contact route.

An open combination padlock resting on a laptop keyboard.

A suspected data breach creates several jobs at once: containing the incident, finding out what happened, assessing obligations and helping the people affected. Clear ownership keeps those jobs from working against one another.

Don’t wait for a finished investigation to activate the incident process. Assign a response lead, technical contact, privacy decision-maker and person responsible for communications. Use a verified channel if normal email may be compromised.

Keep facts separate from assumptions

Create a restricted incident record with the discovery time, affected services, actions taken and evidence sources. Mark what is confirmed, suspected or still unknown. Update that distinction as new information arrives.

Preserve relevant records with the technical responder. Avoid wiping a device, deleting messages or changing log settings as an improvised cleanup step. Urgent containment and evidence preservation need to be coordinated.

Keep a decision log too: who authorized an action, why, when it happened and what remains to be checked.

Assess the notification duties that apply

Involve the privacy lead and legal adviser in working out which laws, contracts and reporting requirements apply. A technical outage and a personal-information breach aren’t the same assessment.

For organizations subject to PIPEDA, the OPC’s breach guidance explains reporting to the OPC and notifying individuals where a breach creates a real risk of significant harm. It also addresses records of all breaches and notification as soon as feasible after determining that a reportable breach occurred.

Record the assessment and revisit it when the facts change. Sector and provincial requirements may also apply; don’t borrow a deadline from another country’s guide.

Send one clear message with a contact people can verify

State what is known, what information may be involved and what the affected person can do. Explain uncertainty plainly. Avoid assurances that no data was taken unless evidence supports that conclusion.

Give staff the agreed wording and a place to send questions. A customer shouldn’t receive incompatible explanations from support, management and a supplier. Have the technical and privacy leads review factual statements before release.

Provide a known contact route for checking whether a notice is authentic. Don’t ask recipients to provide passwords or full identity documents by replying to an ordinary email.

Make help usable for the people affected

Choose practical instructions based on the information involved. Account recovery, payment verification and identity-related assistance address different risks. Avoid a generic list that shifts all responsibility to the recipient.

Offer an accessible way to ask questions and explain when the next update is expected. Send a correction if earlier advice changes. Keep the communication record with the incident file.

Separate restored service from resolved exposure

Restoring files or reopening a system doesn’t retrieve information already disclosed. Track technical recovery, privacy assessment and outstanding notifications as separate work with named owners.

Before closing the response, review the incident record, communication gaps and corrective actions. Verify that fixes were completed and that the contact routes still work. Use the findings to improve the next exercise.


Featured Image Credit