Making Django Really, Really, Ridiculously Secure (CW)
summary
Callisto secures survivor reports by design not buzzwords it uses Django features like pbkdf2 password rehashing and a CDN for DDoS mitigation hosts on Heroku and removes prod admin access the reports are encrypted with a user-held encryption key so exported subpoenas return unreadable blobs rate limiting and session expiration mitigate brute force and shared-computer risks and password UX uses zxcvbn password strength feedback the project undergoes a formal pen test and fixes found issues per the uploader notes including review by NCC Group audit.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:17MAKING DJANGO REALLY, REALLY RIDICULOUSLY SECURE
- 3:10YOU CAN SECURE DATA ON THE INTERNET
- 6:06YOU GET A LOT FOR FREE
- 9:45KNOW YOUR THREATS
- 13:25YOUR BIGGEST THREAT IS IN THIS ROOM
- 17:03YOUR SECOND BIGGEST THREAT IS WHO YOU'RE TRYING TO PROTECT
- 23:42DON'T GET CUTE
- 24:09SOMEONE SMARTER
related talks
48mPractical Django Secuirty
26mOh, I Found a Security Issue
29mSecuring Django Applications
31mhunter2: A Symphony of Password Horror
27mAccount Security for the Fashionable App Developer
41mProduction Django: Building a Highly Scalable, Secure Django Site
16mDeath Star Security: A Realtime Look At How A Site Is Hacked
37mFrog and Toad Learn About Django Security