AccountingFreelance

WISP and the FTC Safeguards Rule: What Small Accounting Firms Need to Know

Why tax preparers are legally required to have a written information security plan, what it must cover, and how a small or solo practice can meet the requirement.

Updated November 7, 2026

If you prepare tax returns for pay, federal law requires you to have a written information security plan (WISP). Many solo and small practices don't have one, or have a template they've never put into practice. Here's what the requirement is and how to meet it.

Where the requirement comes from

The Gramm-Leach-Bliley Act and the FTC Safeguards Rule (16 CFR Part 314) treat professional tax preparers as "financial institutions". The rule requires them to develop, implement and maintain an information security program, set out in writing.

The IRS reinforces the requirement:

  • Publication 4557 (Safeguarding Taxpayer Data) explains the obligations.
  • Publication 5708 walks through creating a WISP for a tax and accounting practice.
  • Form W-12, which you file to get or renew your PTIN, asks you to confirm that you're aware paid preparers are required by law to create and maintain a WISP.

What a WISP must address

The Safeguards Rule lists the elements of an information security program. In plain terms:

  1. A Qualified Individual responsible for the program. It can be you or an outside provider.
  2. A risk assessment: where client data lives and what threatens it.
  3. Safeguards, including:
    • access controls (only the right people see the data)
    • an inventory of your data and systems
    • encryption of client data, stored and in transit
    • multi-factor authentication for anyone accessing client information
    • secure disposal of data you no longer need (generally within two years of last use, unless you must keep it)
    • monitoring and logging of access
  4. Regular testing and monitoring of your safeguards.
  5. Security training for everyone at the firm.
  6. Service provider oversight: choose capable vendors and require safeguards by contract.
  7. Keeping the program current as your practice changes.
  8. An incident response plan.
  9. Reporting on the program (to a board, or the owner of a small firm).

Firms holding information on fewer than 5,000 consumers are exempt from some of the documentation requirements, including the written risk assessment, the incident response plan and annual reporting. The core safeguards and the written plan still apply.

Since 2024, firms must also notify the FTC of security events affecting the information of 500 or more consumers.

How to build yours

  1. Start from Publication 5708, and adapt it to how your practice actually works.
  2. Map your data: devices, email, tax and accounting software, cloud storage, paper files and vendors.
  3. Put the technical controls in place: MFA, encryption, backups, updates and endpoint protection. A written plan without working controls doesn't protect anyone.
  4. Write it down concisely. A small firm's WISP can be short, as long as it's accurate and followed.
  5. Train your staff, including seasonal help, and keep a record that you did.
  6. Review it every year, and whenever your systems change.

Check where you stand

Take our free 3-minute WISP & Safeguards Rule assessment. You'll get a score and a specific fix for every gap.

General information, not legal advice. See IRS Publications 4557 and 5708 and the FTC Safeguards Rule for the full requirements.