Some thoughts about Quick Assist.
remote user: the user who asks for help (needs help).
session Administrator: the user who controls the remote session (gives the help)
- It is a cloud-based Microsoft app installed by default (does not use Remote Desktop).
- For convenience, the app can be pinned to the taskbar.
- After restarting the remote machine during the session, the remote user must sign in and start Quick Assist to continue the remote session.
- When something is executed with Admin rights on the remote machine, the session Administrator can see only the black screen because of an alert on the Secure Desktop on the remote machine. The remote user must accept the UAC prompt to continue. This can be inconvenient if the session is long and requires several admin tasks.
- To avoid the issue from point 4, the session Administrator can temporarily change the Registry key on the remote machine:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
PromptOnSecureDesktop -----> 0 (the value 1 will restore UAC on the Secure Desktop)
Edit.
It is important to teach the remote user (dad, mum, etc.) that Quick Assist should be always initiated by the remote user and not on a tip from unconfirmed persons. I think that it is good to set a standard, that the person who needs help (dad, mum, etc.) must first call the concrete & trusted helper (son, daughter, etc.). This can prevent abusing Quick Assist by malicious actors.
[URL unfurl="true"]https://malwaretips.com/threads/threat-actors-misusing-quick-assist-in-social-engineering-attacks-leading-to-ransomware.131046/[/URL]
