Command Shell behavior change in 25.3.1 – security and policy control concerns
Hi everyone,we would like to raise a concern regarding the Command Shell behavior introduced in Remote Support 25.3.1.The fact that the shell now starts in the context of the logged-in user by default (without requiring user credentials or consent) is, from our perspective, a significant security regression.In previous versions, this behavior was not possible — access to the user context required explicit authentication. Now, support staff can directly access user-level resources such as OneDrive, network shares, or SharePoint without the user being aware.In regulated environments (e.g., banking), this is a serious issue:- it breaks the separation between user and system privileges- it introduces potential audit and compliance risks- it allows unintended access to sensitive user dataAt the same time, our operational requirement remains:- we must be able to perform support actions without user interaction- but strictly
