Secure Your Logs Down to the Root
summary
Includes a concrete description of forward-secure sealing and why per-interval keys prevent retroactive tampering, explains redaction/tokenization with database references rather than dumping PII into logs, prescribes append-only files plus per-file encryption and key rotation, details TLS and limited-key ingestion for secure shipment, demands access controls and separated tenants on aggregation, sets up alerts for interrupted log shipping, and clarifies the operational difference between delete versus wipe.
AI-written summary · about
chapters (20)
- 0:00Start
- 1:25Quick Overview of Terms and Concepts
- 1:40Hash: obscuring data (one-way)
- 2:03Encrypt: obscuring data (reversibly)
- 3:08Always be aware of your objective(s).
- 4:30The main event: how does this apply to logs?
- 5:08Do not. write. sensitive data. to your logs.
- 6:31Essentially, log only what you need.
- 6:56"What if I really need that sensitive data", you ask?
- 7:14Food for thought, this is CWE-532.
- 8:21Now what to do with these logs?
- 14:36Closing Tips
- 15:00Know your infrastructure
- 15:19Know your risks
- 16:18Trust, but verify
- 16:42Use your metrics
- 17:06Protect & utilize your audit trail
- 17:43Use well designed alerts judiciously
- 18:27Don't be a target - find help as needed
- 19:21Prevention is the difference between This Is a Problem and This Is a Disaster.
related talks
29mApplication logging in the era of GDPR
26mSecuring Containers: Preventing Data Leaks
39mPrivacy-preserving Approaches to Transparency Logs
29mCrucial Log Management Skills for DevSecOps
48mOWASP cautions against “insufficient logging & monitoring.” What does sufficient l...
58mWhat the log4j incident taught us about Secure by Design
40mSecure application design with high data privacy requirements
37mAdd security to architecture one step at a time