Remote access to building and industrial systems is usually solved with a shared VPN account, a jump box, and a great deal of trust. The vendor gets in, does the work, and the record of what happened is whatever they choose to tell you. When something breaks two days later, nobody can reconstruct who did what.
Status: product concept, in active development. This is something we are building, not something you can buy today. We publish our roadmap because the engineering thinking behind it is the useful part — and because we would rather show you the design than imply a finished product.
Designed Capabilities
- Identity and device verification — who, and from what machine.
- Ticket- and approval-linked access — access exists because a job authorised it.
- Site and application-level authorization — this site, this system, nothing else.
- Time-window and session policies — access expires on its own.
- Session recording and command logging — a reconstructable record of the work.
- Controlled file transfer — what came in and what left.
- Bastion and protocol proxying — no direct route to the control network.
- Customer asset and audit integration — access tied to the asset register.
Built for OT Realities
Operational networks cannot simply adopt corporate remote-access tooling — the systems are fragile, the vendors are numerous, and the access is occasional but highly privileged. Time-bound, ticket-linked, recorded access fits how this work genuinely happens, and complements the passive assessment side of our OT and network forensics practice.
Tell us if this matches a problem you have — early input shapes what we build first, and we will give you an honest view of where it stands.
Related services
- OT and ICS Security Assessment — Remote access is a finding in most control networks: OT and ICS security assessment.