liveBook · Manning

Multifactor authentication

As explained in Grokking Software Architecture

Multi-factor authentication is an authentication method that requires evidence from two or more independent credential factors.

Multi-factor authentication (MFA) requires evidence from two or more independent credential factors. In a secure architecture, it adds a check to identity verification; it does not replace protecting passwords and secrets. section 11.8 section 11.3.2

Make MFA a requirement wherever project identities gain access:

  • Require it for every developer account, cloud console login, and code repository. section 11.8
  • Use an identity provider to centralize credential management and MFA instead of handling authentication separately in each application. section 11.3.2

Treat MFA as one layer of architectural security, not a substitute for protecting developer devices: a compromised laptop can still put the wider system at risk. section 11.8

How Grokking Software Architecture covers it

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.
How it connects
Connects MFA with identity providers and centralized credential management.

Also explained in

Compare how 12 books explain multifactor authentication →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.