Topic starter
21/08/2026 4:47 pm
TL;DR: Remote desktop teams still spread SSH, RDP, VPNs and credentials across spreadsheets, script files and ad hoc sharing, according to Devolutions. Remote access governance weakens when sessions, roles and secrets are managed apart from one another.
Editorial analysis by NHI Mgmt Group, based on content published by Devolutions: “White papers”.
Key questions
Q: What breaks when remote desktop credentials are stored in spreadsheets and scripts?
A: Revocation, audit and access review all become incomplete.
Q: What are the best practices for shared remote administration sessions?
A: Use permissions to control who can see, reuse or modify a session, and keep the session data in an encrypted central store.
Q: How should teams govern remote access credentials across SSH, RDP and VPN tools?
A: They should treat remote access credentials as governed assets, not user conveniences.
Practitioner guidance
- Implement a central remote access vault Consolidate passwords, session settings and other sensitive values into one governed store instead of keeping them in spreadsheets or script files.
- Apply role-based access control to sessions Define specific roles and groups for remote sessions so users can open, share and edit only the connections tied to their duties.
- Turn on session logging and change tracking Record who opened, closed or modified each session so shared administration has an audit trail that supports review and separation of duties.
Bottom line: Remote desktop environments fail when access tools, session data and credentials are managed as separate islands rather than one governed identity surface.
Glossary terms: Remote Desktop Management, Session Control, Credential Vaulting, Segregation of Duties
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
21/08/2026 5:06 pm
Remote desktop management is an identity governance problem, not just a productivity problem. The article shows that sysadmins accumulate sessions, credentials and permissions across many access tools, then compensate with informal storage and sharing. That is a governance pattern, because the same user often holds many remote pathways with different privilege levels and no single place to enforce policy. The practitioner conclusion is that remote access should be treated as governed identity infrastructure, not a convenience layer.
A question worth separating out:
Q: How do organisations know whether remote session governance is actually working?
A: Look for whether sessions, roles and credentials are managed in one place and whether every open, close or change event is logged. If users still depend on ad hoc sharing or duplicated stores, the governance model is not operating at the point of use.
👉 Read our full editorial: Remote desktop management needs vaulting, RBAC and session control
This post was modified 4 days ago by NHI Mgmt Group