What happened.
The Office of the Privacy Commissioner of Canada investigated a breach in which an employee copied personal information from shared storage. Data had moved from controlled systems into locations accessible to employees who did not have the same rights in the original warehouse. The investigation identified deficiencies in safeguards and retention.
The 9.7 million figure concerns individuals described in the OPC investigation, while the frequently cited 4.2 million figure concerns active-account holders. The settlement cap of approximately C$200.9 million is an aggregate amount, not compensation for each individual. The OPC also recognized the organization’s response after the breach was discovered.
Protection can weaken as information is copied, retained, and reused. A risk workflow needs explicit authority for the data it receives, limited access, and an evidence trail that survives handoffs.
From individual facts to a fuller picture.
- Personal information was copied into shared folders outside the original warehouse access controls.
- The OPC identified retention and safeguard weaknesses, and recognized the post-discovery response.
- What authority supports collecting and retaining each item of customer evidence?
- Can reviewers explain who accessed a record and why it was needed?
- How are affected-customer follow-ups assigned, documented, and completed?
The review questions are analytical prompts. They do not establish that particular data was available to the institution at the time, or that a different process would have changed the outcome.
A different decision starts here.
Improve the financial investigation that follows compromised information, with controlled access to the evidence used for each decision.
Authorized customer identity records, financial activity, investigation labels, and permitted workspace access and audit records.
01 Keep evidence access accountable
- Evidence to connect
- The evidence needed for a financial review and the institution’s permitted users and roles.
- Amlok output
- A scoped review package with source references and an auditable record of access within the configured Amlok workflow.
Decision it could supportLimit review access to the approved purpose and retain the evidence used for a decision.
02 Resolve identity with corroborating evidence
- Evidence to connect
- Customer records, account ownership, financial counterparties, and independently supported relationship evidence.
- Amlok output
- Resolved, uncertain, and conflicting links rather than identity matches based on a shared attribute alone.
Decision it could supportSend uncertain links for human review before using them in a post-incident financial investigation.
03 Connect activity to the investigation
- Evidence to connect
- Authorized transaction records and the verified parties associated with them.
- Amlok output
- Named counterparties and linked activity that investigators can compare with the incident scope.
Decision it could supportPrioritize supported financial anomalies and record the basis for further investigation or customer support.
Put numbers behind the opportunity.
These scenarios apply Amlok’s supplied comparison rates to the review described above. They are projections, not measured results at Desjardins. Count-based scenarios use an assumed population, not the institution’s actual records.
Graph relationship precision
Assumed population: 1,000 accepted identity and account links.
A post-incident investigation could work from a more accurate set of accepted financial relationships.
Calculation & assumptions
Comparison inputs: 80% → ≈95%.
Population calculation: 1,000 × 80% = 800; 1,000 × 95% ≈ 950. Difference: ≈150 additional.
Relative change: (95 − 80) ÷ 80 × 100 ≈ +18.75%.
15 percentage points higher than the input baseline. Assumes authorized data and independently labeled links. Holds the accepted-link population constant; it does not measure identity-theft prevention.
View the supplied comparison inputsNamed counterparty coverage
Assumed population: 1,000 eligible post-incident financial records.
More reviewed financial activity could be connected to a named party for investigation.
Calculation & assumptions
Comparison inputs: 65% → ≈86%.
Population calculation: 1,000 × 65% = 650; 1,000 × 86% ≈ 860. Difference: ≈210 additional.
Relative change: (86 − 65) ÷ 65 × 100 ≈ +32.31%.
21 percentage points higher than the input baseline. Assumes comparable counterparty evidence is available. The population is a financial-review scenario, not the people affected by the breach.
View the supplied comparison inputsFrom a projection to a validated result.
Use an authorized, labeled post-incident financial-review set. Compare correct and false relationship links, named counterparties, and access-log completeness without using breached data as proof of identity.
Amlok is not an endpoint or data-loss-prevention system. These figures do not estimate a breach prevented or a reduction in affected people. The supplied comparison rates are approximate scenario inputs; no institution-specific replay or confidence interval is available for these estimates. The two metrics describe separate dimensions and should not be added together.
Read the source material.
This is a data-governance case, not evidence of an Amlok deployment. Endpoint monitoring, USB controls, and data-loss prevention remain separate security capabilities.
- 01
- 02
- 03Canadian Underwriter / Canadian Press: settlement approval and the 4.2M active-account figureReputable reporting, corroboration
Amlok’s interpretation is independent of the institutions discussed. Public records are limited to their stated scope and period. Historical figures describe the source events; the separately labeled Amlok scenarios are calculated projections. Institution names and logos do not imply affiliation or endorsement.
