trio.so
Templates

Remote Access Policy Template (Remote Desktop, Word + Excel)

Free remote access policy template in Word and PDF: approved methods, RDP and MFA rules, vendor access, logging, an acknowledgment form and an Excel register.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

A remote access policy template gives you a written rule set for everyone who connects to company systems from outside the office: staff on remote desktop, IT on a remote support tool, admins on servers, and vendors who log in to fix the software they sold you. It says which methods are allowed, how people sign in, which devices may connect, what happens during a session, how vendor access is time-boxed and what gets logged.

This guide goes through each part for an IT manager or security lead at a company of 20 to 1,000 people, writing or updating remote access rules for ISO 27001, SOC 2, HIPAA, PCI DSS or a cyber insurance renewal. The download has the policy in Word and PDF, a one-page checklist, a request form, a third-party access form, the employee acknowledgment form, a filled-in example and an Excel register.

In short

  • Name the approved methods (VPN or ZTNA, an RD Gateway, one remote support tool, a jump host) and ban everything else.
  • Never leave RDP open to the internet. Port 3389 stays closed at the firewall.
  • MFA on every remote sign-in, NLA on every RDP host, and only managed, encrypted, patched devices.
  • Give vendors an end date, a sponsor and a supervised session, and turn their accounts off when the work is done.

What Is a Remote Access Policy?

A remote access policy is the document that decides who may reach company systems from outside the network, what they may reach and how. Some companies call it a remote access security policy or a remote access control policy; older templates, including the earlier version of this one, call it a remote desktop access policy because RDP was the main way in. The rules now cover more than RDP: the VPN or zero trust layer people connect through, the remote support tools IT uses on users' laptops, admin access to servers and cloud consoles, and vendor access.

Three other documents sit next to it. The VPN policy sets the rules for the VPN itself (clients, protocols, split tunneling). The access control policy decides who may open which data once they are in. The remote work policy covers working from home in general: hours, equipment, expenses. The remote access policy is the one that governs the connection itself.

How to Write a Remote Access Policy in 7 Steps

  1. List who connects. Staff, IT, vendors and service accounts, and what each reaches.
  2. Pick the approved methods. VPN or ZTNA, an RD Gateway, one remote support tool, a jump host for admins. Ban the rest.
  3. Close direct exposure. No RDP, SSH or VNC open to the internet; check from outside.
  4. Set sign-in rules. MFA everywhere, NLA on RDP hosts, no shared accounts.
  5. Set device and session rules. Managed, encrypted, patched devices; idle timeouts; redirection off for systems with sensitive data.
  6. Write vendor and admin rules. Time-boxed, supervised vendor access; admin access through a jump host or just-in-time grant.
  7. Log, review and sign. Log sessions, review access every 6 months, and have every user sign the acknowledgment.

Start from what you actually run. If a vendor connects through its own remote tool today, write that down and either allow it with an exception or replace it before the policy takes effect.

What a Remote Access Policy Should Include

The template has 17 sections: purpose; scope and definitions; roles; approved remote access methods; eligibility and approval; authentication; device requirements; session rules; third-party and vendor access; privileged remote access; VPN and the connection layer; logging and monitoring; personal devices; lost or stolen devices; exceptions; enforcement; and review. Four forms follow: a monthly checklist, a remote access request, a third-party access form and the employee acknowledgment.

Approved Remote Access Methods

Section 4: the approved ways in, and the one that is never allowed
Section 4: the approved ways in, and the one that is never allowed

Section 4 lists each approved method, what it is for and its rules:

MethodUsed forRules
Company VPN or ZTNAStaff reaching internal apps, file shares and the gatewaysMFA at sign-in; managed devices only; rules in the VPN policy
RD Gateway (or a published remote desktop service)Staff or IT reaching a Windows desktop or server by RDPRDP only through the gateway; NLA on every host; port 3389 closed at the perimeter
Remote support toolIT helping a user on their own deviceApproved tool only; the user is told before IT views or controls the screen; sessions logged
Jump hostAdmins reaching servers, network gear and cloud consolesNamed admin accounts; MFA; no email or web browsing on the jump host
Not allowedRDP, SSH or VNC open to the internet; personal remote control apps; shared remote accountsBlocked at the firewall; found ones are closed the same day

