Skip to main content
  • For Support:

    815-308-2095

  • New Client
    815-788-6041
February 4, 2025

Why Are Password Changes Required? A Complete Guide to Passwords and MFA for Businesses


Passwords are still the front door to your business. Despite the rise of biometrics and passkeys, Microsoft’s Digital Defense Report found that 97% of identity attacks still target passwords. And according to the Verizon Data Breach Investigations Report, over 80% of hacking-related breaches begin with compromised credentials.

The question isn’t whether passwords matter. It’s whether your organization is managing them well enough to keep attackers out.

This guide covers everything Chicagoland businesses need to know about defending against identity-based attacks through stronger password security and multi-factor authentication (MFA):

Table of Contents


Are Passwords Still Important?

Yes, and they will be for the foreseeable future. Passkeys and biometrics are gaining traction, with Apple, Google, and Microsoft all supporting FIDO2 authentication. But passwords remain the default access method for the vast majority of business applications, especially legacy systems and industry-specific software. Most systems still rely on a username and password as the primary means of authentication before any additional security measures are applied.

Consider this: global cybercrime costs are projected to grow from $11.5 trillion in 2023 to $23.8 trillion by 2027 (Statista). Stolen credentials are one of the primary drivers of that growth. Until every platform supports passwordless login (and every employee has the hardware to use it), passwords remain your first line of defense.

The real problem isn’t passwords themselves. It’s how most businesses manage them.


Why Password Changes Are Required

Organizations require password changes for several reasons, and not all of them are about scheduled rotation.

Data breaches are constant. More than 1 billion records were exposed in 2024 alone (McAfee). When a service you use gets breached, any password associated with that account is compromised. If your employees reuse that same password across multiple systems (and studies show 59% of people do, even though 91% know the risk), one breach can cascade across your entire network.

Brute force and credential stuffing attacks are automated. Attackers use software that tests millions of password combinations per second. They also purchase stolen credential lists on the dark web and systematically test them against other services. This is called credential stuffing, and it works because of password reuse.

Phishing campaigns target credentials directly. Social engineering remains the most common way attackers steal passwords. A single clicked link in a convincing phishing email can hand your login credentials to an attacker.

Compliance frameworks require it. HIPAA, PCI-DSS, the FTC Safeguards Rule, and the CJIS Security Policy all include requirements around password management. Some mandate regular password changes; others require change-on-compromise policies with continuous monitoring. Failing to comply can result in regulatory penalties on top of the breach itself.

The NIST Debate: Scheduled Rotation vs. Change on Compromise

There’s an important shift happening in how security experts think about password changes. The National Institute of Standards and Technology (NIST SP 800-63B) no longer recommends forcing users to change passwords on a set schedule (like every 90 days). Their updated guidance says passwords should be changed when there is evidence of compromise, not on a calendar.

The reasoning is sound: forced rotation leads to weaker passwords. Employees get frustrated and start using predictable patterns like “Spring2026!” followed by “Summer2026!” Attackers know these patterns.

The better approach is to pair strong, unique passwords with continuous breach monitoring. When credentials appear on the dark web or a service reports a breach, you change them immediately. The rest of the time, a strong password that isn’t reused is more secure than a weak one that gets rotated every quarter.

That said, it takes an average of 241 days to detect a breach according to IBM. If your organization doesn’t have dark web monitoring in place, you may not know a password is compromised until it’s too late. Monitoring is what makes the “change on compromise” model work.


Does Changing Your Password Actually Stop Hackers?

If your password has already been stolen, changing it immediately locks the attacker out (assuming they haven’t already installed a backdoor or escalated their access). In that scenario, yes, a password change is one of the most important things you can do.

If your password hasn’t been compromised, changing it on a schedule offers limited additional protection. The old password wasn’t the vulnerability. The real risks are reuse, weak complexity, and phishing, and a scheduled change doesn’t address any of those.

The bottom line: change passwords after any suspected breach. Pair that with MFA, a password manager, and monitoring tools, and you’re far better protected than any 90-day rotation policy could provide.


What Is a Compromised Password?

A compromised password is any password that has been exposed to an unauthorized party. This can happen through a data breach at a service you use, a phishing attack, malware that logs keystrokes, or even a coworker who shared login credentials over an unsecured channel. Once an attacker gains access, they can move laterally through your network and escalate privileges.

