Topics of Interest: Five philosophies to building better application logs
summary
A concrete claim: the five philosophies (simplicity, tagging/metadata, hygiene, assume compromise, device-aware storage) produce forensically useful logs; evidence includes 12 years of incident work finding secrets in logs and a case where adding event categories surfaces an influx tied to a faulty component. Tools and artifacts include an OWASP secure logging benchmark spreadsheet, examples like Apple-style tagging, sprint-based log debt fixes (one backlog item per sprint), training materials and an active project that shows measurable debugging gains.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:29Who am I
- 2:33Understanding the attack process
- 4:06Unicorn Project and Phoenix Project
- 4:47The 5 philosophies
- 8:53The developers
- 9:09Keep it simple
- 10:33Keep it tagged
- 12:30Keep it cleaned
- 14:23Log accordingly
- 16:20Consider who has access to logs
- 17:54Incident response
- 19:17Be kind to your future
- 23:03Outro
related talks
05mLogging is a Team Sport
38mLogging as a Painkiller
29mAre logs a software engineer's best friend? Yes - follow these best practices
27mLogs Are Good, Actually
36mBeyond grep: Practical Logging and Metrics
29mCrucial Log Management Skills for DevSecOps
48mI Want to See My Logs
39mThe 5W’s of Observability with Practical Examples