Guide · 8 min · For Accounting Firms

Why accounting firms are targets

Attackers don't pick targets by size. They pick by what a breach is worth, and a CPA firm is unusually rich for its footprint. In one small office you have Social Security numbers, dates of birth, bank-account and routing numbers, brokerage details, payroll data, and a year-by-year financial portrait of every client. That is a complete identity-theft and fraud kit, multiplied by your entire client list.

Two things make it worse. First, accounting firms move money and authorize transactions — which makes them a natural fit for wire-fraud and invoice schemes. Second, the calendar. For four months a year your team is heads-down, working long hours under deadline pressure, processing a flood of email from clients and the IRS. Urgency plus volume is precisely the environment social-engineering attacks are built for.

The threats that actually hit accounting practices

What good IT support covers for a CPA firm

The baseline isn't exotic, and most of it is inexpensive relative to a single incident:

  1. MFA on everything — email, the tax software, the document portal, remote access, and banking. This is the single highest-impact control and the one most firms only half-finish.
  2. EDR with monitoring, not legacy antivirus. Endpoint detection and response watches behavior and is backed by a team that can act at 2 a.m. Signature antivirus alone no longer clears the bar — your cyber-insurance carrier likely already requires EDR.
  3. Email security that catches impersonation, not just spam — the layer that blunts BEC and credential phishing.
  4. Encrypted devices and mobile management. Laptops leave the office during busy season; full-disk encryption means a lost laptop is a lost laptop, not a reportable breach.
  5. Backups you have actually restored. A backup that's never been test-restored is hope, not a plan. The restore is the test.
  6. A secure client file exchange — a portal, not email attachments — so SSNs and returns aren't sitting in inboxes.
  7. Tax-software environment ownership. Whether you run UltraTax, Lacerte, CCH, ProSeries, or Drake, someone needs to own its updates, performance, and backups — not just the hardware it runs on.

The written plan the IRS now expects

Here's the part most small firms miss: a security plan is no longer optional. Under the FTC Safeguards Rule — which implements the Gramm-Leach-Bliley Act — tax and accounting firms are treated as "financial institutions" and must maintain a Written Information Security Plan (WISP). The IRS spells this out in Publication 4557, "Safeguarding Taxpayer Data," around its "Security Six" basics, and now ties having a plan to PTIN renewal for paid preparers.

A real WISP names a responsible person, documents a risk assessment, lists the specific safeguards you've implemented, and shows that staff are trained. The value isn't the document — it's that writing it forces you to confirm the controls above are actually in place. If an examiner, an insurer, or a client asked to see your plan tomorrow, could you produce one that's true?

What to look for in a provider

Most general IT shops can manage your laptops. Fewer understand an accounting practice. Before you sign:

The right setup should feel like a quiet partner: the deadlines get met, the client data stays protected, and you have one number to call when something looks wrong.

Frequently asked questions

Does a small CPA firm really need managed IT and security?
A two-person tax practice holds the same kind of data a large firm does — Social Security numbers, bank accounts, and complete financial records — and attackers automate their way to it regardless of firm size. The controls below aren't enterprise luxuries; most are inexpensive, and several are now required of every paid preparer by federal rule. The question isn't whether you're big enough to be a target. It's whether you can produce your written plan if the IRS or a client asks.
What is a WISP, and is it actually required?
A WISP is a Written Information Security Plan. Under the FTC Safeguards Rule (which implements the Gramm-Leach-Bliley Act), tax and accounting firms are "financial institutions" and must maintain a written security plan with a named responsible person, a risk assessment, specific safeguards, and staff training. The IRS reinforces this in Publication 4557 and now ties it to PTIN renewal. Most small firms either don't have one or have a template they've never implemented.
Can't we just use antivirus and be careful with email?
Careful people still get caught — busy-season urgency is exactly what business-email-compromise attacks exploit. Legacy antivirus also misses modern attacks that never drop a traditional virus file. The practical baseline today is MFA on every account, EDR with monitoring instead of signature antivirus, email filtering that catches impersonation, encrypted devices, and backups you've actually tested. Care is necessary; it isn't a control.
What about IT support during tax season?
Response time is the whole game from January to April. A break-fix shop that gets to you "in a day or two" is a liability when a return is due. Before you sign with any provider, ask for their guaranteed response time, confirm it holds during their own busy periods, and make sure someone owns your tax-software environment — not just the laptops.

Related reading