News for hackers. Stuff that matters.
Re:We found and fixed a rare race condition in our session h... by kevingadd on Thursday March 18, 2021 @08:07PM (#26508934)
It's pretty common to do exhaustive logging even if the data is enormous. It's valuable for debugging and security investigations. As far as the security of storing log data, you need log messages to not contain PII regardless of how long you retain them.

It's not uncommon to see companies talk about processing terabytes or even petabytes of log data per day. In the end the storage isn't that expensive [1], and you can discard everything after a little while.

[1] Assuming of course that any company generating a petabyte of logs every day is doing so because they have an enormous number of customers, AFAIK the cost of storing 1PB of logs on something like Glacier is in the 100-300k USD/yr range. Absolutely a tolerable expense for the peace of mind you get by knowing you can go back in 2 months and find every single request that touched a security vulnerability or hunt down the path an attacker took to breach your infrastructure.

Re:We found and fixed a rare race condition in our session h... by marshmellman on Saturday March 20, 2021 @03:06AM (#26521368)
Any idea how GitHub could tell that the cookies in the response are wrong, without logging the session cookie?
Re:We found and fixed a rare race condition in our session h... by londons_explore on Sunday March 21, 2021 @05:55AM (#26529319)
Just log the session cookie...