VPN for Tax Professionals: Secure Remote Access Guide

A VPN for tax professionals is a Virtual Private Network configured to meet the encryption, authentication, and access control requirements established by the IRS Security Six framework — a mandatory set of cybersecurity controls for tax preparers handling nonpublic personal information (NPPI). Under IRS Publication 4557, every tax preparer holding a Preparer Tax Identification Number (PTIN) must implement six essential safeguards, with a properly configured VPN serving as the primary mechanism for securing remote access to client data.

Tax professionals handle concentrated volumes of sensitive financial data — Social Security numbers, bank account details, prior-year returns, and income records — that make remote access security a regulatory obligation. The FTC Safeguards Rule requires financial institutions and tax preparers to encrypt all client data in transit when accessing it remotely. A compliant VPN creates an encrypted tunnel between remote devices and your practice network, protecting NPPI whether your staff connects from home offices, coffee shops, or client locations.

With remote work now standard across the profession, implementing a VPN for tax professionals directly affects your ability to operate, pass IRS security audits, and maintain your PTIN. The average data breach costs $4.88 million according to the IBM Cost of Data Breach Report, while an IRS-mandated PTIN suspension can halt practice revenue entirely. This guide covers IRS VPN requirements, implementation steps, protocol selection, common compliance failures, and vendor evaluation criteria — giving tax practices a complete framework for secure, compliant remote access.

Understanding the IRS Security Six VPN Mandate

The IRS Security Six framework establishes minimum cybersecurity standards for tax professionals through six mandatory controls designed to protect NPPI. Tax professionals face unique cybersecurity challenges because they aggregate large volumes of sensitive financial data during filing season — a single compromised remote connection can expose hundreds or thousands of client records simultaneously.

The VPN requirement directly addresses risks inherent in remote access scenarios: when tax preparers connect to office networks from external locations, access cloud-based tax software over public internet connections, or work from home offices without enterprise-grade network security. According to the Verizon 2025 Data Breach Investigations Report, over 80% of hacking-related breaches involve compromised or weak credentials — making VPN implementation with multi-factor authentication (MFA) essential for protecting NPPI during remote work sessions.

The CISA Telework Essentials Toolkit provides detailed guidance on VPN selection and hardening that directly supports IRS compliance efforts for tax professionals working remotely. These federal guidelines emphasize that secure remote access is a business-essential safeguard for practices handling sensitive taxpayer data outside traditional office environments — not merely a technical checkbox.

Your IRS cybersecurity requirements extend beyond simply deploying a VPN. The Security Six framework treats VPN as one component of a layered defense that also includes firewalls, anti-malware software, MFA, backup solutions, and employee security training. Failing to implement any single component — or implementing it without proper documentation — can result in an IRS security audit finding and potential PTIN suspension.

Remote Access vs. Site-to-Site VPNs for Tax Practices

Tax practices typically implement one of two VPN architectures based on their operational structure. Understanding the distinction helps you select the right solution that meets both IRS requirements and your practice's workflow.

Remote access VPNs allow individual users to connect from any location to your practice network or cloud resources. This is the most common implementation for tax practices with mobile employees, work-from-home preparers, or staff who visit client offices. Remote access VPNs authenticate each user individually, enforce per-user access policies, and create encrypted tunnels on demand when staff connect from home networks, coffee shops, or other external locations.

Site-to-site VPNs create permanent encrypted connections between entire networks — linking your main office to a satellite location or connecting your office infrastructure to a cloud data center. All traffic between connected locations flows through the encrypted tunnel automatically, without requiring individual authentication for each session.

Most small to mid-sized tax practices need remote access VPN capabilities to support teleworking staff. Firms with multiple physical offices may benefit from a hybrid deployment combining remote access for individual users with site-to-site connections between locations. The key consideration is ensuring your solution provides the granular logging, user authentication, and access controls required by the IRS Security Six framework.

For practices using cloud-based tax software, a VPN may still be necessary when accessing client data stored on local servers, connecting to office shared drives, or when your software vendor requires access from a trusted IP address range. Review your software vendor's specific security requirements before assuming cloud tools eliminate the need for remote access infrastructure.

Multi-Factor Authentication: The Non-Negotiable VPN Requirement

