Eat Your Vegetables Data Security for Data Scientists
summary
Claim: basic hygiene plus a few concrete tools block most attacks while full cryptography is hard. Evidence and examples: Lloyds estimates ~$400B annual loss, Heartbleed and Code Spaces failures show supply‑side risk, Nissan Leaf leak shows missing access control, TLS via Let's Encrypt is cheap, use short‑lived credentials and account separation to limit blast radius. Practical builds: sign artifacts for integrity, avoid unencrypted logs, use client‑side encryption or provider Key Management Service, prefer the high‑level cryptography library over raw pycrypto/pyOpenSSL.
AI-written summary · about
chapters (10)
- 0:00Data security introduction
- 3:16Why security matters
- 8:33Easy security wins
- 16:25Account separation credentials
- 21:00Data integrity signatures encryption
- 27:38Safe encrypted data handling
- 30:27Python security libraries
- 33:18Cloud security features limits
- 36:07Summary key takeaways
- 37:32Q&A cryptography standards
related talks
21mData Security for Data Engineers
52mPrivacy & Security, Policy & Technology
50mSecuring IoT Data with Pervasive Encryption
44mCryptography in the age of Heartbleed
35mCYBERSECURITY! The good, the bad, and the hacked
22mSecurity for Data Scientists
16mSecurity, Fraud, and Compliance
42mReal-World Security Implementations and Key Lessons