Every client file you handle holds the kind of information criminals want most: Social Security numbers, bank account details, W-2s, K-1s, and sometimes a family’s whole financial history.
That’s why cybersecurity compliance for CPA firms isn’t optional anymore. It’s federal law. The IRS ties it to your PTIN, and many states add their own rules.
The hard part is that the rules come from three directions: the FTC, the IRS, and state governments. Each one uses its own language, and most guides only explain one of them.
This guide covers all three. You’ll see who requires what, where the rules overlap, which firms get a break, and a 30-day plan to close the gaps.
Quick answer: what does cybersecurity compliance mean for a CPA firm?
If your firm prepares tax returns or handles client financial data, three layers of rules usually apply:
- Federal (FTC): The Gramm-Leach-Bliley Act (GLBA) Safeguards Rule, 16 CFR Part 314, treats tax preparers as “financial institutions.” You need a written information security program with nine required elements.
- IRS: Publication 4557, the “Security Six” controls, Publication 5708 (the WISP template), and the data security attestation on your PTIN renewal.
- State: Every state has a breach notification law. Some, like Massachusetts, also require a written security program for residents’ data, no matter where your firm is located.
The good news is that one well-built written information security plan (WISP) can satisfy most of all three at once, as long as your firm actually follows it.
Why CPA firms are a target (and why regulators care)
Tax and accounting firms keep a huge amount of personal data, often with less security than a bank. Criminals know this.
A stolen client list doesn’t just mean an embarrassing email. Criminals use it to file fake returns, steal refunds, and open credit in your clients’ names, sometimes before you even notice anything is wrong.
Attacks are also getting smarter. Phishing emails now look like real IRS notices. Fake “verify you’re human” pages trick staff into running malicious commands (here’s how ClickFix attacks work against CPA firms). Staff pasting client data into AI tools has become a compliance problem of its own (what to do if staff put client data into ChatGPT).
Regulators tightened the rules because of this. Through the Security Summit, the IRS has repeatedly reminded tax professionals to keep an up-to-date WISP.
Layer 1: The FTC Safeguards Rule
Does it really apply to my firm?
Yes. Most firm owners still assume the Safeguards Rule is a banking rule. It isn’t.
GLBA defines “financial institution” broadly enough to include professional tax preparers. In the FTC’s own rule, a tax preparation business is a named example. Firm size doesn’t matter: a solo PTIN holder preparing returns for pay is covered, and so is a 40-person regional firm.
Key dates
- 2003: The original Safeguards Rule took effect. It was vague and rarely enforced.
- June 9, 2023: The amended rule’s new, specific technical requirements took full effect.
- May 13, 2024: Breach reporting to the FTC became mandatory.
The nine required elements (16 CFR 314.4)
This is the core of the rule. Your written program has to cover all nine:
1. A Qualified Individual. One named person oversees and enforces your security program. It can be a partner, an employee, or an outside provider like a managed IT firm. If you outsource the role, the firm is still responsible and has to supervise that provider.
2. A written risk assessment. Identify where client data lives, what could go wrong, and how bad it would be. The assessment has to be written down and updated as things change.
3. Safeguards that address those risks. The rule names specific ones:
- Access controls, so staff only reach the data they need
- A current inventory of data, devices, and systems
- Encryption of customer information at rest and in transit
- Secure development practices for any in-house apps
- Multi-factor authentication for anyone accessing your information systems (our full guide to MFA for tax firms)
- Secure disposal of customer data, generally within two years of last use unless you have a legitimate business or legal reason to keep it
- Change management procedures
- Monitoring and logging of user activity
4. Regular testing. You need either continuous monitoring, or an annual penetration test plus vulnerability scans at least every six months.
5. Staff training. Security awareness training for everyone, kept current, plus qualified people running your security program.
6. Vendor oversight. Choose service providers that can protect your data, require it in your contracts, and check on them periodically. This covers your tax software host, cloud storage, client portal, and IT provider.
7. Keep the program current. Update it when your firm changes: a new office, a new portal, a switch to cloud hosting, or a new threat.
8. A written incident response plan. It should spell out who does what, how you communicate, how you fix the problem, and how you document it when something goes wrong.
9. An annual report to leadership. At least once a year, the Qualified Individual reports in writing to the partners (or the owner, in a small firm) on the program’s status, risks, test results, and incidents.
The 5,000-consumer exemption (and why it’s smaller than it sounds)
Firms holding customer information on fewer than 5,000 consumers don’t have to meet four of the nine items:
- The written risk assessment
- The pen testing and vulnerability scan schedule
- The written incident response plan
- The annual written report
Everything else still applies: the Qualified Individual, the safeguards, MFA, encryption, training, and vendor oversight.
Two warnings:
- It’s per consumer, not per active client. Former clients whose records you still keep count too. Many firms cross 5,000 without noticing.
- The exempted documents are the ones you’ll need most after a breach. Insurers, the IRS, and the FTC will ask for them. Most firms are better off creating them anyway.
FTC breach reporting: 500 consumers, 30 days
Since May 13, 2024, covered firms have to notify the FTC when unencrypted customer information of 500 or more consumers is acquired without authorization. The deadline is as soon as possible and no later than 30 days after discovery. You file the report on the FTC’s online form, and the FTC has said these reports go into a public database.
Note the word “unencrypted.” Properly encrypted data can keep a stolen laptop from turning into a reportable event, which is one of the strongest arguments for encrypting everything.
What happens if you ignore it?
The FTC can open an investigation and seek civil penalties, which are adjusted for inflation every year and can add up per violation. The IRS link matters too: the IRS may treat a Safeguards Rule violation as a violation of Revenue Procedure 2007-40, the rules for Authorized IRS e-file Providers. That puts your e-file status at risk, not just your reputation.
Layer 2: IRS requirements
The IRS doesn’t enforce the Safeguards Rule directly, but it has built a lot of practical guidance around it, and it connects compliance to your PTIN.
The PTIN renewal attestation (Form W-12)
When you renew your PTIN on Form W-12, Line 11 asks you to confirm that you’re aware of your legal obligation to have a data security plan and to protect taxpayer data.
Renewals usually open in mid-October, and PTINs expire on December 31. Checking the box doesn’t prove your plan exists or works. If you check it without a real plan in place, you’ve made a statement you can’t back up. Use renewal season as your yearly reminder to open the plan and update it.
Publication 4557 and the “Security Six”
IRS Publication 4557, Safeguarding Taxpayer Data, is the IRS’s plain-English guide to meeting the Safeguards Rule. Its best-known part is the Security Six, the baseline every firm should have:
- Anti-virus software on every device, kept updated
- Firewalls protecting your network and devices
- Multi-factor authentication on tax software, email, cloud apps, and remote access
- Backup software or services with copies stored securely and tested regularly
- Drive encryption on every laptop, desktop, and removable drive
- A Virtual Private Network (VPN) for anyone working remotely or on public Wi-Fi
If you run Drake or Lacerte on an office server, delivering these controls consistently across every workstation is hard. That’s one reason more firms are moving to secure tax software hosting (Drake hosting, Lacerte hosting), where encryption, backups, and MFA are built into the environment.
Publication 5708: the WISP template
Publication 5708 is the IRS’s fill-in template for building a written information security plan. It makes clear that firm size doesn’t remove the requirement. A sole practitioner’s plan can be simpler than a large firm’s, but it still has to exist and match how you actually work.
Want a head start? Get our free WISP template and checklist for CPA firms.
What the IRS expects after a data theft
The IRS reporting process is separate from the FTC’s, and speed matters most. If you report quickly, the IRS can block fake returns filed in your clients’ names. The IRS outlines these steps:
- Report the theft to your local IRS Stakeholder Liaison, who alerts IRS Criminal Investigation and other offices for you
- Contact the state tax agencies in every state where you prepare returns (the Federation of Tax Administrators keeps a state-by-state list)
- Notify state Attorneys General where required
- Contact your local FBI office and file a police report
- Notify your tax software provider
- File with the FTC if 500 or more people are affected
Put these contacts in your incident response plan before you need them. Nobody finds phone numbers well in the middle of a breach.
Layer 3: State rules
This is the layer most guides skip, and it can catch out firms that serve clients in several states.
Breach notification laws apply in all 50 states
Every state has a data breach notification law. Each sets its own rules on what counts as personal information, how quickly you must notify affected residents, and whether you must also tell the state Attorney General.
What matters is where your clients live, not where your office is. A Delaware firm with clients in New York, California, and Texas may have to follow four different notification rules after one breach.
Massachusetts 201 CMR 17.00
Massachusetts has one of the strictest state rules. Anyone who owns or licenses personal information about a Massachusetts resident must keep a comprehensive written information security program, wherever the business is located. It includes specific technical requirements such as encrypting personal data on laptops and portable devices and when it’s sent over public networks.
If you have even a handful of Massachusetts clients, your WISP needs to meet this standard.
New York SHIELD Act
The SHIELD Act requires “reasonable” administrative, technical, and physical safeguards for the private information of New York residents, and it widened breach notification duties. Businesses already compliant with GLBA are generally treated as meeting its safeguards requirement, which is another reason to get your Safeguards Rule program right first.
Delaware and other “reasonable security” states
Delaware, like a growing number of states, requires businesses holding residents’ personal information to maintain reasonable security procedures. It also has its own breach notification rules, including notice to the Attorney General when a breach affects a large number of residents. Check the current rules in each state where you have clients.
What about NYDFS Part 500?
The NYDFS cybersecurity regulation comes up often, and searches for it are rising. It applies to entities licensed by the New York Department of Financial Services, such as banks, insurers, and certain lenders. Most CPA firms aren’t covered directly. You may still feel it indirectly if a DFS-regulated client asks you to meet its vendor security standards.
Professional duties still apply
On top of all this, the AICPA Code of Professional Conduct and your state board of accountancy expect you to protect client confidentiality. A breach caused by weak security can turn into a professional conduct issue, not just a regulatory one.
How the three layers fit together
| Requirement | FTC Safeguards Rule | IRS (Pub 4557 / 5708 / W-12) | State laws |
|---|---|---|---|
| Written security plan | Required (written program) | Required (WISP, attested at PTIN renewal) | Required in some states (e.g. MA) |
| MFA | Required | Part of the Security Six | Expected as “reasonable security” |
| Encryption | Required at rest and in transit | Drive encryption in the Security Six | Required in some states (e.g. MA) |
| Risk assessment | Required (written, unless under 5,000 consumers) | Recommended | Often required |
| Staff training | Required | Recommended | Often required |
| Vendor oversight | Required | Recommended | Required in some states |
| Breach reporting | FTC within 30 days if 500+ consumers | Stakeholder Liaison, as fast as possible | Residents and often the AG, timelines vary |
The pattern is clear: build to the FTC standard, use IRS publications as your playbook, and add state-specific items on top. One program can cover everything.
The most common compliance gaps we see in CPA firms
After working with tax and accounting firms, these are the problems that come up again and again:
- A WISP that’s just a document. It was written once, put in a drawer, and never matched to how the firm actually works.
- Client documents sent by plain email. This undercuts several encryption and access requirements at once. Use a secure portal.
- MFA on some systems but not all. Tax software has it, but email, remote desktop, or the backup console doesn’t.
- No named Qualified Individual. “Our IT guy handles it” isn’t a designation.
- Untested backups. A backup you’ve never restored from is only a hope.
- Vendors nobody has checked. Your hosting provider, portal, and payroll tools all hold client data.
- Former employees who still have access. Accounts stay active months after people leave.
- An office server with no monitoring. Nobody would notice an intruder until returns start getting rejected.
If several of these sound familiar, you’re not alone. Most firms have at least three. A free IT assessment is the fastest way to find out where you stand.
A 30-day cybersecurity compliance action plan
You don’t have to fix everything this week. Here’s a realistic order to work in.
Week 1: Ownership and inventory
- Name your Qualified Individual in writing
- List every device, application, and vendor that touches client data
- Count your consumers (current and former) to see whether the 5,000 exemption applies
Week 2: Close the biggest risks
- Turn on MFA everywhere: email, tax software, remote access, cloud apps
- Confirm full-disk encryption on every laptop and desktop
- Move client document exchange off plain email
- Remove access for former staff and unused accounts
Week 3: Write it down
- Do your risk assessment
- Build or update your WISP (start from Pub 5708 or our WISP template)
- Draft your incident response plan, including IRS, state, and FTC contacts
Week 4: Test and train
- Run a real backup restore test
- Hold security awareness training and keep a record of attendance
- Review vendor contracts for security language
- Schedule your next vulnerability scan or set up continuous monitoring
- Put the annual review on the calendar for PTIN renewal season
When to bring in outside help
Plenty of small firms can handle the administrative side themselves. The technical side is harder: monitoring, patching, encryption, secure remote access, and testing. It’s also where most audit failures happen.
The Safeguards Rule explicitly allows a service provider to serve as your Qualified Individual or deliver key safeguards, as long as you supervise them. Many firms find it cheaper to hand this to a specialist than to build it in-house.
TechFiscal works only with accounting and tax firms on exactly this. We offer managed IT for CPA firms, WISP compliance services, security solutions built around the Safeguards Rule, and remote managed IT that keeps monitoring and patching running all year. If your server is the weak point, cloud migration to a secure hosted environment can remove a big share of the risk at once.
Not sure where your firm stands? Get a free IT assessment. We’ll map your current setup against FTC, IRS, and state requirements and show you exactly what to fix first.
FAQs
Does the FTC Safeguards Rule apply to solo tax preparers?
Yes. If you prepare tax returns for pay, you’re treated as a financial institution under GLBA. Your plan can be simpler than a large firm’s, but you still need a written program, a Qualified Individual (which can be you), MFA, encryption, and the other core safeguards.
Is a WISP legally required for CPA firms?
Yes. Federal law under the FTC Safeguards Rule requires tax preparers to keep a written information security program, and the IRS asks you to confirm you’re aware of that duty when you renew your PTIN. Some states, such as Massachusetts, require one separately for residents’ data.
What is the difference between IRS Publication 4557 and 5708?
Publication 4557 explains what safeguarding taxpayer data involves, including the Security Six. Publication 5708 is a fill-in template for writing your WISP. Most firms use 4557 to understand the requirements and 5708 to document them.
What are the IRS Security Six?
Anti-virus software, firewalls, multi-factor authentication, backup software or services, drive encryption, and a VPN for remote access.
Do I have to report every data breach to the FTC?
No. FTC reporting applies when unencrypted customer information of 500 or more consumers is acquired without authorization, within 30 days of discovery. You should still report any client data theft to your IRS Stakeholder Liaison quickly, and check the breach notification laws in each state where affected clients live.
What counts as a “consumer” for the 5,000 exemption?
It’s based on the number of individuals whose information you keep, not the number of documents. Former clients whose records you still hold usually count, so many firms are over the threshold without realizing it.
How often should a CPA firm update its WISP?
Review it at least once a year. PTIN renewal season is a natural time. Update it sooner after any major change, such as a new office, a new client portal, a move to cloud hosting, a new IT provider, or a security incident.
Can my IT provider be our Qualified Individual?
Yes. The Safeguards Rule allows a service provider to fill the role. Your firm is still responsible for compliance, so you need to supervise the provider and keep records showing you do.
Does using cloud-hosted tax software make my firm compliant?
Not by itself. A good hosting provider takes care of a lot of the technical safeguards, such as encryption, backups, MFA, and monitoring. You still need your own WISP, staff training, access policies, vendor oversight, and incident response plan.
