A caller says they're from your software supplier and need to connect to the office computer. The product name is familiar. You're busy, and the explanation sounds plausible. This is the moment a vendor remote access checklist should help an employee make a clear decision: who approves this work, and how do we verify the request?
Give Staff a Sentence They Can Use
An employee shouldn't have to judge a caller's technical knowledge under pressure. Don't read out passwords or sign-in codes to an unexpected caller while verifying the request. Give them permission to stop and use the company's known contact route.
For example:
I need to verify remote support before starting a session. I'll contact our usual support number and confirm the request with the person who approves this work.
Use a number from company records or an established vendor portal, rather than one supplied during the unexpected call. Staff also need to know who inside the business can approve the session. "Ask IT" is less useful if nobody knows how to reach IT while the caller is waiting.
Make a Short List of the Vendors Who Connect
Include the people supporting business software, office equipment and any specialist machinery. Ask how each connects and what they can reach. A remote-control app, an unattended account and a supervised support session are different arrangements.
You don't need a polished technical diagram to begin. A useful first record answers:
- Which vendor is this, and what work do they support?
- Who in the business approves their access?
- What systems and connection method do they use?
- How is access ended or reviewed after support?
Have IT confirm the record against the actual accounts and tools. A contract from several years ago may describe a different support arrangement from the one in use now.
Agree on the Job Before Starting the Session
Describe the fault and the work being authorized. Ask the technician to tell the responsible person before a restart, installation or configuration change that could interrupt staff. Where appropriate, have IT prepare the recovery route first.
Access should fit the task. Ask about individual accounts, multifactor authentication, logging and whether access can be limited in time. The FTC's remote-access guidance supports strong authentication and controlled connections; the settings available depend on the product you're using.
If someone requests broader access than expected, pause and ask why. A specialist may have a valid reason, but the business should understand and approve it.
Finish the Visit, Including the Access
Ask the employee who uses the system to confirm that the original task works again. Keep the ticket reference and a short account of what changed. If the technician created temporary access, assign someone to confirm that it closes when agreed.
Review continuing connections when a contract ends or equipment is replaced. Arrange that cleanup with the system owner so you don't remove the only support route for a working application without a replacement.
You can start today by listing the vendors allowed to connect and the person who approves each one. If nobody can identify the tools already installed, ask IT to compare them with the approved vendor list.
Reference and Next Step
FTC: Secure Remote Access. Reference checked November 15, 2026. The checklist above is a suggested operating process to adapt to your environment.
Contact NHM Ohio about your checklist.
Drafted with AI assistance.