The banned row is there for a reason. In 2018 the FBI and DHS warned that attackers were getting into companies through RDP left open on TCP port 3389, helped by weak passwords and unlimited login attempts, and were using that access to deploy ransomware. CISA's #StopRansomware Guide still lists limiting RDP and closing unused RDP ports among its first steps. A Remote Desktop Gateway solves the access problem without the exposure: users connect to the gateway over HTTPS on port 443, sign in with MFA, and the gateway passes the session to the host inside the network.

Pick one remote support tool and run it from your managed console. If every technician uses a different free app, nobody can tell which sessions were legitimate.

Authentication and Device Rules

Section 6 sets how people sign in:

  • Multi-factor authentication (MFA) for every remote connection: the VPN or ZTNA sign-in, the RD Gateway and every remote support tool account.
  • Network Level Authentication (NLA) on every Windows host that accepts RDP, so users authenticate before a session is created.
  • Personal named accounts only. No shared or generic remote accounts; service accounts can't sign in interactively.
  • Account lockout after [10] failed attempts, and failed sign-ins logged.
  • Admin rights come from a dedicated admin account, never the account used for email and browsing.

Network Level Authentication makes the user prove who they are before Windows builds a remote session, so an unauthenticated attacker can't reach the login screen. It is on by default in current Windows versions; the policy keeps it that way and makes any exception a written one.

Section 7 lists what a device needs before it may connect:

RequirementWhat it means (example values in brackets)
ManagedEnrolled in [the device management console] and listed in the device inventory with an owner and serial number
EncryptedFull-disk encryption on (BitLocker, FileVault, LUKS) or, on phones, a passcode with storage encryption on
PatchedOperating system and third-party updates installed within [14 days], critical fixes within [72 hours]
ProtectedEndpoint protection running and its alerts reviewed
LockedScreen lock after [5 minutes] idle; the device is never left signed in and unattended

"Managed" is the requirement that makes the others checkable: a device in your management console shows its owner, encryption status and patch level, so you can tell before you grant access. Our data encryption policy template sets the encryption rules in detail.

Session Rules: Timeouts, Redirection and Support Sessions

Section 8 covers what happens once someone is connected:

RuleRequirement
Idle timeoutRemote sessions disconnect after [15 minutes] without input; PCI DSS asks for re-authentication after 15 minutes idle in the cardholder data environment
Session lengthVPN and gateway sessions re-authenticate after [12 hours]
Clipboard and drive redirectionOff by default on RD Gateway and hosts that hold sensitive data; on only with an approved need
Printing and file transferNo local printing or file copy from systems with sensitive data over remote desktop
Support sessionsIT tells the user before viewing or controlling their device and gets their agreement when the user is present; unattended access only to company devices, with a ticket
RecordingRecord or keep a transcript of privileged and vendor sessions where your tools allow it; tell users which sessions are recorded

Clipboard and drive redirection are how files leave a remote desktop session. Turning them off on systems that hold patient records or card data closes that path. Remote support sessions need their own rule because IT is looking at a user's screen, which may show personal messages: tell the user first, and keep unattended access for company devices with a ticket behind it.

For Windows hosts, our guide on enabling Remote Desktop with Group Policy shows where NLA, timeouts and redirection are set.

Third-Party and Vendor Access

Vendor accounts are a common gap: a support contract ends, and the vendor's VPN account keeps working for another year. Section 9 sets these rules:

  • Each vendor has a named sponsor and a signed agreement that covers confidentiality and remote access rules.
  • Vendor accounts are personal, use MFA, and reach only the systems in the agreement.
  • Access is time-boxed: enabled for the agreed window and disabled when it ends (PCI DSS 8.2.7).
  • The sponsor supervises sessions on systems with sensitive data, or the session is recorded and reviewed.
  • Vendors use the company's approved remote access method, not their own tools, unless an exception is approved.
  • The third-party access form (Appendix C) is filled in before the first session.