Common attack methods include:

  • Password spraying — trying a small number of commonly used passwords across many accounts
  • Brute force attacks — trying every possible combination
  • Credential stuffing — using stolen credentials from one breach to access other services
  • Phishing — tricking users into entering credentials on a fake login page

You can check whether your email or passwords have appeared in known breaches at Have I Been Pwned.

The most commonly used passwords, including “123456,” “password,” “qwerty,” and variations of names and birthdays, appear on every attacker’s list. If any of your employees use passwords like these, your accounts are at risk right now.


The Real Danger of Password Reuse

According to the Verizon DBIR, more than 50% of breaches involve stolen or reused credentials. A GoodFirms survey found that 30% of IT professionals have experienced a breach directly caused by weak passwords.

Here’s how it plays out: an employee uses the same password for their work email, personal email, and a personal shopping account. The retailer gets breached. The attacker takes that stolen email/password combination and tests it against common business platforms and online accounts (Microsoft 365, VPNs, cloud storage). If the credentials match, they’re in.

This is why password reuse is arguably the single biggest credential risk for small and mid-sized businesses. It turns every external breach into a potential internal one.

Yet only 46% of SMBs have any formal password management in place (LastPass). Many businesses still have employees storing passwords in spreadsheets, sticky notes, or shared documents. Leadership often writes a password policy but never enforces it. Password security needs to be treated as a culture issue, not just an IT checkbox.


Password Best Practices for Businesses

Good password hygiene starts with clear policies and the tools to enforce them.

Length over complexity. Modern guidance favors long passphrases (16+ characters) over short, complex strings. A passphrase like “correct-horse-battery-staple” is both easier to remember and harder to crack than “P@ssw0rd!23.”

Unique passwords for every account. No reuse, period. This is the single most impactful habit your organization can adopt.

Use a password manager. Tools like Bitwarden, 1Password, Dashlane, and LastPass create and store unique, complex passwords for every account. They auto-fill credentials so employees don’t need to remember anything except one master password. When a user creates a new account, the manager generates a strong credential automatically. They also alert you when stored passwords appear in known breaches.

Implement privileged access management. Administrative accounts and executive logins should use separate, stronger passwords stored in a dedicated vault with additional access controls. These accounts can access your entire network, so they deserve extra protection. Effective access management means limiting access rights to only what each role requires, reviewing permissions quarterly, and immediately revoking credentials when employees leave. This reduces your attack surface and keeps sensitive accounts and sensitive information protected from unauthorized users.

Enforce policies through your MSP or IT team. Password management is time-intensive, and most SMBs don’t have the bandwidth to handle it internally. A Chicago managed IT services provider can deploy password management tools across your organization, enforce complexity requirements, and integrate them with your broader cybersecurity strategy.


Are Password Managers Safe?

Password managers encrypt your stored passwords using zero-knowledge architecture, meaning even the password manager company cannot see your actual passwords. If the service itself is breached (as happened with LastPass in 2022-2023), attackers can see metadata like email addresses and website URLs, but the actual passwords remain encrypted.

That said, your master password is the key to everything. Never share it. Never reuse it. And enable MFA on your password manager account.

If a password manager you use reports a breach, change your master password immediately and rotate any passwords you’re especially concerned about. The encrypted vault itself is extremely difficult to crack if your master password is strong.


Multi-Factor Authentication: Your Second Line of Defense

Passwords alone are not enough. Even the strongest password can be stolen through phishing or a breach. Multi-factor authentication adds a second (or third) verification step that makes stolen passwords far less useful to attackers. Multifactor authentication, sometimes called two-factor authentication (2FA) or two-step verification, requires proof beyond just a password before granting access.

According to Microsoft, MFA can prevent up to 99.9% of unauthorized access attempts.

How MFA Works

MFA requires two or more verification methods from different categories, known as authentication factors:

Something you know: your password, PIN, or security question answer. Something you have: your phone (for authenticator apps or SMS codes), a hardware security key, or a smart card. Something you are: your fingerprint, facial recognition, or other biometric.

Some implementations add location-based verification (are you logging in from a recognized location?) and time-based restrictions (is this login attempt within normal business hours?). These additional factors further reduce risk without adding friction for legitimate users.

MFA can be applied at the device level (when logging into a computer) or at the application level (when accessing specific apps or databases). For maximum protection, implement it at both levels. The goal is to verify the user’s identity through multiple independent factors before granting access.

