What is a one sentence summary of your feature request?
Implement a policy exit point or update the existing VNC exit point to that it is able to log/identify TightVNC file transfers.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Based on some testing, the current VNC policy exit point doesn’t log any TightVNC file transfers. It will log RealVNC, just not TightVNC which is heavily used in my environment. I’d like the ability to be able to monitor any file transfers happening over TightVNC.
How do you currently solve the challenges you have by not having this feature?
I currently don’t have any solution to this problem, if there is one I would love to learn about it.
Thank you for the detailed report and for taking the time to test and document the behavior. We have registered this as a feature request with our engineering team for further investigation.
Our team will look into extending the VNC policy exit point to cover TightVNC file transfer activity. While we cannot commit to a timeline at this stage, your submission has been noted and will be considered in our planning process.
If there are any updates or if we require additional information from your environment during the investigation, we will reach out to you directly.
We appreciate your feedback — reports like this help us prioritize coverage gaps that matter to real-world deployments.