@valorin You want the IP. Or any other way to follow "usersessions". And when you need to debug login issues also some user id.
But in general all userinfo is PII. whether that is a name or an email or an ID. As we need to be able to identify the user with it. Even the ID is not anonymized but at max pseudonymized.
So I'd rather only log that in special cases/times for debugging than in general.
@valorin Only option I see is to use a non-stored hash of some sort of some user info.
That way it should not be possible to identify a specific user from the log entry but you can group things from tue same user. But that is only of limited help in special cases so being able to activate additional logging on-the-fly is helpful.
@heiglandreas
You're thinking of it purely from a debugging point of view. I'm not talking about debugging, I'm saying that you need logging for security reasons. You need to be able to actively monitor activity and identify attacks on your app. Debugging doesn't and cannot give you this.
@valorin absolutely. But do you need PII to fimd attack patterns? Or aren't we more talking about an audit trail? Which at least to me isn't about logging but about specific acrions specific users did. Which is rather domain specific and so usually needs a separate process. Especially as that information might need to be kept for legal reasons for a longer time than a log.
@heiglandreas
I feel like we're going around in circles a bit here...
My point was simply that logging login activity is good for security. That could be verbose logs, or anonymous logs, an audit trail, a separate process, or something else entirely. If you have visibility of what's going on in your login flow, you may be able to identify attacks and malicious behaviour.
If you have PII and/or legal requirements, then by all means follow them. 🤷
Add comment