A machine vendor may need to diagnose a controller, update software, or troubleshoot a building system from off-site. The request can be legitimate and still leave important questions unanswered: who is connecting, to which system, for what task, and how will the session end?
Use this checklist before granting a contractor, equipment maker, integrator, or service provider remote access to production equipment or other operational technology (OT). It is designed to help the business owner, operations lead, and IT partner agree on a safe, documented process without treating every support request as an emergency.
Ask the vendor to identify the equipment, the reason for access, the work they expect to perform, and the data or controls involved. Have the system owner confirm that the request fits the problem being solved. If the scope changes during the session, pause and get approval before adding systems or tasks.
Record the vendor technician’s name, company, contact method, and the internal person sponsoring the work. Give each person a unique account when the system allows it; avoid shared logins and default credentials. Confirm how the technician’s identity will be checked and whether multi-factor authentication (MFA) is available.
Use the organization’s approved remote-access method and confirm that the system is not exposed directly to the public internet. CISA’s guidance for operational technology says that when remote access is essential, organizations should use a private network connection and VPN functionality with a strong password and phishing-resistant MFA. The right implementation depends on the equipment and environment, so involve the system owner and IT/security team before changing connectivity.
Limit access to the specific asset, account, and actions needed for the work. Ask whether the path is separated from general office systems and whether the vendor can reach other devices from the same connection. CISA recommends least-privilege access and network segmentation for OT environments. These are planning prompts, not a plug-and-play configuration: have qualified people review changes against the equipment’s safety and availability requirements.
Schedule a maintenance window with the operations lead, tell the affected staff, and name the person who can approve or stop the work. Agree on what a normal session should look like and what would trigger a pause. NIST emphasizes that OT remote-access procedures should be justified, limited to the business need, and must not bypass safety or security controls.
Decide who will monitor the connection and where the activity will be logged. Keep a simple record of the request, approver, account, start and stop time, systems reached, and work completed. For systems where a change could affect production or building operations, coordinate the steps with the people responsible for safe operation. Do not rely on a vendor’s ticket alone as your organization’s record.
At the end of the job, disconnect the session, remove temporary permissions, disable temporary accounts or access paths, and confirm that no new remote tool or account was left behind. CISA also recommends disabling dormant accounts and removing access that is no longer required. Record any configuration change, unresolved issue, or follow-up owner before closing the work request.
Create a short runbook that lists the system owner, approved access method, vendor contacts, approval steps, maintenance windows, logging location, and shutdown procedure. Keep an inventory of systems that can be reached remotely and review it when vendors, equipment, or support agreements change. That way, the next service request starts with known owners and boundaries.
These recommendations are practical security guidance, not a claim that every business is subject to the same regulation. CISA’s OT guidance is written for critical-infrastructure environments; organizations should adapt it with their equipment vendor, operations lead, and security adviser.
Remote access touches identity, network design, monitoring, and day-to-day support. Talk with Technic about cybersecurity and secure access for your business. We can discuss your environment, priorities, and the right next step.
CISA, FBI, EPA, and DOE: Primary Mitigations to Reduce Cyber Threats to Operational Technology (May 2025).
NIST SP 800-82 Rev. 3: Guide to Operational Technology Security. NIST currently lists Rev. 3 as final and Rev. 4 as an initial public draft, with comments due November 30, 2026.