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.15 Encryption of Nonpublic Information?

Short Answer

23 NYCRR 500.15 requires a written policy requiring encryption that meets industry standards for nonpublic information held or transmitted, both in transit over external networks and at rest. If encryption at rest is infeasible, the CISO may approve effective compensating controls in writing and must review feasibility and effectiveness at least annually. The compensating control option for data in transit was removed.

23 NYCRR 500.15 Encryption of Nonpublic Information at a Glance

  • Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
  • Section: 23 NYCRR 500.15 Encryption of Nonpublic Information.
  • 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.15.
  • Compliance dates: The amended encryption requirement applied from November 1, 2024, one year after the Second Amendment took effect (500.22(d)(2)).

Section 500.15 changed from risk-based encryption controls to a written policy requiring encryption that meets industry standards, both in transit over external networks and at rest.

The Second Amendment removed the option to use compensating controls for nonpublic information in transit over external networks. Compensating controls remain available only for encryption at rest, with written CISO approval and an annual review of feasibility and effectiveness.

What Does 23 NYCRR 500.15 Require?

The following is the text of 23 NYCRR 500.15 Encryption of Nonpublic Information as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability.

  • (a) As part of its cybersecurity program, each covered entity shall implement a written policy requiring encryption that meets industry standards, to protect nonpublic information held or transmitted by the covered entity both in transit over external networks and at rest.
  • (b) To the extent a covered entity determines that encryption of nonpublic information at rest is infeasible, the covered entity may instead secure such nonpublic information using effective alternative compensating controls that have been reviewed and approved by the covered entity’s CISO in writing. The feasibility of encryption and effectiveness of the compensating controls shall be reviewed by the CISO at least annually.

Source: NY DFS, Second Amendment to 23 NYCRR 500 (text).

How Does 23 NYCRR 500.15 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.15 to 7 SCF controls through 8 relationships (8 "intersects with").

How to read the mapping: each relationship runs from the Part 500 text to 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.

  • CRY-02 Use of Cryptographic Controls. Intersects with (strength 5): 500.15(a), 500.15(b). SCF control: Mechanisms exist to facilitate the implementation of cryptographic protections controls using known public standards and trusted cryptographic technologies.
  • CRY-05 Encrypting Data In Transit. Intersects with (strength 5): 500.15(a). SCF control: Cryptographic mechanisms exist to prevent the unauthorized disclosure of data in transit.
  • CRY-07 Encrypting Data At Rest. Intersects with (strength 5): 500.15(a). SCF control: Cryptographic mechanisms exist to prevent the unauthorized disclosure of data at rest.
  • GOV-04 Publishing Security, Compliance & Resilience Documentation. Intersects with (strength 5): 500.15(a). SCF control: Mechanisms exist to establish, maintain and disseminate policies, standards and procedures necessary for secure, compliant and resilient capabilities.
  • CRY-03.1 Alternate Physical Protection. Intersects with (strength 5): 500.15(b). SCF control: Cryptographic mechanisms exist to prevent unauthorized disclosure of information as an alternative to physical safeguards.
  • GOV-04.2 Exception Management. Intersects with (strength 5): 500.15(b). SCF control: Mechanisms exist to prohibit exceptions to standards, except when the exception has been formally assessed for risk impact, approved and recorded.
  • RSK-18 Compensating Countermeasures. Intersects with (strength 5): 500.15(b). 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.15

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

  • Relying on old in-transit exceptions. Compensating controls for data in transit over external networks are no longer permitted under the amended section.
  • No written encryption policy. 500.15(a) requires a written policy requiring encryption that meets industry standards.
  • At-rest exceptions without written approval. Compensating controls for data at rest need CISO review and approval in writing.
  • Missing the annual review. The CISO must review the feasibility of encryption and effectiveness of compensating controls at least annually.

What Is Reasonable Evidence for 23 NYCRR 500.15?

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

  • E-GOV-01.11 Cryptographic Protections Policy. Documented evidence of a cryptographic protections policy.
  • E-CRY-01 Cryptographic Protections. Documented evidence of organization-approved cryptographic solutions and modules for both data at rest and in transit.
  • 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-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-06 Exception Management. Documented evidence of authorized exceptions to standards (e.g., configurations, practices, etc.)
  • E-GOV-20 Compensating Controls. Documented evidence of compensating controls (e.g., countermeasure to reduce risk associated with control deficiencies).

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

  • Encryption policy. A written policy requiring industry-standard encryption in transit over external networks and at rest.
  • Encryption configuration. TLS settings, storage and database encryption settings for systems holding nonpublic information.
  • At-rest exception register. Each infeasibility finding, the compensating controls, the CISO's written approval and the latest annual review.
  • Key management records. How encryption keys are generated, stored and rotated.

Which ComplianceForge Documents Support 23 NYCRR 500.15?

The following ComplianceForge documents can help you document and implement 23 NYCRR 500.15 Encryption of Nonpublic Information:

  • SCF Policies & Standards (SCRP): editable SCF-based cybersecurity policies, standards and control objectives covering all 34 SCF domains.
  • SCF Procedures (CSOP): editable SCF-aligned cybersecurity procedures covering all 34 SCF domains, mapped 1-to-1 to the SCRP standards.

Frequently Asked Questions (FAQ)

Does 23 NYCRR 500.15 require encryption at rest? Yes. The written policy must require encryption that meets industry standards for nonpublic information both in transit over external networks and at rest. Where encryption at rest is infeasible, the CISO may approve effective compensating controls in writing.

Can compensating controls replace encryption in transit under 500.15? No. The Second Amendment deleted the in-transit compensating control provision. The remaining compensating control option in 500.15(b) applies only to encryption at rest.

How often must encryption exceptions be reviewed? The CISO must review the feasibility of encryption and the effectiveness of the compensating controls at least annually.

Do small entities with a limited exemption need to meet 500.15? No. 500.15 is one of the sections waived for entities that qualify for the 500.19(a) limited exemption.

Bottom Line on 23 NYCRR 500.15 Encryption of Nonpublic Information

500.15 now requires a written encryption policy and leaves no room for in-transit exceptions. Encrypt nonpublic information in transit over external networks and at rest, keep any at-rest exceptions in writing with CISO approval, and review them every year.

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.14 Monitoring and Training. Next section: 500.16 Incident Response and Business Continuity Management. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.