An office computer freezes, the support technician connects remotely, and work returns to normal. It is a useful, time-saving service. The question to ask afterwards is who else can connect to that computer, and under what conditions.
A business may have several access routes in place at once: a tool used by its IT provider, a connection for the business software supplier, and access installed long ago for a one-off support task. Each route needs to be known, justified and owned by someone. The aim is to know who is allowed in and ensure their permissions match the need.
Who needs access, and when?
Consider an illustrative example: a supplier connects to a computer to investigate an accounting application fault. Does the employee need to approve every connection, or can the supplier connect when she is away from the computer? Is access limited to that computer? And what happens when the supplier relationship ends?
There is no single answer for every business. Support with an employee present differs from scheduled maintenance at night. Persistent access may be justified, but it should be a conscious decision with defined permissions and a way to revoke it.
Permission to connect should also be distinguished from permission to make changes. Someone who needs to check a function in an application does not necessarily need full administrator rights on the computer.
An inventory of installed applications is a starting point. It is also necessary to establish who controls the accounts used to operate them, whether connections require local approval and whether access remains available after the employee signs out.
Some support tools allow connections without the user first connecting to the office network. Disabling a user on one access route therefore does not prove that all other routes have been closed.
Individual accounts for service providers make it easier to identify who has been authorized and revoke access when needed. Review additional authentication where the system supports it, along with connection logs showing who connected, when and to which computer. Logs help an investigation; they do not, by themselves, prove that every action was justified.
Employees also need to recognize the approved support process. An unexpected request to install a tool or share a connection code should be checked with the known contact using details already held by the business.
Revoke access when it is no longer needed
Before removing a familiar tool, check who depends on it. Map its uses, coordinate with service providers and then reduce duplicate or outdated access routes.
Every persistent access arrangement should have an owner and a review date. Staff departures, supplier changes and computer replacements are opportunities to check whether permissions still fit. The review should also establish how access can be revoked and who is authorized to request it.
The business owner does not need to know every technical setting. They do need a clear answer about who can connect, why and with which permissions. Suntech can help review your remote support and access tools.