Skip to content

Safe as a habit, not a project

Part 07 of 7

On this page

Keeping email secure after a cleanup takes one named owner and a few dates on the calendar. For a six-person firm that’s about 20 minutes a month, 15 minutes a quarter and one morning a year. Most of what goes wrong in a mailbox doesn’t arrive as an attack. It builds up slowly, every time someone joins, leaves, buys a phone or tries an app. A habit catches that at the pace it happens.

Maya Okafor’s firm worked this out on a Wednesday. Her Columbus practice keeps the books and files the taxes for small businesses, with six people on staff. Over the past two weeks her account was broken into, the firm locked every door it could find, and on Monday a phishing email got past Google and past a careful person. It didn’t get past the passkey. Everything that held on Monday had been set up the week before.

This last part of the series is how she made sure it would still hold in March. It covers why a secure mailbox drifts, what the FTC and the IRS expect a tax practice to review after the first year, who owns it, and what went on the calendar. If you’ve just finished a week like Maya’s, you’ve done the hard part. What’s left is small, and it repeats.

Point is behind this series, and the last section of this page names the key an assistant like it holds. You’ll find what Point does on a separate page. The rest of this page holds whatever app reads your mail.

Two years of small changes

Maya started Wednesday with the one-page record from Friday and a fresh legal pad. On the left she listed everything the week had found. On the right she wrote down how each one got there.

  • Rachel’s delegate access. Rachel left in 2023. Someone changed her password, and nobody removed her from Maya’s mailbox.
  • Contact Sync. An app from around 2022 that could copy every client’s contact details. Nobody could say who added it.
  • Ben’s old laptop. He replaced it in the spring. It was still signed in, in a closet at home.
  • Last season’s preparer. Her account was still active in October.
  • The info@ password. Three people shared it, because the mailbox had been set up for one.
  • Maya’s recovery address. A personal account she hadn’t opened in years.

Not one of these was an attack. Each was an ordinary change with no follow-up. Someone left, a phone got replaced, a trial ended, the firm grew. The forwarding rule was the only thing an outsider set up, and it used a password that had been reused for years.

So the firm hadn’t been careless once. It had been busy for two years. That’s the speed a mailbox drifts at: the speed the firm changes. A week of cleanup resets the clock. It doesn’t stop it.

Maya wrote one line at the bottom of the page. “Whatever we do has to run at the speed of people leaving and phones dying.”

What the rules expect after the first week

A tax practice has a second reason to keep checking. The IRS says it plainly in its August 2026 reminder to tax professionals. Under the Gramm-Leach-Bliley Act, “tax and accounting professionals are considered financial institutions and must implement a data security plan.” Then it says what the plan is for:

Tax professionals are legally required to have a written, accessible plan and should review, test, and update it regularly.

The rule behind that is the FTC’s Safeguards Rule, 16 CFR 314.4. Who still has a key already covered why it asks a firm to know who can reach client data. Maya read it again for the parts that repeat. Four of them speak to a firm’s ongoing habits:

SectionWhat it saysWhat it meant for Maya’s firm
314.4(a)“Designate a qualified individual responsible for overseeing and implementing your information security program”Somebody has to own this by name
314.4(c)(1)“Implementing and periodically reviewing access controls”The Friday list of keys gets checked again, on a schedule
314.4(e)(1)“Security awareness training that is updated as necessary to reflect risks identified by the risk assessment”Monday’s phishing email becomes part of what everyone learns
314.4(g)“Evaluate and adjust your information security program” after testing, monitoring and “material changes to your operations”A new hire, a departure or a new app is a reason to look again

Small firms get some relief. Under 16 CFR 314.6, a business holding information on fewer than 5,000 consumers is exempt from four parts of the rule. Those are the written risk assessment, the annual penetration testing, the written incident response plan and the annual report to a board. Maya’s firm has a few hundred clients, so those four don’t apply. The four in the table still do.

The IRS template fills in the timing. Publication 5708 is a sample written security plan for tax and accounting practices. Its sample plan includes “reviewing the scope of the security measures in the WISP at least annually or whenever there is a material change in our business practices.” It also includes “an annual training session for all owners, managers, employees, and independent contractors.” On people leaving, it adds one line that could have been written about Rachel:

Having a systematic process for closing down user rights is just as important as granting them.

So the law and the IRS describe the same shape Maya had reached on her own. One named person, a yearly review, training that keeps up, and a fresh look whenever the firm changes.

Giving it one owner

Maya had been the one doing this all week, and she was the wrong person to keep it. She also prepares returns, and she’d be buried by February. A job owned by the busiest person in the firm is a job with no owner in tax season.

Priya, the office manager, was the obvious choice. She’d found the copier’s app password and turned info@ into a group. She already sets up every new hire’s laptop. Maya asked her at 9:30, and Priya said yes on one condition. “Put it on the calendar, so it isn’t me remembering.”

Maya named Priya as the firm’s qualified individual in the written plan. She kept her own name beside it as the owner Priya reports to. Then they sat down to decide what actually needed a date.

What went on the calendar

They had three rules for what made the calendar. Each check had to fit in a short slot. Each had to have one name next to it. And each had to point at something the firm had actually found this month, rather than at a list from somewhere else.