PCI DSS v4.0.1 requirement 8.2.7 says accounts that third parties use for remote access are enabled only for the time they are needed and monitored while in use. The same rule fits any vendor account. The register's Third-Party Access tab flags any vendor whose end date has passed while the account is still on. Our vendor management policy template covers the contract side, and third-party risk management the wider assessment.

Privileged Remote Access

Admin access to servers, network devices, cloud consoles and the device management console carries more risk than an employee opening a file share. Section 10 says:

  • Privileged remote access goes through a jump host, a gateway or a just-in-time grant, never straight from a laptop to a server.
  • Admin access is granted for the task and the time it needs, with the reason recorded.
  • Privileged sessions are logged and, where the tool supports it, recorded or transcribed.
  • The admin list is reviewed every [3 months].

Just-in-time access fits here: instead of a standing admin account, a person gets access to one server for the hours the task needs, and the grant ends by itself. If your tools don't offer that, a dedicated admin account with MFA and a reviewed admin list is the minimum.

Where the VPN Fits

Most remote access starts with a connection layer: a company VPN or a zero trust network access (ZTNA) service that checks the user and device before each application. Section 11 of the template says staff connect through it with MFA from managed devices, and stops there. Which VPN clients and protocols you allow, split versus full tunneling, always-on VPN and VPN accounts belong in the VPN policy template, which pairs with this one. For the choice between the two models, see zero trust vs VPN; for a first setup, how to set up a VPN for a small business.

Logging, Personal Devices and Lost Devices

Section 12 asks for a log of every remote sign-in, failed or successful, with the session's start and end, the user, the source and the target system, and a weekly look for odd hours, new countries and repeated failures. It also asks for a monthly check that nothing answers on RDP, SSH or VNC from the internet, which is what the register's Exposure Check tab records.

Personal devices (section 13) connect only as the BYOD policy allows, to a short list of apps, never with full network access or admin rights. When a device is lost (section 14), IT cuts the user's VPN sessions and tokens first, then locks or wipes the device and records what it held. The data breach response plan takes over if data may be exposed, and an incident report records the event.

Exceptions, Enforcement and Review

Some systems can't follow every rule. An imaging viewer may need NLA off until its next upgrade, or a billing team may need a longer session timeout for large uploads. Section 15 lets the policy owner approve an exception with a compensating control and an expiry date no more than 12 months out, and says no exception ever allows RDP open to the internet. Section 16 lets IT suspend remote access at once if an account looks compromised, and section 17 sets a yearly review.

Remote Access Policy Checklist

Appendix A is a one-page monthly check with 14 lines. Six of them:

  • Every person with remote access is in the register with an approver and a review date
  • Every remote connection asks for MFA
  • No host answers on RDP (3389), SSH or VNC from the internet; RDP goes through the gateway
  • Every device used for remote access is managed, encrypted and patched
  • Every vendor account has an end date and a sponsor; expired vendor accounts are disabled
  • Leavers and role changes lost remote access the same day

Remote Access Policy Acknowledgment Form

Appendix D is the form every user signs before getting remote access. It lists six commitments in plain words: connect only through approved methods, use MFA and never share an account, connect only from allowed devices, lock the screen, report a lost device or a session you didn't start, and accept that sessions are logged. Signed forms go in the HR file, and a new form is signed when the policy changes in a way that affects users.

Remote Access Policy Example: Larkspur Dental Group

The download includes the policy filled in for Larkspur Dental Group (fictional), a made-up 180-person dental group with four clinics, a practice management server, an imaging server and an RD Gateway. Part of its monthly check on 16 November:

PersonMethodResult
Ana ReyesRD GatewayReview overdue
Dr. Lee ParkVPNNo MFA, Unmanaged device
Sam ColeVPNNot approved, Unmanaged device, No review date
M. GrantDirect RDPMethod not allowed, No MFA, Unmanaged device, Review overdue

