Remote Equipment Support: Define Vendor Access Before the First Fault

Remote service can reduce travel and make equipment support easier, but a promise of “online diagnostics included” does not describe who can connect to a production asset, what they can do, or how access ends. Buyers of connected industrial equipment should settle those questions while comparing offers and before the first urgent fault. The aim is to coordinate service availability, security and operational safety without treating a vendor account as a permanent blank cheque.

Describe the support scenario first

List the equipment and functions for which remote support may be requested. A supplier may need to view status or logs, while a different task may require permission to change configuration. Ask which actions are available, whether the site can approve them separately, and what the equipment does if the connection is interrupted. Identify the person on site who can coordinate the session and the people whose work might be affected.

Do not assume that a remote connection is harmless because it is used for diagnostics. It may reach a controller connected to physical processes, and any action should remain within the site's approved safety and change procedures. NIST's Guide to Operational Technology Security discusses remote access in the context of operational reliability and safety. Its general recommendations must be adapted to the actual equipment and site.

Ask how access is requested and approved

Request a written description of who initiates a session, how the vendor representative is identified, who approves the connection and how long it stays available. The buyer should know which assets and functions the connection can reach, how access is removed after the job, and what happens if the approved time expires while a critical task is underway. Unique named identities and an agreed approval trail make it easier to associate activity with an authorized person.

Multifactor authentication and restrictions on access can be useful layers, but their availability and compatibility should be checked on the proposed architecture. Avoid assuming that a single technology automatically solves the entire problem. Discuss exceptions, emergency access and any account recovery process with both operations and security staff.

Define the boundaries of the support account

Ask the supplier to distinguish read-only inspection, file transfer, software installation and changes to equipment parameters. Agree which roles may request each action and which changes need a separate approval. A maintenance engineer may require a different scope from an application specialist, and a temporary task should not necessarily grant access to every device in a plant.

CISA's guidance on managing remote access for industrial control systems discusses treating external support entities differently from internal users and restricting access according to roles. This is general guidance rather than a certification of a specific supplier's product. Check current site policies, relevant law and manufacturer documentation before implementation.

Agree on records and an interruption plan

A useful service record identifies the request, approver, vendor representative, connection period, affected asset and the work actually performed. Determine which connection and action logs exist, who retains them, how long they are kept and how the site can obtain them for incident review. Avoid putting confidential credentials or unnecessary process data in the service ticket. If the vendor downloads diagnostic files, agree on their permitted use, storage and deletion.

Plan a contact path if activity looks unexpected or communication is lost. The operations team should understand how to request termination of a session and what equipment-specific recovery process applies. Do not improvise network or control changes during an incident without the appropriate site authority. A connection may be stopped for security reasons while the machine still requires a separate safe-state assessment.

Contracts should also identify a practical fallback when the preferred remote service is unavailable. The buyer can ask whether telephone guidance, a qualified local technician or a scheduled onsite visit is available, along with the expected response process and any extra charges. Those alternatives are business commitments to negotiate, not guarantees that every failure can be resolved remotely. Establish a contact who can authorize escalation and make sure operations personnel know how to reach that person outside normal support hours.

Test the agreement before production urgency

In a planned, approved test, verify that the request and approval process works with the real supplier team. Confirm the agreed scope, observe what is logged, and check that access ends as documented. Record any mismatch between the contract, the demonstration and the deployed system. A supplier's successful video call does not demonstrate that the access controls, audit trail or safe working arrangements meet the buyer's requirements.

Assign an owner to review access after staff changes and at contract renewal. State how subcontractors are approved and how incidents or vulnerabilities are communicated. If a capability is not available, record the limitation and agree on an alternative before depending on it. Our guide to equipment software support commitments and the smart equipment information collection offer related questions for a complete procurement discussion.