Security Control Enhancements
summary
Timeline of concrete Java security changes from Java 8 → 17: SHA‑3 hashing and SHA‑3‑based signatures appear (Java 16), TLS 1.3 and AES‑GCM support mature, ChaCha20/Poly1305 added, root CA store modernized, keytool revamped and security manager tightened. JEP 290 ships a JEP 290 deserialization filter but raw Java serialization remains risky — crafted serialized maps can crash the JVM. Recommends Google Tink or libSodium for crypto primitives. Release cadence shifts to six‑month cycles, breaking old monolith deployment patterns while adding practical mitigations.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:50Java Community
- 3:50Java Enhancement Proposal
- 5:47Java Crypto
- 11:35Java Deserialization
- 14:17Java Deserialization Filter
- 21:10SHA3 Implementation
- 23:44TLS 10 Implementation
- 27:25Java 11 Implementation
- 34:37Java 12 Implementation
- 35:22Java 13 Implementation
- 37:37Java 15 Implementation
- 40:06Java 16 Implementation
- 41:03Java 17 Implementation
- 46:08Digital Signatures
related talks
37mKeeping Your Java Applications Secure - Cryptographic Improvements and Best Practices
44mMaking the JDK More Secure
45mFrom Java 17 to 21: A Showcase of JDK Security Enhancements
39mEvolving the Security of the Java Platform
40mJava Security Evolution - Out with the Old, In with the New
50mMaking the Future Secure with Java
51mJava and Post-Quantum Cryptography
40mMaximizing Security with JDK: Understanding Built-in Capabilities