Why These Two Controls Still Dominate Outcomes
Threat reports change names every quarter. The SMB failure pattern does not: an attacker phishes or buys a password, lands in email or VPN without MFA, escalates, and then deletes or encrypts online backups before ransomware hits production. If you only fund one security sprint this fall, make it identity hardening and immutable recovery. Cyber insurance underwriters increasingly ask for evidence of both—not just a policy PDF.
MFA That Survives Real Attacks
“We have MFA” often means some users get SMS codes while global admins still allow legacy protocols. Attackers exploit MFA fatigue prompts, SIM swaps, and help-desk reset social engineering. Aim for coverage that is boring and complete:
Enforce MFA for every interactive cloud and remote-access login, with no legacy auth exceptions for mail protocols.
Prioritize admins for app-based or phishing-resistant methods (authenticator apps, hardware keys) over SMS.
Separate privileged identities from daily mailboxes so a compromised inbox does not equal domain control.
Monitor MFA reset and Conditional Access changes as high-signal events your MSP should alert on.
Pair MFA with session revocation playbooks: when a mailbox is compromised, you need a scripted path to kill tokens, rotate passwords, and review inbox rules that forward mail to attackers. That operational muscle matters as much as the checkbox.
Immutable Backups: Recovery the Attacker Cannot Edit
Online backup repositories reachable with the same admin credentials as production are not a ransomware strategy. Immutability—or write-once / retention-lock periods—means even a compromised backup console cannot silently purge history during the retention window. Combine that with the classic 3-2-1 pattern: three copies, two media types, one off-site or logically air-gapped.
Questions Underwriters and Boards Ask
Who can shorten or disable retention locks, and is that change dual-controlled?
When was the last successful restore of a critical system, and how long did it take?
Are Microsoft 365 and SaaS data included, or only on-prem servers?
Would a weekend ransomware event leave you negotiating with criminals for the only copy?
If answers are vague, treat October as the deadline to schedule a restore drill and document results. Screenshots of “last successful job” are not the same as a timed recovery of a real workload.
How the Pair Works Together
MFA shrinks the chance of silent takeover. Immutable backups shrink the blast radius when takeover still happens—through a zero-day, a trusted vendor, or an insider mistake. Neither control replaces patching, EDR, or email security; together they stop the most common path from “phish” to “business-ending outage.”
For distributed teams, these controls travel well. Identity is already cloud-centric. Backup immutability and restore testing can be run by a remote operations team without standing in your server room. That is why national
remote managed IT programs put MFA and backup verification on the same monthly scorecard as ticket SLAs.
What BitBlockIT Implements
We align Conditional Access and MFA policies with least privilege, then design backup stacks with retention locks and scheduled restore evidence your leadership—and your insurer—can read. Explore
cybersecurity services alongside remote managed IT so monitoring, identity, and recovery are not three disconnected vendors.
Take Action This Month
Ask for an MFA coverage export and a dated restore report before the next board or insurance renewal conversation. Ready for a partner that executes nationally?
Review remote managed IT,
request a risk assessment,
book a demo, or
contact BitBlockIT to close the two doors attackers still walk through most often.