Canadian election databases use "canary traps"—and they work
Summary
The canary trap, a security technique used to identify information leakers, involves distributing unique versions of a document or database to different recipients. Each version contains subtle, individualized alterations, allowing the source of any leaked information to be pinpointed if those specific changes appear. This method, a staple in espionage fiction and practice, recently gained public attention in Canada when Elections Alberta used it to identify the source of a leaked electoral list. The list, containing voter information, was provided to political parties with usage restrictions. Elections Alberta had salted the Republican Party of Alberta's copy with bogus entries, which subsequently appeared in an online database run by "The Centurion Project," a separatist group. This enabled officials to quickly confirm the Republican Party's copy as the source of the leak, leading to the site's shutdown.
Key takeaway
For CTOs and VPs of Engineering managing sensitive data distribution, implementing canary traps offers a robust, low-tech solution for leak detection. Your teams should consider embedding unique, non-obvious identifiers into critical datasets or documents shared with external parties. This proactive measure provides clear attribution, enabling swift action against unauthorized disclosures and reinforcing data governance policies.
Key insights
Canary traps embed unique identifiers into distributed information to trace leaks back to specific recipients.
Principles
- Uniqueness identifies source
- Subtle changes are effective
Method
Distribute information with unique, recipient-specific alterations (e.g., bogus entries, synonym-shuffled paragraphs). Monitor for these alterations in any leaked data to identify the source.
In practice
- Embed unique IDs in sensitive documents
- Use AI to generate plausible false data
Topics
- Canary Trap
- Data Leak Detection
- Electoral List Security
- Elections Alberta
- Information Security Techniques
Best for: CTO, VP of Engineering/Data, Security Engineer, AI Security Engineer, Legal Professional
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by AI - Ars Technica.