How to Create a Data Security Plan for Tax Preparers

Every professional tax preparer in the United States must maintain a written information security plan for tax preparers, and building one comes down to seven moving parts: a written risk assessment, a designated person in charge, specific technical and physical controls, staff training, vendor oversight, secure disposal rules, and an incident response procedure. The requirement flows from the FTC Safeguards Rule at 16 CFR Part 314, which treats tax preparers as financial institutions under the Gramm-Leach-Bliley Act.1Federal Trade Commission. 4 Gramm-Leach-Bliley Tips to Take From FTCs TaxSlayer Case IRS Publication 4557 layers on the agency’s own expectations for safeguarding taxpayer data.2Internal Revenue Service. Publication 4557 – Safeguarding Taxpayer Data The good news: the IRS publishes a free 28-page template built specifically for smaller firms, and the work is more manageable than the rule text suggests.

Who Has to Have One, and the Small-Firm Carveout

The Safeguards Rule applies to any business that provides financial products or services, and tax preparation qualifies. The 2023 revisions to the rule replaced discretionary guidance with specific technical requirements: designated leadership, a documented risk assessment, encryption, multi-factor authentication, penetration testing, vendor oversight, and a written incident response plan.3eCFR. 16 CFR 314.4 – Elements

Firms that maintain client information on fewer than 5,000 consumers are exempt from certain provisions, including the written risk assessment, the formal penetration testing schedule, and the incident response plan documentation.4Federal Trade Commission. FTC Safeguards Rule – What Your Business Needs to Know That exemption reduces paperwork; it does not eliminate the obligation to protect client data. Most solo practitioners fall below the threshold, but using the full rule as your benchmark is safer. If you ever cross 5,000 consumers, you are already compliant.

State law adds another layer. All 50 states, the District of Columbia, and U.S. territories have data breach notification statutes, each with its own timelines and definitions of personal information. Your plan needs a response procedure flexible enough to cover every state where you prepare returns.

Start With the IRS Template

Before drafting anything, download IRS Publication 5708, “Creating a Written Information Security Plan for your Tax & Accounting Practice.”5Internal Revenue Service. IRS, Security Summit Remind Tax Pros They Must Have a Written Information Security Plan to Protect Client Data It is written for smaller firms and walks through compliance requirements section by section. Use it as your skeleton and fill in the specifics of your own practice from there.

Conduct the Risk Assessment

The risk assessment is the foundation. Under the Safeguards Rule it must be in writing and include criteria for evaluating and categorizing the risks your firm faces.3eCFR. 16 CFR 314.4 – Elements Treat it as an honest inventory of what could go wrong: a laptop stolen from a car, an employee falling for a phishing email, a former staffer whose login was never revoked, a breach at your cloud storage provider, ransomware locking your server mid-season.

For each risk, document the controls you have and whether they are adequate. A locked filing cabinet is a control, but not if the key hangs beside it. MFA on email is a control, but not if it only covers some accounts. Note both likelihood and severity. Phishing is highly likely and highly damaging; a tornado hitting the office is catastrophic but rare. Spend accordingly.

Categorize data by sensitivity so controls match the stakes. A mailing address is not a Social Security number. Consider internal risks like employee mistakes alongside external ones like a vendor platform vulnerability. Reassess on a regular cycle and whenever your operations or technology change materially: new tax software, new hires, a new office. An annual review is the minimum.

Designate a Qualified Individual

The rule requires you to name a Qualified Individual to oversee and enforce the program.4Federal Trade Commission. FTC Safeguards Rule – What Your Business Needs to Know That person can be an employee, an affiliate, or a third-party service provider. For a solo practitioner, you are the Qualified Individual. For a small firm, it is often the managing partner or an outsourced IT provider. If you outsource, you remain ultimately responsible. Whoever holds the role needs authority to make decisions and enough technical knowledge to judge whether safeguards are working, and should report regularly to firm leadership on program status, incidents, and testing results.

Map Where Client Data Lives

