Securing IoT Data with Pervasive Encryption
summary
13 billion breached records since 2013 and only 4 percent encrypted makes the case concrete: protect IoT health data at every hop — device, network, app, database, storage and archive. Regulatory titles matter: HIPAA, PCI DSS and GDPR impose obligations. Use TLS (including TLS 1.3) for transit, prefer AES-256 for strong rest encryption, avoid DES (56‑bit keys break in days), use database/column-level crypto to protect memory buffers, enforce key management (lost keys = unrecoverable data), and consider HSMs, crypto anchors and emerging homomorphic encryption.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:42Eyshas background
- 4:02Eyshas current role
- 6:59Eysha background
- 7:42Internet of Things
- 8:59Data Security
- 10:37Personal Health Information
- 12:05IoT Data
- 12:29Who Does HiTech Impact
- 13:18GDPR
- 15:15Risk
- 18:25Information Lifecycle
- 19:43Where might your data reside
- 21:55Data flow chart
- 24:15Encryption in flight
- 27:34Data Arrests
- 34:06Encryption
- 41:08Encryption keys
- 43:37Encryption engines
related talks
47mData at Rest Encryption Going Beyond the Basics to Address Modern Attacks
30mSecuring the Connected World - Detangling Encryption and Decryption
28mSecuring the IoT: High-speed cryptography and Edward Snowden
40mEat Your Vegetables Data Security for Data Scientists
49m4 Ways IoT Devices Are Creating Privacy Implications For Organizations
41mKeeping Secrets: Emerging Practice in Database Encryption
46mPrivacy Preserving IoT
26mPrivacy Issues in Big Data Processing in light of Data Breaches