Cyber Services / All lessons / Diploma in Cyber Security / Multifactor Authentication & Password Policies

Multifactor Authentication & Password Policies

Module 8 of 30 · 4 min read · Free to read

MODULES ↓ Command blocks have a COPY button

Building a Layered and Resilient Identity Defense

A user's identity is the key to an organization's kingdom. While passwords are the traditional gatekeepers, they are fundamentally flawed and vulnerable. This module explores the two most critical defenses for protecting digital identities: creating robust password policies to strengthen the first line of defense, and implementing Multifactor Authentication (MFA) as an essential, non-negotiable security layer.

The First Line of Defense: Strong Password Policies

A password policy is a set of rules designed to enhance security by encouraging users to employ strong passwords and use them properly. The goal is not to make passwords impossible to remember, but to make them computationally difficult for an attacker to guess or crack.

Length is Strength

The single most important factor in password strength is length. Each additional character exponentially increases the number of possible combinations, making brute-force attacks much harder.

Best Practice (NIST): Enforce a minimum length of at least 8 characters for all user passwords, and a minimum of 12-14 characters for privileged/administrator accounts. Longer is always better.

Complexity Requirements

Complexity rules force a mix of character types to prevent attackers from using simple "dictionary" attacks. While less important than length, it's still a valuable part of a defense-in-depth strategy.

Common Policy: Require at least three of the following four character types:

  • Uppercase letters (A-Z)
  • Lowercase letters (a-z)
  • Numbers (0-9)
  • Symbols (!, $, #, @, etc.)

Password History

This policy prevents users from reusing old passwords. It is critical for mitigating the risk of credential stuffing, where an attacker uses a password stolen from a previous breach to try and log into other systems.

Best Practice: Remember the last 10-24 passwords so users are forced to create a genuinely new and unique password each time a change is required.

Banned Password Lists

A modern and highly effective control. The system checks a new password against a database of known-compromised passwords (e.g., "Password123", "12345678", "qwerty") and common patterns (e.g., "Company_Name2025"). This stops users from choosing the most obvious and vulnerable passwords from the start. Azure AD and other identity systems have this feature built-in.

The Essential Layer: Multifactor Authentication (MFA)

MFA is a security process that requires users to provide two or more verification factors to gain access to a resource. Even if an attacker steals a user's password, they cannot get in without also having access to the second factor. Implementing MFA is the single most effective action you can take to protect your accounts.

Possession Factor (Something You Have)

This is the most common form of a second factor, where a user must prove they possess a specific device or token.

  • Authenticator Apps (TOTP): The user's smartphone generates a Time-based One-Time Password (e.g., using Google Authenticator, Microsoft Authenticator). This is a highly secure and recommended method.
  • Hardware Tokens (U2F/FIDO2): A physical USB key (e.g., YubiKey) that generates a secure response when touched. This is considered the gold standard as it is resistant to phishing.
  • Push Notifications: The user receives a simple "Approve" or "Deny" notification on their phone. It's very convenient but can be vulnerable to "MFA Fatigue" attacks, where an attacker spams a user with requests, hoping they'll eventually approve one by mistake.
  • SMS / Email Codes: A code is sent via text message or email. This is better than no MFA, but is considered the weakest form due to the risk of SIM-swapping attacks and email account takeovers.

Inherence Factor (Something You Are)

This factor uses a unique biometric trait of the user for verification. It's extremely convenient and is becoming more common.

  • Fingerprint Scans: Used on laptops and smartphones.
  • Facial Recognition: Technologies like Windows Hello and Apple's Face ID.
  • Voice Recognition: Used in some phone-based banking systems.
The primary drawback is that if a biometric template is ever compromised, it cannot be changed like a password.

Real-World Defense in Action: An attacker buys a list of credentials from a past data breach on the dark web. They find an employee's email and password, which the employee foolishly reused for their corporate account.

The attack stops here. Without physical access to the employee's phone, the attacker cannot provide the second factor and is locked out. This demonstrates perfectly how MFA renders stolen passwords useless. The attacker goes to the corporate login page and enters the correct username and password. The system authenticates the password (the "something you know" factor). However, it then presents a second screen: "Please enter the 6-digit code from your authenticator app."

Modules (30) ← Diploma in Cyber Security