improving data protection
summary
Company productizes format-preserving encryption to deidentify records so credit card numbers still look like cards but have no value, and integrates key management with emerging Hadoop features such as transparent HDFS encryption and column-level protection in Hive/Falcon. Recommended operational steps: perform a full data inventory, never store credit card numbers in plaintext, deidentify at ingestion, apply tokenization or column/volume encryption where needed, and treat encryption as an IT utility with developer-friendly APIs.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:42Is data nowadays different
- 3:26How to make data more secure
- 5:21Data identification
- 6:51Encryption in Hadoop
- 8:02Advice to CIOs
- 9:46Whats next for Voltage
related talks
30mProtecting Data While Maintaining Analyzability & Its Business Value: Is It FACT or FICTION
47mData at Rest Encryption Going Beyond the Basics to Address Modern Attacks
41mKeeping Secrets: Emerging Practice in Database Encryption
26mDefining a Data Masking Framework at Scale
24mData Security for startups
24mStop Making Your Data Team the 'Data Police'
40mSecure application design with high data privacy requirements
31mDemystifying Data Protection: Steps To Find, Monitor And Control Without Chaos