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.9 Risk Assessment?

Short Answer

23 NYCRR 500.9 requires a periodic, documented risk assessment of the covered entity’s information systems that informs the cybersecurity program, carried out under written policies and procedures. Since the Second Amendment it must be reviewed and updated at least annually and whenever a business or technology change materially changes cyber risk.

23 NYCRR 500.9 Risk Assessment at a Glance

  • Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
  • Section: 23 NYCRR 500.9 Risk Assessment.
  • Status: Amended by the Second Amendment, effective November 1, 2023.
  • Who it applies to: Every covered entity unless exempt from Part 500 entirely. 500.9 is not waived by the 500.19(a), (c) or (d) exemptions.
  • Class A companies: None beyond the general requirement. The Class A independent audits in 500.2(c) are based on the risk assessment.
  • Limited exemption (500.19(a)): Not exempt under 500.19(a), (c) or (d).
  • Compliance dates: The amended review frequency in 500.9(a), at least annually and after material changes, applied from April 29, 2024 (500.22(c)).

The risk assessment is the foundation the rest of Part 500 refers back to. The program in 500.2, the policies in 500.3, scanning frequency in 500.5, access limits in 500.7, monitoring in 500.14 and third-party policies in 500.11 are all meant to be based on it.

The Second Amendment set a minimum: review and update at least annually and whenever a change in the business or technology causes a material change to cyber risk. It also rewrote the definition of risk assessment in 500.1(p) to describe identifying, estimating and prioritizing cybersecurity risks, using threat and vulnerability analysis.

What Does 23 NYCRR 500.9 Require?

The following is the text of 23 NYCRR 500.9 Risk Assessment as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability. Text not changed by the Second Amendment (500.9(b)) is shown as published in the New York Codes, Rules and Regulations, which keeps the capitalized defined terms of the original 2017 regulation.

  • (a) Each covered entity shall conduct a periodic risk assessment of the covered entity’s information systems sufficient to inform the design of the cybersecurity program as required by this Part. Such risk assessment shall be reviewed and updated as reasonably necessary, but at a minimum annually, and whenever a change in the business or technology causes a material change to the covered entity’s cyber risk. The covered entity’s risk assessment shall allow for revision of controls to respond to technological developments and evolving threats and shall consider the particular risks of the covered entity’s business operations related to cybersecurity, nonpublic information collected or stored, information systems utilized and the availability and effectiveness of controls to protect nonpublic information and information systems.
  • (b) The Risk Assessment shall be carried out in accordance with written policies and procedures and shall be documented. Such policies and procedures shall include:
  • (1) criteria for the evaluation and categorization of identified cybersecurity risks or threats facing the Covered Entity;
  • (2) criteria for the assessment of the confidentiality, integrity, security and availability of the Covered Entity's Information Systems and Nonpublic Information, including the adequacy of existing controls in the context of identified risks; and
  • (3) requirements describing how identified risks will be mitigated or accepted based on the Risk Assessment and how the cybersecurity program will address the risks.

Source: NY DFS, Second Amendment to 23 NYCRR 500 (text) and 23 NYCRR 500.9 as published in the NYCRR (Cornell LII).

