# NYDFS Part 500.5: Timely Remediation, No Day Count

Canonical: https://patchmanagementpolicy.com/patch-windows/nydfs-part-500/
Last reviewed: 19 Nov 2026

## NYDFS patch management

NYDFS 23 NYCRR 500.5(c) requires covered entities to "timely remediate vulnerabilities, giving priority to vulnerabilities based on the risk they pose." No number of days is set. Section 500.5 was amended effective 1 Nov 2023 and also requires written vulnerability management policies. Read on the Cornell LII copy, 19 Nov 2026.

### The section as published

Section 500.5, titled Vulnerability management, begins by requiring each covered entity, "in accordance with its risk assessment," to "develop and implement written policies and procedures for vulnerability management that are designed to assess and maintain the effectiveness of its cybersecurity program." Those policies must be designed to ensure that the entity does three things.

| Paragraph | Verbatim text | Timing wording |
|---|---|---|
| 500.5(a)(1) | penetration testing "from both inside and outside the information systems' boundaries by a qualified internal or external party at least annually" | At least annually |
| 500.5(a)(2) | "automated scans of information systems, and a manual review of systems not covered by such scans" | "at a frequency determined by the risk assessment, and promptly after any material system changes" |
| 500.5(b) | "are promptly informed of new security vulnerabilities by having a monitoring process in place" | Promptly |
| 500.5(c) | "timely remediate vulnerabilities, giving priority to vulnerabilities based on the risk they pose to the covered entity" | Timely, risk-prioritized |

23 NYCRR 500.5, Adopted 1 Mar 2017 (eff. 3/1/2017), Amended 1 Nov 2023 (eff. 11/1/2023), per the register notes on the Cornell LII copy.

Four time words appear (annually, promptly, timely and a frequency set by the risk assessment) and none is a number except the yearly penetration test. The department's own site, dfs.ny.gov, was reached but the Part 500 text was not read there, so this page relies on the Cornell Legal Information Institute copy.

### What changed in 2023

The register notes show the section was adopted effective 1 Mar 2017 and amended effective 1 Nov 2023. The text as read is the amended one. Which words the 2023 amendment changed was not compared against the 2017 text and is not stated here.

### What a policy must write

- A written vulnerability management policy and procedure that cites the entity's risk assessment as its basis.
- A definition of timely for remediation, in days per risk tier, since the regulation leaves it open. The tiers must trace to the risk each vulnerability poses to the entity, because 500.5(c) orders priority by risk.
- A scan frequency chosen from the risk assessment, a manual review for systems the scans do not cover, and a rule to scan promptly after material system changes.
- A monitoring process that tells the entity of new vulnerabilities, with the sources named.
- An annual penetration test by a qualified party, inside and outside the boundary.

### Evidence

The paragraph structure shows what can be checked: the written policy, the risk assessment that sets scan frequency, scan and manual review records, evidence of the monitoring process, the penetration test report and dates, and remediation records showing risk-based ordering. Any inspection practice of the department beyond the text was not read. For a regulator that names a number, compare [HIPAA's proposed 15 and 30 days](https://patchmanagementpolicy.com/patch-windows/hipaa-security-rule/); for one that also leaves the number to the entity but requires escalation, see [DORA](https://patchmanagementpolicy.com/patch-windows/dora/); and see the full [Patch Window Table](https://patchmanagementpolicy.com/patch-windows/).

### Sources

- [Cornell LII, 23 NYCRR 500.5 Vulnerability management](https://www.law.cornell.edu/regulations/new-york/23-NYCRR-500.5), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patch Window Table: Deadlines in 12 Frameworks](https://patchmanagementpolicy.com/patch-windows/)
- [HIPAA Patch Rules: In Force Text and the 15/30 Day Proposal](https://patchmanagementpolicy.com/patch-windows/hipaa-security-rule/)
- [DORA Patch Management: Article 10 of RTS 2024/1774](https://patchmanagementpolicy.com/patch-windows/dora/)
- [Severity and Patch Windows: What Each Framework Sets](https://patchmanagementpolicy.com/policy-sections/severity-and-patch-windows/)