They ended up with five entries:

WhenWhat gets looked atWhoHow long
The day someone joins or leavesTheir account, any delegate access, which groups they’re in, and the firm’s list of who can reach client dataPriya15 minutes
The first Monday of each monthApps connected across the firm, forwarding rules on every mailbox, and any sign-in Google flaggedPriya20 minutes
The first staff meeting of each quarterEveryone opens Google’s Security Checkup on their own account. Then the strangest email of the quarter gets read out.Everyone15 minutes
Mid-October, when PTIN renewal opensThe written plan, the one-page record, recovery phones and addresses, and the phone numbers the firm relies on in a hurryMaya and PriyaOne morning
The first week of JanuarySeasonal staff get accounts with passkeys, and an end date goes on the calendar the same dayPriyaOne hour

The October slot was Priya’s idea. The IRS says every PTIN expires on December 31, and renewal season opens in mid-October. Every preparer in the firm already has IRS paperwork open that week. Adding a morning to it costs less than inventing a new date. This year it’s two weeks away, so the firm’s first annual review is almost here.

The monthly check is the one that does the most work. In a month with no changes, it’s 20 minutes of finding nothing, and that’s the result Priya hopes for. A new app on the list is just a question. Priya asks whoever added it what it’s for, and it either stays with a name next to it or goes.

The quarterly one is short on purpose. Google’s Security Checkup lets each person “check recent security events” on their own account. Six people do it at once, at the table, and anyone who sees something odd says so. It takes less time than the coffee.

The how of each check already lives in the earlier parts of this series. The account underneath covers sign-ins and recovery. Who still has a key covers apps, devices, delegates and forwarding. The calendar only says when.

The day someone leaves

One entry has no date, and it’s the one that would have stopped Rachel.

Joining and leaving are when access changes most. The firm hires a seasonal preparer every January and loses one every April. Under the old way, setting someone up was urgent and taking them out was a favor somebody might remember.

Now the two happen as a pair. When Priya creates an account, she puts the end on the calendar in the same sitting. For a seasonal preparer that’s the last Friday in April. For a permanent hire it’s a line in the firm’s list with a blank date beside it. When someone leaves, Priya works through that person’s line in one go. Their account, their place in the info@ group, any mailbox they could open as a delegate, and any app they connected for the firm.

The firm’s list follows the shape of Publication 5708: name, role, what they can reach, the date access was given, and the date it ended. Rachel’s line, written now, would have read “granted 2021, ended 2026.” The gap between her leaving and that last date is the problem the list exists to close.

Keeping the walk-over

The passkey stopped Monday’s phishing email from opening anything. Jess was what stopped it from going further. She noticed something was wrong, she stood up, and she walked to Maya’s office within four minutes. The one that got through is that morning.

Maya wanted that walk to be just as fast in March, from someone with fifty returns on their desk. She didn’t think a yearly slideshow would do it. A habit would, if it stayed recent.

So the quarterly meeting ends on a real email. Priya keeps the strangest one each quarter, whether someone clicked it or not. Then she reads it out and asks what gave it away. This quarter it was Monday’s, and Jess told the story herself. Next quarter it might be an invoice from a vendor nobody uses.

Each time, Maya says the same sentence: anyone who clicks something odd walks over, and nobody’s in trouble for it. Saying it four times a year is the training. The FTC asks for training “updated as necessary to reflect risks.” A real email from your own inbox is about as up to date as it gets.

Once a year, in the October morning, everyone also signs a one-page note that they’ve read the firm’s plan. Publication 5708 suggests that kind of certification. It takes two minutes. It also reminds the firm the plan exists.

The key an assistant holds

Priya raised the last question while they were filling in the monthly entry. Maya had been reading about AI assistants for the inbox. If the firm ever connected one, where would it go on the list?

“Same place as the e-signature service,” Maya said. An assistant that reads your mail holds a key to the mailbox, whichever one it is. So she added a line to the first-Monday entry: any connected assistant, checked by name in the third-party access list with every other app.

For Point, that key is a grant made at Google’s own sign-in page, and where your email credentials are kept shows exactly what it holds.

The invite

At 11:15, Priya sent the first recurring invite. It went to Maya and herself, every first Monday at 9:00, and it read:

Mailbox check, 20 minutes. Connected apps across the firm. Forwarding rules on every mailbox. Any sign-in Google flagged. Anything new gets a name next to it or goes. If you find nothing, that’s the job done.

Maya accepted it and closed the legal pad. Two weeks ago, the firm’s security had been a password and a lot of hope. This week it was a list of keys, a person who owns them and a date when somebody looks again.

The first invite fires in less than a month. The October review comes sooner, in the same week the PTIN renewals open. And Dale Huang will email in January, the way he always does, with a question about his books. When he does, Maya will open it the way she used to, before any of this. That’s the point of a habit.

If you’re on the Tuesday morning of your own scare, this series starts with the scare.

Ready for a calmer inbox?

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.

Private beta

What you're joining

It runs on the mail you have

Point sits on top of Gmail or Outlook. Your address, your history and your contacts stay exactly as they are, so there is nothing to migrate.

You set how much Point does

Out of the box everything waits for your review, replies included. You hand over only what you trust, one kind of work at a time.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.