Home › Guides › Secure remote access setup

How to set up secure remote access: best practices

Remote access is powerful — and powerful means risky if misconfigured. Follow these best practices to set up remote access that's convenient for you and hard for attackers.

Independent & reader-supported. GoToResolve is not affiliated with any vendor listed here. When you buy through links on our site we may earn a commission, at no extra cost to you. This never influences our ratings — see how we test.

First principle

Every remote-access tool is only as secure as how you configure and use it. The software is rarely the weak point — weak passwords, no MFA and careless session-granting are.

1. Choose a reputable tool

Start with software that offers strong encryption, multi-factor authentication, granular permissions and session logging. Every tool in our best remote support guide qualifies. Avoid obscure or cracked tools — you're handing them the keys to your machine.

2. Turn on multi-factor authentication (MFA)

This is the single most important step. MFA means a stolen password alone can't grant access — an attacker also needs your second factor (an app code or hardware key). Enable it for every technician account and, where possible, require it across the organisation.

3. Use strong, unique passwords

Each account should have a long, unique password stored in a password manager — never reused from another service. For unattended access, never leave default or simple access passwords in place.

4. Lock down unattended access

Unattended access is convenient and risky: it lets anyone with the credentials connect any time. Limit it to devices that genuinely need it, restrict which accounts can use it, and review the list regularly. Remove access the moment it's no longer needed.

5. Apply the principle of least privilege

Give each technician only the access and permissions their role requires. Use role-based access controls, allow-lists of permitted devices, and separate admin accounts from everyday ones.

6. Enable session logging and recording

Keep an audit trail of who connected to what, when, and ideally a recording of the session. This deters misuse, supports investigations and is often required for compliance.

7. Keep everything updated

Patch the remote-access software, the operating system and other applications promptly — outdated software is a common entry point. If you manage many devices, an RMM can automate this (see patch management).

8. Train your users

The biggest real-world threat is social engineering. Teach everyone the golden rule: never install remote-access software or grant a session to someone who contacted them unexpectedly. Our scam-awareness guide covers the warning signs.

Quick checklist

✓ Reputable tool with encryption & MFA
✓ MFA enabled on every account
✓ Strong, unique passwords in a manager
✓ Unattended access minimised & reviewed
✓ Least-privilege, role-based permissions
✓ Session logging/recording on
✓ Software & OS kept patched
✓ Users trained against scams

Frequently asked questions

What is the most important remote-access security setting?

Multi-factor authentication. It ensures a stolen password alone can't grant access, blocking the most common attack path.

Is unattended remote access safe?

It can be, if locked down: limit it to devices that need it, restrict which accounts can use it, use strong credentials and MFA, and review access regularly. Left wide open, it's a serious risk.

How do attackers exploit remote access?

Most commonly through social engineering — tricking users into installing software and granting a session — or by exploiting weak/reused passwords and missing MFA. Good configuration and user training defeat most attacks.