Why Your Business Needs MFA Now

Stronger MFA security isn’t optional anymore. Here’s why.

Cyber insurance requires it. Most cyber liability insurance carriers now require MFA as a condition of coverage. Businesses without MFA are being denied coverage or facing premium increases of 20-50% year over year (Aon PLC). The Verizon DBIR shows that 61% of breaches begin as credential thefts, and stolen passwords account for roughly 50% of cyber insurance claims. Insurers aren’t requiring MFA arbitrarily. They’re requiring it because credential theft is their biggest payout category.

Compliance mandates it. HIPAA, PCI-DSS, and the CJIS Security Policy all require MFA for accessing sensitive systems. The NIST Level of Assurance standards make MFA mandatory for any federal government operations or electronic commerce.

Remote work demands it. With employees accessing corporate networks from home offices, coffee shops, and airports, verifying identity at every login attempt is essential. Pairing MFA with single sign-on (SSO) lets your team work from anywhere without compromising security.

It should cover every user, not just admins. A common mistake is enabling MFA only for administrative or remote-access accounts. Attackers look for the weakest entry point. If a standard employee account lacks MFA, that’s where they’ll focus. Every account in your organization should be MFA enabled, from executive logins to frontline staff.

Which MFA Method Should You Use?

Not all MFA methods are equally secure. Here’s the ranking from weakest to strongest:

SMS text codes: Vulnerable to SIM swapping, where an attacker convinces your mobile carrier to transfer your phone number to their device. Once they have your number, they receive your MFA codes. Move away from SMS-based MFA wherever possible.

Email codes: Only as secure as the email account itself. If the attacker already has access to the employee’s email, email-based MFA provides no additional protection.

Authenticator apps (Google Authenticator, Microsoft Authenticator, Authy, Duo): Significantly stronger. These generate time-based codes on the user’s device and work on most mobile phones. An attacker would need physical access to the device to intercept them. An authenticator app is the most practical upgrade for most businesses moving away from SMS.

Hardware security keys (FIDO2-compliant): The strongest option. A physical security key like a YubiKey (including NFC-enabled models) requires the user to physically touch the key during login. They’re phishing-resistant because the key verifies the actual website domain, making fake login pages useless.

Biometrics (fingerprint, face scan): Strong for device-level authentication. Best used in combination with another factor as a second verification method.


How Attackers Bypass MFA (and How to Stop Them)

MFA is not bulletproof. Cybercriminals have developed several techniques to get around it. Understanding these attacks helps you implement defenses that actually work.

MFA fatigue attacks (prompt bombing). The attacker already has the employee’s password and triggers MFA push notifications repeatedly, sometimes dozens of times, hoping the employee eventually taps “Approve” just to stop the notifications. This is how Uber was breached in September 2022. Defense: enable number matching in push notifications (the user must enter a code from the login screen, not just tap approve) and set rate limits on MFA push notifications.

SIM swapping. The attacker calls the employee’s mobile carrier, impersonates them, and transfers the phone number to a new SIM card. They then receive all SMS-based MFA codes. Defense: switch from SMS to authenticator apps or hardware keys, and set up a carrier PIN that requires in-person verification for SIM changes.

Man-in-the-middle attacks. The attacker sets up a proxy between the user and the real login page. As the user enters their password and MFA code, the proxy captures both in real time and uses them before they expire. Defense: use HTTPS everywhere and consider FIDO2 hardware keys, which verify the actual domain and can’t be fooled by proxy sites.

Phishing for MFA codes. Sophisticated fake login pages now capture both passwords and MFA codes simultaneously. Defense: phishing awareness training, email filtering, and password managers that detect when a URL doesn’t match the legitimate site. Ongoing user education is essential. Train users to reject any MFA prompt they didn’t initiate, no matter how persistent.

Account recovery exploitation. Attackers bypass MFA entirely by exploiting weak account recovery processes. According to Google research, an attacker has up to a 43% chance of successfully guessing a user’s security answer within ten attempts. Defense: require multiple verification factors for account recovery and avoid using guessable security questions.

Security teams should monitor the authentication process for unusual spikes in MFA prompts, which can help detect MFA fatigue attacks before they succeed. Risk-based authentication (sometimes called adaptive authentication) adds another layer by adjusting verification requirements based on login location, device, and behavior, helping to identify patterns and flag suspicious access attempts automatically.