8 people have remote access and 4 have no open issue. The worst row is a former IT contractor whose contract ended in June: the account still connects by direct RDP, without MFA, to the backup server. The same check found that server answering on port 3389 from the internet, through a firewall rule made for that contractor.

VendorResult
BrightRay ImagingEnds soon
Molarix SoftwareUnsupervised
Cobalt IT ServicesExpired, still active, Unsupervised
Lineway TelecomClosed
Inkpath ServicesNo end date, Not approved

The former MSP's contract ended on 30 September and its VPN account is still active. The practice software vendor's sessions aren't watched, and the exception that allowed that expired in August. A printer service was set up by the front desk with no end date and no approval.

Remote Access Register (Excel)

The workbook turns the policy into a monthly list of things to fix:

  • Access Register flags people with no approval, a method your policy doesn't allow, no MFA, an unmanaged device, or an access review that is overdue or missing.
  • Third-Party Access flags vendors whose end date passed while the account is still on, vendors with no end date, unsupervised access and missing approvals.
  • Exposure Check flags hosts with RDP or another remote port open to the internet, hosts not behind a gateway or VPN, NLA turned off, and checks that are out of date.
  • Exceptions shows which approvals are missing, expired or about to expire.
  • Settings, Example, Dashboard and Sources hold the thresholds and the allowed methods, the filled-in example, access by method and the references. Formulas only, no macros.
The register's Example tab: people, vendors and hosts for a made-up dental group, with the checks it raises
The register's Example tab: people, vendors and hosts for a made-up dental group, with the checks it raises

Remote Access Policy in ISO 27001, NIST, CIS, HIPAA and PCI DSS

Every common framework has remote access rules, and none of them names a product. The template's mapping table (Appendix F) points each section to these references:

FrameworkWhere remote access appears
ISO/IEC 27001:2022A.6.7 remote working, A.8.5 secure authentication and A.8.20 networks security, with A.5.15 and A.8.2 for access and privileged rights, A.5.19 and A.5.20 for suppliers and A.8.15 for logging.
NISTSP 800-46 Rev. 2 (telework, remote access and BYOD security) and SP 800-53 Rev. 5 AC-17 remote access, whose enhancements cover monitoring, cryptographic protection, managed access points and privileged commands.
CIS Controls v8.16.4 MFA for remote network access, 12.7 remote devices on a VPN connected to your AAA infrastructure, 13.5 access control for remote assets.
HIPAA Security Rule164.312(a)(2)(iii) logoff after inactivity (addressable), 164.312(b) audit controls, 164.312(d) person or entity authentication, 164.312(e)(1) transmission security.
PCI DSS v4.0.18.2.7 third-party remote access accounts, 8.2.8 re-authentication after 15 minutes idle, 8.4.3 MFA for remote network access from outside your network.

Cyber insurance questionnaires ask the same things in plainer words: is RDP exposed, is MFA on for remote access, is vendor access controlled. The mapping is a general guide; your auditor or counsel decides what counts for your scope.

What's in the Download

The policy PDF: cover, approved methods and session rules, and the filled-in example
The policy PDF: cover, approved methods and session rules, and the filled-in example
  • Word policy (Remote-Access-Policy-trio.so.docx): 17 sections, the monthly checklist, the request form, the third-party access form, the acknowledgment form, an exception form, the filled-in example and the framework mapping, with fillable fields.
  • PDF (Remote-Access-Policy-trio.so.pdf): the same policy, forms and example, ready to print.
  • Excel register (Remote-Access-Register-trio.so.xlsx): the tabs described above.

Where trio.so Fits

