Mitigations for unauthorized clients registering in ScreenConnect
This is a follow-up to support case I raised. Apparently, this is the best place to raise a feature request, though I'd argue this isn't really a feature request but rather a product flaw that should have been addressed long ago.
To address the growing cases of unauthorised clients we're seeing register without our on-prem ScreenConnect instance, ScreenConnect needs to add features for administrators to control and mitigate this growing problem. A lot of these unauthorised clients we're now seeing are obvious honey pots rather than any form of sandbox detonation, though sandbox detonations shouldn't be appearing in our ScreenConnect either.
Having unauthorised clients in the system should is an obvious concern for several reasons:
- Some non-IT staff need access to select computers via ScreenConnect, and I'm concerned they may interact with one of these honey pots before we can delete it, either accidentally or out of curiosity.
- If we run a command on a wide-selection of computers that may contain sensitive information like a password, it could expose that information to the honey pot.
- More generally, we can't fully trust the machine list in our own instance if unknown/unauthorised hosts can add themselves to it. It's like having random computers join your Active Directory domain or Entra tenancy. It's absurd.
To address this, there are number of features that could be added:
- Require admin approval for all new "access" devices - This could be an optional setting, but it would require an administrator to approve any new devices that are attempting to register. Pending devices shouldn't even appear in the access list.
- Requirement for passphrase/key/secret to be provided to installer - For silent installs, this can be provided via a command-line argument, environment variable or config file; NOT embedded in the installer. If anyone got a copy of the exe/msi, it'd be useless without this "secret". If a "secret" is ever compromised, it can be easily reset on the server.
ScreenConnect seems very dismissive of this being a problem which boggles my mind given the obvious risks it presents and how many relatively easy ways there are to help customers address this growing threat. It's not acceptable in this day and age.
Please ConnectWise, can you address this problem and stop pretending it's not an issue.