The extension crunch is over. October 15 has come and gone, the coffee has worn off, and for about six weeks a tax office gets something it never has in March: a quiet afternoon.

Most of us spend it catching up. I'd like to make the case for spending one of them on locks.

Because security work in a tax office has a way of being scheduled for "after the season." And after the season, nobody has the energy for it. So here's a list for the one quiet stretch a practice gets, written so you can steal it.

In one paragraph: before the filing season starts, a small tax practice should spend one afternoon checking every login and turning on multifactor authentication, updating every device, reading (or writing) its written information security plan, agreeing how bank-detail changes get verified, and writing down who to call if something goes wrong. That's the whole article. The rest is how.

The timing isn't only mine. October is Cybersecurity Awareness Month, and the IRS has named the week of October 19th Tax Professional Awareness Week. Its announcement lists cybersecurity and identity theft prevention among the topics. When the agency that receives our returns spends a week telling us to check our locks, it's worth an afternoon.

The short version

  • Pick one afternoon before November and walk your own office the way a thief would.
  • Start with logins: unique passwords, a password manager, and multifactor authentication everywhere it's offered.
  • Update everything, then turn on automatic updates so you don't have to remember next time.
  • Read your written information security plan. If you don't have one, that's the first job.
  • Agree, as a firm, how you'll check any request to change bank details, payroll details or an email address.
  • Decide now who you call if something goes wrong, so nobody is searching for a phone number in March.

Why do this in October and not in May?

Because the threat doesn't wait for us to be rested. Extension season ends. Phishing season doesn't.

The IRS's own reminder this month says scammers keep using mail, email, text messages, social media and phone calls to impersonate trusted organizations. It also says something that should land with every one of us: tax professionals "should watch for phishing emails and other schemes designed to steal sensitive taxpayer data," and scammers "may pose as a prospective client or use a compromised email account."

Picture the second week of February. The phones haven't stopped. Organizers are coming back half-filled. A new client emails at 9:40 at night: "Referred by a friend. My W-2s are attached." You want that email. That's exactly why a fake one works.

The defenses you set up in October are the ones that are still standing when you're too busy to think.

There's a second reason. Security changes create friction. A new login step slows people down for a week while they get used to it. A week of friction in October costs almost nothing. The same week in February costs you returns.

Where do I start if I've never done a formal review?

Start with the doors people actually walk through: logins.

The IRS list for this month is short and plain. Use strong, unique passwords, and different ones for important accounts. Consider a password manager. Turn on multifactor authentication wherever it's available. None of that is new advice, which is exactly why it gets skipped. Everyone assumes it's already done.

So check, don't assume. Sit down with a list of every system that touches client information: email, file storage, your tax software, your e-signature service, your client portal, your bank, your payment processor, your phone system, the IRS's own services. For each one, answer three questions. Does every person have their own login, or is someone sharing? Is multifactor authentication on? When did anyone last remove access for a person who left?

That third question is the one worth lingering on. Your seasonal hire's login shouldn't outlive their last paycheck. When seasonal help leaves, check that their logins left too.

What about the machines themselves?

Update them. The IRS reminder says to install updates on computers, phones, tablets, apps, browsers and security software, and to turn on automatic updates when possible.

That second half matters more than the first. An update you install by hand in October is a good afternoon. An update that installs itself in February, while you're asleep, is a habit. Turn on the automatic setting wherever you can and you've moved one job off your own shoulders for the rest of the season.

While you're there, look at where your files sit and how they're backed up. The same reminder says to store digital tax records securely, encrypt sensitive files and back up important information. Ask yourself a blunt question: if the laptop under my desk died tonight, what would I lose? If the answer is "anything," that's tomorrow's job.

And one habit for the road. The IRS says to avoid using public Wi-Fi to access financial accounts, tax records or IRS online services. It's tempting to answer a client's urgent question from an airport or a coffee shop. Decide now what you'll do instead, whether that's a phone hotspot or simply waiting until you're back.

Do I really need a written security plan (WISP)?

Yes. And this one isn't a best practice; it's the law. The IRS states it plainly in this month's reminder: "Federal law requires tax and accounting professionals to create and maintain a WISP to protect client information." WISP stands for written information security plan.

If you've never written one, don't let the name scare you. A WISP is a document that says, in your firm's own words, what information you hold, who can reach it, how you protect it, and what you'll do when something goes wrong. The IRS publishes material to help small practices write one; search IRS.gov for "written information security plan."