How Does 23 NYCRR 500.9 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.9 to 23 SCF controls through 30 relationships (2 "subset of", 28 "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-02 Risk Management Program. Subset of (strength 10): 500.9(a), 500.9(b). SCF control: Mechanisms exist to facilitate the implementation of strategic, operational and tactical risk management controls that are aligned with: (1) The organization's Enterprise Risk Management (ERM); and (2) Industry-recognized cybersecurity risk management practices.
  • RSK-13 Risk Assessment. Intersects with (strength 5): 500.9(a), 500.9(b), 500.9(b)(1), 500.9(b)(2). SCF control: Mechanisms exist to conduct recurring assessments of risk that includes the likelihood and magnitude of harm, from unauthorized access, use, disclosure, disruption, modification or destruction of the organization's Technology Assets, Applications, Services and/or Data (TAASD).
  • RSK-13.2 Risk Assessment Update. Intersects with (strength 5): 500.9(a). SCF control: Mechanisms exist to routinely update risk assessments and react accordingly upon identifying new security vulnerabilities, including using outside sources for security vulnerability information.
  • RSK-14 Risk Register. Intersects with (strength 5): 500.9(a). SCF control: Mechanisms exist to maintain a risk register that facilitates monitoring and reporting of risks.
  • GOV-07 Materiality Determination. Intersects with (strength 5): 500.9(b)(1), 500.9(b)(2). SCF control: Mechanisms exist to define materiality threshold criteria capable of designating an incident as material.
  • RSK-05 Risk Framing. Intersects with (strength 5): 500.9(b)(1). SCF control: Mechanisms exist to identify: (1) Assumptions affecting risk assessments, risk response and risk monitoring; (2) Constraints affecting risk assessments, risk response and risk monitoring; (3) The organizational risk tolerance; and (4) Priorities, benefits and trade-offs considered by the organization for managing risk.
  • RSK-05.1 Risk Tolerance. Intersects with (strength 5): 500.9(b)(1). SCF control: Mechanisms exist to define organizational risk tolerance, the specified range of acceptable results.
  • RSK-05.2 Risk Threshold. Intersects with (strength 5): 500.9(b)(1). SCF control: Mechanisms exist to define organizational risk threshold, the level of risk exposure above which risks are addressed and below which risks may be accepted.
  • RSK-05.3 Risk Appetite. Intersects with (strength 5): 500.9(b)(1). SCF control: Mechanisms exist to define organizational risk appetite, the degree of uncertainty the organization is willing to accept in anticipation of a reward.
  • RSK-06 Material Risks. Intersects with (strength 5): 500.9(b)(1), 500.9(b)(2). SCF control: Mechanisms exist to define criteria necessary to designate a risk as a material risk.
  • RSK-09 Risk Identification. Intersects with (strength 5): 500.9(b)(1). SCF control: Mechanisms exist to identify and document risks, both internal and external.
  • RSK-10 Risk Catalog. Intersects with (strength 5): 500.9(b)(1). SCF control: Mechanisms exist to develop and keep current a catalog of applicable risks associated with the organization's business operations and technologies in use.
  • THR-04 Threat Intelligence Feeds. Intersects with (strength 5): 500.9(b)(1). SCF control: Mechanisms exist to maintain situational awareness of vulnerabilities and evolving threats by leveraging the knowledge of attacker tactics, techniques and procedures to facilitate the implementation of preventative and compensating controls.
  • THR-06 Threat Catalog. Intersects with (strength 5): 500.9(b)(1). SCF control: Mechanisms exist to develop and keep current a catalog of applicable internal and external threats to the organization, both natural and manmade.
  • THR-07 Material Threats. Intersects with (strength 5): 500.9(b)(1), 500.9(b)(2). SCF control: Mechanisms exist to define criteria necessary to designate a threat as a material threat.
  • THR-08 Threat Analysis. Intersects with (strength 5): 500.9(b)(1). SCF control: Mechanisms exist to identify, assess, prioritize and document the potential impact(s) and likelihood(s) of applicable internal and external threats.
  • GOV-04.2 Exception Management. Intersects with (strength 5): 500.9(b)(3). SCF control: Mechanisms exist to prohibit exceptions to standards, except when the exception has been formally assessed for risk impact, approved and recorded.
  • RSK-07 Risk-Based Security Categorization. Intersects with (strength 5): 500.9(b)(3). SCF control: Mechanisms exist to categorize Technology Assets, Applications, Services and/or Data (TAASD) in accordance with applicable laws, regulations and contractual obligations that: (1) Document the security categorization results (including supporting rationale) in the security plan for systems; and (2) Ensure the security categorization decision is reviewed and approved by the asset owner.
  • RSK-07.1 Impact-Level Prioritization. Intersects with (strength 5): 500.9(b)(3). SCF control: Mechanisms exist to prioritize the impact level for Technology Assets, Applications and/or Services (TAAS) to prevent potential disruptions.
  • RSK-15 Risk Ranking. Intersects with (strength 5): 500.9(b)(3). SCF control: Mechanisms exist to identify and assign a risk ranking to newly discovered security vulnerabilities that is based on industry-recognized practices.
  • RSK-16 Risk Response. Intersects with (strength 5): 500.9(b)(3). SCF control: Mechanisms exist to ensure proper risk response actions were performed to remediate findings from security, compliance and/or resilience-related: (1) Assessments; (2) Audits; and/or (3) Incidents.
  • RSK-17 Risk Remediation. Intersects with (strength 5): 500.9(b)(3). SCF control: Mechanisms exist to remediate risks to an acceptable level.
  • RSK-18 Compensating Countermeasures. Intersects with (strength 5): 500.9(b)(3). 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.

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.9

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

  • An assessment that does not drive the program. The assessment must be sufficient to inform the design of the cybersecurity program. If controls do not trace back to it, that link is hard to show.
  • No trigger for material changes. Annual updates are a minimum. Mergers, new systems or major platform changes that materially change cyber risk need an update too.
  • Missing written methodology. 500.9(b) requires written policies and procedures with criteria for categorizing risks, assessing confidentiality, integrity, security and availability, and deciding how risks are mitigated or accepted.
  • Treating exemption as exemption from risk assessment. None of the exemptions in 500.19(a), (c) or (d) waive 500.9.

What Is Reasonable Evidence for 23 NYCRR 500.9?

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.9 include:

  • E-RSK-01 Risk Management Program (RMP). Documented evidence of a Risk Management Program (RMP). This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on organizational practices that support existing policies and standards.
  • E-RSK-04 Cybersecurity Risk Assessment (RA). Documented evidence of a cybersecurity-specific risk assessment.
  • 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.
  • E-RSK-06 Risk Threshold. Documented evidence the organization has a defined risk threshold.
  • E-RSK-07 Risk Tolerance. Documented evidence the organization has a defined risk tolerance.
  • E-RSK-08 Risk Appetite. Documented evidence the organization has a defined risk appetite.
  • E-RSK-10 Material Risk Definition. Documented evidence of criteria necessary to designate a risk as a material risk.
  • E-GOV-06 Exception Management. Documented evidence of authorized exceptions to standards (e.g., configurations, practices, etc.)

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

  • Risk assessment methodology. Written policies and procedures covering the three items in 500.9(b).
  • Current risk assessment report. Dated within the last year, with identified risks, ratings and treatment decisions.
  • Material change log. Records of business or technology changes and the related assessment updates.
  • Risk treatment register. How each risk will be mitigated or accepted and how the program addresses it.

Which ComplianceForge Documents Support 23 NYCRR 500.9?

The following ComplianceForge documents can help you document and implement 23 NYCRR 500.9 Risk Assessment:

Frequently Asked Questions (FAQ)

How often must the 23 NYCRR 500.9 risk assessment be updated? At a minimum annually, and whenever a change in the business or technology causes a material change to the covered entity's cyber risk.

What must the written risk assessment policies and procedures include? Under 500.9(b): criteria for evaluating and categorizing identified cybersecurity risks or threats; criteria for assessing the confidentiality, integrity, security and availability of information systems and nonpublic information, including the adequacy of existing controls; and requirements describing how identified risks will be mitigated or accepted and how the program will address them.

Do exempt entities still need a risk assessment? Yes. 500.9 is not listed in the 500.19(a), (c) or (d) exemptions, so entities that rely on those exemptions still need one.

How does the Second Amendment define a risk assessment? 500.1(p) defines it as the process of identifying, estimating and prioritizing cybersecurity risks to organizational operations, assets, individuals, customers, consumers, other organizations and critical infrastructure resulting from the operation of an information system, incorporating threat and vulnerability analyses and considering mitigations provided by security controls.

Bottom Line on 23 NYCRR 500.9 Risk Assessment

500.9 is the requirement the rest of Part 500 leans on. Write the methodology, update the assessment at least every year and after material changes, and make sure program decisions trace back to it.

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.8 Application Security. Next section: 500.10 Cybersecurity Personnel and Intelligence. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.