Windows Hello for Business- Goodbye to Passwords

Akins IT • July 12, 2018
Connect with us

Windows has come a long way since the breach-prone Windows XP era of computing. Microsoft continues to show its commitment as a security-first company with Windows 10. No longer are the days that a hacker can use a Pass-The-Hash attack when features like Windows Hello for Business are enabled on end points.


Take the current state of a password: It’s meant to authenticate the user’s identity to a network or a service. That password is stored on a hosting server, hopefully with tightened security in place like encryption or password hashing. And yes, even when these measures are in place, passwords are susceptible to breaches by man in the middle attacks, compromised servers, and end-user password phishing – by far the most common.


Microsoft attempts to resolve this problem with Windows Hello for Business. Leveraging modern built-in TPM chips, Windows 10 can provide a quicker login and a Seamless Single Sign On experience to the end user, eliminating the burden of traditional passwords.


Windows Hello for Business takes two keys, one public and one private, to authenticate. It’s known as an Asymmetric Approach. The public key is stored in the cloud, in our instance, Azure AD. The private key is safely locked in the TPM chip, only accessible when a user provides their sign-in gesture at login. This results in an authentication token request by the computer from Azure AD in cloud only environments.

I’ll leave you with my favorite feature incorporated into Windows Hello For Business: Dynamic Lock. My phone is connected to my computer via Bluetooth. When I manage to leave the range of my computer, it will automatically lock itself. This comes handy when in public settings you hear your name being called out, letting you know your Chai Latte is ready.

View a Sample of our Cybersecurity Report
By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts