Hi,
We recently noticed, that the logging feature of RDM+RDGW is not sufficient, when it comes to Devolutions Gateway Tunnel with dynamic targets (SOCKS/HTTP Proxy listener). What is logged is only who and when started/stopped the tunnel, but not what connections went over it. This is a major security gap, as because it is possible to define a filter that would wildcard the target host it is then not possible to know what connections were made over this type of tunnels.
In the diagnostic logs of the Gateway itself, there are some jmux lines containing target IP/port/protocol informations, but to corelate them with a particular open session, user information of who opened it etc. is very cumbersome and I am not even sure if the retention of this diagnostic informations is sufficiently long.
In order to provide non-repudiality and a complex end-to-end secure connection logging, in my opinion this feature is a must. Especially that the gateway has all the informations needed.
In addition to the minimal log informations like who, when started and when finished and of course target host/port/protocol it would be also a nice to have feature to get as well some basic statistics as number of bytes in/out. This should be really trivial to implement and would close a very important security gap, that currently allows to pass *not audited* connections over devolutions gateway that will be really hard to proof.