Before writing controls, inventory every place client data sits: tax preparation software, email, cloud storage, physical filing cabinets, portable drives, laptops, and any personal devices used for work. Trace the flow from the moment a client hands you a W-2 to the moment you e-file and store or dispose of the record. Every system that touches client data falls within scope.3eCFR. 16 CFR 314.4 – Elements

Bring-your-own-device arrangements deserve special attention because you have limited control over personal hardware. Either prohibit personal devices for client data or impose specific requirements: device encryption, screen locks, remote wipe.

Technical Safeguards

Access Controls

Each employee should have access only to the systems and files they need. An administrative assistant does not need every client’s return; an associate preparing individual returns does not need business entity files they aren’t working on. Review access regularly and revoke it immediately when someone leaves or changes roles. Remote access through VPNs or remote desktop connections warrants extra scrutiny because these are the pathways attackers exploit most often. Log every remote session and restrict remote access to approved devices.3eCFR. 16 CFR 314.4 – Elements

Multi-Factor Authentication

MFA is required for anyone accessing your information systems.3eCFR. 16 CFR 314.4 – Elements It combines at least two of three factors: something you know, something you have, something you are. The only way around it is written approval by your Qualified Individual of an alternative control that provides equivalent security. For most firms the practical answer is to turn MFA on everywhere: tax software portals, email, cloud storage, VPN, and any other system holding client data.

Encryption

Client information must be encrypted both in transit over external networks and at rest.3eCFR. 16 CFR 314.4 – Elements Use current protocols like TLS 1.2 or higher for web connections and encrypted email for messages containing personal information; older protocols like SSL are deprecated. For data at rest, enable full-disk encryption on every laptop and workstation, and confirm that your cloud storage and tax software vendors encrypt stored data on their end. If encryption is not technically feasible for a specific system, your Qualified Individual must approve an alternative control in writing.

Monitoring and Patching

Run up-to-date anti-malware on every device, managed from a central dashboard so you can verify coverage. Configure firewalls to block all traffic that isn’t specifically needed. Review intrusion detection alerts daily if you have them, or have your IT provider do so.

Patching is where small firms fall behind, and attackers know it. Operating systems, tax software, browsers, and PDF readers all need security updates applied promptly. Enable automatic updates where possible and check manually on systems that don’t support them.

Physical Safeguards

Technical controls only go so far if someone can walk in and photograph a file on a desk. Lock any room containing servers or physical client records. Enforce a clean-desk policy so sensitive documents are put away when not in use. Secure laptops with cable locks when left in the office. Either prohibit USB drives or restrict them to approved, encrypted models. Maintain a visitor log and do not leave non-employees unattended where client data is accessible.

Train Every Employee

People remain the weakest link. Phishing emails impersonating the IRS, a tax software vendor, or a client are the most common entry point into a tax firm’s systems. Everyone on staff, including administrative employees, needs security awareness training covering how to spot phishing, how to handle client data, and how to report suspicious activity.2Internal Revenue Service. Publication 4557 – Safeguarding Taxpayer Data

The rule requires policies and procedures that keep personnel able to carry out the program, including security updates and steps to keep key staff current on emerging threats.3eCFR. 16 CFR 314.4 – Elements Train new hires before they touch client data, and refresh at least annually. A short monthly email flagging a recent scam keeps security in mind between formal sessions.

Oversee Your Vendors

Your plan does not stop at your network boundary. The rule requires you to select capable service providers, contractually require them to maintain appropriate safeguards, and periodically assess their performance.3eCFR. 16 CFR 314.4 – Elements That reaches your tax software vendor, cloud storage service, IT support company, shredding vendor, and anyone else who touches client information.

Before signing, confirm the vendor can demonstrate adequate security practices; ask for evidence like a SOC 2 audit report. Your contract should include a right-to-audit clause, prompt notification of any security incident, and cooperation in your breach response. A vendor who won’t agree to basic security terms is a warning sign.

Set Retention and Disposal Rules

