Remote support software lets your IT provider fix a computer. It may also let the operator install software, retrieve files, or reconnect after the employee closes the support window. Check who has that access, how they obtained it, and when it ends.

That decision cannot be made from the software’s brand or digital signature alone. A legitimate application connected to an unauthorized operator is still unauthorized access. An assessment needs to establish the relationship behind the tool.

A recognized application can be the wrong installation

Microsoft’s September 29 research describes phishing that delivered legitimate remote management installers under misleading names. In the observed activity, one remote administration tool installed a second channel. Microsoft distinguished this misuse from exploitation of a vulnerability in ScreenConnect itself.

Check which management account controls the installed agent, who approved enrollment, and whether it belongs to your current IT provider. Recognizing the software vendor is only the first check.

Take a 40-person company whose IT provider installs an approved support product. An employee later downloads the same product from an unsolicited support link. Both copies may carry the vendor’s signature, but the second can belong to someone else’s management account. An allowlist based only on the vendor can miss this.

Build an inventory that includes the operator

For each remote access installation, record the device, software, management tenant or server, business owner, approving ticket, and access mode. Distinguish an attended support session from unattended access that survives a restart. Include deployment tools and scripts that can install additional agents.

Reconcile that record with actual endpoint observations. Ask the provider for its enrolled-device list, then compare it with installed services and the organization’s device inventory. Investigate devices present on only one side. An old laptop still enrolled after a provider change is an operational gap worth resolving, even if no malicious activity is found.

The assessment should state its limits. A public-domain check cannot inspect services on employee computers or identify the tenant controlling them. Endpoint access or appropriate evidence from the administrator is needed for that portion of the review.

Define how a support request proves its identity

The employee should have a known route to the help desk that does not depend on the incoming message. A request to install remote support software should resolve to an approved ticket or a callback using an established contact. An urgent voice call and a familiar logo are insufficient evidence of that relationship.

Test the process as a tabletop exercise. Give a participant a synthetic request claiming that a meeting application needs repair. Ask what they would verify, who can approve installation, and how they report uncertainty. Measure whether the person can reach the real help desk quickly. A process that exists only in a policy document will be hard to use during a busy workday.

Keep the normal support experience workable. If legitimate assistance routinely requires employees to bypass the written process, the organization is teaching people that bypasses are normal. Resolve that mismatch before treating training attendance as evidence the workflow is safe.

Test retirement and redundant access paths

Use a designated test device to verify the end of a support relationship. Remove the authorized operator’s grant or uninstall the agent according to the agreed procedure. Then check whether remote access still works after a restart and whether a second authorized test channel remains.

Retain the initial inventory, removal action, final service state, and access-test result. If the endpoint shows evidence of an unapproved installation, preserve relevant logs and involve the incident response owner before routine cleanup removes useful evidence. The depth of that investigation depends on what the tool could do and what activity is observed.

Make this part of Ceron’s agreed assessment scope

When remote support is relevant to a Ceron engagement, identify the public management interfaces, account controls, endpoint evidence, and provider responsibilities in advance. Testing the application portal and reviewing the enrolled fleet are different pieces of work. Make both boundaries explicit rather than assume one implies the other.

Ask for an inventory of operators and devices, unresolved enrollment discrepancies, and the results of access-removal tests. Each finding should explain what the operator could do. For example, an unapproved account might still control a computer used to administer customer systems.

Ask your provider to show which devices it can control and which staff can connect to them. When you remove that access, repeat a connection test and keep the result with the removal record.

The IT provider handover guide addresses retiring old access. The vendor access guide covers authentication for external administrators. The company and support exercise above are illustrative.

Back to the blogExplore Ceron