Hi, I’m currently investigating Teltonika as a solution for allowing our customers to have remote access the IOT products we sell them via our cloud solution and was surprised that the remote access links that Teltonika creates are public URLs with no authentication.
These URLs are hard to guess, but that doesn’t stop intermediaries on the network from seeing the traffic.
A fix for this might be that when creating a link an allow list of IP addresses that can make requests to the link could be provided preventing anyone who gains access to the URL from accessing the IOT device on the internet.
This would allow us to proxy the remote connections via our servers, with authentication, and limit the networks the remote access link is exposed to.
If I’m missing some features that harden these links, please let me know.
For a more secure remote access solution, I would recommend using RMS VPN Hubs. This feature allows you to create a controlled VPN environment where only authorized clients can connect. Within a VPN hub, you can explicitly define which clients are allowed access, and only those clients will be able to reach the devices that are assigned to the same hub. This provides a significantly higher level of security compared to publicly accessible links.
For more information about RMS VPN hubs you can refer to this wiki article:
Additionally, RMS VPN supports different connection methods (such as OpenVPN), giving you flexibility depending on your use case and security requirements. You can also manage access centrally, monitor connections, and revoke permissions when necessary.
At the moment, there is no functionality that allows restricting access to generated RMS links based on specific IP addresses.
If your use case requires stricter access control, implementing an RMS VPN Hub would be the recommended approach.
If you have any further questions or need assistance setting this up, please feel free to let me know.