Common Risks - March 2026 Edition

Written by FENCECORE FRANK | Mar 11, 2026 2:35:18 PM
This March update builds on our February “Common Cyber Risks” post and shows how the risk picture is shifting as AI and vendor dependencies grow.
 
 
Small Business - (3-25 users)
 
Threats are getting smarter and faster. Criminals now use AI to write convincing phishing emails, fake voices, and large‑scale scams. This raises the chance that a busy staff member will click, reply, or pay. Many small companies still lack cyber insurance, which means one incident can become a major cash‑flow crisis.

Start with the basics that block the most attacks. Turn on multi‑factor authentication for email, VPN, and admin accounts. Roll out endpoint detection and response. Patch monthly. Test your backups and keep at least one copy offline. Run short, frequent phishing drills and teach staff how to verify requests that involve money or data. Look beyond your four walls. Map your key vendors and the data they hold. Ask them about MFA, backups, and incident response. A vendor outage or breach can stop your work even if your own systems are fine.

Build a simple playbook: who to call, what to shut off, and how to talk to customers if something happens.
Finally, set rules for AI use. If staff are pasting sensitive data into public tools, restrict it now. Limit access, restrict data, and add human checks for important decisions. Small, steady steps in people, process, and tools will reduce risk fast—and cost far less than cleaning up a major incident.
 
 
Medium - (26-99 users)
 
Mid‑sized organizations face more incidents as they add cloud apps, vendors, and AI tools. Over the last year, mid‑market firms made up the largest share of cyber claims, showing how exposure grows with scale. At the same time, many teams report skills gaps in AI governance and data handling, which makes it harder to spot issues early and respond fast.

Focus on attack paths you can control today. Enforce MFA everywhere, especially for admins and remote access. Segment critical systems and restrict service accounts. Monitor for unusual logins and large data movement.
Test recovery quarterly, not yearly. Include “what if our SaaS or cloud goes down?” in drills, because outages and vendor problems can spread quickly across customers.
 
Watch for AI‑specific risks. Prompt injection, data poisoning, and automated social engineering can bypass old playbooks. Add AI scenarios to tabletop drills and make sure business leaders join. Review contracts with key vendors for security controls, breach notice times, and backup commitments. Tie these checks to your risk register so they don’t get lost.
Finally, align security and IT with teams rolling out AI. Require human approval for sensitive actions like payments or data exports. These steps cut risk without slowing the business.
 
 
Large - (99+ users)
 
For large enterprises, the biggest cyber risk now comes from how systems connect. AI agents, data pipelines, and third‑party services create complex webs. When one piece fails, the impact can ripple across teams and regions. Recent industry analysis stresses that risk often comes from the overall system, not just the model.
 
Cloud and vendor outages have also shown how a single event can hit many customers at once, so resilience now depends on planning for these “shared” failures. Update your risk lens. Map critical dependencies—identity, DNS, cloud regions, core SaaS, and major data flows. Set recovery targets by system. Add chaos tests and vendor failover drills. Require stronger tenant isolation, private connectivity, and backup strategies for crown‑jewel apps.
 
Governance must keep pace. AI is part of many enterprise strategies, but full governance is still rare. Close that gap with standard patterns: human‑in‑the‑loop for money moves and access changes, prompt/agent testing, and independent review for high‑risk use cases. Expand incident response to include AI failures, model rollback, and data‑handling mistakes. Add fraud and comms teams to the table. Track leading indicators: privileged login anomalies, large data exports, and sudden changes in agent behavior—paired with business metrics like orders per hour. The sooner you see drift, the smaller the blast radius.