A Look Into Quantum-Safe Postgres
summary
Claims that quantum reduces brute force times from weeks or months to days or hours, cites IBM Cucabaro at 4,158 qubits and predicts cloud quantum access in one to two years, recommends following NIST and using AES-256 through 2050, compares disk, filesystem (LUKS) and DB options including PGcrypto, urges a Fujitsu 256-bit tablespace encryption example plus hybrid encryption, careful key management and rotation, and flags potential but unmeasured performance impacts.
AI-written summary · about
chapters (14)
- 0:00Quantum-safe Postgres intro
- 1:04Who is Tim Stewart
- 3:10Data encryption explained
- 7:27Quantum threats to encryption
- 9:38What is a quantum bit
- 11:25IBM’s quantum roadmap
- 16:01Quantum computing use cases
- 17:06NIST quantum-safe standards
- 20:23Postgres post-quantum strategies
- 23:41Robust encryption strategy
- 25:54Fujitsu’s quantum-safe Postgres
- 27:20Encryption security lessons
- 29:32Right encryption matters
- 29:55Q&A
related talks
37mPreparing for Constant Change With Quantum Agility
21mCybersecurity in the Age of Quantum
43m📙 Is Q-Day Worse than Y2K? Strategies for Surviving the Quantum Threats
05mLightning Talk: Building Quantum-Safe Applications
20mCryptographic Resilience in the Quantum Era
27mQ-Day Survival Guide: What the Post-quantum Cryptography Transition Means for Confidential Computing
20mPost-Quantum Cryptography- Preparing digital communication for a Q
40mWhy Quantum Safe Encryption Is the Next Y2K and How to Be Prepared