Remote support
Govern technician access as an authorized support session rather than treating remote control as an anonymous connection.
What the administrator needs to solve.
Remote access solves the immediate support problem but can create a governance problem if technician identity, authorization and session evidence are unclear.
How ZENQIX handles it.
ZENQIX treats remote support as a controlled workflow: technician, authorization, target endpoint, session, result and audit evidence.
Requested action and verified outcome stay separate.
What is currently in scope.
Authenticated remote-support launch path
Endpoint-to-remote-node binding
Controlled session brokering
Session-oriented audit architecture
Future terminal/file actions where supported
Availability by operating system.
Physical customer acceptance remains staged.
Production broker integration exists; broader physical acceptance remains staged.
Physical customer acceptance remains staged.
Inspect the state the UI needs to expose.
This panel uses synthetic data. A genuine ZENQIX Endpoint screen can replace it only after sanitization and publication approval.
Security
- • Broker authentication
- • Per-action authorization boundaries
- • No public Windows RDP forwarding requirement
- • Remote node identifiers normalized only at the integration boundary
Evidence
- • Technician identity
- • Target endpoint
- • Launch request
- • Authorization result
- • Session timestamps where available
Technical detail
- • Remote-support infrastructure is separated from the public marketing website
- • Product storage preserves the raw remote node identifier and normalizes at the broker boundary
Technical questions for this capability.
Is ZENQIX Remote Support just remote desktop?
No. The intended product model includes authorization, technician identity, target binding and auditable session context around the remote tool.
Does it require exposing RDP/3389 publicly?
The current architecture does not require public Windows RDP forwarding.
Evaluate remote support in your environment.
Use the capability matrix and the written acceptance checklist to confirm whether the current status matches your pilot needs.