Identity and device binding
After controlled provisioning, a router gets its own certificate identity. The HTTPS management channel uses mutual TLS authentication: both the platform and the device control the other party. This management channel is separate from the connection with which a mechanic reaches the location.
Rights are enforced in traffic
A name in the portal is not the security limit. The set permissions are translated into concrete devices, protocols and ports. The session environment and local router apply these limits. Part blocks have priority. These functions require the current supported agent and client to be installed.
Personal access and MFA
Invitations are tied to a personal account. For sensitive access and management actions, ServiceGate uses a time-bound authenticator confirmation. The current authenticator is TOTP; this is not a phishing-resistant hardware security key.
Logs with a clear limit
ServiceGate records platform actions, access decisions, sessions and agent results. Records are linked to hashes and protected against regular change. This is not a WORM storage. A fully compromised management environment remains a risk; independent preservation may therefore be necessary.
The software does not automatically record all actions within a PLC programming environment or interactive shell. Allowing an IP address does not independently prove the physical identity of the sensor behind that address.
No automatic compliance claim
ServiceGate supports an approach with limited rights, time-bound access and traceability. An IEC 62443 assessment or other conformity assessment requires more than a product function. Think of system architecture, configuration, procedures and testing.
For general OT guidelines we refer to CISA on OT security and the NIST Guide to OT Security.