trio.so is not a VPN, a ZTNA service or an RD Gateway. What it covers is the device side of this policy and its own remote tools: keeping the devices people connect from managed, encrypted and patched, and giving IT remote desktop and terminal sessions that only the right roles can start and that leave a record. In practice that means:

  • Remote desktop to Windows, macOS and Linux devices from the console, with a remote terminal and task manager, in every plan.
  • Only console roles that hold the remote desktop permission can start a session (Owner, Super Admin and Admin by default, or a custom role you build), and only roles with the manage permission can end someone else's session.
  • Every remote desktop session start, end (with its length) and failed connection goes into the audit log and the device's session history, with the name of the person who started it.
  • Remote desktop sessions that end after five minutes without input from the admin.
  • Just-in-time access to servers in IT Operations: an admin grants a console user, or someone outside the company through a link that works in one browser only, a terminal on a server (or the desktop of a Windows Server running the trio.so agent) for a set window; the grant ends at its end time or when an admin revokes it, and terminal commands are kept in a session transcript.
  • A device inventory with each device's owner, serial number and encryption status, so you can tell a managed device from one that isn't.
  • BitLocker policies on Windows, FileVault policies on Macs, passcode policies for iPhone, iPad and Android, and required storage encryption on Android.
  • Vulnerability findings matched to CVEs with CVSS, EPSS and CISA KEV data; OS updates through Auto Patch policies and third-party fixes through remediation plans, with the result shown for each device.
  • Policy status for each device: applied, failed or pending.
  • Remote lock on Mac, iPhone, iPad and Android, and remote wipe of company-owned devices.
  • Console roles, user sync from Microsoft Entra ID and Google Workspace, and SCIM 2.0 provisioning; MFA and single sign-on are in the Zero Trust plan.
  • Compliance evidence you can export for auditors.

It manages Windows, macOS, Linux, iOS/iPadOS and Android from one console. Our page on remote control in MDM shows how remote sessions work from a device console. Plans start at $5 per device.

Start free trial Book a demo

14-day free trial. No credit card required.

Related Templates and Guides

Sources. Last reviewed November 2026. Framework references are short pointers to ISO/IEC 27001:2022, NIST SP 800-46 and SP 800-53, the CIS Controls, the HIPAA Security Rule and PCI DSS v4.0.1; the wording of every section is ours. trio.so is not affiliated with or endorsed by ISO, NIST, the Center for Internet Security, HHS or the PCI Security Standards Council.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Remote desktop that only the right roles can start

trio.so gives IT remote desktop and a remote terminal for Windows, macOS and Linux, limited to roles with the remote desktop permission, with every session start and end in the audit log.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

It is a written set of rules for connecting to company systems from outside the office network: who may connect, to which systems, with which tools (VPN or ZTNA, remote desktop, remote support tools), how they sign in, which devices they may use, how vendors get access and what is logged.

Scope and definitions, roles, approved methods, eligibility and approval, authentication (MFA, NLA), device requirements, session rules, vendor access, privileged access, the VPN or ZTNA layer, logging, personal devices, lost devices, exceptions, enforcement, review and an acknowledgment form users sign.

No. The FBI, DHS and CISA have all warned that RDP open on port 3389 is a common way in for ransomware. Put remote desktop behind an RD Gateway, a VPN or a ZTNA service with MFA, keep NLA on, and check from outside the network that nothing answers on 3389.

Give each vendor a named sponsor, personal accounts with MFA, access to only the systems in the contract and an end date. Turn the account on for the agreed window and off afterward, and supervise or record sessions on sensitive systems. PCI DSS 8.2.7 sets the same rule for card data environments.

It is the page each user signs before getting remote access, confirming they will use only approved methods, keep MFA and credentials to themselves, connect only from allowed devices, lock their screen and report lost devices or sessions they didn't start. The template includes one as Appendix D.

The remote access policy covers every way in: VPN or ZTNA, remote desktop, remote support tools, vendor and admin access. A VPN policy covers the VPN itself in more depth, such as approved clients, protocols, split tunneling and VPN accounts. Most companies keep both and link them.

Review each person's remote access at least every six months, remove it the same day someone leaves or changes role, check vendor accounts against their end dates every month, and review the policy every 12 months or after a remote access incident.

Related

From the blog

The related industry news, interviews, technologies, and resources.