Property managers rely on outside companies to install and support the systems that run their buildings: heating and cooling controls, elevators, fire alarm monitoring, cameras, access control, intercoms, internet service and the management software itself. Many of those vendors need remote access to do their work, and once it is set up it tends to stay. This article explains how vendor access to building systems usually works, why it needs managing, and the controls that keep it under your control.
How vendors connect to building systems
Vendor access takes several forms, and a single property may have all of them:
- Remote support tools installed on a workstation or server so the vendor can take control of the screen.
- VPN accounts that put the vendor’s laptop on your network.
- Cloud portals run by the manufacturer, where the vendor manages devices on your site.
- Forwarded ports on the internet router that expose a device’s web page or management interface.
- Cellular modems or separate internet lines installed with the equipment, which bypass your network entirely.
- Shared administrator accounts on controllers, recorders or building automation systems, created at installation.
Some of these are visible to your IT provider. Others, particularly cellular modems and vendor cloud portals, may not be documented anywhere.
Why it needs managing
Vendor access is legitimate, but unmanaged access causes predictable problems:
- Accounts remain after the vendor relationship ends, with no one checking whether they are still used.
- Shared logins mean you cannot tell which vendor technician made a change.
- The vendor holds the only administrator password, so you depend on them to make changes or to hand the system to a new provider.
- Remote paths that bypass the firewall are not monitored or logged.
- A breach at a vendor can reach every customer site the vendor can access.
Controls that keep vendor access in check
Know every path in
Make a list, per property, of every vendor with access: who they are, which systems they reach, how they connect, which accounts they use, and who in your company approved it. Include cellular modems and cloud portals. This list is the basis for everything else.
Own the administrator accounts
The property should hold the master administrator credentials for every building system, stored in a company password manager. Vendors get their own named accounts with the permissions their work requires. When a system is installed, make handing over admin credentials part of the acceptance.
Require individual accounts and MFA
Each vendor technician should have their own login, and remote access should require multi-factor authentication. If a vendor’s tool cannot support either, document the exception and limit what that tool can reach.
Route access through controlled paths
Replace forwarded ports with a VPN or a remote access gateway you control, and close ports that are no longer needed. Keep building systems on their own network segments so a vendor connecting to the HVAC controller cannot reach office computers or tenant data. A managed firewall is where these rules live.
Limit access in time
Where possible, turn remote access on for a scheduled visit or support case and turn it off afterward. Permanent access should be the exception and should be reviewed.
Log and review
Keep logs of vendor connections and review them, particularly connections outside agreed hours or to systems the vendor does not support. Centralized logging makes this practical; our SIEM and MDR page explains how we collect and review security events. Titan Tech provides 24/7 monitoring.
Put it in the contract
Vendor agreements should cover how the vendor protects its own remote access tools, whether it uses MFA, how quickly it tells you about a security incident on its side, and that it will return or hand over credentials when the contract ends.
When a vendor relationship ends
Treat the end of a vendor contract like an employee leaving. Disable the vendor’s accounts, remove its remote tools, close any ports or VPN accounts created for it, change any shared passwords it knew, and confirm the new vendor has received the administrator credentials from you, not from the departing vendor.
Review on a schedule
Accounts and remote tools accumulate again over time. Review the vendor access list on a regular schedule and whenever a property is bought, sold or renovated, since those events tend to bring new vendors and new equipment.
What to do next
Start the vendor access list with one property: walk through each building system and ask who can reach it remotely and how. Check that the company, not the vendor, holds the administrator password for each one. If you want help finding remote access paths you may not know about, you can request a Blind Spot Scan.