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:

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.

Heads up

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.

$3B+
Business email compromise scams, as reported by The Record

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:

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

  1. Open Outlook (or Word).
  2. Go to File > Account. That's where Microsoft says you can see the update channel Microsoft 365 Apps is configured for.
  3. Use the update option on that screen to check for and install updates, let it finish, and restart Outlook.
  4. Go back to File > Account and write down the channel, version and build.
  5. 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.
Tip

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:

ApproachGood forWhat you getWatch out for
Walk-around check (steps above)Small officesCertainty for each machineRemote and home laptops get missed
Ask staff to send a screenshot of File > AccountHybrid teamsFast, no tools neededPeople screenshot the wrong app or skip the update step
Device management reportsOffices already using device managementOne list of devices and versionsCheck that every device is enrolled in management
Your IT provider's patch dashboardOffices with a managed IT contractOngoing trackingAsk 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:

  1. 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.
  2. 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.
  3. 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:

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.

DayTaskWhoTime (our estimate)
MondayRun updates on all 16 machines; record channel and build in a shared sheetOffice manager1–2 hours
MondayChase the two laptops that are out with partners; get screenshots of File > AccountOffice manager15 minutes
TuesdayAdmin reviews spoof intelligence, honor-DMARC and first-contact tip in the anti-phishing policyIT provider or admin30 minutes
TuesdayFind out who controls DNS; recover registrar login if neededOwner0–2 hours (often the slow part)
WednesdayCheck SPF covers Microsoft 365, the tax software and the newsletter tool; publish DMARC at p=noneIT provider1 hour
Following weeksReview DMARC reports, fix any legit senders that fail, then step toward quarantine and rejectIT providerA 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

The one-page checklist

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