Short answer: our advice is to get every office PC onto the newest Microsoft 365 Apps build for its update channel, then review two mail protections: the spoofing settings in your Microsoft 365 anti-phishing policy, and a DMARC record for your own domain. CISA has added six new vulnerabilities to its Known Exploited Vulnerabilities (KEV) Catalog based on evidence of active exploitation. Checking the update is a quick job per computer. The mail settings take longer, but both are worth starting this week, not next quarter.
This post is for the owner or office manager of a clinic, law firm, accounting practice, contractor or agency who wants a plain checklist for the office email. It doesn't replace your IT provider; it gives you the right questions to ask them.
What actually happened, in plain words
CISA's catalog describes the Outlook flaw this way: Microsoft Office Outlook "contains a missing user interaction for potentially unsafe action vulnerability that allows an unauthorized attacker to perform spoofing over a network".
That's a mouthful, so here's how to think about it in office language:
- Microsoft's own definition, for email: spoofing is when the From address that email clients show doesn't match the domain of the email source.
- How the attack starts. As BleepingComputer reported, an unauthenticated attacker could send a specially crafted message file and convince a user to open it in an affected version of Microsoft Outlook. In other words, the attacker doesn't start with a login to your systems; they start with something your staff are tempted to open.
Put together, in our reading: a message or file that looks more trustworthy than it should. That's exactly the kind of setup invoice fraud and fake "change our bank details" requests rely on, so it's worth taking seriously even if you've never been targeted before.
Don't wait for a suspicious-looking email to show up before acting. Convincing fakes work *because* they don't look suspicious. Our recommendation is the update plus the settings below, not just "be careful."
Why an Orange County office should care this week
If your office runs its day out of the inbox, your email app is probably open on every front-desk and back-office computer. Money moves through email: invoices, wire instructions, payroll changes, settlement statements, vendor bank-detail updates. Anything that makes a fake sender look more believable is a direct threat to that money.
That's why spoofing matters more than it sounds. Business email compromise is the "your vendor has a new bank account" or "the owner needs gift cards today" email, and it depends almost entirely on the recipient believing who the message is from. The Record reported business email compromise scams at over $3 billion. Microsoft says DMARC validation helps prevent spoofed senders that are used in business email compromise, ransomware and other phishing attacks, and you enable it by creating a TXT record in DNS at your domain registrar or DNS host.
Does the "federal deadline" apply to you?
You may see headlines about CISA deadlines. The CISA directive text says it applies to all software and hardware found on federal information systems, whether managed on agency premises or hosted by third parties on an agency's behalf. In our reading, a private dental office in Mission Viejo isn't bound by it.
But that doesn't mean you can ignore the list. CISA says organizations should use the KEV catalog as an input to their vulnerability management prioritization framework. It also strongly recommends that all organizations review and monitor the catalog and prioritize remediation of listed vulnerabilities to reduce the likelihood of compromise by known threat actors. Our take: if it's on the KEV list and you run the software, treat it as this week's job.
Step 1: Confirm every office PC has the update
The catch is that "gets updates" and "is updated" aren't the same thing. PCs that stay asleep, sit in a closet, or haven't restarted Outlook in a while can lag behind.
Here's what Microsoft's update channel overview says that matters for you:
- Security updates for Current Channel, if needed, are released on the second Tuesday of the month.
- Security updates are cumulative: the most current Current Channel release includes the security updates from previous releases. So you don't have to install anything in order. You just need the latest one.
- Don't assume every device uses the same update channel, because different devices, even the same user's, can be set up differently without anyone noticing.
Microsoft's advice is simple: always update to the most current version and build available for your update channel to have the most up-to-date security and non-security updates. For this specific CVE, ask your IT provider to confirm against Microsoft's security guidance which builds include the fix.
How to check one PC
- Open Outlook (or Word).
- Go to File > Account. That's where Microsoft says you can see the update channel Microsoft 365 Apps is configured for.
- Use the update option on that screen to check for and install updates, let it finish, and restart Outlook.
- Go back to File > Account and write down the channel, version and build.
- Compare it with the latest build listed for that channel on the official update history page. If yours matches the newest entry for your channel, you're done with that machine.
If one PC shows a different channel than the rest, flag it and ask your IT provider why. Check any odd-one-out machine first, since a PC that doesn't match the rest of your fleet is easy to overlook.
How to check the whole office
For a very small office, walking around with a clipboard works. As you grow, it gets old fast. Here are the options we'd consider, from simplest to most robust:
| Approach | Good for | What you get | Watch out for |
|---|---|---|---|
| Walk-around check (steps above) | Small offices | Certainty for each machine | Remote and home laptops get missed |
| Ask staff to send a screenshot of File > Account | Hybrid teams | Fast, no tools needed | People screenshot the wrong app or skip the update step |
| Device management reports | Offices already using device management | One list of devices and versions | Check that every device is enrolled in management |
| Your IT provider's patch dashboard | Offices with a managed IT contract | Ongoing tracking | Ask them to confirm Office apps specifically, not just Windows |
Whatever you pick, we suggest ending with a single list: every PC, its channel, its build, a check mark. Keep it for the next KEV entry.
Step 2: The two mail settings to switch on
Patching addresses a specific bug. The two settings below are about making spoofing tricks in general less effective, whether they ride on a software flaw or just on a convincing fake sender.
Setting 1: Review your anti-phishing policy in Microsoft 365
"On by default" isn't the same as "still on," though. Have your admin open the policy and check three things:
- Enable spoof intelligence. Microsoft recommends leaving it turned on. If someone switched it off to stop a vendor's newsletter going to junk, that's the wrong fix in our view. Allow that one sender instead.
- Honor DMARC record policy when the message is detected as spoof: this setting turns on honoring the sender's DMARC policy for explicit email authentication failures. This setting turns on honoring the sender's DMARC policy for explicit email authentication failures. In anti-phishing policies you can control whether p=quarantine or p=reject values in sender DMARC policies are honored. In plain terms: when a domain like your bank's says "treat fakes of us strictly," this is where you decide whether your mail system listens. Our suggestion is to have your admin enable it unless they have a specific reason not to.
- Show first contact safety tip: this setting is available in anti-phishing policies for all cloud mailboxes and in Defender for Office 365 anti-phishing policies. According to Microsoft, the tip is shown to recipients the first time they get a message from a sender, or when they don't often get messages from that sender. It's available in anti-phishing policies for all cloud mailboxes and in Defender for Office 365 anti-phishing policies, and has no dependency on spoof intelligence or impersonation protection settings.
Setting 2: Publish a DMARC record for your own domain
The anti-phishing settings above protect your staff from fakes coming in. Think of DMARC as protecting your clients and vendors from fakes that claim to come from you.
Here are the points from the official DMARC setup guide we'd want you to know:
- You enable DMARC for a domain by creating a TXT record in DNS.
- Microsoft 365 has no admin portals or PowerShell cmdlets to manage DMARC TXT records in your custom domains; you create the record at your domain registrar or DNS hosting service. That's whichever company your web person used to register or host your domain.
- If you haven't already, you need to configure SPF for all custom domains and subdomains you use for email.
- Microsoft recommends a gradual rollout. The goal is a p=reject policy for all of your custom domains and subdomains.
- Use a specific mailbox or Microsoft 365 Group to receive DMARC reports, not a user's mailbox.
Here's how we'd suggest a starter record looks (ask your IT person to swap in your domain and a reports mailbox set aside for this):
Host/Name: _dmarc
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@yourfirm.com
Starting gently matters. Microsoft notes you need to test and verify along the way so destination email systems don't reject good mail because of unintentional DMARC failures. If your billing software, your website's contact form, or your payroll service sends mail "as" your domain, the monitoring phase shows you who sends on your behalf before you start blocking anything.
A worked example
Hypothetical: a 14-person accounting office in Irvine. Outlook runs on 12 desktops and 4 laptops, mail is on Microsoft 365, and the domain was registered by a former office manager.
| Day | Task | Who | Time (our estimate) |
|---|---|---|---|
| Monday | Run updates on all 16 machines; record channel and build in a shared sheet | Office manager | 1–2 hours |
| Monday | Chase the two laptops that are out with partners; get screenshots of File > Account | Office manager | 15 minutes |
| Tuesday | Admin reviews spoof intelligence, honor-DMARC and first-contact tip in the anti-phishing policy | IT provider or admin | 30 minutes |
| Tuesday | Find out who controls DNS; recover registrar login if needed | Owner | 0–2 hours (often the slow part) |
| Wednesday | Check SPF covers Microsoft 365, the tax software and the newsletter tool; publish DMARC at p=none | IT provider | 1 hour |
| Following weeks | Review DMARC reports, fix any legit senders that fail, then step toward quarantine and reject | IT provider | A few short check-ins |
In this example, the riskiest delay isn't technical: nobody remembers the registrar password. If that sounds familiar, start there today.
Pitfalls we see
- Assuming Windows updates cover Outlook. Don't rely on one screen for everything. Check Outlook itself, in File > Account.
- Checking just the computers in the office. Laptops at home, the reception PC that's always on but never restarted, and the owner's personal machine with Outlook installed all count.
- Jumping DMARC straight to reject. Microsoft's guidance is a gradual approach. Monitor first.
- Turning off spoof protection to "fix" a missing email. Allow the specific sender; don't lower the guard for everyone.
- Thinking the patch ends the job. The real risk is trust in what a message appears to be. Our advice: keep a phone call-back rule for any change to bank details or wire instructions, no matter how real the email looks.
The one-page checklist
- [ ] Every PC and laptop: open an app such as Word, go to File > Account, and check the update channel, version and build under Product Information; install updates, restart, and record them
- [ ] Builds match the latest on Microsoft's update history page for your channel
- [ ] Any odd-channel machines flagged and discussed with your IT provider
- [ ] Anti-phishing policy: spoof intelligence left on, as Microsoft recommends
- [ ] Confirm who can log in to your domain registrar, and save that login in your password manager
- [ ] SPF covers every service that sends as your domain
- [ ] DMARC published at p=none, with a dedicated report mailbox
- [ ] Calendar reminder to review reports and move toward p=reject
- [ ] Staff told: call back on a known number before changing any payment details
What we'd do
If we were sitting in your office this week, we'd do the update check first, because it's the most direct step you control. Then the anti-phishing settings, because that's a short session in the admin portal. DMARC comes last because it needs DNS access and some time watching reports. In our view, much of this may come down to settings you already have rather than new software, but ask your IT provider to confirm what your plan includes.
Where we add value is turning this into a repeatable routine rather than a one-off scramble. An inventory sheet that keeps itself current, a regular check against the KEV catalog for the software you actually run, and an alert when a PC falls behind are the kind of small jobs we build with AI automation for small business. If you'd rather talk it through first, we'd suggest an AI and security consultation to map what you run, what's exposed and what to automate. We work with offices across Orange County.
Next step
Start with the update check today. If you hit a PC that won't update, a DNS login nobody can find, or you just want a second set of eyes on your anti-phishing policy, book a Free Automation Audit. We'll go through your Microsoft 365 setup with you and leave you with a short, prioritized list. No hard sell.
Sources
- CISA — CISA Adds Six Known Exploited Vulnerabilities to Catalog (November 10, 2026)
- CISA — Known Exploited Vulnerabilities Catalog (November 10, 2026)
- CISA — BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities (June 10, 2026)
- CISA — Known Exploited Vulnerabilities Catalog (about) (November 10, 2026)
- Microsoft Learn — Anti-phishing policies in Microsoft 365 (August 21, 2026)
- Microsoft Learn — Set up DMARC to validate email in Microsoft 365 (July 17, 2026)
- Microsoft Learn — Overview of update channels for Microsoft 365 Apps (June 23, 2026)
- BleepingComputer — Microsoft November 2026 Patch Tuesday fixes 1,235 flaws, Outlook zero-day (November 10, 2026)
- The Record from Recorded Future News — Cyber fraud surges to $17 billion, FBI IC3 report (April 6, 2026)