If you're a CPA or accounting firm in the Treasure Valley, you have two seasons: tax season, and the time you're recovering from tax season. The IT and cybersecurity side of both seasons is brutal in different ways.
During tax season, you're moving high volumes of sensitive client data: SSNs, W-2s, K-1s, complete financial pictures of every individual and business client. Your phishing exposure is at its annual peak. Your staff is exhausted and clicking through email faster than they should. And federal rules set specific requirements for how you handle that data.
Off-season is when you actually have time to fix the security posture you wished you had during tax season. Most firms never get around to it because they're catching up on continuing education, marketing, or sleep.
Here's the playbook to fix it during the lighter season, plus the checklist to walk through before next April hits.
IRS Pub 4557 and the WISP Requirement
IRS Publication 4557, Safeguarding Taxpayer Data , has been around for years and explains the requirement. The requirement itself comes from federal law: under the Gramm-Leach-Bliley Act and FTC Safeguards Rule (which applies to tax preparers and CPAs), every firm that prepares returns is required to maintain a Written Information Security Plan (WISP).
The WISP isn't optional. It's a federally mandated document, and the IRS keeps raising it:
- PTIN renewal applications include a question about your data security responsibilities
- The IRS regularly reminds tax professionals, including e-file providers, that a WISP is required
- Practitioner audits and complaints can trigger a WISP review
What a WISP must include (per FTC Safeguards Rule, updated effective 2023-2024 with full implementation requirements):
- Designation of a qualified individual to oversee the information security program
- Risk assessment (documented, written)
- Safeguards based on the risk assessment (technical, physical, administrative)
- Service provider oversight (BAAs-equivalent agreements with vendors)
- Ongoing monitoring and testing
- Employee training program
- Incident response plan
- Annual review and update of the WISP
- Reporting to leadership
One important exception: firms that hold information on fewer than 5,000 consumers are exempt from some of these (the written risk assessment, the written incident response plan, and the annual report), though most are still good practice.
A WISP for a typical small CPA firm runs 15-25 pages. It's not a one-day project, but it's also not a 12-month project. Most firms can produce a defensible WISP with 20-40 hours of focused effort and a competent IT provider to help with the technical sections.
The cost of not having one: the FTC can pursue enforcement actions, the IRS can sanction practitioners through OPR (Office of Professional Responsibility), and your professional liability carrier will likely have coverage gaps when an incident occurs.
Client Portal vs. Unencrypted Email
The single biggest day-one improvement most CPA firms can make is moving client document exchange off email and into a portal.
The math is simple:
- Email-based document exchange: unencrypted by default, no audit trail, no expiration on links, no access control after delivery, broad email signatures and forwarding risk
- Portal-based document exchange: encrypted in transit and at rest, MFA-protected access, audit logs of every download, expiration controls, revocable access
Portals are not novel. Every modern tax software has one (Drake Portals, Lacerte, ProSeries Online, etc.), and there are dedicated portal products (SafeSend, TaxDome, Citrix ShareFile, FileMobi) that integrate cleanly with the major tax platforms.
The transition pattern:
- Roll out the portal to new clients first. Onboarding new clients during the off-season gives time to refine the process.
- Migrate existing clients in waves. Don't try to switch everyone in February. Move them as their next engagement starts.
- Email-with-encryption as the fallback. For clients who refuse the portal, M365 Message Encryption or similar gives a secure path without forcing portal adoption.
- Hard rule on SSN and DOB. Never send those over unencrypted email. Period. The portal or encrypted message is required.
Document the policy in the WISP. Train the staff. By next March, the portal is the default.
Why Phishing Spikes in March-April
Tax season is open season for phishing attacks on CPAs. The patterns get more sophisticated every year. Specifics:
1. Client impersonation phishing. A criminal impersonates a real or fake client, sending "my W-2" or "updated K-1" attachments that contain malware. Volume is high during tax season because CPAs expect these attachments. The attack hides in normal traffic.
2. Refund redirect schemes. Criminals file fraudulent returns using stolen SSNs (often harvested from previous breaches) and try to redirect refunds. Sometimes they target the CPA's e-file process directly through compromised accounts.
3. IRS impersonation. Fake IRS notices, fake EFTPS confirmations, fake practitioner-priority-service emails. Convincing enough that even experienced staff misjudge them under time pressure.
4. Internal BEC during high-stress periods. "Hi, this is [ partner name], can you send me [ client's tax data / W-2 of an employee / payroll info] urgently? I'm with a client." Senior staff getting impersonated to junior staff who can't easily verify, especially during off-hours.
5. Last-minute software update scams. Around extension deadlines, fake "tax software security update" emails try to get firms to install malware disguised as patches.
For more on what these emails actually look like in the wild for small businesses , our earlier post breaks down recent examples.
Defensive posture for tax season:
- Quarterly phishing simulations, with a specific tax-season-themed campaign in February
- Refresh training in January and again mid-March
- External email tagging visible at the inbox level so spoofed messages are obvious
- Microsoft Defender for Office 365 (or equivalent) with anti-phishing impersonation protection enabled
- Strict policy on out-of-band verification for any "send me [ client data] urgently" request
- A documented "if you suspect you fell for it" reporting procedure, no-blame culture for fast reporting
April 14 Disaster Preparedness
The most-stressed day of the year for a CPA firm is the last working day before April 15. It's also a high-risk day for things to go sideways:
- Internet outage = no e-file
- Tax software outage = no returns processed
- Phishing click on an exhausted staff member = breach
- Ransomware event = absolutely catastrophic timing
Mitigations specifically for tax-deadline days:
- Failover internet. Dual ISP with automatic failover. The marginal monthly cost is trivial compared to a 4-hour outage on April 14.
- Tested IT support availability. Your IT provider should know your tax season schedule and have response commitments for peak days. "We have 24/7 support" needs to mean something on April 14.
- Pre-tested backups, in writing. If something happens and you need to restore, you need to know it works before April 14, not at 11pm that night.
- A documented "everything goes wrong" plan. Where does the firm work from if the office loses power? Who can take over e-filing if the primary processor's account is locked out? What's the IRS practitioner priority line and who has authority to call?
- A debrief on April 16. What worked, what didn't, what to fix during the off-season. Most firms don't do this and the same problems recur next year.
Off-Season Cybersecurity Work to Do
The post-tax-season period (May through November) is when the real cybersecurity work gets done. The priority list:
May-June: WISP refresh and risk assessment
- Update the WISP with anything that changed last year
- Run a fresh risk assessment: what's the threat landscape, what's the firm's exposure
- Document new vendors added and BAAs/security terms in place
July-August: Technical controls
- M365 conditional access review (especially MFA enforcement, geographic restrictions, legacy auth blocks)
- Endpoint inventory and EDR coverage check
- Patch management audit. Is everything actually current?
- Backup restore tests, documented
September-October: Training and tabletop
- Refresh annual security training for all staff
- Run a quarterly phishing simulation, review results
- Tabletop exercise: walk through a simulated incident
- Vendor security review: request updated SOC 2 reports from critical vendors
November-January: Tax-season-readiness
- Pre-tax-season phishing simulation with tax-themed scenarios
- Failover internet test
- Confirm IT support availability and response commitments for peak season
- Final WISP review and sign-off
That's an annual cycle. Most firms compress it into "we'll deal with it after April 15" and never circle back. The cycle is what produces a defensible security posture.
Insurance Implications
CPA firms typically carry professional liability (E&O) and increasingly cyber insurance. The carriers have caught up to the WISP requirement and the FTC Safeguards Rule. Renewal questionnaires now routinely ask about:
- Documented WISP on file
- MFA on email and client portals
- EDR deployment
- Tested backups
- Documented incident response plan
- Security awareness training
If your answers can't be substantiated, you're at risk of denied claims, coverage exclusions, or non-renewal . The combination of FTC Safeguards Rule and cyber insurance requirements has effectively made the technical security posture a business requirement on top of a best practice.
The Honest Take
Tax season is going to be brutal regardless. The question is whether your security posture survives it intact. A WISP-aligned firm with tested controls and trained staff handles the season with annoyance but not crisis. A firm that's been winging it is one phishing click away from a breach disclosure to clients who chose the firm specifically for trustworthiness.
The off-season is when you fix this. The fix is straightforward, the cost is manageable, and the timing is now. If you're a Treasure Valley CPA, start with a free 15-minute call. We'll go over WISP status, technical controls, training program, and tax-season readiness, and figure out what to tackle first. Anything we document is something you can hand to your insurance broker and keep with your WISP.
For more on the CPA-specific IT setup , our accounting and CPA services page covers the broader picture, and our cybersecurity services cover the full security stack.
Let's Talk
Cybersecurity for a CPA firm isn't a one-time project. It's an annual cycle that fits around tax season instead of getting buried by it. Let's get the cycle started.