The safest exposed service is the one that is not exposed
Firewalls, VPNs, strong passwords and encryption are essential controls. But they all protect an access path that still exists. If a remote-maintenance gateway remains connected around the clock, it must remain secure around the clock.
For equipment that only needs occasional remote maintenance, another principle is possible: make the remote path available only during the intervention. Outside that window, there is no active tunnel providing remote access to the maintenance LAN.
A smaller attack window
Reducing the time during which remote access exists reduces the period in which that access can be targeted. This does not replace authentication, encryption or good network design; it complements them by removing unnecessary exposure.
This is particularly relevant for PLCs, HMIs, BMS/SCADA equipment and industrial PCs that may remain installed for many years while remote maintenance is required only occasionally.
Independent from the customer’s Internet connection
RescueLAN uses its own 4G/LTE connectivity. The customer does not need to expose an inbound port, modify the site router or provide a permanent VPN account. The industrial network therefore does not need a permanent Internet-facing maintenance route simply to keep future support possible.
What happens during an intervention?
When remote maintenance is required, RescueLAN is started and establishes the connectivity needed for the session. A temporary encrypted path is created to allow the authorised maintenance session. Once the session is finished, that temporary remote-access path is closed again.
The objective is not to claim that any connected system is invulnerable. It is to combine normal security controls with a simple architectural advantage: do not keep remote access available when nobody needs it.
Security through reduced exposure
For occasional maintenance, permanent connectivity is not always an advantage. An on-demand architecture limits exposure by design: access is available when there is a legitimate operational need and is removed afterwards.
That makes the security model easy to explain to a customer or IT department: RescueLAN is not intended to create a permanently reachable entry point into the site.