Multifactor authentication
Multifactor authentication is an identity-verification method requiring evidence from at least two distinct authentication-factor categories.
ASP.NET Core in Action, 3e
Multifactor authentication is authentication that requires evidence from multiple independent credential or verification factors.
- How it is used
- Provides an additional sign-in safeguard within user account management.
- How deep it goes
- Defines MFA and points to authenticator setup, while deferring QR code generation details to Microsoft’s documentation.
- Examples
- Uses codes sent by SMS or generated by a mobile authenticator app as sign-in examples.
- What you can do after
- Operate/configure MFA through ASP.NET Core Identity’s account-management pages and identify the additional QR code setup.
Read how ASP.NET Core in Action, 3e explains multifactor authentication →
Acing the CCNA Exam: Volume 2 Advanced Networking and Security
Multifactor authentication is an identity-verification process that requires authentication factors from multiple categories before granting access.
- How it is used
- Frames MFA as a stronger alternative to username-and-password authentication and a password-policy concept.
- How deep it goes
- Explains the definition, security rationale, three factor categories, and valid combinations, but stops short of configuration or protocol implementation.
- Examples
- Uses passwords, PINs, badges, smartphones, SMS codes, authenticator apps, biometrics, badge readers, and fingerprint scans.
- What you can do after
- Evaluate authentication methods by classifying factors and determining whether combinations satisfy true MFA.
Microsoft Azure in Action
Multi-factor authentication (MFA) is an authentication technique that requires two or more independent types of evidence to verify an identity.
- How it is used
- Protects Azure sign-ins against weak, reused, or compromised passwords by requiring another authentication factor.
- How deep it goes
- Defines three factor types and outlines an Entra ID Conditional Access policy, including targets, grant requirement, and licensing.
- Examples
- Uses reused passwords, a phone-based sign-in prompt, and Entra ID authentication for Azure SQL to illustrate MFA.
- What you can do after
- Operate/configure it in the Azure Portal by creating an Entra ID Conditional Access policy that requires MFA.
Read how Microsoft Azure in Action explains multifactor authentication →
Data-Driven Cybersecurity
An authentication method requiring two or more independent factors to verify a user's identity.
- How it is used
- Reduces the risk of unauthorized access when passwords or credentials are compromised.
- How deep it goes
- Defines factor types and token options, including context-aware MFA, but does not give configuration steps.
- Examples
- Uses a remote-access breach and an IAM dashboard reporting 95% authentication success after improvements.
- What you can do after
- Operate/configure it for critical systems or remote access, then monitor access violations and authentication results.
Read how Data-Driven Cybersecurity explains multifactor authentication →
Software Security for Developers
Multifactor authentication verifies identity using two or more independent authentication factors.
- How it is used
- Deploys MFA for higher-risk logins and as a fallback authentication option in modern applications.
- How deep it goes
- Defines factor categories and explains password-plus-OTP flow, risks, rate limiting, monitoring, and safer OTP practices.
- Examples
- Uses password-plus-OTP login, authenticator apps, SMS codes, fingerprints, face scans, and security tokens.
- What you can do after
- Apply it via OTPs, authenticator apps, SMS codes, biometrics, or security keys while controlling replay and guessing risks.
Read how Software Security for Developers explains multifactor authentication →
Grokking Web Application Security
Multifactor authentication is an authentication technique that requires a user to provide at least two distinct forms of identification.
- How it is used
- Strengthens web logins by requiring an additional proof alongside a username and password.
- How deep it goes
- Explains factor choices, accessibility trade-offs, TOTP behavior, and WebAuthn registration safeguards without detailing a full server implementation.
- Examples
- Uses SMS codes, authenticator-app codes, push approvals, biometrics, and a browser WebAuthn credential-creation configuration.
- What you can do after
- Apply MFA by selecting accessible factors, recognizing SMS risks, and configuring WebAuthn biometric registration with replay-resistant challenges.
Read how Grokking Web Application Security explains multifactor authentication →
Azure Security
Multifactor authentication is an authentication method that requires two or more independent factors to verify an identity.
- How it is used
- Protects Azure identities by requiring additional verification when credentials may be compromised or sign-in risk is elevated.
- How deep it goes
- Defines factor types and demonstrates a Conditional Access policy, while deferring broader attack containment to layered Azure security services.
- Examples
- Uses brute-force risk, Bob's Azure sign-in, FIDO2 security keys, and a report-only Conditional Access policy.
- What you can do after
- Configure MFA through Microsoft Entra ID Conditional Access and test the policy in report-only mode before enforcement.
Read how Azure Security explains multifactor authentication →
Grokking Software Architecture
Multi-factor authentication is an authentication method that requires evidence from two or more independent credential factors.
- How it is used
- Protects project access by requiring MFA for developer accounts, cloud consoles, and code repositories.
- How deep it goes
- Defines MFA as independent credential factors and recommends enforcement, but does not explain factor setup or implementation.
- Examples
- Names developer accounts, cloud console logins, and code repository access as places to require MFA.
- What you can do after
- Operate/configure project access by requiring MFA across developer, cloud, and repository accounts.
Read how Grokking Software Architecture explains multifactor authentication →
MongoDB 8.0 in Action, Third Edition
MFA, or multifactor authentication, verifies an identity using two or more independent authentication factors.
- How it is used
- Assigns customers responsibility for configuring and enforcing identity protection when managing Atlas access.
- How deep it goes
- Explains MFA’s placement in shared responsibility and defense in depth, but does not provide a step-by-step configuration procedure.
- Examples
- Lists SMS, voice calls, authentication applications, YubiKey, and external identity providers as authentication examples.
- What you can do after
- Operate/configure Atlas UI access with added MFA and combine it with layered network, authentication, and authorization controls.
Read how MongoDB 8.0 in Action, Third Edition explains multifactor authentication →
Fundamentals of Cybersecurity
Authentication that requires evidence from multiple independent credential categories.
- How it is used
- Strengthens authentication against unauthorized access, including when a password has been compromised.
- How deep it goes
- Defines MFA, distinguishes it from single- and two-factor authentication, and illustrates factor categories without implementation steps.
- Examples
- Uses password-plus-phone-code and password-plus-token examples, and contrasts distinct factors with username-plus-password.
- What you can do after
- Evaluate whether an authentication setup uses multiple factor categories rather than multiple credentials from one category.
Read how Fundamentals of Cybersecurity explains multifactor authentication →
Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
Multifactor authentication is an authentication method that requires evidence from multiple independent credential factors.
- How it is used
- Protects AWS root-user and IAM-user sign-in against stolen or cracked passwords and access keys.
- How deep it goes
- Defines MFA and provides console enrollment steps for root users and IAM users, without covering token internals.
- Examples
- Uses a smartphone TOTP application, QR-code enrollment, virtual MFA devices, YubiKeys, and hardware tokens.
- What you can do after
- Operate/configure MFA for AWS root users and IAM users through the Management Console.
The Cloud at Your Service: The when, how, and why of enterprise cloud computing
Multifactor authentication verifies identity using two or more distinct types of authentication factors.
- How it is used
- Strengthens cloud sign-in access control beyond password-only credentials and is projected as a standard requirement for cloud users.
- How deep it goes
- Recommends MFA and contrasts it with password-only sign-in, but does not detail factor enrollment or recovery.
- Examples
- Pairs a password with a time-based hardware token such as RSA SecurID.
- What you can do after
- Evaluate sign-in choices by recognizing MFA as stronger than password-only authentication.
Also covered in
- Real-World Cryptography
- Architecting AccessibilityIn early access (MEAP)
- Authorization in Action
- Build AI-Enhanced Web Apps
- Pro ASP.NET Core 7, Tenth Edition
- Think Like a CTO
- Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu
- Snowflake Data Engineering
What to know first
- password authenticationPassword authentication is a method of verifying a claimed identity or access by checking a supplied secret password, often alongside a user identifier.
- authenticationAuthentication is the process of verifying the claimed identity of a user, service, device, or other entity.
- credentialA credential is information or an artifact presented to verify an entity’s identity or establish its authorization to access a system or resource.
- public keyA public key is the openly distributable key in an asymmetric cryptographic pair, used for operations such as encrypting data or verifying signatures.
Related concepts
- authentication factoruses · An authentication factor is a distinct category of evidence used to verify a subject’s identity during authentication.
- Microsoft Entra IDused by · Microsoft Entra ID is Microsoft's cloud-based identity and access-management service for authenticating users, applications, and services and controlling their access to resources.
- access controluses · Access control is the set of policies and mechanisms that determines which users or processes may access resources and what actions they may perform.
- conditional accessconfigured by · Conditional access is an access-control technique that grants or denies requests according to contextual conditions and policy requirements.
- IAM userused by · An IAM user is an AWS identity representing a person or application with credentials and assigned permissions within an account.
Questions about multifactor authentication
What is multifactor authentication?
Multifactor authentication is an identity-verification method requiring evidence from at least two distinct authentication-factor categories.
Which Manning books explain multifactor authentication?
ASP.NET Core in Action, 3e, Acing the CCNA Exam: Volume 2 Advanced Networking and Security, Microsoft Azure in Action, Data-Driven Cybersecurity, Software Security for Developers, Grokking Web Application Security, Azure Security, Grokking Software Architecture and 4 more.
What should I know before learning multifactor authentication?
Manning books that teach multifactor authentication usually introduce password authentication, authentication, credential and public key first.
What is multifactor authentication also called?
Multifactor authentication is also called MFA or multi-factor authentication.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.











