BifrostConnect flips the model by keeping all remote access software off the target. Our hardware gateway sits between technician and device, capturing keyboard, video and mouse traffic in silicon and routing it over Ethernet, WiFi or LTE — on a separate data path that never touches the production network. Because the gateway operates independently of the OS, it stays live during boot, BIOS flashes and software failures.
- Browser-based technician access
- Or a lightweight agent on the technician side (e.g. for Direct Tunnel)
In both cases, the system under repair stays agent-free — a core part of the mitigation strategy we’ve submitted to MITRE ATT&CK.
- Network isolation that actually isolates: traffic runs on a management link
- No patch race: no software on the asset means fewer vulnerabilities to manage
- BIOS-level reach: reinstall or recover even when OS is down
- Physical kill switch: unplug and it’s gone
- Audit logs built-in: session trails ready for NIS2 documentation
NIS2 requires “robust remote access & privileged control.” Hardware-based isolation delivers that by default: traffic segregation, just-in-time access and immutable logs, baked into the appliance, not bolted on later.
We’ve formally proposed hardware KVM as a mitigation in MITRE ATT&CK — highlighting clientless target access, out-of-band networking and time-limited sessions. It’s already deployed in critical infrastructure, regardless of when it gets listed.
Yes, a gateway costs more up front than another VPN license. But the first time you avoid a technician flight or breach response retainer, the ROI is obvious. Every saved truck-roll adds to the bottom line.
The “install-an-agent-everywhere” approach is done. There’s a better way now.
Visit our OT Cybersecurity area, for more knowledge on compliance, best practice and how we can help