A supplier’s engineer may need to fix a server, support an application or investigate a fault. That does not mean they should have an open-ended route into your network.
For many UK SMEs, third-party access has accumulated over time: a remote support tool installed during an urgent call, an agent that connects back to a supplier, a permanent VPN tunnel or a shared “support” account. Each may have seemed convenient when it was set up. The risk is that nobody has a reliable record of what remains active, who can use it or where it leads.
The question is not whether a supplier is based abroad. It is whether access is identifiable, limited, authorised and monitored. A compromised supplier account can give an attacker a trusted route into systems that would otherwise sit behind your perimeter controls.
How supplier access arrives, and stays
Remote access often enters through ordinary business activity. A software provider may ask an employee to download a support tool during a call. A vendor may install an always-on agent that “phones home” when assistance is needed. An engineer may be given a VPN account, a remote desktop login or a jump account shared across a support team.
The problem is not that every remote support tool is unsafe. It is that access can be established without being assessed as part of the organisation’s IT estate. Temporary arrangements then become permanent by default.
Access also includes more than connections to on-site computers. Supplier accounts in SaaS admin portals, delegated cloud administration and third-party identity integrations all count. A vendor that can alter user permissions or manage cloud settings may have substantial influence without connecting to your office network at all.

Why trusted access changes the risk
If a supplier’s credentials are stolen, an attacker may be able to use the supplier’s legitimate access path. Depending on how it is configured, that path can bypass some of the checks that would apply to an unfamiliar connection. If one vendor account can reach multiple systems, the attacker may also be able to move beyond the device the supplier was meant to support.
This is why supplier access belongs in cyber security and business continuity planning, not just in a support contract. The NCSC’s supply chain security guidance recommends that organisations establish control over supplier access, limit what suppliers can reach, and monitor activity. Its supplier assurance questions provide a useful starting point for understanding what a supplier does to manage cyber risk.
For an SME, applying that advice does not have to mean building a complex security operation. It means making access visible, assigning clear ownership and putting practical boundaries around each connection.
Build one register before adding another tool
Start with a single register of supplier access. For each supplier, record:
- The supplier, the service they provide and an internal owner.
- The systems, accounts or data they can access.
- The access method, such as a remote support tool, VPN, cloud portal or delegated administration.
- The named users who can connect, and the authentication controls in place.
- Whether access is permanent, time-limited or approved for each support request.
- When access was last reviewed, and how it will be removed.
Include services that may be overlooked: cloud platforms, telecoms, print or network providers, application support, and specialist contractors. For example, a Dynamics 365 Jump Start project may involve implementation partners who need temporary administrative access. The same principle applies to suppliers supporting Voice and Connectivity services.
The register is not paperwork for its own sake. It gives the IT estate owner a view of who can reach what, and makes it possible to spot access that no longer has a business reason.
Make each connection identifiable and limited
Wherever possible, give each supplier engineer an individual account rather than a shared login. Require multi-factor authentication for remote access, and assign only the permissions and systems needed for the agreed work. Individual accounts make activity attributable; least privilege limits the damage if an account is misused.
Avoid permanent access when the supplier only needs occasional support. A better model is to approve access for a support request, enable it for a defined period and close it when the work is complete. If continuous connectivity is genuinely required, document the reason and apply stronger monitoring and restrictions.
Restrict remote support to tools the organisation has approved. A new tool should not become part of the environment simply because a supplier says it is convenient. The IT estate owner should know what is being installed, why it is needed, who manages it and how it will be removed. That does not require the owner to handle every support call: the Fractal IT Director sets the strategy and approves the guardrails; Managed IT Services and Helpdesk Support can execute and maintain the agreed process.

Restrict reach with network boundaries
Authentication tells you who is connecting. Network controls determine where they can go.
Use segmentation and firewall rules so that a supplier supporting one device can reach that device, not the wider office network by default. Keep supplier access paths separate where practical, and avoid routing a vendor connection into a broad, trusted network zone. A well-planned Network Solutions design can make those boundaries clearer and easier to maintain.
This matters especially for older systems that have been supported for many years. IBM i and AS/400 environments may rely on long-standing vendor relationships and familiar green-screen access. Familiarity is not a substitute for review: identify named accounts, confirm which systems they can reach and remove access that is no longer required. Specialist IBM i Management should account for how support is delivered as well as how the platform is maintained.
Keep logs of supplier access and review them in proportion to the risk. If a third party has privileged access to a business-critical system, you should be able to establish who connected and when, and investigate activity that falls outside the agreed support work.
Review access when people, contracts or plans change
Supplier access should be revisited when a contract ends, the scope of work changes or a supplier contact leaves. The same applies internally: when the employee who approved or manages the relationship moves on, make sure responsibility is reassigned. Remove accounts and connections promptly when there is no longer a business need.
Include vendor access in Disaster Recovery and incident response planning. In an incident, the organisation may need to pause supplier connections quickly, identify which services depend on them, and restore approved access safely. A list of connections and owners makes that response more controlled. It also helps avoid disabling a critical support path without understanding the operational consequences.
For Cloud Solutions, apply the same discipline to delegated administration and SaaS roles as to VPNs and remote desktop tools. Review who holds privileged roles, whether those privileges are still necessary and how they can be withdrawn in an emergency.
A periodic review can also support Technology Expense Management. Old access arrangements may reveal duplicate services, unused subscriptions or support contracts that no longer match the organisation’s needs. Security and cost control often begin with the same question: what are we paying for, and who actually uses it?
A practical vendor-access checklist
- List every supplier connection, including remote tools, agents, VPNs, jump accounts and cloud delegations.
- Name an internal owner for each supplier relationship and each access route.
- Use individual accounts and MFA; eliminate shared logins wherever possible.
- Limit permissions and network reach to the systems required for the agreed task.
- Approve, time-box and close access rather than leaving it permanently available.
- Approve the tools suppliers may install or use, and record any exceptions.
- Log and review activity, especially for privileged or business-critical systems.
- Revoke access when contracts, roles or support requirements change.
- Include supplier connections in incident and recovery plans.
A supplier may need to connect from another country. Geography alone does not tell you whether that access is safe. Good governance does: clear ownership, a defined purpose, limited reach and a reliable way to review or revoke access.
For a broader view of Evestaff’s services, visit evestaff.co.uk.
SEO keywords: Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity
Join The Discussion