Currently the session id is logged directly (on debug level).
This allows a malicious user to hijack the session.
We could change the logging of the session id for a trace and/or span id.
We could also look into a distributed tracing mechanism, since multiple services are being called from the same frontend.
The distributed tracing mechanism can show insights on potential bottlenecks and can show an audit log of what a user has done between a specific timespan.
Currently the session id is logged directly (on
debuglevel).This allows a malicious user to hijack the session.
We could change the logging of the session id for a
traceand/orspanid. We could also look into a distributed tracing mechanism, since multiple services are being called from the same frontend. The distributed tracing mechanism can show insights on potential bottlenecks and can show an audit log of what a user has done between a specific timespan.Examples of distributed tracing mechanisms: