Security today: change your habits and make it safer and efficient
summary
Describes security as continuous engineering and gives concrete measures used at Clever Cloud: recompiling KVM to remove unused features (e.g., floppy emulator), weekly shuffling/recompiling binaries per hardware profile to reduce exploit ROI, and recording authorization events in a blockchain-backed audit called "biscuit" for forensic traceability. Recommends developer practices: strong-typed input validation, avoid runtime plugin loading, prefer compiled languages (Rust/Scala), use Argon2/BCrypt for passwords, and operate on the assumption of breaches so all traffic is encrypted and auditable.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:20Insurance or responsibility transfer
- 27:32Example on the linux kernel
- 27:52Kernel size
- 30:29So, about so-called containers....
- 34:00NO FRIENDS, EVERYONE CAN GO ROGUE
- 35:38The complex topics of passwords
- 37:36Code injection
related talks
32mRugged Building Materials & Creating Agility with Security
38mSecuring the Cloud
33mLearning from Past Security Breaches: Strengthening AppSec Efforts and Focus
32mSoftware security as a force of nature
52mContinuous Security
52mPrinciples for Developing More Secure Systems
26mBoost your security and resiliency in Kubernetes
52mSecurity in Cloud-Native