Topic starter
08/07/2026 7:09 pm
TL;DR: Remote-control software designed for supervised maintenance is being used to reach office workstations from home, even though that model breaks the security assumptions behind telework access, according to Systancia. The real issue is not convenience but governance, because session control, accountability, and identity boundaries shift when access is mediated by a tool built for hands-on support rather than remote work.
Editorial analysis by NHI Mgmt Group, based on content published by Systancia: “Mobilité”.
Key questions
A: Remote control tools can blur accountability and expand exposure because they are designed for a user to observe or manage an endpoint, not to enforce granular access policy.
Q: When should organisations prioritise ZTNA over remote-control software for home-working?
A: They should prioritise ZTNA when the need is controlled access to applications or internal resources rather than direct desktop takeover.
Q: How do teams know a remote access model is misaligned with telework governance?
A: A warning sign is when the same tool is used for both helpdesk support and employee remote work, because that usually means the organisation has blurred ownership, approval and audit responsibilities.
Practitioner guidance
- Separate support and telework access patterns Keep supervised remote-control tools for maintenance use cases and route ordinary home-working through governed access controls that are designed for employee sessions.
- Define session accountability rules Require clear approval, logging and termination rules that identify who initiated the session, who authorised it and what actions were performed.
- Review policy exceptions for home access Inventory any remote-control exceptions used for telework and retire the ones that depend on a human supervisor being present throughout the session.
Bottom line: Remote-control software for telework is a governance mismatch because it was designed for supervised support sessions, not routine employee access.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
08/07/2026 7:33 pm
Remote-control software for telework creates a governance mismatch, not just a usability trade-off. The session model in these tools was built for supervised assistance, where one party initiates and another watches. Telework turns that model inside out because the remote user becomes the primary actor, so the identity and session controls have to stand on their own. Practitioners should treat this as a control-design problem, not a convenience debate.
A question worth separating out:
Q: Who should own the governance of telework remote access?
A: IAM, PAM and security governance teams should own it jointly, because telework remote access is an identity and session-control problem, not a desktop support problem. The governing team should define who can connect, how the session is approved, what is logged and when the access path must be denied.
👉 Read our full editorial: Remote-control software and the telework access control gap