The takeaway: MFA is not a silver bullet, but it remains one of the most effective security measures available. The key is choosing stronger MFA methods and layering them with the defenses described above.


Passkeys, Biometrics, and the Future of Authentication

The authentication landscape is shifting. Passkeys, built on the FIDO2/WebAuthn standard, eliminate passwords entirely. Instead of typing a password, you authenticate using your device’s biometric sensor (fingerprint or face scan) or a hardware key. The credentials never leave your device and can’t be phished because they’re cryptographically bound to the specific website.

Apple, Google, and Microsoft all support passkeys in their operating systems and browsers. Major services like Amazon, PayPal, and GitHub have adopted them. NIST has endorsed biometric authentication as part of its updated identity guidelines.

For most Chicagoland businesses, the practical reality is that passwords won’t disappear overnight. Legacy systems, industry-specific software, and vendor portals will continue to require traditional credentials for years. The smart move is to adopt passkeys where available while maintaining strong password and MFA practices everywhere else.


What to Do If Your Passwords Are Compromised

If you suspect a breach, or if dark web monitoring alerts you to exposed credentials, act immediately.

First, change the compromised password and review all potentially affected accounts that used the same or a similar password. Second, enable MFA on every account that supports it (if you haven’t already). Third, check Have I Been Pwned to see if other user credentials have been exposed. Fourth, monitor your accounts for suspicious activity over the following weeks. Finally, report the incident to your IT team or managed service provider so they can investigate whether attackers accessed internal systems.

If an employee’s email was specifically compromised, review our guide on whether someone can hack your email without the password for additional steps.


Frequently Asked Questions

Does changing your password stop hackers?

If your password has been stolen, changing it immediately prevents the attacker from using it going forward. However, if the attacker has already installed malware or created a backdoor, a password change alone won’t remove them. Pair password changes with a full security review.

What is a compromised password?

A compromised password is any credential that has been exposed through a data breach, phishing attack, malware, or unauthorized sharing. You can check whether your credentials appear in known breaches at Have I Been Pwned.

How often should you change your password?

Modern guidance from NIST recommends changing passwords when there’s evidence of compromise rather than on a fixed schedule. The exception is compliance frameworks that still require periodic rotation. Continuous breach monitoring makes this approach effective.

Why might forced password changes threaten security?

Frequent mandatory changes lead to weaker passwords. Employees default to predictable patterns (“Winter2026!” becomes “Spring2026!”) or write passwords on sticky notes. NIST found that scheduled rotation creates more vulnerabilities than it prevents.

Are password managers safe?

Yes. Password managers use zero-knowledge encryption, meaning even the provider can’t see your stored passwords. Choose a reputable manager (Bitwarden, 1Password, Dashlane), use a strong master password, and enable MFA on the manager itself.

Is MFA required for cyber insurance?

In most cases, yes. The majority of cyber liability insurance carriers now require MFA as a condition of coverage. Businesses without it face coverage denials or premium increases of 20-50%.

What is an MFA fatigue attack?

An MFA fatigue attack (also called MFA bombing or push bombing) is a technique where attackers repeatedly send MFA push notifications to a user, hoping they’ll approve one out of frustration. The Uber breach in 2022 was executed this way. Defenses include number matching (requiring the user to enter a displayed code) and rate-limiting notifications.

Why is it important to keep your password private?

Shared passwords can’t be traced to a single user, making it impossible to identify who accessed what. If a shared credential is compromised, every user of that password is exposed. Every employee should have their own unique login.


Protect Your Chicagoland Business with Stronger Authentication

Password security and MFA aren’t just IT best practices. They’re business essentials that affect your insurance eligibility, regulatory compliance, and ability to survive a cyberattack.

If you’re not sure where your organization stands, LeadingIT’s CyberSCORE assessment evaluates your current authentication practices, identifies gaps, and provides a clear action plan.

LeadingIT is a cyber-resilient IT MSP and cybersecurity services provider. With our concierge support model, we provide customized solutions to meet the unique needs of nonprofits, schools, manufacturers, accounting firms, government agencies, and law offices with 25-250 users across the Chicagoland area. Our team of experts solves the unsolvable while helping our clients leverage technology to achieve their business goals, ensuring the highest level of security and reliability with our managed IT services.

Let Us Be Your Guide In Cybersecurity Protections
And IT Support With Our All-Inclusive Model.