Defining a Data Masking Framework at Scale
summary
Example company RealCorp evolves from blanket encryption to hashing, then to format-preserving encryption and finally to tokenization to enable analytics while protecting salaries and IDs; an IBM-inspired scheme uses epoch-based token key rotation with update tweaks so hosts can roll mappings forward without rekeying the whole dataset. Presentation lists concrete failures: hashing is rainbow-table vulnerable, FPE leaks type-based inferences, token maps fail catastrophically if breached, and masking often preserves too much structure.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:04Data security evolution
- 6:23Tokenization approach
- 9:35Dynamic key rotation
- 11:22Privacy vs security
- 13:30User-facing privacy controls
- 15:58Other protection techniques
- 18:08Choosing protection strategies
- 19:54Common pitfalls
- 21:39Q&A session
related talks
40mKeeping data private in real-time pipelines
12mStriking the Balance: Safeguarding Customer Privacy While Empowering Employees
51mKeynote: Data is a new security boundary
30mProtecting Data While Maintaining Analyzability & Its Business Value: Is It FACT or FICTION
32mAnonymization and Dynamic Masking with PostgreSQL
24mStop Making Your Data Team the 'Data Police'
11mimproving data protection
26mAnalytics & Data Science with Privacy at its Core