Guía de Riesgos del Hosting de Software de Impuestos

The Cybersecurity Risk of Running Drake Tax Desktop on a Local Network

Software: Drake Tax | Proveedor: Drake Software

Idea clave

In a Drake Tax Desktop network setup, every workstation that can reach the shared Drake data path effectively shares the security boundary for the entire return database, including Drake Documents content.

A quién aplica esto

Tax preparation firms, CPA firms, EAs, bookkeepers, EROs, and accounting offices that run Drake Tax on local PCs, mapped network drives, peer-to-peer shares, or an in-office file server.

Drake Tax is commonly used by tax professionals, and many firms run it as a desktop or local-network install because it is familiar, fast, and convenient. The tradeoff is that local convenience can create serious cybersecurity exposure when sensitive taxpayer data lives on office PCs, shared drives, mapped network paths, or an in-office file server.

What Drake Tax is

Drake Tax, from Drake Software, is one of the most popular professional tax packages in the U.S., particularly among small to mid-sized firms, EROs, and high-volume 1040 preparers. Drake also offers Drake Tax in a hosted environment and Drake Zero / Drake Tax Online for cloud workflows, but this article focuses specifically on Drake Tax Desktop installed on local PCs and shared over an office network.

How local Drake Tax setups usually work

A typical Drake Tax Desktop firm installs Drake on each workstation and points everyone at a shared "DrakeXX" data folder on a host PC, server, or NAS, usually via a mapped drive. Multiple preparers and a reviewer open returns concurrently from the same dataset over the office LAN. Many firms also run Drake Documents alongside Drake Tax on the same path. Remote staff frequently connect through RDP, VPN, or a third-party remote tool, and backups are often handled by an external drive in the same office.

Definiciones rápidas

Mapped drive — a Windows drive letter (like T:\ or Z:\) that points to a shared folder on another computer or server.
Local server / file server — a computer in the office that hosts shared files for other workstations.
Hosted server — a server in a controlled hosting environment (cloud or properly hardened internal) that users reach through controlled remote sessions.
MFA — multi-factor authentication; requires a second factor (app code, hardware key) in addition to a password.
WISP — Written Information Security Plan, expected of tax professionals under IRS Publication 4557 and FTC Safeguards Rule expectations.
Ransomware — malware that encrypts files and demands payment for a decryption key.

Why taxpayer data inside Drake Tax is so valuable

Return data inside professional tax software typically includes:

Names, addresses, and dates of birth
Social Security numbers and dependent information
Employer information and W-2, 1099, and K-1 details
Bank account and routing numbers used for refunds and payments
Prior-year return data and carryforwards
Tax credits, deductions, and filing status
Identity verification information
E-file submission data

That combination is exactly what attackers need for identity theft, refund fraud, business email compromise, extortion, and ransomware. It is a major reason tax offices are repeatedly targeted, particularly during filing season.

Risk summary

Local setup element	Why it creates risk	Better hosted-server control
Shared / mapped tax data folder	Malware on one workstation may reach all shared files	Keep tax data inside a controlled hosted session
Shared Windows credentials	Hard to prove individual accountability	Require unique user accounts with MFA
Local workstation storage	Data may remain on laptops and desktops	Centralize data on a secured, segmented server
Local backups	Backups may be reachable by ransomware	Use protected, segmented, monitored backups
Uncontrolled remote access	Attackers may abuse exposed RDP / remote tools	Use MFA-protected remote sessions only

The inherent problem with local network sharing

When Drake Tax data is shared over the office LAN, the security of the tax database effectively depends on the weakest workstation, weakest password, weakest Windows account, weakest remote access tool, weakest backup process, and weakest shared-folder permission in the office. Common risks include:

Compromised Windows logins and phishing attacks on staff
Malware on a single workstation that reaches all shared data
Ransomware encrypting mapped drives and reachable backups
Weak, reused, or shared passwords; no individual MFA on app access
Local admin rights granted too broadly
Exposed RDP or poorly secured third-party remote access tools
Unencrypted or co-located backups
Old workstations and missing patches during busy season
Inconsistent endpoint protection across the office
Over-permissive file shares with no centralized audit trail
No clear evidence of access controls or written security plan

Escenarios de ataque realistas

A staff member opens a malicious PDF; ransomware enumerates mapped drives and encrypts both the Drake data folder and Drake Documents storage.
A weak password on the host PC is brute-forced through an exposed remote tool, exposing live returns to an attacker.
A seasonal preparer's personal laptop is infected and connects through VPN, introducing malware to the Drake data path.
Backups stored on a USB drive plugged into the host PC are encrypted alongside the live data.
A single shared Windows login is used by multiple staff, making it impossible to attribute access to specific returns.

