Unvarnished notes on the security misconfigurations, backup gaps, and vendor reassessments we run for Minnesota businesses every week. Written for the people signing the checks, not the people holding the certs.
After years of Microsoft 365 evaluations, the same three problems show up every time: wide-open permissions, incomplete MFA, and factory-default security settings. Here is the playbook we use to fix them.
Read the DispatchSorted most recent first.
Hackers hit more than 30 Minnesota water systems in one weekend, including Plymouth. Here is what is publicly known, what is not, and what we would check this week.
ReadSecure Score is the first number we pull in every tenant audit, and the same handful of low-effort, high-impact fixes are missing almost every time.
ReadYour MSP keeps the lights on. That is not the same discipline as detecting and responding to an active attacker — and pretending otherwise is how breaches happen.
ReadEvery Microsoft 365 tenant we evaluate has the same three problems: wide-open permissions, incomplete MFA, and factory-default settings.
ReadMicrosoft's position is explicit: it's your data, it's your responsibility to protect it. Recycle bins, version history, and retention policies are not backup.
ReadWe had contracts. Our people were trained on it. We replaced it anyway. Here is what happened after we layered in Huntress for a side-by-side test.
ReadWe work with Minnesota businesses. Tell us what you are running and what is hurting, and we will tell you what we would change.