Email Security for Small Business: The 5 Layers to Put in Place

JD Sentz
November 13, 2026

Email security for small business comes down to five layers: a locked mailbox, a filter in front of it, a domain nobody else can send as, staff who know what to report, and a plan for the day a mailbox gets taken over anyway. This guide, for owners and office managers in Buffalo and Western New York, covers what each layer stops and what it doesn't.

JD Sentz, COO and CTO of 360 Business Solutions, puts the problem this way: "The crazy thing about these types of phishing emails is how good people can get at posing as businesses now."

What does email security for a small business include?

Email security for a small business means protecting two things: the mailboxes your staff use, and the domain your email comes from. It takes five layers. Multi-factor authentication on every mailbox. Filtering on incoming mail. SPF, DKIM and DMARC records for your domain. Staff training. And a written plan for when a mailbox is taken over. 360 Business Solutions is a managed IT and compliance company in Amherst, NY, that supports Microsoft 365 email and accounts for its clients. Call (716) 650-7200.

Layer 1: Lock every mailbox with MFA

Multi-factor authentication (MFA) means a password alone can't open a mailbox. CISA tells small businesses that passwords used alone "are no longer enough to keep accounts and systems safe." It says to require MFA on email, file storage and remote access, starting with admin accounts and the people who handle sensitive data.

The MFA method matters too. CISA rates a physical security key as the strongest protection against phishing. A code sent by text or email is the weakest, to use only when nothing stronger is available for that account.

When 360 takes over a new client, JD's answer: "Password hygiene is terrible." In his words, "Passwords are very weak, and there is no requirement to change them." MFA doesn't fix a weak password. It means a guessed or stolen one isn't enough by itself.

Layer 2: Filter mail before your staff see it

An email filter screens incoming mail before it lands in anyone's inbox. Asked what email security tools go on every client, JD's answer was short: "We use Proofpoint." So 360 puts Proofpoint email filtering on its clients.

A filter only sees mail coming in. It does nothing about someone sending mail as your domain to your customers, and that's the next layer. Our cyber insurance checklist covers how filtering shows up on an insurance application.

Layer 3: Secure your domain with SPF, DKIM and DMARC

Domain authentication is the layer JD ties convincing phishing back to. When a fake email seems to come from an address you'd expect, he says that is often "because people aren't taking the appropriate steps to secure their domains."

Securing a domain means publishing three DNS records.

SPF: who is allowed to send as you

An SPF record lists the services allowed to send email for your domain. Google's email sender guidelines say the record "should include all email senders for your domain." That means your Microsoft 365 or Google account, plus your invoicing software, newsletter tool and anything else that sends as you. Google says mail from senders left off the record is more likely to be marked as spam.

DKIM: a signature on every message

DKIM adds a digital signature to the mail your domain sends. Per Microsoft's email authentication guide, the receiving server uses it to check that the signed parts of the message, including the From address, weren't changed on the way.

DMARC: matching the address people actually see

DMARC closes a gap the other two leave open. Microsoft's guide explains that SPF doesn't check the domain in the From address, and DKIM doesn't care whether the signing domain matches it. DMARC checks that they match. It also tells receiving servers what to do with mail that fails. The current DMARC standard (RFC 9989) defines three policies:

  • none: you state no preference about failed mail
  • quarantine: you consider failed mail suspicious
  • reject: you consider any failure a clear sign someone is misusing your domain

A DMARC policy of none blocks nothing. It only gets you reports, so it's a fine place to start as long as someone reads them. Google's DMARC rollout advice is to start at none and watch the reports for at least a week. Then move to quarantine on a small share of your mail, and raise it step by step. Reject is the last step, because rejected mail is never delivered. Our own domain, businesswny.com, is set to reject. Google's sender guidelines also recommend DMARC reports, because they help you spot senders that may be impersonating your domain.

Gmail and Yahoo already expect this

