Skip to main content

IAC-37.1: Replay-Resistant Multi-Factor Authentication (MFA)

IAC 8 — High Protect

Automated mechanisms exist to enforce replay-resistant Multi-Factor Authentication (MFA) through authenticators whose outputs cannot be reused, using: (1) Nonces; (2) One-time challenges; (3) Time-synchronous values; and/or (4) Channel binding.

Control Question: Does the organization use automated mechanisms to enforce replay-resistant Multi-Factor Authentication (MFA) through authenticators whose outputs cannot be reused, using: (1) Nonces; (2) One-time challenges; (3) Time-synchronous values; and/or (4) Channel binding?

General (6)
APAC (1)
Framework Mapping Values
APAC Malaysia RMiT 2025 A3-6(a)
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.07.05.B

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

Level 2 — Planned & Tracked

Identification & Authentication (IAC) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with IAC domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with IAC domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with IAC domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Identity & Access Management (IAM)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines) to enforce Logical Access Control (LAC). ▪ IAM may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel to implement Role Based Access Control (RBAC) practices for the management of user, group and system accounts, including privileged accounts. ▪ A directory services technology is used to centrally manage identities and permissions with RBAC. Due to technical or business limitations, asset/process owners are empowered to operate a decentralized access control program for their specific Technology Assets, Applications and/or Services (TAAS) that cannot be integrated into directory services.

Level 3 — Well Defined

Identification & Authentication (IAC) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with IAC domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with IAC domain capabilities are well-documented and kept current by process owners. ▪ An Identity & Access Management (IAM) team, or similar function, is appropriately staffed and supported to implement and maintain IAC domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of IAM operations (e.g., directory services, Authenticate, Authorize and Audit (AAA) solution). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with IAC domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls).

Level 4 — Quantitatively Controlled

Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. IAC-37.1_A01 the accounts, Technology Assets, Applications and/or Services (TAAS) and access scenarios for which replay-resistant Multi-Factor Authentication (MFA) is required are defined.
  2. IAC-37.1_A02 automated mechanisms enforce replay-resistant Multi-Factor Authentication (MFA) such that authenticator outputs cannot be reused to authenticate a subsequent session.
  3. IAC-37.1_A03 where nonces are used, the verifier generates a unique nonce for each authentication attempt and rejects authenticator outputs that reuse a prior nonce.
  4. IAC-37.1_A04 where one-time challenges are used, the verifier issues a unique challenge for each authentication attempt and rejects responses to previously issued challenges.
  5. IAC-37.1_A05 where time-synchronous values are used, the verifier accepts each One-Time Password (OTP) value only within its validity window and rejects reuse of a previously accepted value.
  6. IAC-37.1_A06 where channel binding is used, the authenticator output is cryptographically bound to the authenticated protected channel so that it cannot be replayed over a different channel.
  7. IAC-37.1_A07 configurations of in-scope authentication mechanisms are reviewed to confirm replay-resistant Multi-Factor Authentication (MFA) remains enforced.

Evidence Requirements

E-IAC-16 Multi-Factor Authentication (MFA) Configuration

Documented evidence of Multi-Factor Authentication (MFA) enforcement, including replay-resistant and phishing-resistant authenticators for privileged and non-privileged network access.

Identity & Access Management

Technology Recommendations

Micro/Small

  • Authenticator app TOTP (e.g., Microsoft Authenticator, Google Authenticator) rather than SMS where possible
  • Microsoft Entra (https://microsoft.com)

Small

  • Authenticator app or push MFA (e.g., Microsoft Authenticator, Duo)
  • Microsoft Entra (https://microsoft.com)
  • Duo (https://duo.com)

Medium

  • Microsoft Entra (https://microsoft.com)
  • Okta (https://okta.com)
  • Duo (https://duo.com)
  • FIDO2 security keys for administrators (e.g., Yubico)

Large

  • Microsoft Entra (https://microsoft.com)
  • Okta (https://okta.com)
  • Yubico (https://yubico.com)
  • Conditional access policies enforcing replay-resistant methods

Enterprise

  • Enterprise identity platform with authentication strength policies (e.g., Microsoft Entra, Okta, Ping Identity)
  • FIDO2 / passkeys for workforce
  • Yubico (https://yubico.com)
  • Legacy authentication protocols blocked

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.