If you already have one, open it. When did you last read it? Does it still describe the office you actually run, with the people and the systems you have today? A plan written three seasons ago for a different staff is a plan for a firm that no longer exists.

Here's a simple test. Hand the plan to the newest person in the office and ask them what they'd do if they clicked a bad link. If they can't answer from the document, the document isn't finished.

How do we handle requests to change bank details?

Slowly, and through a channel you already trust.

The IRS's October reminder tells businesses, payroll professionals and HR offices to stay alert for phishing, fake invoices and W-2 and payroll schemes, and says requests to change sensitive employee or payment information "should be verified through a trusted channel."

That applies inside a tax office too. A client emails to say their refund should go to a new account. A vendor writes to say they've changed banks. A "partner" asks someone junior to send a copy of every W-2 on file. Each one can be real. Each one can also be the most expensive email you open all year.

Write a rule and give it to everyone: no change to bank details, payment details or contact details happens on the strength of an email or a text alone. Call back on the number you already have. Never the one in the email. Then write the rule into your WISP, so it outlasts the person who remembered it.

What should we offer clients this year?

Protection they can turn on themselves. The IRS points taxpayers to an Identity Protection PIN, "a six-digit number that helps prevent someone else from filing a federal tax return using a taxpayer's Social Security number or individual taxpayer identification number."

You don't have to diagnose anyone's risk to mention it. A single line in your year-end letter does the job: here's what an Identity Protection PIN is, here's where to get one, and here's why it's worth five minutes. Clients remember the firm that told them before something happened. They also remember the firm that didn't.

The IRS's page "How to know it's the IRS" describes how it contacts people: normally by mail first, with emails or texts only when a taxpayer has opted in, and never through social media direct messages. That's worth putting in the letter too. A client who knows how the IRS really reaches them is a client who calls you before they pay a scammer.

Who do we call if something goes wrong?

Decide that today, not on the day.

The IRS says tax professionals who experience a data breach should report it as soon as possible to their stakeholder liaison. Find out who yours is and put the contact in the plan. Add your insurance carrier, whoever manages your computers, and the person in your firm who makes the call to clients.

Nobody wants to write the "what if we're breached" page. But the hour after you find out is the worst possible hour to start looking for phone numbers. Write the page while you're calm. Then hope you never need it.

The one-afternoon checklist

  1. List every system that touches client data, and who has a login to each.
  2. Turn on multifactor authentication on all of them, starting with email.
  3. Remove every login that belongs to someone who has left.
  4. Run updates on every device, then switch on automatic updates.
  5. Check the backups by restoring one file.
  6. Open the WISP, or start one.
  7. Write the bank-change rule and hand it to everyone.
  8. Put the stakeholder liaison, insurer and IT contact on one page.

Frequently asked questions

Is a WISP only for large firms?
No. The IRS's statement is that federal law requires tax and accounting professionals to create and maintain one. A solo practice needs a plan the same as a larger one; it will simply be shorter.

How long should this review take?
For a small office, an afternoon is a realistic start for the logins, the updates and a first read of the plan. Writing a plan from nothing takes longer. Start anyway, and finish it before the first client documents arrive.

What's the single most useful thing to do this week?
Turn on multifactor authentication on your email. Email is where clients send documents, where scammers pretend to be clients, and where a stolen password does the most damage.

Who do tax professionals report a data breach to?
The IRS says to report it as soon as possible to your IRS stakeholder liaison.

What is an IRS Identity Protection PIN?
In the IRS's words, "a six-digit number that helps prevent someone else from filing a federal tax return using a taxpayer's Social Security number or individual taxpayer identification number."

This is a good week for it. If you've run a review like this, what was the one thing you found that you didn't expect?

Yatin Miglani is an Enrolled Agent in Phoenix, Arizona, and the founder of Sophicor.

Sources referenced: IRS, IR-2026-124, "IRS announces 2026 Tax Professional Awareness Week, highlighting resources to help tax professionals prepare for the 2027 filing season" (Oct. 16, 2026), irs.gov.
IRS, IR-2026-119, "IRS reminder: Cybersecurity Awareness Month offers simple steps to protect tax data" (Oct. 2, 2026), irs.gov.
IRS, "How to know it's the IRS," irs.gov/help/how-to-know-its-the-irs.

— Yatin Miglani

Enrolled Agent · Phoenix, Arizona
Founder, Sophicor · sophicor.com