Remote Access
Also known as: RDP (Remote Desktop Protocol), VPN access, remote desktop, remote work access
Remote access refers to the ability to connect to and control a computer, network, or application from a different physical location.
It enables working from home, accessing office systems while travelling, and IT support of remote computers. Common remote access technologies include RDP (Remote Desktop Protocol, built into Windows), VPN (Virtual Private Network, which extends corporate network access to remote locations), and remote support tools (TeamViewer, AnyDesk, LogMeIn). Remote access became foundational infrastructure during the COVID-19 pandemic as organizations enabled mass remote work.
Remote Access, explained at three levels
At home
Remote access lets you use a computer or access files that are located somewhere else, as if you were sitting right there. Working from home and connecting to your office computer is remote access. IT support viewing your screen to fix a problem is remote access. Accessing company systems through a VPN is remote access. It's the technology that makes location irrelevant for computer work.
At work
Remote access is essential infrastructure for modern distributed work. Employees working from home need to access corporate applications, files on office servers, and internal systems that aren't publicly internet-accessible. IT teams need to remotely diagnose and fix employee computers without being physically present. Both scenarios require remote access technology configured securely so that only authorized users can connect.
At home
VPN (Virtual Private Network) creates an encrypted tunnel from a remote device to the corporate network -- all traffic flows through the corporate network as if the device were physically on-site. This enables access to internal resources (file servers, internal applications, printers) from anywhere. Split tunneling routes only corporate traffic through the VPN (leaving personal internet traffic going directly to the internet), reducing VPN bandwidth requirements and improving performance.
At work
Zero Trust Network Access (ZTNA) is the modern evolution of VPN-based remote access: instead of granting blanket network access via VPN tunnel, ZTNA grants access to specific applications based on user identity and device security posture, verified continuously. If a user's device fails a security check mid-session (malware detected, OS not updated), ZTNA can terminate access automatically. ZTNA reduces the attack surface compared to traditional VPN (which gives network-level access that an attacker who steals credentials can exploit broadly).
At home
RDP (Remote Desktop Protocol) security is a significant attack surface: open RDP ports (TCP 3389) exposed to the internet are among the most frequently scanned and attacked services by automated bots. RDP brute-force attacks (trying millions of password combinations) and RDP vulnerabilities (BlueKeep, DejaBlue) have enabled widespread ransomware deployment. Best practices: never expose RDP directly to the internet; require RDP connections through VPN or Remote Desktop Gateway with multi-factor authentication; use Windows Firewall to restrict RDP access to specific source IPs.
At work
Enterprise remote access architecture has evolved toward: identity-centric access (user + device identity verified by Azure AD or Okta before any access is granted), least-privilege access (each user granted minimum access required, not blanket network access), continuous verification (device security posture checked throughout the session, not just at login), and session recording for privileged access (all administrative remote access sessions recorded for security audit). These principles, collectively described as Zero Trust, represent the enterprise security architecture standard for remote access as of the mid-2020s.
Real-world examples
At home
Marcus worked from home three days a week. His company provided a VPN client he activated before connecting to internal systems. Once connected, his laptop was effectively 'on' the corporate network -- he accessed internal SharePoint, the ERP system, and file servers exactly as he would from the office. For IT support, the IT team used TeamViewer to remotely view his screen when he had technical issues, resolving problems without requiring him to come to the office.
At work
Nadia managed IT for a company that went fully remote in 2020. She scaled VPN capacity by moving from on-premises VPN appliances to Cisco Umbrella cloud-based secure access. She implemented MFA for all remote access, configured split tunneling to reduce VPN bandwidth pressure, and deployed Azure AD Conditional Access policies that blocked remote access from devices that weren't compliant with security requirements (missing updates, no endpoint protection).
Common confusions
- Many people think a VPN connection means all their internet traffic is secure and private — A corporate VPN routes your traffic through the corporate network, giving IT visibility into your internet activity and potentially logging it. A corporate VPN is not a privacy tool -- it's an access tool that extends corporate network access. Consumer VPN services (like NordVPN or ExpressVPN) are designed for privacy (hiding your traffic from your ISP), but these are different products with different purposes from corporate VPNs. Mixing up these two categories leads to misunderstanding both.
- Some employees assume remote access tools give IT support access to their personal files and accounts — Remote support tools (TeamViewer, AnyDesk) give IT temporary control of the specific session shown on screen -- the IT technician can see and control whatever is currently visible on the user's screen. They can't access files that aren't open or browse private folders that aren't shown. However, if a personal file or account is visible during a remote support session, the technician can see it. For personal computer support sessions, close personal accounts before allowing a remote support session.
For analysts
When a client's IT environment has RDP or other remote access services exposed directly to the internet (detectable with a port scan or security audit), escalate this as an urgent security vulnerability. Exposed RDP is one of the most common initial access vectors for ransomware attacks. The immediate recommendation is to close the public port and require remote access through a VPN with MFA -- a change that can typically be implemented in one IT day.
History & origin
Remote access technology dates to the early computing era of timesharing systems. Modems and dial-up connections enabled remote access in the 1980s. The internet provided the network infrastructure for internet-based remote access in the 1990s. Microsoft's RDP (Terminal Services, introduced in Windows NT 4.0 in 1998) became the dominant enterprise remote desktop protocol. VPNs became widespread in the 2000s as a security layer for remote network access. SSH (Secure Shell) became the standard for remote server administration. Remote support tools (GoToMyPC, LogMeIn, TeamViewer) emerged in the early 2000s for consumer and SMB remote access. COVID-19 (2020) created unprecedented demand for enterprise remote access infrastructure that most organizations weren't prepared to scale -- VPN capacity, RDS (Remote Desktop Services) licensing, and cloud endpoint solutions all faced supply strain.