5. Incident Response

Version 1.0 · Adopted 2026-10-25 · Owner: Security Officer · Review: yearly

Any suspected security or privacy incident is logged within 1 hour, contained as fast as possible, assessed for a real risk of significant harm, and, when that risk exists, reported to the regulators and the people affected as soon as feasible.

Severity

Level Meaning Response
SEV-1 Active compromise of money, keys or member data Start within 15 minutes; on call until contained
SEV-2 Exploitable weakness with no sign of use, or an outage Start within 4 hours; fix within 24 hours
SEV-3 Limited weakness Fix within 7 days

Steps

  1. Detect and log the incident in the incident register.
  2. Contain it: block the route or address, disable the feature, revoke tokens, end sessions, rotate the affected secret, or pause payments or withdrawals.
  3. Preserve evidence before changing anything.
  4. Fix through the emergency change path.
  5. Assess harm: what information or money was affected, how many people, and whether there is a real risk of significant harm.
  6. Notify as set out below.
  7. Recover: restore from backup where data changed; reverse fraudulent ledger entries with a recorded reason.
  8. Review: a blameless post-mortem within 10 business days.

Notification duties

Who When Law
Office of the Privacy Commissioner of Canada As soon as feasible after determining a breach creates a real risk of significant harm PIPEDA s. 10.1
Commission d’accès à l’information du Québec Promptly, for a confidentiality incident presenting a risk of serious injury Quebec private-sector Act s. 3.5
Affected individuals Directly, as soon as feasible, with what happened and what they can do PIPEDA s. 10.1(3); Quebec s. 3.5
Organisations that can reduce the harm When notifying them may reduce the risk PIPEDA s. 10.2

Every breach of security safeguards is recorded and kept for at least 24 months, whether or not it was reported (PIPEDA s. 10.3; Quebec s. 3.8).

Contacts

Security: security@gend.me · Privacy: privacy@gend.me