The IRS explicitly requires MFA for all remote access to systems containing NPPI. Your VPN for tax professionals must enforce MFA before allowing any connection — single-factor authentication using only a username and password does not meet compliance requirements, regardless of password length or complexity.

This requirement applies with particular force when preparers connect from home networks, public WiFi, or client locations where network security is outside your direct control. When a preparer connects from a coffee shop or hotel, the VPN and its MFA gate are the primary barriers between an attacker on that same network and your client records.

Acceptable MFA implementations for tax practice VPNs include:

• Authenticator apps generating time-based one-time passwords (TOTP) — such as Microsoft Authenticator or Google Authenticator
• Hardware security keys such as YubiKey (the most secure option for high-risk environments)
• Push notifications sent to registered mobile devices
• SMS or voice codes (the weakest acceptable option — avoid for practices handling high data volumes)

Your Written Information Security Plan (WISP) must document your MFA implementation in detail: which method you use, how you provision credentials to new employees, and the procedure for handling lost or compromised authentication devices. Many tax practices fail IRS audits not because they lack MFA, but because their WISP documentation doesn't adequately describe the MFA policy.

For remote environments, consider extending MFA beyond the VPN itself to your tax software applications, email systems, and cloud storage platforms. Layered authentication controls throughout the remote access chain reduce the risk that a single compromised credential opens access to all client NPPI.

"Tax practices using VPN without MFA are operating in direct violation of IRS Publication 4557. PTIN suspension cases frequently trace back to IRS security audits discovering single-factor VPN authentication." — Aligned with NIST Cybersecurity Framework guidance for small businesses

Common VPN Implementation Mistakes Tax Practices Make

Even well-intentioned practices make configuration errors that create compliance gaps or security vulnerabilities when implementing VPN for remote access. These are the most consequential mistakes to avoid:

Using Consumer VPN Services

Services like NordVPN, ExpressVPN, or Private Internet Access are designed for individual privacy browsing, not business access control. They lack centralized user management, cannot integrate with enterprise MFA systems, do not generate the connection logs IRS audits require, and route your traffic through shared servers worldwide — the opposite of what you need when accessing sensitive client data. An IRS auditor reviewing your security documentation will not accept a consumer VPN subscription as evidence of compliant remote access infrastructure.

Neglecting Kill Switch Configuration

A kill switch automatically blocks all internet traffic if the VPN connection drops unexpectedly. Without it, your device may continue transmitting data over an unencrypted connection without your knowledge — potentially exposing client NPPI to anyone monitoring that network segment. This risk is elevated when staff work from coffee shops, airports, hotels, or other shared WiFi environments. Configure kill switch policies at the client level to prevent any data transmission outside the encrypted tunnel.

Insufficient Log Retention

IRS Publication 4557 requires maintaining records that demonstrate your security controls function as documented. VPN logs must be retained for at least one year, but many default VPN configurations only keep 30 to 90 days of records. Configure extended retention periods and ensure logs are backed up before system upgrades or vendor migrations. This documentation becomes the primary evidence during an IRS security review.

Skipping Endpoint Compliance Checks

Before allowing VPN connections, verify that connecting devices have current antivirus software, OS patches applied, and endpoint detection and response (EDR) agents installed and active. A valid VPN session from a malware-infected device gives attackers authenticated access to your practice network. Many enterprise VPN platforms support device posture checks that automatically block connections from non-compliant endpoints before granting network access.

VPN Performance Optimization for Tax Season

VPN connections introduce some latency due to encryption overhead and routing. Poorly optimized implementations can slow tax software to unusable levels — especially during peak filing season when multiple remote workers access practice systems simultaneously. Selecting the right VPN for tax professionals requires balancing security requirements with operational performance.

Start by calculating your concurrent user count and multiplying by the bandwidth each person needs. Most tax applications require 5 to 10 Mbps per user when uploading returns or accessing cloud-based platforms. A practice with 10 simultaneous remote users needs at least 100 Mbps of internet bandwidth at the server termination point — with additional headroom for peak season loads when all remote workers connect at once.

If you use a cloud-based VPN service, select server locations geographically close to your users. A preparer in Chicago connecting through a VPN server in California experiences significantly more latency than connecting to a Chicago-region server. Many enterprise VPN platforms offer automatic server selection based on user location, optimizing performance without manual configuration for each user.

