Shadow AI often starts with one helpful shortcut and a pasted spreadsheet.
Welcome to Week 5 of “How to Get Breached,” the series where we give you terrible advice so you can do the opposite.
This week’s tip is a time saver. Let every employee paste contracts, customer lists, and spreadsheets into whatever free AI tool looks helpful. No approval, no policy, no questions. Your data will be handled with all the care a stranger’s free website can offer.
If you own a business, the joke lands close to home. Your team is probably already doing a version of this.
What Shadow AI Looks Like
Shadow AI is any AI tool your staff uses for work that the business has not reviewed or approved. It usually shows up in three ways:
Personal AI accounts used for business tasks, outside your control and your records.
AI tools connected to company email, calendars, or files with a single click, with no one in IT approving it.
AI reading mailboxes and documents that were never meant to be shared with it.
Nobody is acting maliciously. People are trying to work faster. The problem is that the data leaves your environment, and you cannot protect or retrieve what you do not know about.
A Hypothetical Example
Picture a 25-person company. An office manager wants a vendor contract summarized and a customer pricing sheet cleaned up. She opens her personal AI account and pastes both in. It works well, so she connects the assistant to her work mailbox to sort the inbox.
No one approved it. The owner learns about it months later, by accident. Now contracts, pricing, and customer emails sit in an account the company does not control, under terms no one read. When she leaves, the account goes with her.
Nothing dramatic happened. That is the point. This kind of exposure is quiet.
What To Do Instead
For the owner and IT team:
Define off-limits data. Customer personal information, financial records, credentials, and contracts should not go into unapproved tools.
Write a short AI acceptable use policy. One or two pages is enough. Say what is allowed, what is not, and who to ask.
Choose approved tools on purpose. Look for business-tier plans with admin controls, single sign-on and multifactor authentication, activity logging, and clear written terms on how your data is stored and whether it is used for training. Terms differ by vendor and plan, so read them.
Take inventory. Ask staff what they already use. Make it safe to answer honestly.
Control integrations. Limit who can grant third-party apps access to company email and files, so an AI connector needs admin approval.
Filter at the network level. DNS filtering can block or flag AI services you have not approved.
Monitor for unusual activity. Endpoint and log monitoring helps you notice what policy alone will miss.
Train people and update offboarding. Staff should know the rules, and departing employees should lose access to every tool tied to company data.
Review quarterly. New AI tools appear constantly.
Questions Your Clients May Ask
Are you putting my information into AI tools? A good answer is: “We only use approved tools under a written policy, and client data is handled according to that policy.”
Can your team use AI at all? Yes, with guardrails. The goal is safe use of AI, not a ban. A ban tends to push usage out of sight.
What happens if something is exposed? You should have an incident response plan that covers AI tools and a clear process for notifying affected parties.
How Farmhouse Networking Can Help
We are vendor neutral. We do not resell AI tools. We advise on which fit your business and configure them securely. We can:
Create AI acceptable use and data-handling policies written for your team.
Set up DNS filtering to block or flag unapproved AI services.
Use event log monitoring to help surface unusual activity.
Review your tools against the CIS Controls to find gaps.
Ask for a Free Breach-Readiness Review
Not sure what your team is already pasting into AI? Email support@farmhousenetworking.com to request a free breach-readiness review. It includes a policy review, basic penetration testing, and a network inventory, with written deliverables in about one week.
Next week: How to Get Breached, Step 6: Share Files However Is Fastest.
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?
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.
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.
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.
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.
What Every Small Business Owner Needs to Know Before June 3 — Even If You’re Not a Bank
The SEC’s updated Regulation S-P sets a new standard for data protection that every small business owner needs to understand — not just financial firms. Is your incident response plan ready?
A practical guide to the new cybersecurity standard that financial regulators are enforcing — and that your customers, partners, and insurers are already expecting.
Why June 3 Should Be on Your Radar
On June 3, 2026, smaller SEC-regulated financial institutions, investment advisers, broker-dealers, and similar firms, hit their final compliance deadline under the SEC’s updated Regulation S-P. After 20+ years without a major update, the SEC overhauled how these businesses must protect customer data, respond to breaches, and oversee their technology vendors.
So why does this matter to you as a small business owner outside the financial sector?
Because the requirements the SEC is now enforcing represent the new normal for data protection across all industries. Your cyber liability insurance carrier already asks about these controls. Your enterprise clients are putting them in vendor agreements. Your customers assume you have them. And regulators in healthcare, retail, and professional services are moving in the same direction.
This is your roadmap – not just for compliance, but for running a business that customers can trust.
What Regulation S-P Requires (and What It Means for You)
The six pillars of the SEC’s updated data protection framework – applicable in spirit to every business handling customer information:
Incident Response Program – A written, tested plan for what happens when you’re breached. Not if. When.
30-Day Breach Notification – Customers must be notified quickly. Waiting weeks or months is no longer acceptable to regulators or the public.
Vendor Oversight – If a third-party vendor can access your customer data, you are responsible for their security practices.
Secure Data Disposal – Customer information must be destroyed securely when no longer needed.
Written Recordkeeping – You need to be able to prove you have a program, not just claim it.
Practical Action Steps for Your Business
For You, the Business Owner
Identify what sensitive customer data you hold, credit cards, SSNs, health information, financial records, and where it lives.
Review your cyber liability insurance policy for coverage gaps and required controls.
Audit your vendor relationships: which ones can access your customer data, and do they have security obligations in writing?
Designate someone, internal or external, responsible for cybersecurity decisions and incident response.
Draft a customer breach notification letter template now, before you need it.
For Your IT Department or Provider
Perform a full security assessment covering endpoints, cloud accounts, email, and network access.
Implement multi-factor authentication on every system – this alone stops 99% of credential-based attacks.
Establish and test an encrypted, off-site backup routine.
Write and test an Incident Response Plan – including who to call (legal, insurance, IT forensics) and in what order.
Update vendor contracts to include explicit security requirements and breach notification timelines.
Implement a data retention and secure disposal policy.
Document your security controls in writing – for insurance audits, client questionnaires, and regulatory inquiries.
Questions Your Customers and Partners May Ask
Q: How do you protect my personal information when I do business with you?
A: We use encrypted storage, access controls that limit who can view customer data, and multi-factor authentication for all staff. We also have a written security policy and an incident response plan in place.
Q: What happens if you experience a data breach? Will I be told?
A: Yes. If your information is involved in a breach, we are committed to notifying you promptly – within 30 days of discovering the incident. We have a documented notification process ready.
Q: Our company requires vendors to meet certain cybersecurity standards. Do you comply?
A: We have a written security program, documented controls, and an incident response plan. We’re happy to provide documentation and answer your vendor security questionnaire.
Q: I heard new SEC rules are tightening cybersecurity requirements. Should I be worried about businesses I work with?
A: It’s a fair question. The SEC’s updated Regulation S-P has raised the bar for financial firms, and similar standards are spreading across industries. We’ve proactively aligned our security practices with this framework — and we work with Farmhouse Networking to maintain and demonstrate compliance.
How Farmhouse Networking Helps Small Businesses
Farmhouse Networking is a Managed IT Services provider built for small and mid-sized businesses that take data protection seriously but don’t have an in-house IT team. We make enterprise-grade security practical and affordable:
Security Assessments – We evaluate your current posture and give you a prioritized action plan, not a list of scary jargon.
Incident Response Planning – We write your IRP, help you test it, and make sure your team knows what to do under pressure.
Vendor Security Reviews – We assess the tools and platforms you rely on and flag gaps in your vendor agreements.
MFA, Encryption, and Endpoint Protection – Deployed correctly, documented thoroughly.
Compliance Documentation – We produce the written records that satisfy insurance carriers, enterprise clients, and regulators.
Ongoing Managed IT – We become your IT department, watching your systems so you can run your business.
Ready to Get Compliant? Let Farmhouse Networking Help.
Don’t wait for a breach to take cybersecurity seriously. Email us today for a free SMB security assessment: support@farmhousenetworking.com
You don’t have to be a Fortune 500 company to be a target. You just have to be open for business.
Cybercriminals no longer need technical skills to target your business — Fraud-as-a-Service puts sophisticated attack tools in anyone’s hands.
You’ve heard of Software-as-a-Service. Now meet its criminal counterpart.
Fraud-as-a-Service (FaaS) is a booming underground economy where cybercriminals sell ready-made attack tools, stolen credentials, phishing kits, and ransomware packages to anyone willing to pay a subscription fee. No technical skill required. No barriers to entry. Just a dark web account and criminal intent.
This new economy lowers the barrier for entry and accelerates the pace of attacks. Even young and inexperienced fraudsters can access sophisticated tools that can be deployed with minimal technical knowledge. The result? A surge in attacks aimed squarely at small and mid-sized businesses — businesses exactly like yours.
In 2025, the FBI received over one million cybercrime complaints for the first time ever. Cyber-enabled fraud accounted for $17.7 billion in total losses. And small businesses are absorbing a disproportionate share of the damage.
Why Your Business Is the Target
Large corporations have security teams, compliance officers, and dedicated budgets. You have a team wearing multiple hats and a firewall that hasn’t been updated since the last administration.
Criminals who used to target only large enterprises now see small businesses as easier prey — because many don’t think they’re targets and often lack the protections to defend themselves.
FaaS attacks against SMBs typically arrive as:
Business Email Compromise (BEC): A convincing email, apparently from your bank or a vendor, redirects a payment to a criminal’s account.
Phishing kits: Pre-built fake login pages that steal employee credentials in seconds.
Ransomware subscriptions: Criminals rent ransomware, deploy it against your files, and split the ransom with the developer.
AI-generated deepfakes: Voice or video impersonations of you or your staff, used to authorize fraudulent transfers.
Business Email Compromise alone generated over $3 billion in losses in 2025.
Practical Action Steps for You and Your IT Team
Enable Multi-Factor Authentication (MFA) on everything — email, banking portals, cloud tools, and remote access. This one step blocks the majority of credential-based attacks.
Conduct a phishing simulation and security awareness training with all staff at least twice per year.
Verify all payment change requests by phone using a known number — never by replying to the email that requested the change.
Audit your email environment for misconfigured permissions, stale accounts, and unusual forwarding rules.
Review and restrict vendor and third-party access to your systems on a quarterly basis.
Maintain tested, offline data backups so ransomware cannot encrypt your only copy.
Create an incident response plan — a written document that tells your team exactly what to do if an attack succeeds.
Questions Your Clients May Ask You
“How do I know my data is safe with you?” You should be able to describe exactly where client data is stored, who has access, and what protections are in place. If you can’t answer this with confidence, it’s time to find out.
“Has your business ever experienced a data breach?” Transparency builds trust. If the answer is yes, explain what happened and what changed afterward.
“What would happen to my files if you got hit with ransomware?” Your answer should include a clear backup and recovery plan with a defined recovery time.
“Do your employees know how to recognize a phishing attempt?” This should be a confident yes — backed by regular training, not just a one-time onboarding video.
How Farmhouse Networking Helps
Farmhouse Networking helps SMBs build the defenses that FaaS criminals count on you not having. From setting up MFA and email authentication, to proactive monitoring, security awareness training, and incident response planning — we make enterprise-grade protection practical for businesses your size.
Ready to Stop Being an Easy Target?
Email us at support@farmhousenetworking.com to schedule a free security consultation. We’ll show you exactly where you’re exposed — and how to fix it before someone else finds out first.
That AI tool looked affordable in the demo. Here’s what most small business owners discover after the first real invoice.
You signed up for a sleek AI tool. The demo was impressive. The monthly price seemed reasonable. Then three months later you’re staring at a vendor bill that’s twice what you expected, your team is still confused about how to use the software, and you’re not sure who owns the data you’ve been feeding into it.
If that sounds familiar, you’re not alone. According to a 2025 Fortune analysis, the advertised price of AI automation represents only 20–40% of the true first-year cost for most small businesses. The rest hides in plain sight — buried in data preparation, staff training, integration fees, security gaps, and consumption-based pricing that scales faster than your revenue does.
AI tools promise to save you money. But are they quietly spending it instead? Here’s what every business owner needs to know before the next invoice arrives.
What the Brochure Doesn’t Tell You: The 6 Hidden Costs of AI
1. Data Cleanup Costs: Before AI can do anything useful, it needs clean, structured data. Most businesses discover their records have duplicate entries, inconsistent formatting, or files locked in formats the AI can’t read. Getting data “AI-ready” commonly costs $1,000–$10,000 and is rarely mentioned upfront.
2. Consumption-Based Billing Surprises: Many AI tools — including Microsoft Copilot, ChatGPT, and Salesforce Agentforce — charge by usage (tokens, conversations, or seat upgrades). A 2025 Zylo survey found 78% of IT leaders reported unexpected charges from consumption-based AI pricing. The more your team uses the tool, the higher the bill climbs, often mid-contract.
3. Integration Expenses: Plugging an AI tool into your existing systems — your accounting software, CRM, email platform, or operations tools — typically costs 30–50% of your total AI budget on top of licensing fees. Legacy systems make this worse, adding another 30–50% to integration costs.
4. The Productivity Dip (The J-Curve): Staff productivity typically drops 15–25% for 3–6 months after an AI tool is introduced. Workflows change. People need training. Mistakes happen. This “J-curve” is a real cost that hits your output before the benefits kick in.
5. Ongoing Maintenance and Monitoring: AI tools don’t run themselves. They need updates, performance monitoring, and occasional retraining. Industry estimates put annual AI maintenance at 15–30% of the original implementation cost — every year.
6. Security and Compliance Gaps: When employees use unsanctioned AI tools — what experts call “shadow AI” — your data goes places you haven’t approved. This creates real liability, especially if you handle any customer financial, health, or personal data.
What You and Your IT Team Should Do Now
Audit every AI tool currently in use — sanctioned or not. Shadow AI is a real and growing problem.
Review your vendor contracts for consumption-based pricing clauses and usage caps.
Assess your data quality before adding any new AI tool. Budget time and money for cleanup.
Map out how each AI tool connects to your existing systems and what it costs to integrate.
Train your team with structured onboarding — not just a login link.
Set a usage policy that defines which AI tools are approved and what data can be shared with them.
Schedule quarterly AI cost reviews so billing surprises don’t compound.
Work with your IT provider to conduct a security review of all AI platforms you’ve adopted.
Questions Your Clients or Team May Ask You
Q: Is it really that expensive? The tool only costs $30 a month.
A: The license is just the entry fee. Once you add integration, training, data cleanup, and monitoring, that $30/month tool commonly becomes $300–$500/month in real total cost. Budgeting for only the license is the most common AI financial mistake small businesses make.
Q: Can’t we just let employees figure it out on their own?
A: Research shows that organizations with unstructured AI adoption see double the training costs and far lower ROI. Worse, employees who figure it out on their own often use unapproved tools that create security and compliance exposure.
Q: What happens if we don’t address the security side?
A: Unsanctioned AI usage has been linked to data breaches that add an average of $200,000 to breach costs, according to IBM’s 2025 Cost of a Data Breach report. For a small business, that’s potentially company-ending exposure.
Q: How do we know if our AI investment is actually paying off?
A: You need to measure specific KPIs before and after AI adoption — things like hours saved per week, error rates, and customer resolution times. Without baseline data, ROI is invisible.
How Farmhouse Networking Can Help
Farmhouse Networking specializes in helping SMBs navigate exactly these kinds of IT cost pitfalls. Our local team can help you:
Conduct a full AI tool audit to identify shadow AI and hidden spend across your organization.
Review your vendor contracts and consumption-based pricing to protect you from billing surprises.
Assess data readiness so you’re not paying for expensive data cleanup after the fact.
Build a secure AI governance policy so your team knows what’s approved, what’s not, and why.
Provide proactive IT monitoring that catches cost and security issues before they become crises.
Ready to Find Out What AI Is Really Costing You?
Don’t wait for the surprise invoice. Send us a message and we’ll schedule a free AI cost and security review for your business. We’ll show you exactly where you stand — no obligation, no jargon, no pressure. Email us today: support@farmhousenetworking.com
Use DNS Filtering to Stay Safe and Open for Business
DNS filtering helps small business owners block AI powered social media scams before employees can reach malicious websites
AI tools now let scammers quickly generate deepfake videos, realistic ads, and convincing phishing messages that target small and mid‑sized businesses on social media. These attacks trick employees into clicking malicious links that steal logins, install ransomware, or divert payments, and incident rates and losses are climbing. DNS filtering offers your business a practical, affordable way to block dangerous sites at the network level before a bad click turns into downtime.
Why AI-Driven Social Media Threats Matter for SMBs
AI deepfakes and fake ads can impersonate your brand or suppliers and lead to look‑alike scam sites.
AI-enhanced phishing leverages details from your website and social media to sound like real customers, partners, or executives.
Web‑based phishing and spoofing attempts are rising sharply year over year, driven by generative AI.
What DNS Filtering Does for Your Business
DNS filtering checks where your employees’ devices are trying to connect and blocks known or suspected malicious domains. For SMBs, this:
Prevents access to phishing pages and fake login screens linked from social media or email.
Reduces malware and ransomware risk by blocking communication with malicious servers.
Gives you visibility into risky browsing and helps enforce acceptable‑use policies.
Action Steps for Business Owners and IT
Document where and how your team uses social media for sales, support, and marketing.
Roll out DNS filtering to office networks, remote workers, and any company‑managed laptops or phones.
Integrate DNS filtering logs with your security monitoring to quickly investigate suspicious activity.
Establish a clear process for verifying unusual requests (wire transfers, password resets, gift card purchases) received via social media or email.
Sample Customer Questions and Answers
“Is it safe to click promotions I see about your business on social media?” We recommend visiting our official website or verified profiles directly, because scammers can create fake ads that lead to malicious sites.
“How do you protect my data from online scams?” We use layered security including DNS filtering to block malicious websites, alongside secure payment providers and strong internal controls.
How Farmhouse Networking Helps SMBs
Farmhouse Networking works with you to understand your business, social media use, and risk tolerance, then designs and manages a DNS filtering solution that fits your size and budget. We deploy, configure, and monitor the service, fine‑tune policies over time, and provide clear reports so you always know how your network is being protected. This is included at no additional cost to all our monthly managed IT services clients.
Call to Action: Email support@farmhousenetworking.com for more information about how Farmhouse Networking can help improve your business and defend against AI‑driven social media threats.
A small business owner working with their IT partner to prepare a CIRCIA‑ready cyber incident response plan.
Many small and midsize business owners assume CIRCIA is aimed only at Fortune 500 companies, but that is a risky assumption. Small and mid‑market organizations can be “covered entities” if they provide critical services or support critical infrastructure, and even those outside scope will feel the ripple effects through clients, insurers, and vendors.
CIRCIA in a Nutshell
CIRCIA (Cyber Incident Reporting for Critical Infrastructure Act) requires covered entities to report substantial cyber incidents to CISA within 72 hours.
Ransomware payments must be reported within 24 hours.
Coverage is based on critical infrastructure role, not just size; small entities can be included if their disruption would impact national or regional security, economy, or public health.
Even if you are not covered, your larger customers and partners may require you to meet CIRCIA-like standards to stay in their supply chain.
Concrete Steps for Owners and IT Teams
Owner-level actions:
Determine your exposure: Identify whether you operate in or support critical infrastructure sectors (healthcare, energy, transportation, government services, etc.).
Review contracts and insurance: Look for new clauses about cyber incident reporting, cooperation, and timelines.
Fund the basics: Approve budget for security monitoring, backups, and an incident response plan; these are now business necessities, not IT “nice‑to‑haves.”
IT / MSP actions:
Perform a security and asset inventory: Know what you have, where it is, and how it is protected.
Implement monitoring and logging: Centralized logs and alerts are essential to detect and investigate incidents fast enough for 72‑hour reporting.
Develop and test an incident response plan: Include decision trees for when to treat an incident as “substantial,” who to notify, and how to collect evidence.
Prepare for CISA reporting, even if “not covered”: Templates and processes for structured incident documentation will help with insurers, regulators, and major customers.
Questions Your Customers May Ask – Answer Set
“Are you compliant with CIRCIA?”
We have implemented incident detection, response, and reporting processes aligned with CIRCIA expectations, and we support our critical-infrastructure customers with the evidence they need.
“If a cyber incident hits you, how will it affect us?”
We maintain backups, response playbooks, and communication plans aimed at minimizing downtime and providing transparent updates.
“Will you tell us quickly if our data is involved?”
Yes. Our procedures require rapid notification to affected customers and support for any regulatory or contractual reporting they must perform.
How Farmhouse Networking Helps SMBs Turn CIRCIA into an Advantage
Farmhouse Networking helps small and midsize businesses use CIRCIA as a catalyst to get modern, business-grade cybersecurity in place:
Determining whether your business or key customers are likely covered entities and what that means for your contracts and obligations.
Implementing security controls—MFA, EDR, monitoring, backups, segmentation—that both reduce incident likelihood and support fast, evidence-based reporting.
Building, documenting, and testing an incident response and communication plan tuned to 72‑ and 24‑hour windows.
Acting as your ongoing IT and security partner so you can answer customer and regulator questions with confidence.
Call to action: Email support@farmhousenetworking.com to find out how Farmhouse Networking can help your small business prepare for CIRCIA and improve your overall cybersecurity resilience.
How to Take Back Control of Your Credentials and Phones
When an MSP controls your passwords and phone system, your entire small business can be held hostage by vendor lock‑in and security risks.
If your MSP controls all your admin passwords and has your phone service in their name, they effectively hold the keys to your entire business. In a dispute, a security incident, or even an acquisition of their company, you could find yourself locked out of critical systems that drive revenue and customer service.
The Real Dangers of MSP Lock‑In
Some providers refuse to release credentials or slow‑roll off‑boarding, forcing clients into “hostage” situations that require legal escalation or aggressive technical takeovers. At the same time, attackers increasingly target MSPs because one compromised technician account can reach many customers’ environments.
When your phone system is outdated or fully tied to that MSP, you pay more each year for less functionality, struggle with remote work, and depend on them for every change. The combination of technical dependence and credential lock‑in is a business‑continuity risk you can’t afford to ignore.
Action Steps for Owners and Their IT Teams
Reassert ownership of core assets
Ensure your company owns master accounts for email, cloud services, line‑of‑business apps, domains, DNS, and phone numbers, with internal admin rights documented.
Centralize credentials in a business‑owned vault
Use a secure password manager or encrypted repository where your business controls the master key and you grant time‑bound, role‑based access to MSP staff.
Implement strong identity and access controls
Enforce MFA everywhere, require strong unique passwords, and use least‑privilege and role‑based access so no external user has unchecked power.
Build clean exit ramps into contracts
Document how credentials, documentation, and phone services will be handed back, and set deadlines and formats for off‑boarding deliverables.
Prepare for the worst‑case scenario
Maintain independent backups, keep an internal “break‑glass” account, and have a written playbook for revoking vendor access and rotating credentials quickly.
Questions Your Customers May Ask
Q: Could your IT company access or leak my data? A: We control the master credentials and use MFA, logging, and access controls so any vendor only has tightly scoped, monitored access to what they need to support us.
Q: What happens if your IT provider is hacked? A: We follow best practices for identity security, vendor risk management, and backups so a single compromised account at an MSP cannot easily cascade into your data.
Q: Are you able to stay operational if you change IT providers? A: Yes—because we own our accounts and phone numbers and have a documented exit process, we can transition providers while keeping systems and support running.
How Farmhouse Networking Helps SMBs
Farmhouse Networking works with business owners to document every critical system, transfer licensing and phone services into the company’s control, and consolidate credentials into secure, business‑owned vaults. We then implement MFA, break glass accounts, role‑based access, and incident‑response plans so neither a single technician nor an MSP relationship becomes a single point of failure.
We can also help you renegotiate or replace MSP contracts with clear off‑boarding terms and test those processes before you ever need them in an emergency.
Email support@farmhousenetworking.com to make sure no MSP can ever hold your credentials, phones, or business hostage again.
What Small Business Owners Need to Know About Health Plans and IT Risk
Small business leaders and IT teams should review how the 2027 NBPP proposed rule will change employee health plans, compliance requirements, and data security.
The 2027 NBPP proposed rule, issued February 11, 2026, will reset key rules for ACA Exchanges and small‑group health plans starting in 2027. As a small or mid‑sized business owner, these changes affect your benefit strategy, your HR workload, and the IT systems that support them.
Big Picture: What’s Changing
Catastrophic and some bronze plans can carry significantly higher out‑of‑pocket maximums, shifting more financial risk to employees.
CMS proposes multi‑year catastrophic plans and broader hardship exemptions, making catastrophic coverage more common among workers who cannot or do not enroll in richer plans.
Agents, brokers, and web‑brokers must use standardized HHS‑approved consent and eligibility review forms, creating more structured documentation.
Certain state‑mandated benefits will be treated as “in addition to” Essential Health Benefits, affecting plan design and cost structure.
Concrete Action Steps for Owners and IT
For the business owner/CEO:
Reevaluate your health benefits package
Ask your broker which 2027 plan designs they expect to offer and whether your team could be pushed toward higher‑OOP bronze or catastrophic options.
Model the total compensation impact if benefits become less generous and consider offsetting with stipends, HRAs, or plan upgrades.
Upgrade HR policy and employee education
Provide clear, written explanations of how deductibles, out‑of‑pocket maximums, and catastrophic coverage work under the new rules.
Set expectations about documentation employees should keep (especially standardized federal consent and eligibility forms tied to subsidies).
For your IT department or MSP:
Prepare your systems for new standardized forms and proofs
Ensure HRIS, payroll, and document systems can accept, tag, and secure HHS‑approved consent and application review forms your broker will use.
Build simple workflows for HR to retrieve this documentation during audits, disputes, or employee questions.
Tighten security around benefits and PHI‑adjacent data
Implement strong identity and access management, encryption, logging, and vendor controls for any system that touches health coverage or subsidy information.
Confirm that contracts with benefits platforms, brokers’ portals, and HR tools reflect updated privacy and security expectations.
Likely Employee Questions – And How to Answer
“Why did my maximum out‑of‑pocket jump so much?”
Under the 2027 NBPP, some bronze and catastrophic plans are allowed to exceed prior out‑of‑pocket caps, which can significantly increase your financial exposure if you get sick or injured.
“What are these new standardized forms from the broker?”
Federal rules now require standardized HHS‑approved consent and eligibility review forms to document the accuracy of your application and protect your subsidy eligibility.
“Are all state‑mandated benefits still fully covered?”
Not always; certain state‑required benefits are treated as outside the core Essential Health Benefits package, which may affect how they’re funded and covered.
How Farmhouse Networking Helps SMBs
Farmhouse Networking partners with small and mid‑sized businesses to turn regulatory change into structured, low‑friction processes:
Integrate new federal consent and eligibility documentation into your HR and document‑management stack, so HR can find what they need in seconds.
Implement or enhance cybersecurity controls around benefits, payroll, and identity data to reduce risk as health coverage documentation becomes more standardized and audit‑friendly.
Coordinate with your broker and benefits platforms so technical changes (new forms, new plan designs) are reflected cleanly in your systems with minimal disruption.
Call to Action Email support@farmhousenetworking.com to get a focused assessment of how the 2027 NBPP proposed rule intersects with your benefits, IT, and employee experience – and a concrete plan to get ahead of it.
Essential network firewall for business setup—safeguard your SMB cybersecurity today.
Cyberattacks hit 43% of SMBs last year—costing time and revenue. A network firewall changes that, acting as your business’s frontline defense. Unlock practical insights to protect operations and grow confidently.
The Power of Network Firewalls for SMBs
Firewalls monitor traffic, blocking malware, hackers, and data leaks at the network edge. Ideal for email servers, cloud apps, and remote work, they provide visibility basic antivirus misses.
SMB breaches average $25,000-$100,000; firewalls reduce risks by 75%.
Hands-On Setup Steps
Guide your IT with this roadmap:
Inventory Assets: List devices, apps; identify weak points.
Choose SMB-Friendly Firewall: Next-Gen Firewalls (NGFWs) like Ubiquiti or Araknis—easy, affordable.
Apply Baseline Rules: Block common exploits; enable web filtering.
Deploy Monitoring: Use alerts and reports for proactive defense.
Common SMB Questions Answered
Q: DIY or professional install? A: DIY for basics; pros for complex setups.
Q: Cloud or on-premise? A: Cloud for scalability; on-premise for control.
Q: Impact on speed? A: Negligible with modern hardware.
Q: Ongoing costs? A: $1,000-$5,000/year, offset by risk reduction.
Let Farmhouse Networking Handle It
We specialize in SMB firewall deployments, from assessment to management—driving secure growth for businesses like yours.
Implementing CIS Controls helps small businesses safeguard sensitive data and comply with regulations.
Data breaches can devastate small businesses, but CIS Controls give you a proven path toward robust data protection and regulatory compliance—without breaking the bank. Here’s how any business owner can get started today.
Practical Action Steps
Survey business data assets: Identify your key customer, employee, and business records and where they’re stored.
Classify business data: Assign “Public,” “Internal,” or “Sensitive” tags and limit who can access the most critical files.
Secure device and network configurations: Change default passwords, apply updates, and enable firewall protection.
Monitor and review: Turn on audit logs for key systems; routinely check logs for odd access.
Automate backups and test restores: Protect against ransomware and disasters with offsite, automatic backups.
Educate your team: Organize short trainings so every employee knows cybersecurity basics and your incident response plan.
Frequently Asked Client Questions
Q: Will CIS Controls help with industry regulations (GDPR, CCPA, etc.)? A: Absolutely! CIS Controls support the foundation of compliance for most data protection laws worldwide through access management, encryption, and monitoring.
Q: How much time and expertise does this take? A: With Farmhouse Networking, most controls are easy to implement—even for non-technical teams. We guide you step by step so your team is protected without added stress.
How Farmhouse Networking Can Help
Farmhouse Networking sets up CIS Controls for any SMB: from asset tracking to secure data access, backup management, and employee training. We implement everything, making compliance and security easy and effective for your business.
Call to Action
Protect your business and comply with regulations. Email support@farmhousenetworking.com to connect with our team and get started.
Secure Your Business Future: Enterprise Asset and Software Configuration for Today’s SMBs
A small business owner implements security configuration for business devices and software as part of IT best practices.
Small to mid-sized business owners face the same cyber dangers as Fortune 500 companies. Misconfigurations can open the door to data theft, financial loss, and operational chaos. Secure configuration of every company asset and software is a non-negotiable step in your risk management plan.
Practical Steps for SMBs
Inventory all hardware, mobile devices, and software—no asset is too small to track.
Apply baseline security configurations using global standards, such as CIS Benchmarks and NIST guidelines.
Schedule regular patching and enforce automatic updates.
Limit admin access, enforce strong authentication, and document all configuration changes.
Uninstall anything not needed and disable unused network ports and services.
Encrypt sensitive business data transmissions and use secure protocols for all connections.
Monitor for any changes or vulnerabilities with automated tools.
Client Q&A
Q: Is this overkill? We’re not a bank. A: Basic misconfigurations fuel most breaches, regardless of company size. A secure foundation keeps your doors open and customers confident.
Q: How do I make sure this is all kept up to date? A: Farmhouse Networking offers managed services that maintain and audit your configurations, ensuring nothing slips through the cracks.
How Farmhouse Networking Can Help
Farmhouse Networking is your partner in building, managing, and auditing secure configurations for all your business assets. Trust us to streamline processes, improve productivity, and safeguard data.
Small business security strengthened with CIS account management controls
Small business owners face evolving security threats and regulatory obligations. Implementing CIS Account Management Control is key to protecting data, assets, and reputation.
Practical Steps for SMBs
Catalog All User and Service Accounts: Record names, departments, and account activity for every user and automated process.
Use Strong and Unique Passwords: Demand complex passwords, rotate them annually, and use MFA whenever possible.
Disable Dormant Accounts: Purge inactive accounts every 45 days for better security hygiene.
Limit and Monitor Admin Privileges: Assign admin roles sparingly and monitor usage.
Centralize Account Oversight: Deploy a directory or identity manager for simplified user management and audit trails.
Questions & Answers
Q: What’s the biggest risk of poor account management? A: Unauthorized access can lead to financial loss, data breach, or legal liability—CIS controls dramatically reduce this risk.
Q: Does this require expensive software? A: Many tools, such as Microsoft Active Directory, are affordable and scalable for SMBs. CIS controls guide you in choosing solutions that fit your needs.
How Farmhouse Networking Helps
Farmhouse Networking guides SMBs through creating robust account management policies, deploying affordable directory services, and training your team for optimal cyber hygiene.
Call to Action
Start protecting your business today—email support@farmhousenetworking.com to learn how CIS controls can boost your cybersecurity.
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.