Quality, Expert-Derived Cybersecurity Documentation To Keep Organizations Secure, Compliant & Resilient  |  Got Questions? +1-307-241-8740
ComplianceForge

How Do You Comply With NY DFS 23 NYCRR 500.12 Multi-Factor Authentication?

Short Answer

23 NYCRR 500.12 requires multi-factor authentication for any individual accessing any information system of a covered entity. Entities with a 500.19(a) limited exemption must use MFA for remote access to their systems, remote access to third-party applications from which nonpublic information is accessible, and all privileged accounts other than service accounts that prohibit interactive login. A CISO may approve reasonably equivalent or more secure compensating controls in writing, reviewed at least annually.

23 NYCRR 500.12 Multi-Factor Authentication at a Glance

  • Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
  • Section: 23 NYCRR 500.12 Multi-Factor Authentication.
  • Status: Amended by the Second Amendment, effective November 1, 2023.
  • Who it applies to: Every covered entity unless exempt under 500.19(c) or (d). Entities with a 500.19(a) limited exemption have a narrower MFA scope.
  • Class A companies: None beyond the general requirement.
  • Limited exemption (500.19(a)): Not exempt under 500.19(a), but the required scope is narrower: remote access to the covered entity's systems, remote access to third-party applications with nonpublic information, and all privileged accounts other than non-interactive service accounts.
  • Compliance dates: The expanded MFA requirement applied from November 1, 2025, two years after the Second Amendment took effect (500.22(d)(4)).

The Second Amendment replaced the old risk-based MFA language with a broad rule: MFA for any individual accessing any information system of the covered entity. This is one of the most operationally demanding changes in the amendment, which is why it had the longest transitional period.

Entities that qualify for the 500.19(a) limited exemption still need MFA, but only for remote access, remote access to third-party applications with nonpublic information, and privileged accounts. MFA is defined in 500.1(j) as at least two of knowledge, possession and inherence factors.

What Does 23 NYCRR 500.12 Require?

The following is the text of 23 NYCRR 500.12 Multi-Factor Authentication as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability.

  • (a) Multi-factor authentication shall be utilized for any individual accessing any information systems of a covered entity, unless the covered entity qualifies for a limited exemption pursuant to section 500.19(a) of this Part in which case multi-factor authentication shall be utilized for:
  • (1) remote access to the covered entity’s information systems;
  • (2) remote access to third-party applications, including but not limited to those that are cloud based, from which nonpublic information is accessible; and
  • (3) all privileged accounts other than service accounts that prohibit interactive login.
  • (b) If the covered entity has a CISO, the CISO may approve in writing the use of reasonably equivalent or more secure compensating controls. Such controls shall be reviewed periodically, but at a minimum annually.

Source: NY DFS, Second Amendment to 23 NYCRR 500 (text).

How Does 23 NYCRR 500.12 Map to the Secure Controls Framework (SCF)?

The SCF publishes a NIST IR 8477 Set Theory Relationship Mapping (STRM) between 23 NYCRR Part 500 (2023 Amendment 2) and SCF version 2026.3. It maps 23 NYCRR 500.12 to 6 SCF controls through 8 relationships (1 "subset of", 7 "intersects with").

How to read the mapping: each relationship runs from the Part 500 text to the SCF control. "Subset of" means the Part 500 requirement is fully contained within the SCF control. "Intersects with" means the Part 500 requirement and the SCF control share partial overlap. The strength of relationship runs from 1 (nominal) to 10 (strongest), where 5 is moderately strong and 10 is typically reserved for "equal" and "subset of" relationships.

  • RSK-18 Compensating Countermeasures. Subset of (strength 10): 500.12(b). SCF control: Mechanisms exist to identify and implement one, or more, compensating controls to reduce risk and threat exposure when the primary means of implementing the security function is unavailable or compromised.
  • IAC-37 Multi-Factor Authentication (MFA). Intersects with (strength 5): 500.12(a), 500.12(a)(1), 500.12(a)(2). SCF control: Automated mechanisms exist to enforce Multi-Factor Authentication (MFA) for: (1) Remote network access; (2) Third-party Technology Assets, Applications and/or Services (TAAS); and/ or (3) Non-console access to critical TAAS that store, transmit and/or process sensitive and/or regulated data.
  • IAC-37.5 Multi-Factor Authentication (MFA) For Network Access to Privileged Accounts. Intersects with (strength 5): 500.12(a)(3). SCF control: Mechanisms exist to utilize Multi-Factor Authentication (MFA) to authenticate network access for privileged accounts.
  • IAC-37.7 Multi-Factor Authentication (MFA) For Local Access to Privileged Accounts. Intersects with (strength 5): 500.12(a)(3). SCF control: Mechanisms exist to utilize Multi-Factor Authentication (MFA) to authenticate local access for privileged accounts.
  • GOV-04.2 Exception Management. Intersects with (strength 5): 500.12(b). SCF control: Mechanisms exist to prohibit exceptions to standards, except when the exception has been formally assessed for risk impact, approved and recorded.
  • RSK-17 Risk Remediation. Intersects with (strength 5): 500.12(b). SCF control: Mechanisms exist to remediate risks to an acceptable level.

