The IRS WISP Template for Solo and Small CPA Firms (12 Pages, Not 60)
What an IRS Publication 4557-aligned Written Information Security Plan (WISP) actually has to contain for a small CPA firm in 2026.
Read articleCompliance
What IRS Publication 4557 and the FTC Safeguards Rule actually require of CPA firms in 2026 — the safeguards, the written program, and where firms slip.
Short answer: A CPA firm's information-security programme needs working controls and records, not just a downloaded plan. Keep the written programme aligned with the accounts, systems and data the firm operates. Gather evidence as the work happens. A template alone does not demonstrate that a control is in use.
Many CPA firm owners in 2026 have heard of the FTC Safeguards Rule, have downloaded the IRS sample WISP at some point, and have a folder somewhere they would describe as their information security program.
Far fewer can produce, on demand, the documentation a Stakeholder Liaison, FTC investigator, state attorney general, or cyber-insurance underwriter would accept as evidence of a current, working program.
That is not a moral failure. It is structural. The CPA cybersecurity obligation in 2026 is not a single rule.
It is a four-layer stack — IRS guidance, FTC regulation, AICPA professional standards, and state law — and almost nothing in the day-to-day life of a tax practice surfaces the whole picture in one place.
This guide walks through what each layer requires, where firms most consistently fall short, and what a defensible 90-day path looks like.
A note up front: we operate the technical safeguards side. We are not your Qualified Individual under § 314.4(a) — that role lives inside the firm. We are not a CPA firm and we do not opine on AICPA SSTS interpretation.
Three pages on this site cover this ground, and they are not interchangeable. Pick by what you are trying to do today.
Free cyber-insurance questionnaire review
Obsidian Ridge offers a free, one-off cyber-insurance questionnaire review for small businesses. Email your carrier's questionnaire to security@obsidianridge.io; our CISSP-led practice replies within one business day, serving the Research Triangle and businesses across the United States. We are not an insurance agent or broker.
Request a questionnaire reviewCPA firms in 2026 have to satisfy four overlapping regimes at once:
There is no employee-count exemption. The Safeguards Rule specifically requires:
The program that satisfies the strongest layer usually satisfies the others; very few firms have built that program.
Every CPA firm preparing returns or providing tax services in the United States is subject to all four of these regimes simultaneously. They overlap. They do not replace each other.
Many firms are partially aware of layer 1, vaguely aware of layer 2, surprised by layer 3, and unaware of which parts of layer 4 apply to them. The technical program that satisfies the strongest layer tends to satisfy the others. Very few firms have built that program.
Publication 4557, "Safeguarding Taxpayer Data," is the umbrella document. It has set out safeguarding expectations for paid preparers since 2008, tells a reader to “see Publication 5708 for information on creating a written information security plan” and warns that “failure to do so may result in an FTC investigation,” and cross-references the FTC Safeguards Rule.
It is IRS guidance rather than regulation, but the Return Preparer Office treats it as an operating expectation, and a current WISP is the first thing an IRS Stakeholder Liaison asks about after a suspected data theft.
Publication 5708, "Creating a Written Information Security Plan for your Tax & Accounting Practice" (first issued 2022; current edition Rev. 8-2024) is the operational companion — a sample WISP and a fillable template. Two failure modes: firms that never downloaded it, and firms that filled in their letterhead once and never touched it again.
IRC § 7216 makes disclosure or use of taxpayer return information a federal misdemeanor where the preparer acted “knowingly or recklessly” — up to a $1,000 fine, a year's imprisonment, or both, plus the costs of prosecution (26 U.S.C. § 7216). The related civil penalty under IRC § 6713 needs no such intent: 250 dollars for each prohibited disclosure or use, capped at $10,000 a calendar year, rising to $1,000 and $50,000 where the disclosure relates to identity theft. That is the hook that turns sloppy data handling into a federal exposure for the preparer personally.
IRS Stakeholder Liaison reporting. The IRS expects a preparer who suspects a data theft involving tax-related information to contact their assigned Stakeholder Liaison promptly, per Publication 4557 and Security Summit guidance.
This is in addition to, not in place of, FTC, state, and client notifications.
PTIN consequences. The Return Preparer Office can suspend or revoke a PTIN for misconduct, and serious data-handling failures fall inside that authority. PTIN actions tied to data-security failures are real, and the loss of a PTIN ends a tax practice.
This is the layer most CPA firms underestimate. The Gramm-Leach-Bliley Act defines a "financial institution" broadly enough to include any business "significantly engaged" in providing financial products or services.
The FTC's interpretation, reaffirmed in the 2021 and 2023 amendments, places CPA firms preparing tax returns squarely inside that definition. The Safeguards Rule at 16 CFR Part 314 applies to your firm directly, regardless of whether you think of yourself as a "financial institution."
The 2021 amendments, whose main requirements took effect on June 9, 2023, sharpened the rule into specific named controls.
Designated Qualified Individual — § 314.4(a). One named individual responsible for the program. Not a committee. The rule allows an employee, an affiliate or a service provider in the role. If the firm uses a provider, it keeps responsibility, names a senior member of its own staff to oversee the Qualified Individual, and requires the provider to maintain a security program that protects the firm. In small CPA firms it is usually a partner or the firm administrator.
Written risk assessment — § 314.4(b). Identifies reasonably foreseeable internal and external risks to the security, confidentiality, and integrity of customer information, with periodic reassessment required.
Multi-factor authentication — § 314.4(c)(5). Required for any individual accessing any system containing customer information, subject to a narrow exception for equivalently strong controls approved in writing by the Qualified Individual.
In a CPA firm:
Encryption — § 314.4(c)(3). Customer information must be encrypted in transit over external networks and at rest, with a similar narrow exception.
Access controls and least privilege — § 314.4(c)(1). Limited to authorized users with periodic reviews. Shared "FrontDesk" or "TaxAssistant" accounts are not consistent with this requirement.
Continuous monitoring or periodic penetration testing — § 314.4(d). Continuous monitoring, or annual penetration testing plus biannual vulnerability assessments. Most small firms cannot run continuous monitoring in-house, which makes managed detection and response the practical path.
Service provider oversight — § 314.4(f). Select providers capable of maintaining safeguards, contract with them to do so, and periodically assess them based on risk.
Written incident response plan — § 314.4(h). Roles, communication, remediation, documentation, and post-incident evaluation.
Annual report to the board or equivalent — § 314.4(i). The Qualified Individual reports in writing at least annually to the board or, in firms without one, to a senior officer.
The small-firm exception — § 314.6. For a firm holding customer information on fewer than 5,000 consumers, the written form of the risk assessment (§ 314.4(b)(1)), continuous monitoring or annual penetration testing (§ 314.4(d)(2)), the written incident response plan (§ 314.4(h)) and the annual report (§ 314.4(i)) do not apply. Everything else above does, including the 30-day FTC notification below.
The 2023 amendments added a notification trigger that surprised many firms. For breaches affecting 500 or more consumers, the firm must notify the FTC within 30 days through the FTC's electronic portal — in addition to all state and IRS notification duties.
The Safeguards Rule carries no fine for a first violation. The Gramm-Leach-Bliley Act does not give the FTC civil penalty authority for it, and the FTC has asked Congress for that power (FTC testimony, March 2019).
What the FTC uses instead is a consent order. When it charged TaxSlayer, an online tax preparation service, with violating the Safeguards and Privacy Rules in 2017, the settlement required biennial third-party assessments for ten years, and the order "will terminate 20 years from the date of its issuance" (FTC decision and order). Civil penalties come in if a firm then violates the order.
The practical point holds: a documented program that satisfies § 314.4 costs far less than two decades of FTC reporting, and the IRS and state layers in this guide carry consequences of their own.
Effective January 1, 2024, the AICPA's revised Statement on Standards for Tax Services brought data protection inside the professional standards framework.
SSTS § 1.3 makes confidentiality and safeguarding of taxpayer information an explicit professional obligation for AICPA member CPAs providing tax services.
The standard uses a "reasonable steps" framework that parallels the ABA's Model Rule 1.6(c) sliding scale. It does not list specific controls.
It does require the practitioner to consider:
A CPA who has taken no demonstrable steps is at risk under the standard regardless of whether a breach has occurred.
The disciplinary mechanism is the AICPA Professional Ethics Executive Committee, working through joint enforcement with state CPA societies — a different forum than IRS Office of Professional Responsibility or a state attorney general, and CPAs can be exposed to all three concurrently.
The fourth layer is the one most likely to produce a surprise enforcement letter. A few specific states matter to most firms:
New York — 23 NYCRR 500 (NY DFS). Covered financial services entities, including many accounting firms that hold DFS licenses or meet the rule's coverage tests, must:
The second amendment took effect November 1, 2023 and every one of its phase-in dates has passed; the last, for multi-factor authentication under § 500.12, was November 1, 2025.
Size matters here. A firm meeting any one of § 500.19(a)'s thresholds — fewer than 20 employees and independent contractors including affiliates, under $7,500,000 in gross annual revenue in each of the last three fiscal years, or under $15,000,000 in year-end total assets — is exempt from §§ 500.4, 500.5, 500.6, 500.8, 500.10, 500.14(a)(1), (a)(2) and (b), 500.15 and 500.16, which takes the CISO designation and the encryption requirement off the list above. The program, the written policies, the risk assessment, MFA and the annual notification still apply, and the firm has to file a Notice of Exemption. Our adviser guide sets out what a limited-exemption licensee still owes (23 NYCRR 500, second amendment, read 2026-11-05).
Connecticut — Public Act 21-119, codified at CGS § 42-901. In data-breach tort litigation, the Superior Court cannot assess punitive damages against a business whose written cybersecurity program conforms to an industry-recognized framework. It bars punitive damages only, not compensatory ones, and not where the failure was gross negligence or wilful or wanton conduct.
Massachusetts — 201 CMR 17.00. Any business that owns or licenses personal information about a Massachusetts resident is in scope. Most CPA firms with even a single MA client qualify.
Requires:
California — CCPA/CPRA. Disclosure and consumer-rights obligations attach to firms meeting the revenue or processing thresholds.
The 50-state breach notification patchwork. Every state has a breach notification law. Notification windows range from "without unreasonable delay" to specific day counts.
A CPA firm whose client list crosses state lines is, after a breach, looking at parallel notifications under each state's law.
When the FTC, the IRS, an AICPA panel, a state attorney general, or a cyber-insurance underwriter looks at a CPA firm in 2026, the controls they expect to see converge:
None of these is exotic. The challenge in a CPA firm is rarely technical capability; it is designated ownership and consistent execution.
The failure modes cluster predictably:
The "we are too small" assumption. Solo and two-partner firms commonly believe the Safeguards Rule does not apply. It does.
Firms with customer information on fewer than 5,000 consumers get relief from four requirements under § 314.6 (the written risk assessment, continuous monitoring or annual penetration testing, the written incident response plan and the annual report), and even that does not lift MFA, encryption, access-control, or vendor-oversight requirements.
The static WISP. A firm downloads the Publication 5708 template, fills in the firm name, and treats it as done. The WISP must be reviewed at least annually, updated on material changes, and backed by evidence the controls are in place.
The tax software MFA gap. Firm leadership enforces MFA on Microsoft 365 and feels covered. The tax-prep software has its own login.
A preparer reaches Lacerte, Drake, UltraTax, ProConnect, ATX, or CCH Axcess from a home laptop with a username and password and nothing else. Under § 314.4(c)(5), that single login is a violation — the single most overlooked MFA control in this industry.
Shared front-desk accounts. "ReceptionDesk," "TaxAssistant" — broad data access, no individual accountability, a password that has not rotated since the last associate left. Under § 314.4(c)(1) and § 314.4(c)(6), not defensible.
Free-trial vendor drift. An associate signs up for a free trial of an e-signature service or client-portal tool. The free trial silently becomes production. No contract, no data-handling clause, no inclusion in the risk assessment.
Personal cloud storage. Client tax documents in a partner's personal Dropbox or Google Drive — uncontrolled customer information outside the firm's program.
The named-but-unaware Qualified Individual. The WISP names a Qualified Individual. The named person does not know it. No § 314.4(i) annual report has ever been prepared.
Missing AI vendor inventory. The firm started using an AI tax-research assistant, document summarizer, or client-communication drafter last year.
Not in the vendor inventory, not under a data-handling agreement, possibly sending taxpayer information to a third-party model provider. Layer this on Publication 4557 plus IRC § 7216 and the exposure is non-trivial.
The IRS has not built a public enforcement docket for CPA-firm cybersecurity failures, but state attorneys general have. Two recent matters are useful reference points.
The October 20, 2025 New York Attorney General settlement with Wojeski & Company, an Albany-area CPA firm, covered two separate incidents — a July 2023 ransomware attack and a May 2024 third-party access incident.
The 2023 ransomware event affected 5,881 individuals in total, of whom 4,726 were New York residents; the 2024 incident affected 351 individuals (267 NY residents).
Settlement: $60,000 penalty plus a corrective security program. A clean example of how layer-4 state enforcement reaches a small CPA firm that did not have the layer-2 controls in place. (NY AG press release, 2025-10-20)
The Sax LLP disclosure, filed with the Maine Attorney General, involved approximately 228,876 individuals nationwide (244 Maine residents) notified by a top-100 accounting firm based in Parsippany, NJ.
Sax detected unusual activity on August 7, 2024, completed its data review on December 1, 2025, and began notifying affected individuals on December 16, 2025. The filing characterizes the incident as an external system breach (hacking); Sax has not publicly stated that a ransom was paid.
Firm size does not insulate against the incident profile, and state notification filings have become the de-facto public record for CPA-firm breaches. (Maine AG breach notice)
The pattern across both: the technical compromise is rarely novel. The exposure is built from delayed notification, missing documentation, and program gaps that pre-date the incident.
When a CPA firm suspects a data theft involving taxpayer or customer information, the sequence we run with firm leadership and breach counsel:
The post-incident documentation is not for the file cabinet. It is the evidentiary base that the next investigator, underwriter, or AICPA panel will work from.
For a firm starting from behind, the most useful framing is a 90-day program with milestones the Qualified Individual can actually report against.
Days 1-30 — foundation.
Days 31-60 — program.
Days 61-90 — operationalize.
At day 90 a firm that started from a static WISP has a current, defensible program. It will not be perfect. It will be defensible — which is the operative standard under all four layers.
We deliver the technical safeguards side:
We are not your Qualified Individual. The named role at § 314.4(a) lives with a firm partner or executive. We are not your CPA, and we do not interpret AICPA SSTS § 1.3 — that conversation belongs to your firm and to the AICPA Professional Ethics Executive Committee.
What we bring is the security-operations side that:
The CPA cybersecurity obligation in 2026 is no longer optional and no longer aspirational. The penalty stack now includes:
The technical and documented program that satisfies the strongest of those layers will satisfy the others.
Build it once. Maintain it. Review it annually. Be a firm the IRS Stakeholder Liaison is glad to talk to, and a firm whose cyber underwriter renews without a phone call.
If you are a CPA firm trying to map your current posture against the four-layer stack, Talk with us to start a working conversation that produces a concrete gap list against FTC § 314.4 subsections, Publication 4557, and the state requirements that apply to your client footprint.
The accounting industry overview describes the engagement model in more detail.
This article is general information for educational purposes, not legal or tax-practice advice. IRS guidance, FTC rule text, and state statutes cited above change over time, and application to a specific firm depends on facts and jurisdiction.
Consult qualified counsel and your state CPA society before relying on any specific interpretation. Sources: FTC Safeguards Rule (ftc.gov) and IRS Publication 4557 (irs.gov).
Free cyber-insurance questionnaire review
Obsidian Ridge offers a free, one-off cyber-insurance questionnaire review for small businesses. Email your carrier's questionnaire to security@obsidianridge.io; our CISSP-led practice replies within one business day, serving the Research Triangle and businesses across the United States. We are not an insurance agent or broker.
Request a questionnaire reviewLast updated
November 5, 2026. We refresh this content as the threat landscape and tools evolve.
Every paid tax return preparer with a PTIN is expected by the IRS to maintain a Written Information Security Plan under Publication 4557.
Every CPA firm that prepares tax returns, advises on tax matters for compensation, or otherwise offers a 'financial service' is a financial institution under the Gramm-Leach-Bliley Act and is directly subject to the FTC Safeguards Rule at 16 CFR Part 314.
There is no headcount exemption — a sole practitioner with one client is in scope.
Firms holding customer information on fewer than 5,000 consumers are exempt from four requirements under 16 CFR 314.6: putting the risk assessment in writing, continuous monitoring or annual penetration testing, the written incident response plan and the annual report.
Every other control still applies.
Yes.
Publication 4557 has set out safeguarding expectations for paid preparers since 2008, the IRS states plainly that tax professionals are required by law to have a Written Information Security Plan, and the legal requirement behind that is the FTC Safeguards Rule, which applies to a one-person CPA firm exactly as it applies to a 100-person firm.
The IRS Stakeholder Liaison program treats the WISP as the first piece of evidence it asks for after a suspected data theft.
Solo firms in 2026 are not flying under the radar — they are the demographic that state attorneys general and cyber-insurance carriers are now actively examining.
Publication 4557 is IRS guidance, originally aimed at taxpayer-data confidentiality under IRC § 7216 and at the practitioner's PTIN obligations.
The FTC Safeguards Rule at 16 CFR Part 314 is a federal regulation under the Gramm-Leach-Bliley Act and applies to CPA firms as 'financial institutions.' Publication 4557 tells you to have a WISP.
The Safeguards Rule tells you specifically what has to be in it — designated Qualified Individual, written risk assessment, MFA, encryption, access controls, vendor oversight, incident response plan, and an annual report.
The two regimes overlap but are not interchangeable. A WISP that satisfies Publication 4557 will not by itself satisfy the 2023-amended Safeguards Rule.
The Qualified Individual is the single person designated to oversee, implement, and enforce the firm's information security program.
The rule does not require a specific certification or title — it requires that the person actually be qualified to do the job, and that responsibility be assigned to one named individual rather than diffused across the firm.
In a CPA firm, the Qualified Individual is typically a partner, the firm administrator, or a chief operating officer. The rule lets that person be an employee, an affiliate or a service provider.
If the firm uses a provider, it keeps responsibility for compliance, names a senior member of its own staff to oversee the Qualified Individual, and requires the provider to maintain its own security program.
Firms holding information on 5,000 or more consumers also need the Qualified Individual to report in writing at least annually to the board or equivalent governing body.
Yes. FTC § 314.4(c)(5) requires MFA for any individual accessing any information system containing customer information, with limited exceptions for equivalently strong controls reviewed and approved in writing by the Qualified Individual.
In a CPA firm in 2026 that means MFA on Microsoft 365 or Google Workspace, the tax-prep software login itself, the client portal, the document management system, any remote-access path, and any administrator account.
MFA on email alone is not sufficient. The tax software login is the single most commonly overlooked control.
At least annually, and again on any material change — new tax software, new payroll system, an acquisition, an office move, a significant staffing change, a new vendor that touches customer information, or a security incident.
The Qualified Individual must report to the firm's leadership at least annually under FTC § 314.4(i). A one-time download of the IRS Publication 5708 sample, never revisited, fails that cadence.
FTC § 314.4(f) requires the firm to select service providers capable of maintaining appropriate safeguards, to contract with them to do so, and to periodically assess them based on the risk they present.
For a CPA firm in 2026 this means a written inventory of every vendor that touches customer information — tax software, e-signature vendor, client portal, cloud storage, payroll, bookkeeping, AI assistants — paired with contracts containing data-handling and breach-notification clauses, and a documented review on a cadence appropriate to risk.
Yes. The IRS Return Preparer Office has authority to suspend or revoke a Preparer Tax Identification Number for misconduct, which under published guidance includes serious failures of taxpayer-data safeguarding.
The IRS has not built a public name-and-shame program for CPA firms the way OCR has done in healthcare, but PTIN actions tied to data-handling failures are real, and a Stakeholder Liaison report of a suspected data theft is a moment at which prior compliance posture becomes very visible.
What an IRS Publication 4557-aligned Written Information Security Plan (WISP) actually has to contain for a small CPA firm in 2026.
Read articleFiling season concentrates the exposure. What IT covers, what a security operation covers, and the reporting path the IRS walks after a preparer breach.
Read articleWhat cyber insurance for CPA and tax firms actually covers in 2026, the underwriting questionnaire controls carriers review.
Read article