{
 "page": "https://insights.moraph.com/compare/mfa-requirements",
 "csv": "https://insights.moraph.com/compare/mfa-requirements.csv",
 "publisher": "Moraph",
 "license": "https://creativecommons.org/licenses/by/4.0/",
 "license_note": "License: CC BY 4.0. Underlying government texts are public domain or under their own terms.",
 "attribution": "Moraph Insights, https://insights.moraph.com/compare/mfa-requirements",
 "slug": "mfa-requirements",
 "title": "Multi-factor authentication requirements compared",
 "sector": "Cross-sector",
 "lens": "Security & Resilience",
 "in_short": "The FTC Safeguards Rule and the NYDFS Cybersecurity Regulation both require MFA for any individual accessing an information system, unless equivalent or more secure controls are approved in writing; NYDFS entities with a limited exemption need MFA only for remote access and privileged accounts. For federal agencies, Executive Order 14028 requires MFA to the maximum extent consistent with law, and OMB M-22-09 requires phishing-resistant MFA for staff, contractors and partners. IRS Publication 1075 requires MFA for privileged and non-privileged accounts on systems handling federal tax information. The current HIPAA Security Rule does not explicitly require MFA; the proposed update would, but as of 2026-11-14 it has not been finalized.",
 "method": "We read each rule or directive in its official source: the eCFR for federal regulations, the Federal Register for the executive order and the HIPAA proposal, the NYDFS copy of Part 500, OMB's published memorandum, the IRS's current Publication 1075 and the FBI's CJIS Security Policy version 6.1 PDF. Each cell was first checked on 2026-11-13 and re-checked against the same sources on 2026-11-14; the CJIS row was first checked on 2026-11-14. Requirement text is our short paraphrase of the source. Sources we could not open, or whose license terms are not yet recorded, were left out (see Omitted). This table explains the rules; it is not legal advice.",
 "published": "2026-11-13",
 "last_reviewed": "2026-11-14",
 "columns": [
  {
   "id": "regime",
   "label": "Rule"
  },
  {
   "id": "requirement",
   "label": "Requirement"
  },
  {
   "id": "scope",
   "label": "Scope"
  },
  {
   "id": "effective",
   "label": "Effective date"
  },
  {
   "id": "citation",
   "label": "Citation"
  }
 ],
 "rows": [
  {
   "id": "ftc-safeguards",
   "cells": {
    "regime": {
     "text": "FTC Safeguards Rule",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "requirement": {
     "text": "Implement multi-factor authentication for any individual accessing any information system, unless the Qualified Individual approves in writing reasonably equivalent or more secure access controls",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "Any individual accessing any information system",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "June 9, 2023",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "16 CFR 314.4(c)(5)",
     "source": "s1",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "nydfs-500-12",
   "cells": {
    "regime": {
     "text": "NYDFS Cybersecurity Regulation",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "requirement": {
     "text": "Multi-factor authentication for any individual accessing any information systems. If the covered entity has a CISO, the CISO may approve reasonably equivalent or more secure compensating controls in writing, reviewed periodically and at least annually.",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "All covered entities. Those with a limited exemption must still use MFA for remote access to their systems, remote access to third-party applications holding nonpublic information, and all privileged accounts (except service accounts that prohibit interactive login).",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "The second amendment to Part 500 took effect November 1, 2023 (500.21(b)); covered entities had two years from that date to comply with its new 500.12 requirements (500.22(d)(4))",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "23 NYCRR 500.12; 500.21(b); 500.22(d)(4)",
     "source": "s3",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "eo-14028",
   "cells": {
    "regime": {
     "text": "Executive Order 14028",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "requirement": {
     "text": "Within 180 days of the order, agencies shall adopt multi-factor authentication and encryption for data at rest and in transit, to the maximum extent consistent with federal records laws and other applicable laws. Heads of Federal Civilian Executive Branch agencies unable to fully adopt them within 180 days had to give a written rationale.",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "Federal agencies; reporting duties fall on Federal Civilian Executive Branch agencies",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "Within 180 days of the order of May 12, 2021",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "Executive Order 14028, sec. 3(d)",
     "source": "s4",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "omb-m-22-09",
   "cells": {
    "regime": {
     "text": "OMB Memorandum M-22-09 (federal zero trust strategy)",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "requirement": {
     "text": "Agencies must require staff, contractors and partners to use a phishing-resistant method to access agency-hosted accounts; for their routine self-service access, agency systems must stop supporting methods that fail to resist phishing, such as SMS or voice codes, one-time codes and push notifications. Public-facing systems that support MFA must offer a phishing-resistant option.",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "Executive departments and agencies",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "Issued January 26, 2022. Goals to be met by the end of fiscal year 2024; the public-facing option within one year of issuance.",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "OMB M-22-09",
     "source": "s5",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "irs-pub-1075",
   "cells": {
    "regime": {
     "text": "IRS Publication 1075",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "requirement": {
     "text": "Multi-factor authentication for privileged accounts and for non-privileged accounts. For remote access, one factor must come from a separate device that meets Authenticator Assurance Level 2 under NIST SP 800-63.",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "Federal, state and local agencies that receive federal tax information; privileged accounts may skip MFA only for direct terminal access inside a restricted area",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "The November 2021 revision took effect six months after publication",
     "source": "s6",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "IRS Publication 1075, control IA-2 (CE-1, CE-2, CE-6)",
     "source": "s6",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "cjis-security-policy",
   "cells": {
    "regime": {
     "text": "CJIS Security Policy (FBI), version 6.1",
     "source": "s9",
     "checked": "2026-11-14"
    },
    "requirement": {
     "text": "Implement multi-factor authentication for access to privileged accounts (IA-2 (1)) and for access to non-privileged accounts (IA-2 (2)). Regardless of the type of access (local, network or remote), accounts are authenticated using multi-factor options appropriate for the level of risk.",
     "source": "s9",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "All entities with access to, or that operate systems used to process, store or transmit, criminal justice information (CJI)",
     "source": "s9",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "Version 6.1 is dated June 25, 2026. IA-2 (1) and (2) are marked Priority 1; beginning October 1, 2024, Priority 1 requirements and those existing before the modernization are the set of sanctionable requirements.",
     "source": "s9",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "CJIS Security Policy v6.1 (06/25/2026), IA-2 (1) and (2); sections 1.2 and 1.4",
     "source": "s9",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "hipaa-current",
   "cells": {
    "regime": {
     "text": "HIPAA Security Rule (current)",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "requirement": {
     "text": "No explicit MFA requirement in the Security Rule. Section 164.312(d) requires procedures to verify that a person or entity seeking access to electronic protected health information is the one claimed.",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "HIPAA covered entities and business associates",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "Current rule text as checked on 2026-11-14",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "45 CFR 164.312(d)",
     "source": "s7",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "hipaa-proposed",
   "cells": {
    "regime": {
     "text": "HIPAA Security Rule (proposed update)",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "requirement": {
     "text": "Proposed, not in force: deploy MFA to all technology assets in relevant electronic information systems, and for any action that changes a user's privileges, with listed exceptions",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "HIPAA covered entities and business associates",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "effective": {
     "text": "Proposed January 6, 2025 (comments closed March 7, 2025). As of 2026-11-14 the Federal Register shows no final rule.",
     "source": "s8",
     "checked": "2026-11-14"
    },
    "citation": {
     "text": "Proposed 45 CFR 164.312(f)(2)(ii), 90 FR 898",
     "source": "s8",
     "checked": "2026-11-14"
    }
   }
  }
 ],
 "sources": [
  {
   "id": "s1",
   "title": "16 CFR 314.4(c)(5), Standards for Safeguarding Customer Information",
   "publisher": "Federal Trade Commission",
   "url": "https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-314/section-314.4",
   "checked": "2026-11-14"
  },
  {
   "id": "s2",
   "title": "16 CFR 314.5, Effective date (version in force on 2023-01-01, 87 FR 71510)",
   "publisher": "Federal Trade Commission",
   "url": "https://www.ecfr.gov/on/2023-01-01/title-16/chapter-I/subchapter-C/part-314/section-314.5",
   "checked": "2026-11-14"
  },
  {
   "id": "s3",
   "title": "23 NYCRR 500.12, 500.21 and 500.22, Second Amendment text (DFS copy; DFS notes it is not an official version)",
   "publisher": "New York State Department of Financial Services",
   "url": "https://www.dfs.ny.gov/system/files/documents/2026/10/NYCRR-part-500-Cybersecurity-Regulation_1.pdf",
   "checked": "2026-11-14"
  },
  {
   "id": "s4",
   "title": "Executive Order 14028, Improving the Nation's Cybersecurity, section 3(d) (86 FR 26633)",
   "publisher": "Executive Office of the President (published by the Office of the Federal Register)",
   "url": "https://www.federalregister.gov/documents/2021/05/17/2021-10460/improving-the-nations-cybersecurity",
   "checked": "2026-11-14"
  },
  {
   "id": "s5",
   "title": "OMB Memorandum M-22-09, Moving the U.S. Government Toward Zero Trust Cybersecurity Principles",
   "publisher": "Office of Management and Budget",
   "url": "https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf",
   "checked": "2026-11-14"
  },
  {
   "id": "s6",
   "title": "IRS Publication 1075 (Rev. 11-2021), Tax Information Security Guidelines for Federal, State and Local Agencies, control IA-2",
   "publisher": "Internal Revenue Service",
   "url": "https://www.irs.gov/pub/irs-pdf/p1075.pdf",
   "checked": "2026-11-14"
  },
  {
   "id": "s7",
   "title": "45 CFR part 164, subpart C, Security Standards for the Protection of Electronic Protected Health Information (HIPAA Security Rule), including 164.312(d)",
   "publisher": "U.S. Department of Health and Human Services",
   "url": "https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C",
   "checked": "2026-11-14"
  },
  {
   "id": "s8",
   "title": "HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, proposed rule (90 FR 898)",
   "publisher": "U.S. Department of Health and Human Services",
   "url": "https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information",
   "checked": "2026-11-14"
  },
  {
   "id": "s9",
   "title": "Criminal Justice Information Services (CJIS) Security Policy, Version 6.1 (06/25/2026), sections 1.2 and 1.4 and IA-2",
   "publisher": "Federal Bureau of Investigation, Criminal Justice Information Services Division",
   "url": "https://le.fbi.gov/file-repository/cjis_security_policy_v6-1_20260625-1.pdf",
   "checked": "2026-11-14"
  }
 ],
 "notes": [
  "The FTC's effective date comes from 16 CFR 314.5 as it stood in 2023; the current section 314.5 now gives only the date for the notification duty in 314.4(j).",
  "NYDFS publishes the amended Part 500 on its website with a note that its copy is not an official version."
 ],
 "omitted": [
  {
   "where": "pci-dss/all",
   "reason": "PCI DSS is left out: the PCI Security Standards Council's Terms and Conditions (https://www.pcisecuritystandards.org/terms_and_conditions/), as read on 2026-11-14, permit use of site content for personal, non-commercial purposes only and bar use for any non-personal purpose without a separate written agreement."
  }
 ]
}