Modern protocols like IKEv2/IPsec or WireGuard offer better performance and stronger security compared to legacy OpenVPN configurations or PPTP. If you currently run an older OpenVPN deployment and experience latency complaints during filing season, migrating to WireGuard can meaningfully reduce connection overhead without sacrificing encryption strength or IRS compliance.

Implement monitoring for connection quality, bandwidth utilization, and user experience during filing season peaks. Track metrics like connection setup time, throughput, packet loss, and round-trip latency. Set alerts for degraded performance so you can address infrastructure issues before they affect productivity during critical tax deadlines. Most business VPN platforms include built-in dashboards displaying these metrics in real time, giving your IT support team visibility into remote access health without additional tooling.

Integrating VPN with the Other Security Six Controls

Your VPN operates as one component of a layered security framework — not a standalone compliance solution. Effective tax practice cybersecurity requires integrating your VPN with the other five IRS Security Six requirements.

Firewall configuration: Your firewall should restrict VPN access to only the ports and protocols necessary for operation — typically UDP 500/4500 for IPsec-based connections or TCP 443 for SSL/TLS VPNs. Configure rules that limit what resources each VPN user can reach based on their role. Preparers don't need access to accounting systems, server administration tools, or network management interfaces from remote locations.

Endpoint protection: Your broader remote work security strategy must include verifying that remote devices meet minimum security standards before connecting. Many enterprise VPN platforms support device health checks that enforce endpoint compliance — blocking connections from machines without current patches or active antivirus — before granting network access.

Employee training: Train your staff to recognize phishing attacks targeting VPN credentials. Attackers frequently send fake VPN expiration notices, security alert emails, or impersonation messages designed to capture authentication credentials from remote workers. For specific examples of the tactics used against tax practice staff, see our guide on identifying phishing attacks. Your team remains the last line of defense against credential compromise when working from networks outside your direct security controls.

Incident response: Your incident response plan must include specific procedures for VPN-related security events: compromised credentials, suspicious connections from unusual geographic locations, unauthorized access attempts, and infrastructure failures during peak filing season. Document who to contact, which systems to isolate, and how to preserve logs for regulatory reporting. An untested incident response plan is nearly as risky as having no plan at all.

Selecting a Compliant VPN Vendor for Your Tax Practice

Not all business VPN solutions satisfy IRS Security Six requirements. When evaluating vendors for your VPN for tax professionals implementation, confirm that your chosen platform provides each of the following:

• AES-256 encryption — non-negotiable minimum per IRS Publication 4557
• Native MFA integration — support for Duo, Microsoft Authenticator, or FIDO2 hardware tokens
• Centralized management console — for provisioning users, pushing policy updates, and revoking access instantly when an employee leaves
• 12+ month log retention — with tamper-evident storage formatted for IRS audit documentation
• Role-based access controls — granular permissions restricting each user to only the resources their job requires
• Device posture checks — automated verification that connecting endpoints meet your security baseline before granting access
• 99.9%+ uptime SLA — with redundant infrastructure that prevents outages during peak filing periods
• 24/7 vendor support — with documented response times for priority issues during filing season

Enterprise VPN platforms commonly deployed in tax practices include Cisco AnyConnect, Palo Alto GlobalProtect, Fortinet FortiClient, SonicWall NetExtender, and cloud-managed options like Perimeter 81 or Twingate. Budget $10 to $25 per user per month for platforms that include management, licensing, and vendor support — a fraction of the cost of a data breach or a PTIN suspension event.

When evaluating vendors, request references from other accounting or tax firms of similar size. Ask those references about behavior during peak filing season concurrent loads, support responsiveness outside normal business hours, and their experience when IRS auditors requested VPN log documentation. These conversations reveal operational realities that product demos won't surface.

For a thorough view of how VPN fits into your overall compliance posture, review the FTC Safeguards Rule requirements for tax preparers — including data encryption, access controls, and third-party vendor oversight obligations that extend to your VPN provider. Building a complete tax preparer cybersecurity program means treating VPN as one element of an integrated system, not an isolated compliance checkbox.