2 ms·
Just remember to scrub the logs for privacy sensitive data. Logs are number one for privacy violations. Pin codes, passwords, social security numbers etc. Peop
by flurdy 7y ago
Just remember to scrub the logs for privacy sensitive data.
Logs are number one for privacy violations. Pin codes, passwords, social security numbers etc. People remember to hash the data in their databases, but logs are often forgotten about, then stored and archived containing data that are illegal under many laws such as GDPR. And obviously also a security risk.
Developers most of time remember to scrub the data out of actual log messages but forget trace and rawer logged data also go into some log aggregators.
I am sure I have accidentally done it as well, though I try my hardest not to.
* Twitter: https://twitter.com/TwitterSupport/status/992132808192634881 https://twitter.com/TwitterSupport/status/992132808192634881
* Monzo: https://www.zdnet.com/article/monzo-admits-to-storing-payment-card-pins-in-internal-logs/ https://www.zdnet.com/article/monzo-admits-to-storing-paymen...
* Github: https://www.bleepingcomputer.com/news/security/github-accidentally-recorded-some-plaintext-passwords-in-its-internal-logs/ https://www.bleepingcomputer.com/news/security/github-accide...
* Facebook: https://www.wired.com/story/facebook-passwords-plaintext-change-yours/ https://www.wired.com/story/facebook-passwords-plaintext-cha...
- davinic 7y agoOften you're not scrubbing individual data, you're logging the contents of an entire object. In this case, depending on the language, I will usually use an annotation/decoration on the object itself so the logging platform will know not to log it. I have also seen this method used in environments subject to HIPAA regulations.