The Safeguards Rule sets a specific disposal timeline: securely dispose of client information no later than two years after the last date you used it to serve that client, unless it is needed for ongoing operations, required by law, or targeted disposal is not reasonably feasible.3eCFR. 16 CFR 314.4 – Elements For tax preparers, IRS record retention rules usually push the timeline longer. The IRS generally recommends keeping records at least three years after filing, and up to seven years in specific situations like claims involving worthless securities.6Internal Revenue Service. How Long Should I Keep Records?

Once both windows have closed, dispose securely. Cross-cut shred paper. Degauss or physically destroy hard drives; standard deletion or reformatting does not actually remove data. Keep a certificate of destruction for your audit trail.

Back Up Your Data

The IRS recommends backing up sensitive data to a secure external source that is not connected full-time to your network.2Internal Revenue Service. Publication 4557 – Safeguarding Taxpayer Data The disconnection matters. Ransomware that encrypts your main systems will also encrypt any backup drive that stays plugged in. Use an air-gapped backup, an encrypted external drive connected only during the backup window, or a reputable cloud backup service with its own encryption. Back up daily during tax season and weekly during slower periods, and test the backups periodically by actually restoring files. An untested backup may not work when you need it.

Write the Incident Response Plan

The rule requires a written incident response plan covering your goals, internal processes, roles and responsibilities, communication procedures, and a process for fixing the vulnerabilities that allowed the breach.4Federal Trade Commission. FTC Safeguards Rule – What Your Business Needs to Know You are planning for the worst day of your professional life so you don’t have to improvise through it.

The IRS sets out a specific response sequence for a data theft:7Internal Revenue Service. Data Theft Information for Tax Professionals

  • Contact your local IRS Stakeholder Liaison immediately; the IRS can block fraudulent returns filed with stolen client information, but only if you report quickly. The liaison notifies IRS Criminal Investigation on your behalf.
  • Contact the FBI through your local field office.
  • File a local police report documenting the breach.
  • Report to the FTC if 500 or more people are affected.
  • Notify state tax agencies for every state where you prepare returns, and determine whether each state’s attorney general must be notified. Most states require it.
  • Engage a cybersecurity expert to identify the cause, stop the breach, and prevent recurrence.
  • Notify affected clients by individual letter, coordinating timing with law enforcement so you don’t compromise an active investigation.

Your plan should contain pre-drafted notification templates, a contact list with phone numbers for each entity above, and clear role assignments so everyone on the team knows what to do. Run a tabletop exercise at least once a year; walking through a hypothetical scenario exposes gaps invisible on paper.

Test and Adjust the Plan

Writing the plan is not the finish line. The rule requires regular testing of key controls, meaning either continuous monitoring or a combination of annual penetration testing and vulnerability assessments at least every six months.3eCFR. 16 CFR 314.4 – Elements Penetration testing hires a professional to attempt a break-in the way an attacker would; vulnerability assessments scan for known weaknesses across your network.

You also must evaluate and adjust the program based on testing results, changes in operations, new risk findings, or anything else that could materially affect your security posture.3eCFR. 16 CFR 314.4 – Elements Treat the plan as a living document. When a scan reveals an unpatched system, update the plan with the corrective action. When you add a client document portal, expand the plan to cover it.

What Happens if You Skip It

The FTC enforces the Safeguards Rule and has authority to investigate firms operating without a compliant program.2Internal Revenue Service. Publication 4557 – Safeguarding Taxpayer Data Enforcement actions can produce consent orders with years of monitoring and reporting obligations, plus civil penalties for later violations. The IRS separately controls the e-file program through its suitability standards, and an investigation can lead to EFIN suspension or revocation, which effectively ends a modern tax practice’s ability to operate. The cost of a breach itself often exceeds any regulatory penalty: state notification expenses, potential client lawsuits, forensic investigators, credit monitoring, and reputational damage that drives clients away. Building the plan before something goes wrong is far cheaper than responding without one.