- ZDNET's pick for the best robot vacuum and mop is $300 off for a limited time
- Every iPhone model compatible with Apple's iOS 18 (and which ones aren't)
- Dice: 60% more tech pros lost jobs in 2024 vs 2023
- One of the best tablets for work travel I've tested is not made by Microsoft or Lenovo
- I changed these 5 soundbar settings for a better TV viewing (and audio) experience
Beware the tools that can bring risk to a Windows network
Limit access and federation between on-prem and cloud
One should limit access and federation between on-premises and cloud assets where one can. Yes, we’ve built up reliance on this ability to share data and authentication between cloud assets and on-premises, but too often it’s also introducing weaknesses.
A recent ProPublica article claims that a whistleblower pointed out these risks to Microsoft years before attacks based on them occurred. While the SolarWinds supply chain attacks were the entry points, it was misuse of Active Directory Federation Services that allowed attackers to gain more access. Thus understand the risk involved and add more monitoring resources to review authentication processes.
Finally, if you’ve been a customer of Microsoft 365 for a while, and you haven’t reviewed your security defaults and settings, it’s now time to review those settings. From Microsoft to the Center for Internet Security, various entities have updated and revised benchmarks over the years. Some benchmarks have more manual steps and some are more automated.