Why "we have antivirus" is not enough

Antivirus, endpoint protection, firewall appliances, spam filtering, and backups are useful — but they are not the same thing as a secure architecture. A Drake Tax office can still be exposed if a user is phished, a workstation is compromised, a mapped drive is reachable, a backup share lives on the same network, an attacker gains local admin rights, users share credentials, the tax app does not require individual MFA on every access, or the firm cannot prove who accessed which client file and when.

IRS, WISP, and the compliance angle

Tax professionals are expected to protect taxpayer data and to maintain a Written Information Security Plan (WISP). IRS Publication 4557 and the FTC Safeguards Rule frame this expectation in general terms: a firm needs more than good intentions. It needs documented controls, access management, incident response planning, employee training, backup and recovery planning, and security monitoring. This article is not legal advice — it describes architectural patterns that are easier or harder to defend during a review.

Why hackers target tax offices

Small and mid-sized tax firms are attractive targets because they:

Hold uniquely valuable identity and financial data
Often do not have full-time IT or security staff
Frequently rely on older local-network software workflows
Use seasonal preparers and rush operations during tax season
Sometimes delay patches and upgrades until "after April"
Commonly use multiple remote access tools
Allow a single compromised workstation to expose all shared tax data

A more defensible architecture: hosted server model

For Drake Tax Desktop, a more defensible architecture is to run Drake inside a controlled hosted-server environment — Drake's own hosted offering, a reputable tax software hosting provider, or a properly hardened internal server — where per-user accounts, MFA, segmented backups, and centralized logging replace open shares and peer-to-peer access.

In a properly designed hosted-server model: Drake Tax runs on a controlled server, users access it through secure remote sessions, each user has an individual account, MFA is required, local desktops do not directly store or freely browse the tax database, access is logged, backups are centralized and segmented, permissions are enforced, security updates are managed centrally, and the environment is segmented from the rest of the office network. That is materially easier to document for WISP and compliance purposes than a peer-to-peer or mapped-drive LAN.

Matiz importante

A "hosted server" can be either a reputable remote tax software hosting provider or a properly secured local server environment that is designed to behave like a hosted system — users authenticate individually with MFA and access the tax software through controlled sessions, instead of opening raw shared data from ordinary office desktops. The architecture matters more than the address.

Schedule a Drake Tax security review

If your firm runs Drake Tax from local desktops, mapped drives, peer-to-peer shares, or an office file server, EasyWISP can help you understand the risk, document your WISP, and plan a safer hosted-server model with individual access controls and MFA.

Agenda una Revisión de Seguridad de Software de Impuestos Cómo EasyWISP Ayuda a Firmas de Impuestos

Preguntas frecuentes

Drake Tax Desktop works well on local networks, but the architecture concentrates risk in the shared data folder. Without MFA, segmentation, and protected backups, a single compromised workstation can expose all returns.

In a typical install, Drake is pointed at a shared "DrakeXX" folder on a host PC, server, or NAS (for example, a mapped path like Z:\DrakeXX). Drake Documents content often lives in a related folder structure.

Yes. Drake data files live on a Windows file system. Any ransomware running with write access to the Drake folder can encrypt returns, and any reachable backups typically go down at the same time.

A properly run hosted Drake environment with individual MFA-protected accounts, centralized controls, and segmented backups is generally easier to defend than a peer-to-peer LAN setup.

Exposed RDP is one of the most commonly abused initial access paths in cybersecurity reports. If used at all, it should be behind MFA and ideally replaced by a controlled hosted-session model.

For most multi-user firms, yes. A hosted-server architecture with MFA, segmentation, and centralized backups is significantly easier to defend under IRS Publication 4557 and the FTC Safeguards Rule.

EasyWISP helps document the firm's WISP, evaluate the Drake environment, and plan a safer hosted-server architecture with proper access controls and backup segmentation.

Conclusión

Drake Tax is not automatically unsafe, and many firms have used it for years. The issue is that the local-network architecture gives attackers too many paths to taxpayer data when a single workstation, password, remote access tool, or mapped drive is compromised. For firms handling sensitive taxpayer information, the more defensible model is to move Drake Tax access into a controlled hosted-server environment with MFA, centralized backups, logging, segmentation, and documented WISP controls.