Since February 1, 2024, Google has required every sender to Gmail personal accounts to set up SPF or DKIM. Anyone sending more than 5,000 messages a day to Gmail needs SPF, DKIM and DMARC, with a policy that can be set to none. Yahoo's sender requirements follow the same pattern: SPF or DKIM from every sender, and SPF, DKIM and DMARC from bulk senders. Google recommends all three for every domain, and so do we.

What DMARC won't stop

DMARC protects your exact domain. It doesn't stop a lookalike. Microsoft's guide describes an attacker registering a different domain, setting up SPF and DKIM on it, and passing those checks. CISA also warns that phishing may come from known contacts whose accounts were compromised. Those messages are real mail from a real domain, which is why the other four layers still matter.

Layer 4: Train staff to slow down and report

Staff training catches what gets past the filter. JD's view: "people aren't taking the awareness level that they need when opening and clicking those things."

CISA's guidance on teaching employees to avoid phishing makes three practical points:

  • Once-a-year training isn't enough. Reinforce it regularly.
  • Check an unexpected request by calling a number you look up yourself, not one in the message.
  • Make sure every employee knows who to report a suspicious email to, and how.

Train for the report as much as for the click. The person who clicks and tells someone right away did their job.

Layer 5: Know what to do if a mailbox is taken over

A taken-over mailbox is one an attacker can sign in to and use as if they were your employee. Microsoft's guide on responding to a compromised email account lists the common signs: rules that forward mail to unknown addresses, odd messages in Sent Items or Deleted Items, and frequent password changes or unexplained lockouts. Its steps for regaining control:

  1. Call whoever handles your IT, not by email. Microsoft warns the attacker could have access to the mailbox.
  2. Disable the account or reset the password. Microsoft says to block access as soon as possible, and never to send the new password to the user by email.
  3. Sign the account out everywhere. Microsoft says to revoke all active sign-in sessions for the user.
  4. Remove unknown MFA devices. Microsoft says to remove any devices an attacker added and any MFA methods you don't recognize.
  5. Check inbox rules and forwarding. Microsoft says to look for rules that redirect or forward mail without the user's knowledge, and remove any suspicious forwarding.
  6. Review admin roles and connected apps. Microsoft's guide also has you check the apps the user gave consent to and the admin roles on the account.

Write these steps down, with names and phone numbers, somewhere that doesn't depend on your email.

Questions to ask your IT provider about email security

  • Is MFA on for every mailbox, including mine? Which method?
  • What filters our incoming mail?
  • Do we have SPF, DKIM and DMARC records, and what is our DMARC policy?
  • Is every service that sends as us included, like invoicing and newsletters?
  • Who reads our DMARC reports?
  • When did staff last get phishing training, and who do they report to?
  • If a mailbox gets taken over tonight, who does what?

If you can't answer those for your own office, our compliance and security team can go through your email setup with you. Call (716) 650-7200.

Small business email security questions

Does a small business need DMARC?

If you send more than 5,000 messages a day to Gmail, yes, Google requires it, and Yahoo requires it from bulk senders. Below that, Google still recommends SPF, DKIM and DMARC for every domain. DMARC is also what lets receiving servers spot mail that only pretends to come from your domain.

Does MFA stop phishing?

MFA stops a stolen password from being enough on its own. CISA says some methods are much stronger than others. A physical security key gives the best protection against phishing, and a text or email code gives the weakest.

Does email security count for compliance or cyber insurance?

Often, yes. If your firm is covered by the FTC Safeguards Rule, it requires multi-factor authentication for anyone accessing an information system, unless your Qualified Individual approves an equivalent control in writing. Our FTC Safeguards Rule checklist covers the rest of that rule, and insurers ask about MFA too.

This post explains common email security settings for small businesses. It isn't legal advice. Talk to your compliance advisor about the rules that apply to your firm.

‍

Ready to Talk?

Your first conversation is on us.

Free 30-Minute Technology Assessment

  • Review your current IT setup
  • Identify compliance gaps and quick wins
  • Explore AI & automation opportunities
  • No pitch. No pressure. Just clarity.
Loading booking calendar...