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.8 Application Security?

Short Answer

23 NYCRR 500.8 requires written procedures, guidelines and standards for secure development of in-house applications and for evaluating, assessing or testing the security of externally developed applications used in the covered entity’s environment. The CISO or a qualified designee must review, assess and update them at least annually.

23 NYCRR 500.8 Application Security at a Glance

  • Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
  • Section: 23 NYCRR 500.8 Application Security.
  • Status: Amended by the Second Amendment, effective November 1, 2023.
  • Who it applies to: Every covered entity that does not qualify for an exemption under 500.19(a), (c) or (d).
  • Class A companies: None beyond the general requirement.
  • Limited exemption (500.19(a)): Exempt. 500.19(a) limited-exemption entities do not need to meet 500.8.
  • Compliance dates: 500.8(a) has applied since the original regulation (18 months from March 1, 2017 under 500.22(b)(2)). The amended annual review in 500.8(b) applied from April 29, 2024 (500.22(c)).

Section 500.8 covers both software you build and software you buy. In-house applications need secure development practices, and externally developed applications need a way to evaluate, assess or test their security in your technology environment.

The Second Amendment changed only 500.8(b). The old periodic review became a review, assessment and update at least annually by the CISO or a qualified designee.

What Does 23 NYCRR 500.8 Require?

The following is the text of 23 NYCRR 500.8 Application Security 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.8(a)) 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's cybersecurity program shall include written procedures, guidelines and standards designed to ensure the use of secure development practices for in-house developed applications utilized by the Covered Entity, and procedures for evaluating, assessing or testing the security of externally developed applications utilized by the Covered Entity within the context of the Covered Entity's technology environment.
  • (b) All such procedures, guidelines and standards shall be reviewed, assessed and updated as necessary by the CISO (or a qualified designee) of the covered entity at least annually.

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

How Does 23 NYCRR 500.8 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.8 to 8 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.

  • TDA-02 Technology Development & Acquisition. Subset of (strength 10): 500.8(a). SCF control: Mechanisms exist to facilitate the implementation of tailored development and acquisition strategies, contract tools and procurement methods to meet unique business needs.
  • GOV-04 Publishing Security, Compliance & Resilience Documentation. Intersects with (strength 5): 500.8(a). SCF control: Mechanisms exist to establish, maintain and disseminate policies, standards and procedures necessary for secure, compliant and resilient capabilities.
  • OPS-04 Standardized Operating Procedures (SOP). Intersects with (strength 5): 500.8(a). SCF control: Mechanisms exist to identify and document Standardized Operating Procedures (SOP), or similar documentation, to enable the proper execution of day-to-day / assigned tasks.
  • TDA-03.2 Secure Settings By Default. Intersects with (strength 5): 500.8(a). SCF control: Mechanisms exist to implement secure configuration settings by default to reduce the likelihood of Technology Assets, Applications and/or Services (TAAS) being deployed with weak security settings that would put the TAAS at a greater risk of compromise.
  • TDA-05 Secure Software Development Practices (SSDP). Intersects with (strength 5): 500.8(a). SCF control: Mechanisms exist to develop applications based on Secure Software Development Practices (SSDP).
  • TDA-05.4 Software Design Review. Intersects with (strength 5): 500.8(a). SCF control: Mechanisms exist to have an independent review of the software design to validate: (1) Applicable security, compliance and resilience requirements are met; and (2) Identified risks are remediated.
  • TDA-17 Security, Compliance & Resilience Testing Throughout Development. Intersects with (strength 5): 500.8(a). SCF control: Mechanisms exist to require system developers/integrators consult with security, compliance and/or resilience personnel to: (1) Create and implement a Security Testing and Evaluation (ST&E) plan, or similar capability; (2) Implement a verifiable flaw remediation process to correct weaknesses and deficiencies identified during the control testing and evaluation process; and (3) Document the results.
  • GOV-04.1 Periodic Review & Update of Security, Compliance & Resilience Program. Intersects with (strength 5): 500.8(b). SCF control: Mechanisms exist to review the Security, Compliance & Resilience Program (SCRP), including policies, standards and procedures, at planned intervals or if significant changes occur to ensure their continuing suitability, adequacy and effectiveness.

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

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

  • Ignoring purchased and SaaS applications. 500.8(a) covers procedures for evaluating, assessing or testing externally developed applications used by the covered entity, not only in-house code.
  • Standards with no annual review record. 500.8(b) requires the CISO or a qualified designee to review, assess and update the procedures, guidelines and standards at least annually.
  • Secure development as a slogan. The procedures need to describe actual practices, such as code review, testing and change control, that developers follow.
  • Testing outside the real environment. External applications must be evaluated within the context of the covered entity's technology environment.

