The FTC Safeguards Rule (16 CFR Part 314) treats tax preparation firms as financial institutions, so most accounting and tax practices must run a written information security program with nine required elements, including MFA and encryption. Since May 13, 2024, covered firms must also report certain breaches involving 500 or more consumers to the FTC. This guide explains the requirements in plain terms for small firms in Massachusetts.
The FTC Safeguards Rule for accountants is not optional paperwork. If your firm prepares tax returns, federal rules treat you as a financial institution, which means you need a written information security program with nine specific elements, multifactor authentication (MFA) on your systems, encryption of client data, and, since May 13, 2024, a plan to report certain breaches to the FTC within 30 days.
This guide walks through what the rule says, where small firms get relief, how the IRS templates fit in, and how it all lines up with Massachusetts law. It is general information, not legal advice. Confirm your firm's specific obligations with your attorney or compliance advisor.
Does the FTC Safeguards Rule for accountants apply to your firm?
The Safeguards Rule lives at 16 CFR Part 314 and comes from the Gramm-Leach-Bliley Act. It covers "financial institutions" under FTC jurisdiction, and that phrase is much broader than banks. The rule's definition section lists example entities, and the FTC's own business guidance points out that "tax preparation firms" are on that list.
The IRS says the same thing from its side. IRS Publication 4557 tells tax professionals that, under the FTC Safeguards Rule, tax return preparers must create and enact security plans to protect client data, and it warns that failing to do so may result in an FTC investigation. When the IRS released its WISP template, it was blunter: federal law requires all professional tax preparers to create and implement a data security plan.
So in practice, the FTC Safeguards Rule for accountants is really a rule for anyone in the firm who touches tax work. Two practical points for CPA and accounting practices:
- Coverage follows the work, not the license. A bookkeeping-only practice with no tax or financial services work may land somewhere different, so ask counsel if that describes you.
- Solo practitioners are not exempt from the program itself. Size changes some details (more on that below), but the core duties apply to a one-person shop.
The nine elements of an information security program
Section 314.4 lists what your program must include. Here they are in the order the FTC presents them, with what each one tends to look like in a 5 to 50 person firm.
| Element | What it means in practice |
|---|---|
| 1. Designate a Qualified Individual | One named person oversees and enforces the program |
| 2. Written risk assessment | Identify where client data lives and what could go wrong, then document it |
| 3. Design and implement safeguards | Access controls, MFA, encryption, secure disposal, logging and the rest |
| 4. Regularly monitor and test | Continuous monitoring, or annual penetration tests plus vulnerability scans at least every six months |
| 5. Train staff | Security awareness training for everyone who touches client data |
| 6. Monitor service providers | Pick vendors that can protect data, require it by contract, and check on them |
| 7. Keep the program current | Update it when your systems, staff or threats change |
| 8. Written incident response plan | Who does what when something goes wrong, written down before it happens |
| 9. Report to the board | The Qualified Individual reports in writing at least annually |
If your firm has no board, the annual report goes to a senior officer, which for most small practices means the managing partner. The report should cover the overall status of the program and material matters such as risk decisions, test results, security events and recommended changes.
The Qualified Individual: who can it be?
The rule does not demand a CISO or a certification. The FTC describes the Qualified Individual as someone with practical know-how suited to your business, and that person can be an employee or someone at an affiliate or service provider.
Plenty of small firms hand this role to an outside IT provider. That is allowed, with a catch: the firm keeps responsibility for compliance, must designate a senior member of its own staff to direct and oversee the provider's person, and must require the provider to maintain a compliant program. We think that is the right model for most firms under 20 people. Your IT partner brings the technical judgment, and a partner inside the firm owns the decisions and signs off on risk.
Technical safeguards the rule names explicitly
Most of the rule is principle based, but a few safeguards are spelled out. These are the ones auditors, insurers and clients ask about first.
Multifactor authentication
Section 314.4(c)(5) requires MFA "for any individual accessing any information system." That means email, your tax software, your document management system, remote access tools and your cloud storage, along with the server. The only escape hatch is a reasonably equivalent or more secure control that your Qualified Individual approves in writing. In our experience that exception rarely holds up for a small firm, so plan on MFA everywhere.
Encryption
Customer information must be encrypted both in transit over external networks and at rest. If encryption truly is not feasible for a particular system, the Qualified Individual can approve compensating controls, but that approval should be documented and revisited. Laptops with full-disk encryption, encrypted client portals instead of email attachments, and encrypted backups cover most of the ground.
Secure disposal
You need procedures to dispose of customer information no later than two years after it was last used to serve that client, unless you need it for a legitimate business purpose, the law requires you to keep it, or targeted disposal is not reasonably feasible. Tax firms usually have legitimate retention needs, so the work here is writing a retention schedule and reviewing it periodically rather than shredding everything at 24 months.
Logging and monitoring
Section 314.4(c)(8) requires policies and controls to monitor and log the activity of authorized users and detect unauthorized access or tampering. In a Microsoft 365 shop, much of this is available in audit logs that are already collecting data. The gap is usually that nobody reviews them.
What the fewer-than-5,000-consumers exemption covers
Small firms get partial relief. Under 16 CFR 314.6, if you maintain customer information concerning fewer than 5,000 consumers, four specific requirements in 314.4 do not apply:
- (b)(1): the written risk assessment
- (d)(2): continuous monitoring, or annual penetration testing and vulnerability assessments every six months
- (h): the written incident response plan
- (i): the annual written report to the board or senior officer
Everything else still applies. You still need a Qualified Individual, safeguards based on a risk assessment (just not a formal written one), MFA, encryption, training, vendor oversight and the FTC breach notice.
Our opinion: do the four exempt items anyway, in short form. A two-page written risk assessment and a one-page incident response checklist cost a few hours. They also make the rest of your program defensible, and cyber insurers and Massachusetts law tend to expect similar documentation regardless of the federal exemption.
Reporting a breach to the FTC: the 500-consumer rule
The FTC amended the rule in late 2023 to add a notification requirement. The Federal Register notice states that the amendments are effective May 13, 2024.
Here is how it works under section 314.4(j):
- A "notification event" is unauthorized acquisition of unencrypted customer information involving at least 500 consumers.
- Encrypted data counts as unencrypted if the encryption key was also accessed.
- Unauthorized access is presumed to be acquisition unless you have reliable evidence otherwise.
- You must notify the FTC as soon as possible and no later than 30 days after discovery, through the FTC's online form.
- Discovery is the first day the event is known to anyone at the firm other than the person who committed it.
The notice must include your name and contact information, the types of information involved, the date or date range if you can determine it, the number of consumers affected, a general description of the event, and whether law enforcement has asked for a delay. The FTC has said it intends to put these reports into a publicly available database, which is worth keeping in mind.
The FTC rule does not require you to notify the affected clients. Massachusetts law does, separately, and we cover that in our guide to the Massachusetts data breach notification law. Publication 4557 also tells preparers to keep their IRS Stakeholder Liaison updated after a data theft.
IRS Publication 4557 and the Publication 5708 WISP template
The IRS and its Security Summit partners publish two documents every tax practice should have on file.
Publication 4557, Safeguarding Taxpayer Data (the current revision is dated June 2024) is the practical guide. It covers basic security steps, strong passwords, wireless security, phishing, reporting data loss, and a checklist for building a plan under the Safeguards Rule. It recommends MFA for anyone accessing customer information and encrypted backups kept somewhere not connected to the network full time.
Publication 5708, revised August 2024, is a sample WISP for tax and accounting practices. It runs 29 pages and includes:
- A sample WISP with sections on objectives, scope and responsible individuals
- Guidance on assessing risks, inventorying hardware and documenting safety measures
- Sample attachments for record retention, staff rules of behavior, breach procedures, employee acknowledgment, a hardware inventory, and a list of employees authorized to access PII
Use Publication 5708 as a skeleton, not a finished product. The most common failure we see is a WISP downloaded, logo swapped and filed, with sections that describe controls the firm does not actually have. That is worse than a short, honest plan, because it is the document regulators and insurers will compare against reality after an incident.
How the Safeguards Rule overlaps with Massachusetts 201 CMR 17.00
If you have Massachusetts clients, you are also subject to 201 CMR 17.00, the state data security regulation. It applies to any person that owns or licenses personal information about a Massachusetts resident. The good news is that one well-built program can satisfy both.
| Topic | FTC Safeguards Rule | 201 CMR 17.00 |
|---|---|---|
| Written program | Required, with nine elements | Required (17.03) |
| Responsible person | Qualified Individual | One or more designated employees |
| Risk assessment | Written, unless under 5,000 consumers | Identify and assess foreseeable risks |
| MFA | Required for anyone accessing any information system | Secure user authentication; MFA not named |
| Encryption | At rest and in transit over external networks | Over public networks, wirelessly, and on laptops and portable devices, where technically feasible (17.04) |
| Vendors | Oversee service providers | Select capable providers and require safeguards by contract |
| Review cycle | Keep program current; annual report | Review at least annually |
| Breach reporting | FTC within 30 days for 500+ consumers | State notification law applies separately |
Where the two differ, build to the stricter version. In practice that usually means the FTC's MFA requirement and the Massachusetts annual review.
A practical order of operations for a small firm
If you are starting from little or nothing, this sequence gets the highest-risk gaps closed first.
- Name your Qualified Individual and the senior person who oversees them. Put both names in writing.
- Turn on MFA everywhere: email, tax software, portals, remote access and admin accounts. This is the control most often missing and the one that stops the most common attacks.
- Inventory where client data lives, including old file shares, personal OneDrive folders and scanned documents on desktops.
- Encrypt laptops and backups, and move client file exchange to a secure portal.
- Write the risk assessment and incident response plan, even if the 5,000-consumer exemption applies to you.
- Adapt Publication 5708 into your WISP, describing only controls you actually run.
- Train staff, then schedule the next session. Annual training in January, before filing season, works well for most firms.
- Review vendor contracts for your tax software, document management, IT provider and cloud backup.
- Set a calendar reminder for the annual review and written report.
Our accounting firm IT support work usually starts with steps 2 through 4, because they reduce real risk fastest, and then moves to the documentation. If you want an outside view of where your firm stands against the rule, our cybersecurity services and IT consulting teams can run a gap review and help you turn the IRS template into a plan that matches how your office actually works.
Frequently asked questions
Does the FTC Safeguards Rule apply to CPA firms?
If your firm prepares tax returns, almost certainly yes. The rule's own list of example financial institutions includes tax preparation firms, and the IRS tells tax professionals that the FTC Safeguards Rule requires them to create and enact a security plan. Firms that do no tax or other financial activity should confirm their status with an attorney, because coverage depends on the services you provide, not your professional title.
What is a WISP for tax preparers?
A WISP is a written information security plan: the document that describes how your firm protects client data. The FTC Safeguards Rule requires a written information security program, and the IRS publishes a free sample template, Publication 5708, built for tax and accounting practices. The template includes sample attachments for record retention, staff rules of behavior, breach procedures and a hardware inventory that you adapt to your firm.
Do small accounting firms get any exemption from the Safeguards Rule?
Partly. Under 16 CFR 314.6, firms that maintain customer information on fewer than 5,000 consumers are exempt from four requirements: the written risk assessment, the continuous monitoring or annual penetration testing requirement, the written incident response plan, and the annual written report to the board. Every other element still applies, including the Qualified Individual, MFA, encryption, training and vendor oversight.
When does an accounting firm have to notify the FTC of a breach?
Since May 13, 2024, a covered firm must notify the FTC when unencrypted customer information of at least 500 consumers is acquired without authorization. The notice is due as soon as possible and no later than 30 days after discovery, and it is filed through a form on the FTC website. Massachusetts breach notification law and IRS reporting steps can apply at the same time.
Who can be the Qualified Individual under the Safeguards Rule?
The Qualified Individual can be an employee, or someone who works for an affiliate or a service provider such as a managed IT firm. The FTC does not require a particular degree or title. If you use an outside provider, the rule requires the firm to keep responsibility, designate a senior member of staff to direct and oversee that person, and make sure the provider maintains a compliant program.
Sources and references
- FTC: FTC Safeguards Rule, What Your Business Needs to Know
- 16 CFR 314.4: Elements (Cornell LII)
- 16 CFR 314.6: Exceptions (Cornell LII)
- Federal Register: Standards for Safeguarding Customer Information, final rule (November 13, 2023)
- IRS Publication 4557: Safeguarding Taxpayer Data (Rev. 6-2024)
- IRS Publication 5708: Creating a Written Information Security Plan for your Tax and Accounting Practice (Rev. 8-2024)
- IRS: Security Summit releases new data security plan to help tax professionals
- 201 CMR 17.03: Duty to protect and standards for protecting personal information (Cornell LII)
- 201 CMR 17.04: Computer system security requirements (Cornell LII)