Mapping taken from the STRM published with SCF version 2026.3. Download it at no cost: SCF STRM for NY DFS 23 NYCRR 500 (2023 Amendment 2). The SCF explains the method in its Set Theory Relationship Mapping (STRM) guidance.

Common Pitfalls With 23 NYCRR 500.12

The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:

  • Covering remote access only. For entities without the limited exemption, MFA applies to any individual accessing any information system, not only remote or VPN access.
  • Missing third-party cloud applications. For limited-exemption entities, remote access to third-party applications, including cloud applications from which nonpublic information is accessible, is in scope.
  • Service account confusion. Only service accounts that prohibit interactive login are excluded from the privileged account MFA requirement for limited-exemption entities.
  • Compensating controls without a CISO approval. Compensating controls require written CISO approval and must be reviewed at least annually. 500.12(b) provides this option only where the covered entity has a CISO.

What Is Reasonable Evidence for 23 NYCRR 500.12?

NY DFS does not publish a fixed evidence list. Under 500.17(b)(3), records supporting the annual certification or acknowledgment must be kept for five years.

The SCF Evidence Request List (ERL) ties evidence artifacts to SCF controls. ERL items linked to the SCF controls mapped to 23 NYCRR 500.12 include:

  • E-GOV-20 Compensating Controls. Documented evidence of compensating controls (e.g., countermeasure to reduce risk associated with control deficiencies).
  • 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.
  • E-GOV-06 Exception Management. Documented evidence of authorized exceptions to standards (e.g., configurations, practices, etc.)
  • E-RSK-03 Plan of Actions & Milestones (POA&M) / Risk Register. Documented evidence of a POA&M, or risk register, that tracks control deficiencies from identification through remediation.

Records specific to 23 NYCRR 500.12 that typically show the requirement is designed and operating:

  • MFA standard. A standard defining where MFA is required and the accepted factor types under 500.1(j).
  • MFA coverage report. Identity provider or system reports showing MFA enforcement across in-scope systems and users.
  • Exception register. Any CISO-approved compensating controls with approval dates and the latest annual review.
  • Privileged account MFA. Evidence that privileged accounts, other than non-interactive service accounts, require MFA.

Which ComplianceForge Documents Support 23 NYCRR 500.12?

The following ComplianceForge documents can help you document and implement 23 NYCRR 500.12 Multi-Factor Authentication:

  • SCF Policies & Standards (SCRP): editable SCF-based cybersecurity policies, standards and control objectives covering all 34 SCF domains.
  • SCF Procedures (CSOP): editable SCF-aligned cybersecurity procedures covering all 34 SCF domains, mapped 1-to-1 to the SCRP standards.

Frequently Asked Questions (FAQ)

Does 23 NYCRR 500.12 require MFA for internal network access? For covered entities without the limited exemption, yes. The amended text requires MFA for any individual accessing any information systems of a covered entity, without limiting it to remote access.

What MFA is required for entities with a 500.19(a) limited exemption? MFA for remote access to the covered entity's information systems; remote access to third-party applications, including cloud-based applications, from which nonpublic information is accessible; and all privileged accounts other than service accounts that prohibit interactive login.

Can a CISO approve alternatives to MFA under 500.12? If the covered entity has a CISO, the CISO may approve in writing the use of reasonably equivalent or more secure compensating controls. Those controls must be reviewed periodically, but at a minimum annually.

When did the expanded 500.12 MFA requirement take effect? Covered entities had two years from the November 1, 2023 effective date of the Second Amendment, so the expanded requirement applied from November 1, 2025 under 500.22(d)(4).

Bottom Line on 23 NYCRR 500.12 Multi-Factor Authentication

500.12 now expects MFA for every individual on every information system, with a narrower list for limited-exemption entities. Measure coverage against that scope, close gaps on internal and cloud access, and keep any CISO-approved compensating controls in writing with an annual review.

Authoritative sources:

This page reproduces New York State regulatory text from 23 NYCRR Part 500. It is educational, not legal advice. Last reviewed: 2026-11-15.

Other 23 NYCRR Part 500 Requirements

Previous section: 500.11 Third-Party Service Provider Security Policy. Next section: 500.13 Asset Management and Data Retention Requirements. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.