What Is Reasonable Evidence for 23 NYCRR 500.8?

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

  • E-GOV-01.30 Technology Development & Acquisition Policy. Documented evidence of a technology development and acquisition policy.
  • E-TDA-02 Secure Engineering & Data Privacy (SEDP). Documented evidence of a Secure Engineering & Data Privacy (SEDP) program. 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-GOV-04 Cybersecurity & Data Protection Procedures. Documented evidence of an appropriate appropriately-scoped cybersecurity & data protection procedures. Procedures are a documented set of steps necessary to perform a specific task or process in conformance with an applicable standard. Procedures help address the question of how the organization actually operationalizes a policy, standard or control. The result of a procedure is intended to satisfy a specific control. Procedures are also commonly referred to as “control activities.”
  • E-GOV-02 Cybersecurity & Data Protection Standards. Documented evidence of an appropriately-scoped cybersecurity & data protection standards. Standards are mandatory requirements regarding processes, actions and configurations. Standards are intended to be granular and prescriptive to ensure Technology Assets, Applications and/or Services (TAAS) are designed and operated to include appropriate cybersecurity & data protection protections
  • E-GOV-05 Cybersecurity & Data Protection Policies & Standards Reviews. Documented evidence of a periodic review process for the organization's cybersecurity & data protection policies and standards to identify necessary updates.
  • E-TDA-01 Secure Software Development Principles (SSDP). Documented evidence of a Secure Software Development Principles (SSDP). 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-TDA-03 Application Security Testing (AST). Documented evidence of application security testing (e.g., DAST, SAST, fuzzing, etc.).
  • E-TDA-05 Failure Mode and Effect Analysis (FMEA). Documented evidence of an engineering method designed to define, identify, and present solutions for system failures, problems, or errors.

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

  • Secure development standard. Written procedures, guidelines and standards for in-house development.
  • Third-party application assessment process. How externally developed applications are evaluated or tested before and during use.
  • Testing records. Code review, application security testing or assessment results.
  • Annual review record. Dated review and approval by the CISO or a qualified designee under 500.8(b).

Which ComplianceForge Documents Support 23 NYCRR 500.8?

The following ComplianceForge documents can help you document and implement 23 NYCRR 500.8 Application Security:

Frequently Asked Questions (FAQ)

Does 23 NYCRR 500.8 apply to software we buy rather than build? Yes. 500.8(a) requires procedures for evaluating, assessing or testing the security of externally developed applications used by the covered entity within the context of its technology environment.

How often must application security standards be reviewed under 500.8? At least annually, by the CISO or a qualified designee, under 500.8(b) as amended in 2023.

What changed in 500.8 with the Second Amendment? Only subdivision (b). The review of procedures, guidelines and standards changed from periodic to at least annually.

Are small entities with a limited exemption required to meet 500.8? No. 500.8 is one of the sections waived for entities that qualify for the 500.19(a) limited exemption.

Bottom Line on 23 NYCRR 500.8 Application Security

500.8 needs written secure development standards for your own code, a method to assess the software you buy, and an annual review by the CISO or a qualified designee. Keep the review record with the date.

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.7 Access Privileges and Management. Next section: 500.9 Risk Assessment. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.