Why service-provider access is hard to standardize
Engineers often juggle a different VPN, account and jump host for every customer. That slows support and leaves clients dependent on inconsistent external access methods.
Use cases · OT remote access
Give service providers access without giving up control
Service providers need a practical way to support multiple customers. Asset owners need to keep control of scope, approval, credentials, policy and audit data. Otector supports both through a client-controlled access model and a dedicated Service Provider Portal.
One provider workspace improves the engineer experience while every asset owner remains authoritative for access into its own operational environment.
One provider workspace across clients
The Service Provider Portal shows an engineer the clients and requests available to them in one browser-based workspace, reducing client-specific access friction.
Client-controlled scope and approvals
The asset owner defines sites, assets, profiles, policies and custodians. A provider requests access, but the client decides what is approved and for how long.
Browser sessions and controlled native-tool access
Engineers can use browser-based sessions for common access paths and approved controlled tunnels when a local specialist tool is necessary.
Reports, recordings and audit evidence
Provider identity, requests, approvals and session activity remain visible through the client’s audit model, supporting reviews and customer reporting.
Connected controls
One platform around every access path.
Browser sessions, controlled native-tool access, approvals, monitoring and evidence share one client-controlled model.
Relevant industries
See the use case in context.
FAQ
Questions about this access challenge.
Does the service provider control access?
No. The service provider can request access, but the client remains in control of scope, approval, credentials, policy and audit data.
Can the client approve every request?
Yes. Clients can require approval for provider access and can limit each approval to a defined purpose, asset and time window.
Can service providers access multiple Otector clients?
Yes. Authorized engineers can work across Otector-enabled clients from the Service Provider Portal, subject to each client’s controls.
Are service-provider sessions recorded?
Sessions can be recorded according to the client’s configured policy, connection profile and approved request.
Where are credentials stored?
Asset credentials remain under client control and are used through the client-side access path rather than being handed to external engineers.
Bring your current workflow
See how Otector controls the complete remote session.
We will map your users, providers, assets, approvals and evidence needs in a focused live walkthrough.