Tax Software Hosting Risk Guide

The Cybersecurity Risk of Running CrossLink 1040 Desktop on a Local Network

Software: CrossLink 1040 Desktop / Professional | Vendor: CrossLink

Key takeaway

CrossLink Desktop offices typically combine high-volume 1040 data with bank product / refund-transfer information, which makes them attractive targets — and on a local LAN, every workstation reachable to the data folder shares the same exposure.

Who this applies to

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

CrossLink 1040 Desktop / Professional 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 CrossLink 1040 Desktop / Professional is

CrossLink 1040 Desktop and CrossLink Professional, from CrossLink, are widely used by EROs, service bureaus, and high-volume 1040 retail tax offices that handle bank product / refund-transfer workflows. CrossLink also offers CrossLink Online, but this article focuses specifically on firms running CrossLink Desktop in a shared / networked office environment.

How local CrossLink 1040 Desktop / Professional setups usually work

A typical CrossLink Desktop install places the program on each workstation and points everyone at a shared CrossLink data folder on a host PC or server. Bank product workflows mean that refund-transfer and direct-deposit information also flows through the same environment. Multiple preparers and front-office staff access the same dataset over the LAN, and remote staff frequently connect via RDP, VPN, or third-party remote tools.

Quick definitions

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 CrossLink 1040 Desktop / Professional 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 CrossLink 1040 Desktop / Professional 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

Realistic attack scenarios

A reception PC is compromised through a phishing click; ransomware encrypts the shared CrossLink data folder mid-season.
A weak password on the host PC is brute-forced through an exposed remote tool, exposing live returns and refund-transfer details.
A seasonal preparer's personal laptop is infected and reaches the CrossLink data path through a flat VPN connection.
A single shared Windows login is used across the front desk, eliminating individual accountability.
Local backups on a USB drive in the same office are encrypted along with the live data.

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 CrossLink 1040 Desktop / Professional 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 CrossLink 1040 Desktop and CrossLink Professional, a more defensible architecture runs the application inside a controlled hosted-server environment with per-user MFA accounts, segmented backups, and no raw share exposure to ordinary office desktops or personal devices.

In a properly designed hosted-server model: CrossLink 1040 Desktop / Professional 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.

Important nuance

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 CrossLink 1040 Desktop / Professional security review

If your firm runs CrossLink 1040 Desktop / Professional 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.

Schedule a Tax Software Security Review See How EasyWISP Helps Tax Firms

Frequently asked questions

CrossLink Desktop works on local networks, but high-volume 1040 + refund-transfer workflows on a shared LAN concentrate exactly the kind of data attackers want, with limited segmentation. That is hard to defend without MFA, segmentation, and protected backups.

Yes. In a desktop / network install, return data including SSNs, dependents, W-2 / 1099 details, and refund-transfer / direct-deposit information lives on the firm's own systems.

Yes. Any data writable by the compromised account can be encrypted, including shared CrossLink data and reachable local backups.

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

Antivirus is a baseline control but does not address phished credentials, over-permissive shares, shared logins, or exposed remote tools.

For most multi-user retail tax offices, yes. A hosted environment with MFA, segmentation, and centralized controls is significantly easier to defend under IRS Publication 4557 and the FTC Safeguards Rule.

EasyWISP helps document the WISP, evaluate the CrossLink environment, and plan a safer hosted-server architecture suited to retail tax operations.

Conclusion

CrossLink 1040 Desktop / Professional 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 CrossLink 1040 Desktop / Professional access into a controlled hosted-server environment with MFA, centralized backups, logging, segmentation, and documented WISP controls.