A convincing signature, a sense of urgency, and a “new” bank account. What could go wrong?
One phone call to a number you already trust can stop a fake executive email from emptying your bank account.
Welcome to Step 7 of our series on how to get breached. This week’s technique requires no hacking skill from you and very little from the criminal. Simply receive an email that looks like it came from the boss, skip the questions, and send the wire. For bonus points, make sure the message says it’s confidential, urgent, and sent from a phone. Those aren’t red flags. They’re the script.
Why This “Advice” Is So Expensive
Business email compromise (BEC) happens when a criminal poses as someone you trust, such as an executive, a vendor, or a client, to redirect your money. The FBI’s 2025 Internet Crime Report ranked BEC the second-costliest crime type, with $3.04 billion lost in 2025, up from $2.77 billion the year before. Wire transfers made up the bulk of BEC losses. Those are only the cases that were reported.
BEC usually arrives in two forms:
Fake executive requests: a message from a hijacked or lookalike account asking an employee to send a payment quickly and quietly.
Payment-change fraud: a “vendor” announces new banking details. The email may come from a real vendor mailbox the criminal has taken over, so the conversation history looks perfectly normal.
The FBI now tracks AI-related complaints separately, because polished, error-free fraud emails are easier to produce than ever. The weak point is rarely your firewall. It’s a payment process with no checkpoint.
A Hypothetical Scenario
Consider a made-up 30-person distribution company. On a Friday afternoon, the bookkeeper receives an email from “the owner,” who is traveling and wants $42,000 sent to a new supplier today. An hour later, a longtime vendor “updates” its bank account on the next invoice. Both messages are polite, plausible, and slightly urgent. Nobody calls anyone. Both get paid, and by Monday the money has moved on.
What to Do Instead
For the business owner:
Write a one-page rule. No payment, new payee, or bank detail change is approved by email alone.
Require call-back verification. Call the person at a number already in your records, never a number in the message. Be careful with inbound calls too. Fraudsters may call first, knowing a callback is part of your controls.
Require two approvals for new payees, banking changes, and payments above a set amount.
Add a waiting period. Mandatory cooling-off periods before changes take effect give verification time to work.
Give staff permission to pause. Tell them in writing that no one is penalized for verifying a request, even one that appears to come from you.
Plan for the worst day. Call your bank immediately to request a recall, then report at ic3.gov. Speed matters.
For your IT team or provider:
Enforce multifactor authentication on every mailbox and turn off legacy sign-in methods.
Alert on new inbox rules and automatic forwarding, common signs of a hijacked mailbox.
Set up SPF, DKIM, and DMARC, and flag external email that uses internal names.
Monitor sign-in logs for unusual locations and watch for lookalike domains.
Questions Your Clients May Ask
Why did you call me to confirm a change to my invoice? Because changes to payment details are the most common way criminals redirect money. A two-minute call protects both of us.
How will I know if an email from you about new bank details is real? We never change payment instructions by email alone. Any change is confirmed by phone, using a number we already have on file.
What happens if we already sent money to the wrong account? Call your bank right away and ask for a recall, then report it to the FBI at ic3.gov. Our case study on stopping a business email compromise shows why fast action matters.
Doesn’t verification slow down payments? By minutes, not days. Compared with the cost of one misdirected wire, it’s a bargain.
How Farmhouse Networking Can Help
BEC is mostly a procedure problem, which is why technology alone won’t fix it. We help you close the gap:
Payment-verification policy help: We work with you to write a practical call-back procedure and approval workflow your team will actually follow.
Security awareness training: We train your staff to recognize executive impersonation and payment-change requests, and to feel comfortable saying “let me verify that first.”
Is Your Payment Process Ready for a Polite Stranger Using the Boss’s Name?
Email support@farmhousenetworking.com for a free breach-readiness review. We’ll check your email configuration for the gaps criminals count on, walk through how your team handles payment changes, and send you a one-page summary of what we find.
Next week: How to Get Breached, Step 8: Leave the Default Password on the Printer (and the Cameras, and the Router)
Email attachments, “anyone with the link,” and other ways to hand your data to strangers
One file, two paths: loose in an inbox or locked inside a secure client portal.
Meet Dale, the hypothetical owner of a 25-person contracting company. Dale has a simple file-sharing philosophy: whatever is fastest wins. Signed contracts go out as email attachments. When a bank statement bounced because the file was too big, Dale clicked “Anyone with the link can view,” pasted the URL into an email, and got back to work.
That link never expired. It has since been forwarded twice, saved in a former employee’s inbox, and pasted into a vendor’s project notes. Dale has no idea who can open it. Neither does anyone else.
Why Fast File Sharing Gets Expensive
Every time a sensitive file moves, it creates another copy you do not control. Verizon’s annual breach report has found for years that the human element is involved in most breaches, and that includes plain mistakes like sending data to the wrong person. Convenience is where most of those mistakes start.
Three methods cause most of the trouble:
Email attachments. Encryption in transit protects a message on its way, but the attachment still lives in every mailbox, backup, and phone it touches. One autocomplete error or one compromised inbox exposes all of it.
“Anyone with the link” sharing. No sign-in is required. Whoever holds the URL can open the file, and the link can work indefinitely unless someone sets an expiration.
Secure client portals. This is the fix. A portal requires sign-in, controls who sees what, can expire access, and keeps a record of who opened which file.
Action Steps for Owners and IT
Owner decisions
Define what counts as sensitive: Social Security numbers, bank details, contracts, credentials, and anything covered by a regulation or client agreement.
Approve a one-page file-sharing policy that names the right channel for each type of file.
Assign someone to review external sharing every quarter.
IT tasks
Restrict “anyone” links, set the default link type to specific people, and add automatic expiration to any external links you allow.
Audit existing shared links and external access, then revoke anything old, unused, or unknown.
Turn on data loss prevention and sensitivity labels so files containing SSNs or account numbers are flagged or blocked before they leave.
Use encrypted email for one-off sends and a secure portal for recurring exchanges.
Require multifactor authentication on every account that can share files.
Set alerts for unusual activity, such as mass downloads or sudden spikes in external sharing.
Remove access and review shares whenever someone leaves.
Questions Your Clients May Ask
Why can’t you just email me the contract? For non-sensitive material, we can. For anything with personal or financial details, attachments get copied to places we cannot control. The secure link takes about a minute and keeps your information in one protected place.
Why did my link expire? On purpose. A link that works forever eventually ends up somewhere it should not. We can send you a new one.
How do I know the portal link is really from you? We will never ask for a password by email or text. If anything looks off, call us at the number on our website before you click.
What happens to my files after the project ends? Access is removed, and files are kept or deleted on a schedule we set in advance.
How Farmhouse Networking Can Help
Farmhouse Networking works with owners to close these gaps without slowing the team down:
Link-sharing lockdown: we disable or restrict “anyone” links and set default expiration.
Sharing audit: we find and clean up old links and external access.
DLP and labeling: we configure policies that flag or block sensitive data before it leaves.
Encrypted email and portal guidance: we set up encrypted email and help you choose a portal for recurring exchanges.
Monitoring: our Wazuh-based alerting watches for mass downloads and unusual sharing.
Find Out What Dale Never Did
You probably have a few “anyone with the link” files out there right now. Email support@farmhousenetworking.com for a free breach-readiness review. We perform it in-house, covering a policy review, basic penetration testing, and a network inventory, and you receive written findings in about a week.
Next week: How to Get Breached, Step 7: Wire the Money. The Boss Emailed, So It’s Fine.
Why attackers love MFA fatigue, and how to make multi-factor authentication stronger without driving your team crazy
MFA fatigue attacks count on someone tapping Approve just to make the prompts stop. Number matching, phishing-resistant MFA, and conditional access take that option away.
Welcome back to our guide to doing security wrong. You’re reusing passwords and clicking every link in your inbox. Nice work. This week’s tip is the easiest yet: turn off multi-factor authentication. All those “Is this you signing in?” prompts slow everyone down. And if you can’t turn it off, tap Approve on every one. Your phone stops buzzing, and that’s what matters, right?
Here’s what that looks like in practice.
A Hypothetical Late-Night Buzz
Picture the office manager at a 25-person company. At 11:40 p.m., her phone lights up with a sign-in request. She taps Deny. It comes back. And again. Around the fifteenth prompt, she approves one just to make it stop and goes back to sleep.
The person on the other end already had her password from a list of stolen credentials. By morning, they’ve read two years of email, set up a rule that quietly forwards invoices to an outside address, and sent customers “updated” payment instructions. Nobody broke any encryption. One tired person approved one prompt.
Why MFA Still Matters, and Where It Falls Short
MFA works because a stolen password alone isn’t enough to get in. That’s why attackers now focus on getting around it:
MFA fatigue (push bombing). The attacker already has the password and floods the user with approval requests, hoping one gets accepted out of frustration. Some follow up with a call or text pretending to be IT.
Phishing proxies. A fake login page passes your password and your six-digit code to the real site in real time. Codes and simple push approvals can both be captured this way.
Help desk tricks. An attacker calls in as an employee who “got a new phone” and asks for MFA to be reset.
The Cybersecurity and Infrastructure Security Agency (CISA) calls phishing-resistant MFA, such as passkeys and FIDO2 security keys, the gold standard. For push notifications, CISA recommends number matching as an interim step: the user types a number shown on the login screen into their app before access is granted.
Conditional access ties it together. Instead of treating every sign-in the same, it sets rules for who can sign in, from where, on which devices, and when to ask for stronger proof. Done well, it means fewer prompts on trusted company devices and tougher checks only when something looks off.
Action Steps for Business Owners and IT
Require MFA on every account. Email, Microsoft 365 or Google Workspace, remote access, payroll, banking, accounting, and line-of-business apps. That includes the owner and every admin. Especially the owner and every admin.
Replace simple Approve/Deny prompts. Use an authenticator app with number matching enabled, and phase out text message codes wherever possible.
Give high-risk users phishing-resistant MFA. Owners, admins, and anyone who moves money should use passkeys or FIDO2 security keys.
Turn on Conditional Access. For most small businesses on Microsoft 365, that means Business Premium. Block legacy sign-in methods that skip MFA, block countries you don’t do business in, require company-managed devices for sensitive data, and require stronger sign-in for admin roles and risky logins.
Lock down MFA resets. Verify identity before anyone’s MFA method is changed, and alert when a new device is registered.
Watch for warning signs. Repeated denied prompts, new MFA methods, logins from unexpected locations, and new mailbox forwarding rules should trigger an alert someone actually reads.
Teach one simple rule. If you didn’t start the sign-in, deny it and report it right away. Keep it no-blame, so an employee who approved something by mistake speaks up in minutes instead of hiding it.
Write it down. Document your MFA policy, any exceptions, and who approved them.
Questions Your Customers May Ask You
“If one of your employees gets phished, is my information exposed?” A stolen password alone shouldn’t get anyone in. Every account that touches customer information requires a second check, and our most sensitive accounts use phishing-resistant sign-in.
“Why does your portal make me verify with a code?” It keeps a stolen password from being enough to reach your information. The extra step takes seconds.
“How would you know if someone got into your systems?” We monitor for unusual sign-in activity, like repeated denied approvals or logins from unexpected places, and our team knows to report anything suspicious immediately.
How Farmhouse Networking Can Help
Since 2015, Farmhouse Networking has helped small and mid-sized businesses make security practical. We:
Roll out MFA with number matching, plus passkeys or security keys for owners and admins
Build Conditional Access policies in Microsoft 365 Business Premium that fit how your team works
Enable banned-password protection and dark web monitoring to catch stolen credentials early
Alert on suspicious sign-in patterns through our Wazuh SIEM monitoring
Run simulated phishing and staff training, including how to spot push bombing
Our U.S.-based team answers the phone live, so when an employee gets a strange prompt at 4:55 p.m., they reach a person, not a voicemail box.
Get a Free Breach-Readiness Review
Not sure which accounts have MFA, which still rely on text codes, or whether older sign-in methods are bypassing it altogether? Email support@farmhousenetworking.com for a free breach-readiness review. We’ll show you where the gaps are and what to fix first.
Next week: How to Get Breached, Step 5: Paste Client Data Into Any AI Tool You Find. It’s fast, it’s free, and what could go wrong?
Why phishing still works on smart people, and how to build a “report it, don’t click it” habit across your business
One click on a phishing email can expose your entire business. Building a report it, don’t click it habit starts with knowing what to look for.
Welcome back to our backwards guide to cybersecurity. Last week you reused one password everywhere. This week, the advice is simple: click every link. An invoice from a vendor you’ve never used? Click it. A shared document from “Micros0ft”? Click it twice. An urgent message from your CEO, who is somehow emailing from a Gmail account? Definitely click that one.
Now for the serious part. Government agencies and industry research agree that phishing remains the most common entry point into small businesses, largely because it blends into normal workflows. The scams have also improved. Generative AI tools now write cleaner, more convincing lures than most human attackers could, so the typo-filled email you learned to ignore is no longer the main threat.
A Hypothetical Monday Morning
Picture a 25-person company. The office manager gets an email that looks like a Microsoft 365 storage warning. She signs in on what looks like the normal login page. Nothing seems wrong.
Behind the scenes, the attacker now has her mailbox. They quietly create a rule that forwards anything mentioning “invoice” to an outside address. Three weeks later, a “vendor” sends updated bank details on a real email thread. A $40,000 payment goes to the wrong account. One click started all of it.
How to Spot a Phishing Email
Check the real sender address, not the display name. “Accounts Payable” can be attached to any address.
Look for lookalike domains. Swapped letters (rn for m, 0 for o) and extra words are common.
Hover before you click. On a phone, press and hold to preview the link.
Notice pressure. Urgency, secrecy, and authority are the attacker’s main tools.
Treat unexpected sign-in requests, attachments, and QR codes as suspicious. Microsoft tracked QR-code phishing jumping 146% in Q1 2026, partly because it moves the victim onto a personal phone.
Question any change to payment details, no matter who appears to send it.
Action Steps for Owners and IT
Give staff one place to report. Suspicious email gets forwarded to IT, not deleted and forgotten. Farmhouse Networking clients forward to support@farmhousenetworking.com.
Adopt a no-blame policy. The employee who clicks and reports in five minutes is a hero. The one who stays quiet out of embarrassment gives the attacker weeks.
Verify money requests by phone. Use a number you already have, never one from the email.
Protect your domain from spoofing. Configure SPF, DKIM, and DMARC, and move DMARC to an enforcement policy so criminals can’t send email as you.
Tag external email. A visible “External” banner helps staff catch fake internal messages.
Run simulated phishing tests. Follow each one with short, practical training rather than an annual slideshow.
Require multifactor authentication on email and every cloud app.
Monitor for signs of a compromised mailbox, including new forwarding rules and sign-ins from unusual locations.
Write a one-page “I clicked” plan. Reset the password, end active sessions, check mailbox rules, and decide who notifies customers if needed.
Questions Your Customers May Ask You
“I got an email from your company asking me to pay a new account. Is it real?” Our payment details rarely change, and when they do, we confirm by phone. If you ever receive a request like this, call us at the number you already have before sending anything.
“How do I know emails from you are legitimate?” We have set up email authentication that makes it much harder for anyone to send messages using our domain. If something looks off, forward it to us and we will check.
“What happens if one of your employees clicks a bad link?” Our team is trained to report it immediately, and our IT partner has a response process ready to contain the issue quickly.
How Farmhouse Networking Can Help
Farmhouse Networking helps small and mid-sized businesses turn phishing defense into a routine instead of a scramble. We run simulated phishing campaigns and short staff training, configure SPF, DKIM, and DMARC to stop domain spoofing, and enforce MFA and Conditional Access in Microsoft 365. Our security monitoring watches for suspicious sign-ins and mailbox rule changes, and dark web monitoring alerts us when employee credentials show up for sale. When someone reports a suspicious email, a real person at our U.S.-based help desk responds.
Get a Free Breach-Readiness Review
Would your team report a phishing email or just click it? Find out before an attacker does. Email support@farmhousenetworking.com to schedule a free breach-readiness review. We will check your email security settings, your domain’s spoofing protection, and how prepared your team is to report what lands in their inbox.
Next week: How to Get Breached, Step 4: Turn Off MFA. Those Pop-Ups Are So Annoying.
A NAS can record backup failures every night for weeks. Without centralized log monitoring, nobody sees them.
As an MSP, our focus is providing white labeled Tier 3 IT support services, RMM as a service, and co-managed IT for other IT providers and businesses. This blog will share tips on forwarding Synology NAS logs into a self-hosted Wazuh SIEM using a Bash script.
We recently connected a client’s Synology NAS to their onsite Wazuh server while they worked toward CMMC Level 2. Sending NAS sign-ins, configuration changes, file activity and backup results to a central SIEM supports NIST 800-171 controls 3.3.1 (create and retain audit records) and 3.3.2 (trace actions to individual users). It also gave the client a backup-failure alert they did not have before. We packaged the work into one script that can be run by hand on the Wazuh manager or through SuperOps RMM.
Research
Wazuh does not ship Synology decoders, so the NAS’s syslog arrives and is silently dropped as “no decoder matched.” Getting it right took longer than expected, because almost every mistake fails without an error:
The protocol has to match. DSM’s Log Center was set to UDP while our Wazuh syslog listener was TCP. A Wazuh <remote> syslog block accepts exactly one protocol. tcpdump on the manager still shows the packets, because it sees them before any program does.
DSM only sends the priorities you select. With Info and Notice unticked in Log Filters, failed sign-ins arrived and nothing else did.
Active Backup for Business has its own syslog setting. It does not go through Log Center at all, and its transfer protocol also has to be TCP.
DSM uses several line formats, and Wazuh treats them differently. Lines with a program name (“Connection:”, “ActiveBackup[pid]:”, “Hyper_Backup:”) are only checked against decoders that declare a <program_name>. Lines without one (“System user:”, “FileStation Event:”) are only checked against decoders that don’t. A decoder on the wrong list loads cleanly and never runs. We confirmed this in Wazuh’s source (decoders_list.c and cleanevent.c).
Child rule order is by level, not by file order. Wazuh tries a parent’s children highest level first. A specific rule meant to beat a general one must be at a higher level, or at the same level and earlier in the file.
Not every DSM change writes a log entry. Toggling Log Center’s own archive settings writes nothing. Creating and deleting a scheduled task always does, so that became our end-to-end test.
The results were worth it. The client’s Hyper Backup history showed one stretch of 40 days in a row with no successful backup, because no USB drive was attached. The NAS’s own notification emails had been failing too, so nobody was told. That failure now raises an alert. A scheduled report also flags any 26-hour window without a successful backup, since no rule can fire on a message that is never sent.
Variables
SynologyNasIp = NAS address, or several separated by commas (required for install)
SynologyAction = install, status or uninstall (optional, default install)
SynologyWatchUsers = break-glass account name(s); every sign-in raises a level 10 alert (optional)
SynologyAddListener = yes or no; use no if the NAS is already allowed in an existing syslog block (optional, default yes)
SynologyPort = listener port (optional, default 514)
SynologyProtocol = tcp or udp (optional, default tcp)
SynologyRuleBase = first rule ID (optional, default 127500)
SynologyOpenFirewall = yes or no; opens ufw or firewalld for the NAS address only (optional, default yes)
SynologyRestart = yes or no (optional, default yes)
Script Snippet
Before the manager restarts, the full script:
checks for rule ID collisions and listener conflicts
backs up ossec.conf
compares wazuh-analysisd -t output before and after
feeds 23 real DSM log lines through wazuh-logtest
It rolls back automatically if any of those fail. Here are the key pieces:
# Syslog listener restricted to the NAS, wrapped in markers so re-runs and uninstall can find it
<!-- BEGIN synology-wazuh-install listener -->
<remote>
<connection>syslog</connection>
<port>514</port>
<protocol>tcp</protocol>
<allowed-ips>192.0.2.10</allowed-ips>
</remote>
<!-- END synology-wazuh-install listener -->
# "Connection:" lines have a program name, so this decoder must declare one
<decoder name="synology-conn">
<program_name>^Connection$</program_name>
<prematch type="pcre2">User \[[^\]]*\] from \[[^\]]+\]|Host \[[^\]]+\] (?:was blocked|failed to connect)</prematch>
</decoder>
# "System user:<TAB>message" lines have no program name, so this one must not
<decoder name="synology-system">
<prematch type="pcre2">^System \S+:\s</prematch>
</decoder>
# Hyper Backup: a rotated-out USB drive is expected (level 5); anything else is a real failure (level 10)
<rule id="127564" level="10">
<if_sid>127560</if_sid>
<match type="pcre2">Failed to access the backup destination|Exception occurred while backing up data|Backup task was cancell?ed|Failed to start backup task(?!\. \(The backup destination does not exist)</match>
<description>Hyper Backup: task $(syno_task) failed - $(syno_event)</description>
<group>backup,backup_failure,</group>
</rule>
<rule id="127563" level="5">
<if_sid>127560</if_sid>
<match type="pcre2">Failed to (?:run|start) backup task</match>
<description>Hyper Backup: task $(syno_task) did not run - $(syno_event)</description>
</rule>
# Self-test: every sample line must land on its expected rule, or the install rolls back
while IFS='|' read -r off line; do
want="$(rule_id "$off")"
out="$(printf '%s\n' "$line" | "$OSSEC_DIR/bin/wazuh-logtest" 2>&1)"
got="$(printf '%s\n' "$out" | sed -n "s/^[[:space:]]*id: '\([0-9]*\)'.*/\1/p" | tail -n 1)"
[ "$got" = "$want" ] || fails=$((fails + 1))
done < <(self_test_samples)
The full script, the SuperOps edition, the decoders and the complete ruleset are free on our GitHub. There are 65 rule IDs, covering:
sign-ins and brute force
file activity and mass deletion
account and privilege changes
audit logging being turned down
storage pool and iSCSI LUN failures
power and UPS events
Active Backup for Business and Hyper Backup results
One password for email, payroll, the bank, and that forum you joined in 2014. What could go wrong?
When one password opens email, banking, and payroll, a single breach on any website can unlock your entire business.
Welcome back to our guide to getting breached. This week’s tip is a real time-saver: pick one good password and use it for everything. Email, payroll, the bank, the vendor portal, the site where you ordered the office chairs. You will never click Forgot Password again, and neither will the criminal who bought your login in a leaked list last year.
If you would rather keep your business out of the breach column, read on.
Why password reuse is a business problem
Attackers rarely guess passwords anymore. They collect them. When a website is breached, the usernames and passwords stored there get traded and sold. Automated tools then try those same combinations against thousands of other services: Microsoft 365, banks, payroll providers, accounting software. This is called credential stuffing, and it only works because people reuse passwords.
That means your security depends on the weakest website any employee has ever signed up for with a work password.
A hypothetical example
Picture a made-up 15-person distributor. The office manager uses one password for her work email and for a home decor site she shopped at years ago. The retailer is breached. Months later, an automated tool tries her email address and that password against Microsoft 365, and it works. The attacker reads her inbox quietly for two weeks, learns how invoices get approved, then emails a customer from her real account with new bank details for the next payment.
There was no malware and no alarm. The only thing the attacker needed was one reused password.
Action steps for you and your IT team
Roll out a business password manager. Every employee gets an account, and every login gets a long, unique, generated password. Staff remember one strong passphrase.
Turn on multi-factor authentication (MFA). Start with email, banking, payroll, and remote access. MFA does not make reuse safe, but it keeps many stolen passwords from being enough.
Check for breached passwords. Have IT screen new passwords against lists of known compromised ones, which current NIST guidance calls for, and monitor for company credentials in new leaks. A free service such as Have I Been Pwned shows whether an email address appears in known breaches.
Change passwords on evidence, not on a calendar. Forced 90-day changes produce Spring2026! followed by Summer2026!. Favor length over odd symbols.
Separate work from personal. Work email addresses and work passwords stay out of shopping, streaming, and social accounts.
Retire shared logins where you can. If a shared account is unavoidable, keep it in the password manager’s shared vault, protect it with MFA, and change it whenever someone leaves.
Put it in writing. A one-page password policy gives you something to train on and enforce.
Questions your customers may ask you
Q: How do you protect the accounts that hold our information? A: Every employee uses a unique password for each system, stored in a password manager, with MFA on anything that touches customer data.
Q: What happens if an employee’s password shows up in a breach? A: We monitor for exposed credentials. When one appears, the password is changed right away and we review the account for unusual sign-ins.
Q: Isn’t a password manager putting all your eggs in one basket? A: It is one well-guarded basket instead of dozens of weak ones. The vault is encrypted and protected by a strong passphrase plus MFA.
Q: Do your staff share logins? A: Each person signs in as themselves wherever the system allows, so we can see who did what and remove access the day someone leaves.
How Farmhouse Networking can help
Farmhouse Networking helps small and mid-sized businesses replace password habits with a system. We help you choose and roll out a business password manager, then train your staff so it gets used. Our dark web monitoring alerts us when your company’s credentials appear in a leak. In Microsoft 365, we configure banned-password protection, multi-factor authentication, and Conditional Access so a stolen password alone will not open the door. Our staff is 100% U.S.-based, and a live person answers the phone.
Is one reused password all that stands between you and a breach?
Email support@farmhousenetworking.com to request a free breach-readiness review. We will look at how your business handles passwords, MFA, and exposed credentials, then give you a plain-language list of what to fix first.
Next week: How to Get Breached, Step 3: Click Every Link. What’s the Worst That Could Happen?
A blocked malware site in DefensX becomes a SuperOps ticket within five minutes, with no technician watching a dashboard.
As our business continues to grow our focus is on providing white labeled Tier 3 IT support services, RMM as a service, and co-managed IT services. This blog will be highlighting tips for using an n8n workflow to watch a DefensX global URL group and open a SuperOps ticket whenever a client machine tries to reach a site on it. We keep a global malware list in DefensX that applies to every customer. A block on that list is not routine web filtering. It means something on that machine tried to reach a known bad destination, and we want a technician looking at it in minutes, not at the next report review.
Research
DefensX has a Partner API with log endpoints for every customer, and SuperOps has a GraphQL API that can create tickets. The plan was simple: poll DefensX, find blocks from our list, create a ticket for the right client. Getting there took more discovery than expected. Here is what we ran into:
There is no webhook, and the logs don’t say which group caused the block. The URL log gives you the URL, the action and a category, but not the URL group that matched. The workflow has to pull the group’s entries itself and do the matching. That means handling all three entry styles DefensX allows: exact hostnames, *.domain.com wildcards, and full URLs with a path.
Browser logs are only half the picture. Our first test was a curl from a command prompt, and it never appeared in the URL logs. The browser extension only sees browser traffic. Anything else, including scripts and processes running as SYSTEM, is caught by the agent and written to the DNS logs. Since malware rarely uses the browser, the workflow checks both endpoints for every customer.
DNS logs are large. One customer returned more than 5,700 DNS rows in a 20-minute window, which is over the 5,000-row page limit. Pagination is not optional.
SuperOps required a field the schema calls optional. Our first ticket failed with mandatory_validation_failed on requestType, even though introspection shows it as a plain optional string. The tenant enforces it.
The next error named a field we never sent. After adding requestType: "Incident", SuperOps answered with referred_value_does_not_exist on ticketType. The field was renamed at some point and the error still uses the old name. The real problem was the value: ticket types are customizable per tenant, and ours has no type called “Incident”. It has “Incident – Security”.
Our API token could not look up the answer. We tried reading the type from existing tickets. The list query returned a total count of 429 and zero rows, and single-ticket lookups returned forbidden. The token could create tickets but not read them. What finally explained everything was asking the schema for field descriptions, not just field types. The description for requestType states that it replaced ticketType and tells you which query lists the valid options.
Repeat hits would flood the board. A machine retrying a blocked connection every few seconds would create a ticket on every run. The workflow remembers each user and site pair for 24 hours and tickets it once. It also keeps a separate time cursor per customer, so a failed API call for one customer is retried from where it left off without holding up the others.
Variables
Everything you need to change lives in one Set node at the top of the workflow:
urlGroupName – the exact name of the DefensX URL group to watch, for example Global Malware List
groupOwnerCustomerId – leave blank if the group lives on your partner account; otherwise the ID of the customer that owns it
suppressHours – how long to stay quiet about the same user and site after a ticket is created (default 24)
overlapMinutes – how far each run reaches back past the last one, to catch logs that arrive late (default 5)
includeConsented – whether to report blocks the user clicked through (default true)
defangUrls – writes sites as example[.]com in the ticket so nobody clicks one by accident (default true)
superopsSubdomain – your SuperOps subdomain, sent as the CustomerSubDomain header
ticketRequestType – one of your own ticket type names, spelled exactly as it appears in SuperOps
fallbackSuperOpsAccountId – the client that receives the ticket when a DefensX customer name has no match in SuperOps
customerNameMap – optional JSON for customers whose names differ between the two systems
API keys go in n8n credentials, never in the workflow itself.
Script Snippet
The matching logic runs in a Code node. Wildcard entries match the domain and every subdomain, and path entries are only checked against URL logs because a DNS lookup has no path:
function findEntry(target, hasPath) {
for (const e of ctx.entries) {
const hostOk = e.wildcard
? (target.host === e.host || target.host.endsWith('.' + e.host))
: target.host === e.host;
if (!hostOk) continue;
if (!e.path) return e;
if (hasPath && (target.path === e.path || target.path.startsWith(e.path + '/'))) return e;
}
return null;
}
Both log endpoints use the same pagination settings on the HTTP Request node:
Each ticket lands on the matching SuperOps client with a table showing the time, user, device, site, number of blocks and whether it came from the browser or the agent. Query strings are stripped from URLs before they are written, so session tokens never end up in a ticket.
The complete workflow, with the customer loop, DNS and URL log handling, SuperOps client matching and duplicate suppression, is free on our GitHub: [GITHUB LINK]
If your company is a MSP or wants to become one and automation just seems out of reach, then contact us to run your RMM for you.
Why “nobody wants our data” is one of the most expensive sentences a small business owner can say
Automated cyber attacks don’t check your company size. They look for the easiest open door.
Welcome to How to Get Breached, our weekly guide for business owners who want to make a cybercriminal’s job as easy as possible. Step one is a classic, and it costs nothing to adopt. Just decide that hackers only go after banks, big retailers, and national brands. Not a 20-person company with a modest office and a coffee maker that leaks. Once you believe that, you can skip the security budget, the complaints about multi-factor authentication, and the backup testing. Attackers appreciate the cooperation.
For everyone who would rather not get breached, here’s why this advice backfires.
Attackers Don’t Check Your Size First
Most cyberattacks are automated. Bots scan the internet around the clock for exposed remote access, unpatched firewalls, and email accounts with weak or reused passwords. They don’t look up your revenue before they knock. They look for an open door.
We see this firsthand. The security monitoring we run for our clients records automated login attempts and scans every day against organizations of every size, including small offices most people would assume nobody cares about.
Small Means Easier, Not Safer
Small businesses often have fewer defenses: no dedicated security staff, older equipment, and shared passwords that never get changed. Attackers know this. Verizon’s 2025 Data Breach Investigations Report found ransomware in 88% of breaches at small and mid-sized businesses, compared with 39% at large organizations.
Your business is also a doorway to other people. Your email account can be used to send fake invoices to your customers. Your vendor relationships and bank accounts are worth something to a criminal even if your customer list isn’t.
A Hypothetical Scenario
Picture a fictional 15-person distribution company. The office manager uses the same password for work email as for a shopping site that was breached years ago. There’s no multi-factor authentication. An attacker logs in quietly, watches email for two weeks, then sends a few customers a polite note with “updated” bank details. Nobody notices until payments stop arriving. No advanced hacking was needed. The door was simply unlocked.
Practical Action Steps for Owners and IT
Turn on multi-factor authentication (MFA) for email, remote access, banking, and every cloud app, starting with email.
Patch operating systems, firewalls, and VPNs on a schedule, and replace equipment that no longer receives security updates.
Close exposed remote access. Remote desktop should never face the open internet.
Keep backups with at least one copy offline or immutable, and test a full restore at least quarterly.
Put security monitoring in place so someone reviews suspicious activity around the clock, not just during business hours.
Train staff to spot phishing, and require a phone call to a known number before changing any payment details.
Write a one-page incident response plan listing who to call first: your IT provider, your cyber insurer, and legal counsel.
Review your cyber insurance requirements. Many carriers now require MFA and tested backups before they’ll pay a claim.
Questions Your Customers May Ask You
Is my information safe with you? A strong answer explains what you actually do: MFA, monitored systems, tested backups, and staff training.
Why do you call me to confirm payment changes? Because fake invoice emails are one of the most common scams, and a quick call stops them.
What happens if you get hit by ransomware? You should be able to say that you have tested backups and a plan to restore operations quickly.
Would you tell me if my data were exposed? Yes. Explain that you have a response plan that includes timely notification.
How Farmhouse Networking Can Help
Farmhouse Networking helps small and mid-sized businesses close the gaps attackers count on. We provide 24/7 security monitoring, manage MFA, patching, and backups so they stay current, run staff security awareness training, and support compliance requirements specific to your industry. Our team is 100% U.S.-based, and when you call, a real person answers.
Find Out Where You Stand
You don’t need to guess whether your business is an easy target. Email support@farmhousenetworking.com to schedule a free breach-readiness review. We’ll show you where your gaps are and what to fix first, in plain language.
Next week: How to Get Breached, Step 2: Use the Same Password Everywhere.
Duo authentication and admin activity logs flowing into a self-hosted Wazuh SIEM, ready for MFA monitoring and CMMC audit evidence.
As our business continues to grow our focus is on providing white labeled Tier 3 IT support services, RMM as a service, and co-managed IT services. This blog will be highlighting tips for using a Bash script to forward Cisco Duo MFA logs into a self-hosted Wazuh SIEM.
We recently connected Duo to the onsite Wazuh server of a client working toward CMMC Level 2. Logging every MFA event and every admin change is part of the evidence an assessor wants to see (NIST 800-171 controls 3.3.1 and 3.5.3). Duo ships an official tool for exactly this. Getting it to produce real Wazuh alerts took some work, so we turned everything we learned into one script that you can run by hand or from SuperOps RMM.
Research
Duo publishes DuoLogSync (github.com/duosecurity/duo_log_sync), a small Python service that pulls logs from the Duo Admin API and sends them as JSON over TCP. The plan was simple: run DuoLogSync on the Wazuh manager, send its output to a syslog listener that only accepts local connections, and let Wazuh’s built-in JSON decoder do the rest. No agent, no public port, no custom decoder.
In practice, five things got in the way. They aren’t obvious from the documentation:
Stock Wazuh rule 86600 (Suricata) matches any JSON event that has both “timestamp” and “event_type” fields. Duo auth logs have both, so every event was captured by a level 0 rule and silently thrown away. Our rules now hang under 86600 as child rules.
Wazuh loads every rule file, stock and custom together, in alphabetical order. Naming the file 9999_duo_rules.xml makes sure it loads after the stock rules it depends on.
“action” is a reserved Wazuh field name, so a field match on it stops the whole ruleset from loading. Use the <action> tag or a dotted field like action.name instead.
DuoLogSync 2.4 retired the “adminaction” endpoint. Admin events now come from the “activity” log, which has a completely different JSON layout.
DuoLogSync opens one TCP connection and never reconnects. Every Wazuh manager restart quietly lost the next batch of logs. The fix is a systemd unit tied to the manager with PartOf=wazuh-manager.service.
The payoff showed up right away. The 180-day history pull surfaced twelve failed Active Directory syncs, all caused by a Duo Authentication Proxy outage. If an AD sync fails, a user you just disabled in AD can still pass Duo, so that’s a finding worth knowing about.
Variables
DuoIntegrationKey = The integration key of a Duo Admin API application with only “Grant read log” permission – i.e. DIXXXXXXXXXXXXXXXXXX DuoSecretKey = The secret key for that application (mark this as a secure variable in SuperOps) DuoApiHost = The API hostname from the same application – i.e. api-xxxxxxxx.duosecurity.com DuoEndpoints = Optional. Which Duo logs to pull – default auth,telephony,activity DuoOffsetDays = Optional. How many days of history to pull on the first run, maximum 180 DuoAction = Optional. install, status, resend or uninstall
Script Snippet
The full script handles prerequisite checks, backups, validation, automatic rollback, and a final check with wazuh-logtest. These are the core pieces:
# DuoLogSync config - single quotes are required by DLS
cat > /opt/duologsync/config.yml <<EOF
version: '1.0.0'
dls_settings:
log_format: 'JSON'
api:
offset: $DLS_OFFSET_DAYS
checkpointing:
enabled: True
directory: '/opt/duologsync/checkpoints'
servers:
- id: 'wazuh'
hostname: '127.0.0.1'
port: 5140
protocol: 'TCP'
account:
ikey: '$DUO_IKEY'
skey: '$DUO_SKEY'
hostname: '$DUO_API_HOST'
endpoint_server_mappings:
- endpoints: ['auth', 'telephony', 'activity']
server: 'wazuh'
EOF
# Local-only listener added to ossec.conf
<remote>
<connection>syslog</connection>
<port>5140</port>
<protocol>tcp</protocol>
<local_ip>127.0.0.1</local_ip>
<allowed-ips>127.0.0.1</allowed-ips>
</remote>
# Duo auth events are claimed by Suricata rule 86600 - attach under it
<rule id="120000" level="0">
<if_sid>86600</if_sid>
<field name="txid">\.+</field>
<field name="factor">\.+</field>
<description>Duo: authentication event</description>
</rule>
# systemd: restart with the manager, wait for the listener first
[Unit]
After=wazuh-manager.service
PartOf=wazuh-manager.service
[Service]
ExecStartPre=/bin/bash -c 'until ss -ltn | grep -q "127.0.0.1:5140 "; do sleep 2; done'
ExecStart=/opt/duologsync/venv/bin/duologsync /opt/duologsync/config.yml
Restart=always
The complete script, the SuperOps edition, and the full ruleset (with alerts for MFA fraud reports, MFA fatigue, admin panel brute force, Duo configuration changes and AD sync failures, all tagged for NIST 800-171) are free on our GitHub: https://github.com/FarmhouseNetworking/Duo-Wazuh-LogSync
If your company is a MSP or wants to become one and automation just seems out of reach, then contact us to run your RMM for you.
AI usage limits are now part of every business plan. Here is what happens when your team hits one, and how to keep company data from walking out the door with them.
When AI usage limits stop work, employees often switch to free AI tools. That is how shadow AI puts company data at risk.
It’s 3:40 on a Thursday. Your office manager is halfway through a customer proposal when the company AI assistant stops responding: usage limit reached, try again later. The deadline is 5:00. So she opens a free AI chatbot on her phone, pastes in the customer’s details, and finishes the job. The proposal goes out on time. The customer’s information now sits on a server you have never vetted, under terms nobody at your company has read.
That is the real risk behind AI token limits. The interruption is annoying. What your people do next can be expensive.
What Are AI Tokens and Why Do They Run Out?
Tokens are how AI tools measure work. A token is a small piece of text, often part of a word, and everything counts: the question, any file you attach, the running conversation history, and the answer. Business AI plans come with an allowance, whether the vendor calls it tokens, credits, or messages.
In 2026 those allowances are tighter and more closely metered. Vendors are moving away from flat, unlimited-feeling plans toward usage-based billing. Microsoft, for example, now bills some Copilot features in Copilot Credits with admin spending limits. At the same time, teams are using AI harder. AI agents that handle multi-step tasks, long chat threads, and large uploaded documents burn through tokens far faster than a quick question does.
What Happens When You Hit the Limit
Depending on the tool and plan, one of three things usually happens:
Work stops. New requests are blocked until the allowance resets or an admin raises it. One source reported one consultant waiting 13 hours for tokens to refresh.
The bill grows. Overage billing keeps things running, then shows up as a surprise on next month’s invoice.
People improvise. Employees switch to whatever AI tool they can reach, usually a free personal account.
That third outcome is called shadow AI: AI tools used for work without the company’s approval or oversight. Free consumer tools may retain what you paste in and, depending on settings, may use it to improve their models. IBM’s 2025 Cost of a Data Breach Report found that 63% of the breached organizations it studied had no AI governance policy, and that high levels of shadow AI added about $670,000 to the average cost of a breach.
Action Steps for Business Owners and IT
Inventory every AI tool in use. Ask staff what they use, including free and browser-based tools. IT should confirm with web traffic and application reports.
Standardize on business-grade plans. Choose approved tools with admin controls and contract terms that keep your data out of model training.
Right-size the allowance. Review usage reports monthly. Set spending caps and threshold alerts so IT hears about a limit before employees hit it.
Write an AI acceptable use policy. Spell out approved tools, data that must never be entered, and exactly what to do when a limit is reached.
Build a fast escalation path. If requesting more capacity takes a day, people will go around it. Make the safe option the easy option.
Restrict unapproved AI sites on company devices. Use web filtering and data loss prevention tools to block or flag sensitive data headed to unknown AI services.
Teach token-smart habits. Start a new chat for each new task, attach only the pages you need, and use lighter models for simple work.
Add AI to your continuity plan. List the workflows that depend on AI and document the manual fallback if the tool is unavailable.
Questions Your Customers May Ask
Do you put my information into AI tools? Only into tools we have approved and configured for business use, under agreements that keep your data out of model training. Our policy prohibits entering customer information into personal or free AI accounts.
What happens if an employee uses an unapproved AI app? Our systems restrict unapproved AI services on company devices, and our policy treats it as a security issue. We would investigate and respond just as we would to any other data concern.
If your AI tool goes down or hits a limit, will my project be delayed? No. AI helps our team work faster, but every AI-assisted process has a documented manual fallback.
Does a person check AI-generated work? Yes. A member of our team reviews anything AI helps produce before it reaches you.
How Farmhouse Networking Can Help
Most small businesses adopted AI one employee at a time, which means few owners know which tools are in use, what they cost, or where the data goes. Farmhouse Networking helps you take control without slowing your team down.
We start by identifying every AI tool touching your network, approved or not. From there we help you choose and configure business-grade accounts, set up usage alerts and spending controls, apply web filtering and data loss prevention to stop shadow AI, and write an acceptable use policy your staff will actually follow. We also train your team on efficient, secure AI habits and add AI dependencies to your continuity plan.
Our 100% U.S.-based team answers the phone live, and most issues are resolved in about 15 minutes, so a blocked tool never becomes an all-afternoon problem.
Get Your Free AI Acceptable Use Policy Template
Your employees are going to hit an AI limit. The only question is whether they have a safe path forward when it happens. Email support@farmhousenetworking.com with AI Policy in the subject line and we will send you our free AI Acceptable Use Policy template, ready to customize for your business.
What the growing patchwork of state laws means for your business, and how to track activity responsibly without eroding staff trust.
A clear, written policy is the starting point for legal, trust-friendly employee monitoring
More states are passing laws that require you to tell employees, in writing, when and how you’re monitoring their electronic activity. At the same time, insider incidents, whether malicious or just careless, remain one of the more expensive risks a small business can face. Those two facts point the same direction: employee activity monitoring is worth doing, but only if it’s built on a clear policy rather than software quietly running in the background. Handled well, it protects your business and your staff know exactly where they stand. Handled poorly, it’s a legal risk and a trust problem rolled into one.
Practical Steps to Take
Put a written monitoring and acceptable use policy in place before you turn on any tracking tool. Define what’s monitored, why, and who sees the reports.
Check your state’s specific requirements, and confirm with an employment attorney if you operate in more than one state. New York, Delaware, Connecticut, Illinois, and Colorado already require written notice or signed acknowledgment before monitoring electronic activity, and more states are following.
If you’re in Oregon, note that state law separately requires notifying everyone in a conversation before it’s recorded, which matters for call and video monitoring specifically. If you have employees or customers in California, remember that state privacy law now covers employee data too, so you need clear notice about what you collect and why.
Scope monitoring to company-owned devices and accounts. Personal phones and personal email should stay out of it unless your BYOD policy explicitly says otherwise.
Get signed acknowledgment from every employee, and update it when the policy changes.
Give your IT provider clear rules for who can see monitoring data, and keep that group small.
Set a schedule for reviewing logs and for deleting them. Don’t let data pile up indefinitely just because storage is cheap.
Revisit the whole policy at least once a year. Both the laws and the tools are changing quickly.
Questions Customers May Ask You
“Is it a red flag that your employees are being monitored? Should I trust this business less?” No, it’s the opposite. It means access to your information is tracked and controlled, not left to chance.
“How do you know an employee hasn’t misused my information?” Access to customer data is logged, and unusual activity, like someone accessing records outside their normal role, gets flagged rather than discovered later.
“Do your employees know they’re being monitored?” Yes. Every employee is given written notice and signs an acknowledgment. Transparency with staff is part of what makes the whole system work.
How Farmhouse Networking Can Help
Farmhouse Networking helps small and mid-sized businesses put together a written employee monitoring and acceptable use policy that matches what your state actually requires, then configures the access controls, activity logging, and secure retention to back it up. It’s part of our managed IT services, so you’re not left guessing whether your policy and your technology actually match, or whether either one would hold up if it were ever questioned.
Let’s Take a Look
If you don’t have a written employee monitoring policy, or you’re not sure your current one matches what your state requires, let’s fix that now. Email support@farmhousenetworking.com and we’ll review what you have and tell you plainly what’s missing.
Audit logs won’t stop an incident from happening. They’re what tells you exactly what happened, how bad it is, and how to move forward with confidence instead of guesswork.
Reviewing audit logs regularly helps small business owners catch problems early and respond with confidence.
An employee’s laptop gets stolen from their car. A phishing email lands and someone clicks it. A contractor’s access is never fully removed after the project ends. Any of these can turn into a genuine crisis, or a contained, well-understood incident, and the difference usually comes down to one unglamorous thing: whether your systems were keeping a record of who did what before anyone knew there was a problem.
Audit logs are the timestamped trail of activity across your network, systems, and accounts. Most small business owners never think about them until an incident forces the question: what actually happened here, and how far did it go? Without logs, that question gets answered with guesswork, which means overreacting, locking down everything and alarming customers unnecessarily, or underreacting, missing that the problem is worse than it looks. With logs, you get a fast, factual answer.
Action steps for you and your IT team:
Enable logging on your core systems: email, file storage, remote access tools such as VPN or RDP, and any line-of-business software holding customer or financial data.
Log both successful and failed logins. Repeated failures followed by success is one of the clearest signs of a compromised account.
Set a retention period of at least a year for critical systems, and confirm logs aren’t being quietly overwritten by default settings.
Remove access immediately when an employee or contractor leaves, and confirm the removal itself is logged.
Store logs somewhere separate from the systems they’re monitoring, so an attacker who compromises one system can’t also erase the evidence.
Review logs on a regular schedule, not only when something feels wrong. Most warning signs show up as patterns over time.
Know who on your team, or which vendor, is actually responsible for watching this. If the answer is no one, that’s the gap to close first.
Questions clients ask us about this:
Q: We’re a small business. Do we really need this level of tracking? A: Attackers don’t skip small businesses because they’re small. Many target them specifically because defenses tend to be lighter. Basic logging is inexpensive and often the deciding factor in how quickly you recover from an incident.
Q: We have antivirus and a firewall. Isn’t that enough? A: Those tools help prevent and detect threats, but they don’t give you a full history of user activity across your systems. Logs answer the who and when that other tools weren’t built to track.
Q: If nothing bad has ever happened to us, why start now? A: Most businesses that suffer an incident didn’t see it coming either. Logging is cheap insurance you set up before you need it, because you can’t go back and turn it on after the fact.
How Farmhouse Networking helps: We help small and mid-sized businesses put practical monitoring and logging in place without overcomplicating your environment or your budget. That means configuring logging across your key systems, setting retention that actually covers you, and reviewing activity on a regular schedule so small issues get caught before they become expensive ones. If something does happen, you get a fast, clear answer from a U.S.-based team who already knows your setup, instead of starting from zero during a crisis.
Voice phishing scams are getting harder to spot, and they’re not just an enterprise problem anymore. Here’s what business owners need to do now.
One convincing phone call is often all it takes. Verification before action is the strongest defense against vishing.
A hedge fund employee gets a phone call. The voice sounds exactly like a colleague, tone and pacing included. Within minutes, the caller has talked their way into a password reset. That scenario played out at several major investment firms in August 2026, when AI-generated voice cloning was used to target Point72, Citadel, and Millennium Management. Two Sigma caught the attempt before any damage was done, according to Bloomberg’s reporting.
Most small and mid-sized businesses don’t have that level of security scrutiny watching over them. This is vishing: voice phishing, where a scammer uses a phone call instead of an email to trick someone into handing over credentials, approving a wire transfer, or granting system access. It’s not a future threat. It’s active right now, and AI voice tools are making it more convincing every month.
Why Vishing Works So Well
People trust a human voice more than a written message, and criminals know it. According to Verizon’s 2026 Data Breach Investigations Report, phone-based social engineering succeeds roughly 40% more often per attempt than email phishing. Gartner research found that 35% of organizations have already experienced at least one deepfake-related incident, yet only 10% of security leaders prioritize training staff to recognize a cloned voice, compared to 73% who focus on email phishing alone.
The financial risk is real. In 2023, a vishing call to an IT help desk was the entry point for a breach that cost MGM Resorts an estimated $100 million.
Action Steps for Owners and IT
For the business owner:
Set a rule that no wire transfer, password reset, or system access is approved based on a phone call alone. Require a callback to a known, independently verified number first.
Build a culture where staff can pause and question an “urgent” request without fear of looking difficult.
Schedule recurring, not one-time, staff training on phone-based scams.
For your IT team or provider:
Enforce multi-factor authentication on every account that supports it, and never let it be disabled based on a phone request.
Require independent identity verification before any help desk password reset.
Document and block known scam and spoofed numbers where possible.
Run periodic simulated vishing tests to find gaps before criminals do.
Questions Clients Are Asking
“How do I know if a call is legitimate?” Hang up and call the company or person back using a number you already have on file, not one the caller gives you.
“What should my team do if they’re unsure?” Stop, verify, then act. No legitimate request will penalize someone for double-checking.
“Can this really happen to a business our size?” Yes. Smaller businesses are often targeted precisely because attackers assume less security is in place.
“What’s the first thing we should change?” Put a callback verification policy in place this week. It costs nothing and closes the biggest gap immediately.
How Farmhouse Networking Can Help
Farmhouse Networking builds vishing and social-engineering awareness training around how your team actually works, not a generic slideshow. We run realistic simulated call scenarios, show you exactly where the gaps are, and help you put clear verification procedures in place your staff will actually follow. As a locally based, USA-only provider, we invest heavily in our own team’s ongoing security training, and we bring that same standard to yours.
Protect Your Business Before the Call Comes In
Vishing attacks succeed because they catch people off guard. A short, honest conversation now is a lot less costly than the one you’d have after a breach. Email us at support@farmhousenetworking.com for a free risk assessment. We’ll give you a clear picture of where your business stands, not just against vishing, but across your full security posture.
Why Root Cause Analysis Belongs in Your Incident Response Plan
Finding the root cause of an IT incident is what stops it from happening again.
If your last IT issue got fixed but never explained, you may already be sitting on a repeat problem.
Here’s how it usually goes: an employee’s email gets compromised, your IT provider resets the password, the alerts stop, and everyone moves on. But almost nobody asks the harder question — how did the attacker actually get in, and is that same weakness still open somewhere else in your business?
That question is the entire purpose of root cause analysis (RCA). It’s the difference between putting out a fire and finding out what’s been leaking gas into the building. Skip it, and you’re not preventing the next incident — you’re just waiting for it.
What Root Cause Analysis Actually Means for Your Business
Incident response is the emergency part: contain the threat, restore access, get back to work. Root cause analysis is the follow-up step that asks why it happened in the first place — a phishing gap, a missing security policy, an unpatched system, a training blind spot. Without that step, your business ends up treating the same underlying weakness as a brand-new crisis every time it resurfaces.
Action Steps for You and Your IT Provider
Require a written root cause summary after any security incident — not just a “resolved” notification.
Ask whether your provider monitors for unusual sign-in locations and session activity, not just failed login attempts.
Confirm Conditional Access policies are enforced to block logins from unexpected countries or unmanaged devices.
Review whether staff training addresses the specific method behind the last incident, not just general reminders.
Ask your provider whether an incident was isolated or part of a broader pattern across your systems.
Build a root cause step into your written incident response plan, if you don’t already have one.
Schedule a 30-day follow-up review to confirm the fix actually held.
Questions Your Team Might Ask You
Q: We already fixed it — why dig further? A: Fixing the account doesn’t fix the door the attacker used to get in. Without knowing how it happened, you can’t be confident it won’t happen again the same way.
Q: Doesn’t this slow down how fast issues get resolved? A: No. Containment happens immediately, every time. Root cause review is a short follow-up step afterward — usually a summary or a brief call, not a delay.
Q: Is this really worth the extra step for a business our size? A: Yes — arguably more so. Smaller businesses often can’t absorb the same incident twice. Understanding the cause the first time is what keeps a bad week from becoming a bad year.
How Farmhouse Networking Helps
We recently helped a client contain an incident where an employee’s login session — not just her password — was stolen through a convincing fake sign-in page that looked identical to a real Microsoft 365 login. Containing it was step one. The real work was tracing exactly how the attacker got that session, confirming nothing else in the environment was exposed the same way, and closing the gap permanently.
That’s the process we apply to every incident we handle. Farmhouse Networking documents root cause on every security event, gives you a plain-language explanation of what actually happened and why, and makes sure the fix addresses the cause — not just the symptom.
Want to Know What’s Really Behind Your Last IT Incident?
If your business has had an IT issue that got resolved but never really explained, that’s worth a second look before it repeats itself. Email us at support@farmhousenetworking.com and we’ll walk you through what a proper root cause review looks like — plainly, and without the jargon.
A growing attack technique lets criminals steal a live login session instead of a password — and most businesses have no idea it’s happening until it’s too late.
A single stolen login session can be enough for attackers to bypass MFA and take over a business email account.
For years, business owners have been told the same thing: turn on multi-factor authentication (MFA) and you’re safe. That advice is still mostly true — but a newer style of attack is proving it isn’t the whole story. We recently helped a regional nonprofit contain an incident that shows exactly how this plays out, and it’s a pattern every small business owner should understand.
Here’s what happened, in short: an employee was directed to a fake login page that looked identical to the real Microsoft 365 sign-in screen. She entered her password and completed her MFA step normally. But the fake page was secretly relaying everything to the real Microsoft servers in real time — and it captured the “session” created after she logged in. That session is like a hall pass: once you have it, you don’t need the password or the MFA code again. The attacker used it to log in as her, days later, from the other side of the world.
From there, the attacker spent time reading email, quietly created a mail rule to auto-delete replies, and used the compromised account to send hundreds of file-sharing invitations and emails to external contacts — all appearing to come from a real, trusted employee.
Action steps for you and your IT provider:
Ask your IT provider whether your email platform is monitoring for “impossible travel” or suspicious sign-in locations, not just failed MFA attempts.
Enable and enforce Conditional Access or equivalent policies that block sign-ins from unexpected countries or devices.
Shorten session lifetimes so a stolen session expires faster.
Train staff to check the URL bar before entering credentials — even on pages that look pixel-perfect.
Make sure your provider can see and revoke active sessions instantly, not just reset passwords.
Review mail rules periodically; attackers often hide behind rules named with punctuation marks so they’re invisible in a quick glance.
Confirm your incident response plan includes session token revocation, not just password resets.
Q&A
Q: If we have MFA, aren’t we protected? A: MFA blocks most attacks, but this technique steals the session created after MFA succeeds. You need monitoring and Conditional Access policies layered on top of MFA, not instead of it.
Q: How would we even know this happened? A: Often the first sign is unusual outbound email, unexpected file-sharing invitations, or partners asking why they received a strange invoice link. Proactive monitoring catches it earlier.
Q: Is this expensive to defend against? A: Most of the defenses — Conditional Access policies, session timeout settings, monitoring — are configuration changes, not new purchases, if your provider has the expertise to set them up correctly.
How Farmhouse Networking Helps
Farmhouse Networking configures and monitors Microsoft 365 environments specifically to catch this kind of attack — unusual sign-in locations, hidden mail rules, mass outbound activity — before it turns into a full-blown incident. We also help small businesses put the right guardrails in place from the start, so a stolen password or session doesn’t become a company-wide problem.
Not sure if your email environment could catch an attack like this? Email us at support@farmhousenetworking.com to schedule an MFA and email-security review. We’ll walk through your current setup and tell you plainly where the gaps are.
What the CMMC suspension teaches every small business about the danger of waiting on compliance
Building a cybersecurity policy before it’s required can save your business time, money, and trust.
On July 13, 2026, the Department of War suspended Phase II of its Cybersecurity Maturity Model Certification (CMMC) program — the rule that would have required over 100,000 defense contractors to complete third-party cybersecurity assessments starting this November. The reason wasn’t that cybersecurity stopped mattering. It’s that the compliance system itself couldn’t scale: too few certified assessors, costs approaching $600,000 per certification, and a timeline small businesses couldn’t meet.
That story has nothing to do with defense contracts if you’re not one. But it has everything to do with a mistake we see constantly: business owners treating cybersecurity policy as something to build only when a regulator forces the issue. When the deadline moves or disappears, so does the motivation — right up until a breach, an insurance audit, or a client contract makes it urgent again, usually at the worst possible time.
Why Waiting Is the Expensive Choice
Government programs get delayed, revised, or scrapped. Your actual risk — ransomware, phishing, a stolen laptop, an employee clicking the wrong link — doesn’t wait for anyone’s regulatory calendar. Businesses that build security practices proactively spend less, recover faster, and rarely scramble when a client or insurer asks for documentation they don’t have.
Action Steps for Business Owners
Write down your security policies now, even in simple form: password requirements, data handling rules, who can access what.
Inventory your systems and data — you can’t protect what you haven’t mapped.
Set a patch and update schedule instead of reacting to alerts.
Back up data regularly and actually test that restores work.
Train staff on phishing and basic security hygiene at least twice a year.
Review vendor contracts for the security commitments you’re already making to clients or partners.
Revisit your plan quarterly — don’t let it go stale.
Questions Business Owners Are Likely Asking
“If the government paused its own program, why should I move faster on mine?” Because your risk was never tied to their timeline. The suspension was about assessment logistics, not about cyber threats becoming less real.
“Isn’t this overkill for a small business?” No — attackers target small businesses precisely because they assume no one built a plan. A written policy costs far less than a breach.
“Do I need a full compliance framework?” Not necessarily. You need documented, consistently applied practices. Formal frameworks can come later if a client or contract requires them.
“What if I don’t have an in-house IT person?” That’s exactly where a managed partner earns their keep — building and maintaining the plan so you don’t have to.
How Farmhouse Networking Helps
We help small and mid-sized businesses build the security foundation regulators eventually ask for — without waiting for a mandate to force the issue. That means clear, documented policies, practical safeguards like MFA and monitored backups, and straightforward guidance you can actually act on, without the jargon.
Don’t Wait for the Next Deadline to Get Serious
Regulations pause. Real risk doesn’t. If you’ve been putting off a cybersecurity policy because “nothing’s required yet,” now is the time to close that gap — before something else forces the timeline.
Email us at support@farmhousenetworking.com for a free cybersecurity policy review. We’ll tell you plainly where you stand and what to fix first.
What this summer’s federal security campaign means for any business holding sensitive data
Taking a few hours this summer to review your security practices can prevent a costly data breach later.
What this summer’s federal security campaign means for any business holding sensitive data
This July, the IRS and its Security Summit partners launched Protect Your Clients; Protect Yourself, a five-week campaign built for tax preparers. It walks through the phishing schemes, impersonation scams, and stolen-credential attacks criminals are using against professionals who hold sensitive client data, along with the basic safeguards, written security plans, and verification tools meant to stop them.
Your business may have nothing to do with taxes. But the tactics described in this campaign — fake “new client” emails carrying malware, spoofed calls, and urgent requests designed to pressure someone into clicking or sharing information — are used against every kind of small business, not just tax firms. If your company stores customer records, payment details, or employee data, you’re a target using the same playbook. Summer is a good time to check whether your own safeguards would hold up.
Action Steps for You and Your IT Team
Write down your security practices. A simple, documented policy covering data handling, access, and response is far better than relying on informal habits.
Enable multi-factor authentication on email, financial systems, and any remote access used by your team.
Review employee access regularly, and immediately revoke access for anyone who leaves the company.
Train your team to spot phishing and impersonation attempts, especially fake vendor invoices, urgent executive requests, and unexpected attachments.
Test your backups, not just assume they’re running, to confirm you could actually recover if something went wrong.
Document an incident response plan so your team knows exactly who to call and what to do the moment something looks wrong.
Questions Your Customers or Employees Might Ask
“How do you protect the information you have on file for us?” We maintain a documented security policy, require multi-factor authentication across our systems, and regularly review who has access to sensitive data.
“What would happen if your systems were breached?” We have a tested response plan and know exactly how we’d respond and notify anyone affected.
“Why do you keep asking us to verify things that used to be simple?” Because verification steps protect both of us from scams that specifically exploit shortcuts and urgency.
How Farmhouse Networking Can Help
Farmhouse Networking helps small and mid-sized businesses turn good intentions into an actual, documented security program: written policies, MFA across your critical systems, cleaned-up user access, tested backups, and a clear incident response plan. We handle the technical details so you can run your business with confidence instead of guesswork.
Find Out Where Your Business Actually Stands
Email support@farmhousenetworking.com for a free security assessment, and close the gaps the IRS is warning everyone else about — before they cost you something worse.
Why waiting for an audit notice is the most expensive compliance strategy there is
Proactive compliance planning costs far less than scrambling to fix gaps after an audit notice arrives.
Most business owners don’t think about compliance until someone forces the issue – a new client contract requiring proof of security controls, an insurance renewal asking for documentation, or worse, an audit letter. By then, the real cost isn’t the audit itself. It’s everything you didn’t do in the months or years leading up to it: the gaps that piled up, the records that don’t exist, and the scramble to fix it all under a deadline. Research consistently shows that organizations that wait until they’re forced to comply end up paying roughly two-and-a-half to three times more than those who treat compliance as an ongoing practice. That gap isn’t fines alone – it’s lost productivity, disrupted operations, and the cost of fixing things the hard way instead of the easy way.
What “Waiting” Actually Costs
Lost productivity during the scramble. When an audit notice arrives, someone has to drop everything to assemble records, policies, and proof of controls that should have already existed. That’s time not spent serving customers.
Higher remediation costs. Fixing a security gap proactively might mean a software update or a policy change. Fixing it during an active audit often means emergency vendor calls, rushed system changes, and premium pricing.
Weaker negotiating position. Auditors and regulators view a track record of good-faith effort favorably. A business with no documentation looks like it never tried – and that perception drives harsher outcomes.
Business disruption. Operations can grind to a halt while staff redirect their attention to corrective action plans, investigations, or reporting requirements.
Reputational fallout. Clients, vendors, and partners notice when a business fails an audit or discloses a breach. Rebuilding trust takes far longer than building it the first time.
Action Steps to Take Now
Inventory what you actually have. List every system, vendor, and data type your business touches. You can’t protect, or document, what you haven’t identified.
Run a basic risk assessment. Identify where sensitive data lives, who has access to it, and what would happen if it were exposed or lost.
Document your policies in writing. Verbal habits don’t count as a compliance program. Write down password requirements, data handling rules, and incident response steps.
Check your vendor agreements. Make sure any vendor handling sensitive data on your behalf has appropriate contractual protections in place.
Train your staff and keep records of it. A single untrained employee can undo your entire compliance posture. Training without documentation is nearly as risky as no training at all.
Test your backups and recovery plan. A backup you’ve never tested is a backup you don’t actually have.
Set a recurring review cadence. Quarterly or biannual reviews catch small gaps before they become big ones.
Questions Business Owners Are Likely Asking
“We’ve never had a problem. Why worry about this now?” Most compliance failures aren’t discovered until something else goes wrong – a breach, a complaint, or a routine review triggered by a client or insurer. The absence of a problem so far isn’t the same as the absence of risk.
“Isn’t this what our IT vendor is already handling?” Possibly, but it’s worth confirming directly. Compliance documentation, policy writing, and risk assessments are distinct from day-to-day IT support, and gaps often hide in that space between the two.
“How much time does this realistically take?” A basic risk assessment and documentation cleanup can often be completed in a few weeks. Waiting until an audit forces the same work into days, with far less room for error.
“What’s the actual return on doing this now instead of later?” Beyond avoiding fines, proactive compliance tends to reduce insurance premiums, speed up vendor and client onboarding, and protect the business from disruption that has nothing to do with regulators – like a ransomware attack or a lost laptop.
How Farmhouse Networking Can Help
Farmhouse Networking works with business owners to close compliance gaps before they become expensive problems – not after. That means risk assessments that actually identify where your exposure lives, documentation that holds up under scrutiny, employee training programs with the paper trail to prove it, and ongoing monitoring so nothing slips through the cracks between reviews. Instead of a one-time scramble, you get a system that keeps working in the background, year-round.
The Bottom Line
Compliance isn’t a deadline – it’s a discipline. The businesses that treat it that way spend less, sleep better, and never have to explain to a client, an insurer, or a regulator why the paperwork doesn’t exist. If you’re not sure where your gaps are, that’s the best possible reason to find out now, while you still have the luxury of time.
Don’t wait for an audit notice to find out where you stand. Email support@farmhousenetworking.com and let’s talk about what a proactive compliance check would look like for your business.
Upgrading your device is exciting. Losing access to every business account is not. Here’s what every business owner needs to know before they make the switch.
Switching to a new phone without preparing your MFA can lock you out of every business account. A little preparation before the switch prevents hours of downtime.
email. The system asks for an authentication code. You open the authenticator app. The accounts are gone. Now you’re locked out.
This happens to business owners every day. Multi-factor authentication (MFA) is one of the most effective security tools available – but it’s bound to the device it was set up on. When that device changes, access can disappear instantly unless you prepare in advance.
Here’s exactly what happens, why it matters, and what to do about it.
Why MFA Breaks When You Switch Phones
Authenticator apps like Microsoft Authenticator, Google Authenticator, and Duo Mobile generate time-sensitive codes that are tied to your specific device. The codes work because the app and the service share a secret key established during setup. When you swap phones without transferring that key, the connection breaks.
The result: you cannot complete login, even with the correct password. If your old phone is already wiped or gone, and you have no backup method configured, recovery can take hours, or longer, and usually requires IT intervention.
For a business, that’s more than an inconvenience. It’s a potential compliance issue, a productivity disruption, and in some cases, a security risk if employees start using workarounds.
Action Steps Before You Switch Phones
These steps apply to you, your staff, and anyone who uses MFA to access business systems.
Inventory every account protected by MFA. Email, cloud storage, accounting software, practice management platforms, banking portals – list them all. You cannot protect what you haven’t identified.
Check your authenticator app’s backup settings. Microsoft Authenticator supports cloud backup. Google Authenticator added backup functionality in 2023. Enable it before you wipe or trade in your old device.
Register a backup MFA method. Most platforms allow you to add a secondary method – a different phone number, a hardware key, or an email-based code. Do this now, not after a problem occurs.
Save recovery codes. During initial MFA setup, most services generate one-time recovery codes. Store these in a password manager or a secure, offline location. These are your safety net if everything else fails.
Do not wipe your old phone until the new one is fully verified. Set up the authenticator app on the new device, confirm every account logs in successfully, then decommission the old device.
Notify your IT provider before the switch. If you use a managed IT service, your provider can verify admin-level access to reset MFA on critical accounts if something goes wrong during the transition.
Remove your old device from your account settings. After the switch is complete, log into your security settings for each platform and delete the old device. Leaving it registered is an unnecessary security exposure.
Q&A: What Your Employees (and Clients) Might Ask
Q: Can I just reinstall the authenticator app on my new phone? A: Installing the app is only the first step. You still need to re-link each account, either by restoring from a cloud backup or by re-scanning QR codes through each platform’s security settings. Without prior backup configuration, you’ll need your IT administrator to reset access.
Q: What if I already switched phones and I’m locked out? A: Contact your IT administrator immediately. They can reset your MFA registration at the admin level, which clears the old device and allows you to set up a new one. Do not attempt to bypass MFA – doing so may violate your organization’s security policies.
Q: Is it safe to use text message codes instead of an authenticator app? A: SMS-based codes are better than no MFA, but they’re the weakest option. They’re vulnerable to SIM-swapping attacks, where a criminal hijacks your phone number. An authenticator app is more secure and worth the minor setup effort.
Q: Do I need to do anything with my business accounts specifically? A: Yes. Business accounts managed through Microsoft 365, Google Workspace, or other platforms often have centralized MFA settings controlled by your IT administrator. Those accounts may require admin-assisted recovery if the authenticator app is lost. This is another reason to have a managed IT partner involved before the phone switch.
How Farmhouse Networking Can Help
MFA transitions are a routine part of what we manage for our clients. When one of your employees gets a new phone, we can audit their MFA registrations, verify backup methods are in place, guide them through the device transfer, and reset access at the admin level if something goes wrong.
We also help businesses build a documented MFA policy – so every employee follows a consistent, tested process when devices change, instead of figuring it out under pressure when they’re locked out.
If you don’t currently have backup MFA methods configured across your team, that’s a gap worth closing now.
Ready to Stop Worrying About MFA Lockouts?
Email us at support@farmhousenetworking.com and let’s make sure your team is set up to handle device changes without the drama. One conversation now can prevent hours of lost access later.o handle device changes without the drama. One conversation now can prevent hours of lost access later.
A new attack method bypasses MFA and uses Microsoft’s own login system against you. Every business owner using Microsoft 365 needs to read this.
This login screen asks for an email address only, illustrating how attackers can use familiar Microsoft 365-style sign-in pages to bypass passwords.
Most small business owners believe that a strong password and multi-factor authentication make their Microsoft 365 accounts secure. That assumption is now being exploited at scale. Attackers are targeting Microsoft 365 users with device code authorization phishing – a technique that fools users into approving access tokens, bypassing multi-factor authentication protection entirely.
Campaigns using this method have surged since September 2025, representing a significant shift from limited, targeted attacks to widespread exploitation. Both organized criminal groups and nation-state actors are now using it. If your business runs on Microsoft 365, and most do, you need to act.
How the Attack Works
Microsoft has a login feature designed for devices like smart TVs and printers that can’t display a normal login screen. Instead of typing credentials on the device, a user visits a Microsoft page on their phone or computer and enters a short code. It’s a legitimate, trusted system.
Attackers exploit that trust. They initiate the device login flow themselves, then send your employee an email designed to get them to visit Microsoft’s real login page and enter the code – completing the attacker’s authentication instead of their own.
Your employee does everything right. They visit a real Microsoft website. They complete their MFA. They never hand over their password. And the attacker now has full access to your Microsoft 365 environment.
Action Steps for Your Business
Take these steps now with your IT team or provider:
Block device code flow in Microsoft Entra Conditional Access. This is the strongest mitigation available and can be deployed in report-only mode first to assess impact before full rollout. Most small businesses don’t use this feature and have no reason to leave it enabled.
Audit your Microsoft 365 OAuth app permissions. Review which third-party applications have access to your tenant and remove anything unauthorized.
Train your team on this specific attack. Standard phishing training won’t cover it. The key message is simple: if you receive a request to enter a code on a Microsoft login page that you didn’t initiate, stop and report it.
Review sign-in logs for your Microsoft 365 accounts. Unusual locations, unfamiliar devices, and off-hours logins are indicators of compromise.
Check for email forwarding rules set up without your knowledge. This is a common post-compromise action attackers use to quietly collect your outgoing email.
Review your cyber liability coverage. Confirm that account takeover scenarios are covered and understand what your response obligations are.
Q&A: What Your Clients or Partners May Ask
“How did this happen if you had MFA turned on?” This attack bypasses both traditional credential theft defenses and multi-factor authentication controls. MFA was never designed to protect against this type of authentication abuse.
“Could my information have been accessed?” If a business email account is compromised, any data in that account – client correspondence, contracts, financial information – is potentially accessible to the attacker.
“Is this being fixed by Microsoft?” Microsoft has released tools to block it, but those tools require configuration. Microsoft has been rolling out a managed Conditional Access policy aimed at blocking device code flow authentication, but it requires an administrator to enable and configure it. It doesn’t happen automatically.
“Should I be worried about my own accounts?” If you share Microsoft 365 services with a vendor or partner whose account is compromised, there’s risk of lateral movement. Security is a supply chain concern, not just an internal one.
How Farmhouse Networking Can Help
Farmhouse Networking reviews and configures Microsoft Entra Conditional Access policies to block device code phishing, audits your Microsoft 365 environment for existing unauthorized access, trains your staff on this and other current attack types, and monitors your accounts ongoing. We work with small and mid-sized businesses across Oregon, Northern California, and New Mexico – and we explain everything in plain language without the IT jargon.
Take the Next Step
Email support@farmhousenetworking.com today and ask for a Microsoft 365 security review. We’ll tell you whether this attack vector is currently open in your environment and what it takes to close it.
And God will generously provide all you need. Then you will always have everything you need and plenty left over to share with others. As the Scriptures say, “They share freely and give generously to the poor. Their good deeds will be remembered forever.” For God is the one who provides seed for the farmer and then bread to eat. In the same way, he will provide and increase your resources and then produce a great harvest of generosity in you. - 2 Corinthians 9:8-10
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.