All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Keeping Secrets Out of Logs: A Defense-in-Depth Approach

By

xk3

8mo ago· 31 min readenInsight

Summary

This article discusses strategies for preventing sensitive data (secrets, credentials, PII) from being written to application logs. The author argues there is no single silver bullet solution, but rather a combination of layered approaches ("lead bullets") that can significantly reduce the risk. Based on a talk given at LocoMocoSec 2024, the post covers practical techniques such as structured logging, log scrubbing, detection and alerting, developer education, and tooling to catch secrets before they reach log output. The emphasis is on defense-in-depth rather than relying on any one fix.

Key quotes

· 3 pulled
There's no silver bullet, but if we put some 'lead' bullets in the right places, we have a good shot at keeping sensitive data out of logs.
This post is about how to keep secrets out of logs, and my claim is that (like many things in security) there isn't a singular action or silver bullet that lets you do this.
I would go so far as to say that there's not even an 80/20 rule, where one action gets you 80% of the way there.
Snippet from the RSS feed
There's no silver bullet, but if we put some "lead" bullets in the right places, we have a good shot at keeping sensitive data out of logs.

You might also wanna read