Reference · Cybersecurity
NYDFS Industry Letter on Frontier AI Models and Cybersecurity Risk (21 May 2026)
Cybersecurity Advisory: Heightened Cybersecurity Risks Associated with Frontier AI Models
On 21 May 2026 the New York State Department of Financial Services sent an industry letter to the chief information security officers of DFS regulated entities on heightened cybersecurity risks from certain frontier AI models, which amplify the potency, scale, and speed of identifying vulnerabilities and exploits in information systems.NYDFS frontier AI letter It came with companion guidance of the same date, Measures Regulated Entities Should Consider in a Heightened Cybersecurity Threat Environment.Companion guidance The letter does not impose any new requirements.NYDFS frontier AI letter
An advisory to CISOs that adds no requirements
The letter is addressed to the CISOs of DFS regulated entities, the institutions covered by the Department's cybersecurity regulation, 23 NYCRR Part 500. It changes no rule text and imposes no new requirements.NYDFS frontier AI letter The companion guidance likewise establishes no new legal requirements and leaves what Part 500 requires unchanged.Companion guidance Their force comes from the Part 500 obligations already in place, which the letter asks entities to re-examine against a new threat assumption.
Assume attackers can find and exploit vulnerabilities faster
The letter describes frontier AI models that make threat actors more capable of identifying and exploiting vulnerabilities in information systems, at greater speed and scale, with consequent risk to consumers' nonpublic information. Although certain frontier AI models are not yet broadly available, it says such capabilities may become more available soon. It names no model or vendor.NYDFS frontier AI letter
Accelerate vulnerability work, map dependencies, and review AI-written code
The letter asks entities to take these steps, pointing to sections of the companion guidance for most of them.
- Vulnerability management. Identify and remediate vulnerabilities in firmware, hardware, and software expeditiously, reassess how the criticality and threat of known vulnerabilities are evaluated, and review remediation timelines to decide, based on updated Risk Assessments, whether detection and remediation need to accelerate.NYDFS frontier AI letterCompanion guidance · § 1.1
- Third-party service providers. Develop and maintain dependency maps, coordinate with critical third-party service providers and material downstream providers, review threat intelligence, and monitor and validate third-party code.NYDFS frontier AI letterCompanion guidance · §§ 2.3, 2.5, 2.6
- Secure programming. Restrict and validate inputs before scripts or processes run, confirm that secure programming practices are used, and apply additional testing and validation, including human oversight, to AI-generated code before it is deployed to production. Entities using AI to find and fix vulnerabilities should use practices that prevent unknown changes in code or configurations.NYDFS frontier AI letterCompanion guidance · §§ 1.8, 1.9
- Monitoring and reporting. Make sure suspicious activity is promptly flagged and addressed, evaluate whether existing logging and security event alerting are sufficient, and review and test threat-relevant operational resilience procedures.NYDFS frontier AI letterCompanion guidance · §§ 2.2, 3.2
- Legacy systems. Consider whether to strengthen operational resilience by replacing end-of-life or legacy information systems.NYDFS frontier AI letter
- Part 500. Review the cybersecurity program to ensure full compliance with the regulation, considering the measures in sections 1, 2, and 3.2 of the companion guidance.NYDFS frontier AI letter
The October 2024 letter supplies the Part 500 section numbers
The May 2026 letter cites Part 500 as a whole and uses its defined terms, such as Risk Assessment and Third-Party Service Provider, without pointing to numbered sections.NYDFS frontier AI letter The companion guidance also refers to Part 500 generally, and cites only the definition of nonpublic information in 500.1(k).Companion guidance
The section-by-section mapping is in the Department's letter of 16 October 2024 on cybersecurity risks arising from AI, which the May letter points to for more on AI threats and capabilities.NYDFS frontier AI letter That letter imposes no requirements beyond Part 500, and it ties each area of AI risk management to the sections below.NYDFS AI letter Read together, the May 2026 letter supplies the threat scenario and the October 2024 letter supplies the section numbers.
| Area in the October 2024 letter | Part 500 sections cited |
|---|---|
| Risk assessments and risk-based programs | 500.2, 500.3, 500.9, 500.11, 500.16 |
| Third-party service provider management | 500.11 |
| Access controls | 500.7, 500.12 |
| Cybersecurity training | 500.10, 500.14 |
| Monitoring | 500.5, 500.14 |
| Data management | 500.3, 500.13 |
The September 2026 guidance makes AI adoption a reassessment question
Part 500 requires a Risk Assessment that is reviewed and updated as reasonably necessary, at least annually, and whenever a change in the business or technology causes a material change to the entity's cyber risk.23 NYCRR 500 · § 500.9(a) On 10 September 2026 the Department issued guidance on how to conduct and use that Risk Assessment, and it states that it does not create new obligations.NYDFS Risk Assessment guidance
The guidance says Risk Assessments should consider whether emerging technologies or changes in the threat environment materially affect the entity's risk profile, and its examples include the adoption or use of artificial intelligence.NYDFS Risk Assessment guidance · Emerging Risks Among the material changes that call for a review, it lists significant developments in cybersecurity technologies, giving frontier AI models as the example and citing the May 2026 letter.NYDFS Risk Assessment guidance · § 5
An entity that has adopted AI since it last revisited its Risk Assessment now has the Department's own examples to measure that change against. The AI-specific expectations themselves come from the October 2024 and May 2026 letters.
Control mapping
What a reviewer expects to be able to see.
| Obligation | What the system must do | Evidence a reviewer expects |
|---|---|---|
| Vulnerability criticality and timelines | Reassess how criticality is rated and whether remediation timelines need to accelerate, based on an updated Risk Assessment | Updated Risk Assessment, revised criticality procedure, and timeline changes with dates |
| Dependency maps | Maintain maps of downstream dependencies and coordinate with critical third-party service providers | Dependency map, provider contact and responsibility records, and threat-intelligence reviews |
| Input validation and secure coding | Restrict and validate inputs before scripts or processes run, and confirm secure programming practices | Coding standards, validation controls, and review records |
| AI-generated code | Apply additional testing, validation, and human oversight before AI-generated code reaches production | Review records showing a named person approved each AI-generated change |
| Logging and alerting | Evaluate whether current logging and alerting flag suspicious activity fast enough for the heightened threat | Adequacy review, alert-handling records, and any tuning applied |
| Legacy and end-of-life systems | Decide, and record, whether to replace end-of-life or legacy systems | Inventory of end-of-life systems and the documented decision on each |
Key dates
Timeline, drawn to scale
NYDFS guidance on AI under Part 500
- 1 November 2023Second Amendment to Part 500 takes effect.
- 16 October 2024Industry letter: Cybersecurity Risks Arising from Artificial Intelligence and Strategies to Combat Related Risks.
- 1 November 2025Asset inventory requirement under 500.13(a) applies.
- 21 May 2026Frontier AI advisory and the companion guidance on measures in a heightened threat environment issued.
- 10 September 2026Guidance on How to Conduct and Use Risk Assessments issued. It names the adoption or use of artificial intelligence among the emerging risks to assess, and states it does not create new obligations.
Sources cited
- ×13NYDFS industry letter, 21 May 2026: Heightened Cybersecurity Risks Associated with Frontier AI Models
- ×7NYDFS guidance, 21 May 2026: Measures Regulated Entities Should Consider in a Heightened Cybersecurity Threat Environment
- ×1NYDFS industry letter, 16 October 2024: Cybersecurity Risks Arising from Artificial Intelligence and Strategies to Combat Related Risks
- ×123 NYCRR Part 500, Cybersecurity Requirements for Financial Services Companies, as amended (NYDFS copy, PDF)
- ×3NYDFS guidance, 10 September 2026: How to Conduct and Use Risk Assessments Required by the DFS Cybersecurity Regulation
Common gaps
Where the letter's expectations and current practice most often diverge.
- A Risk Assessment that predates the letter. The letter's asks are conditioned on updated Risk Assessments. An assessment last revised before May 2026 cannot show that the frontier-model threat was considered.
- Patch timelines fixed by calendar. The letter asks whether remediation should accelerate for vulnerabilities an AI-assisted attacker can find faster. A timeline unchanged since 2025 needs a written reason.
- AI-generated code without a named reviewer. The letter names human oversight of AI-generated code before production. A change approved by the same assistant that wrote it, or merged automatically, has no reviewer to name.
- No dependency map for AI providers. Model providers and the tooling around them are downstream dependencies. If the map stops at the traditional vendor list, the coordination the letter asks for has nowhere to start.
- Legacy systems with no decision recorded. The letter asks entities to consider replacement. A system kept with no recorded decision reads as never considered.
In practice
Related
Last reviewed October 11, 2026. This reference summarises publicly available regulatory guidance and is provided for general information. It is not legal advice. Obligations depend on an institution's charter, registration status, size, and activities. Verify against the primary sources cited above and consult counsel before relying on any summary here.