23 NYCRR 500.11 Third-Party Service Provider Security Policy at a Glance
- Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
- Section: 23 NYCRR 500.11 Third-Party Service Provider Security Policy.
- Status: Amended by the Second Amendment, effective November 1, 2023.
- Who it applies to: Every covered entity unless exempt from Part 500 entirely. 500.11 is not waived by the 500.19(a), (c) or (d) exemptions.
- Class A companies: None beyond the general requirement.
- Limited exemption (500.19(a)): Not exempt under 500.19(a), (c) or (d).
- Compliance dates: Third-party policies have been required since the original regulation (two years from March 1, 2017 under 500.22(b)(3)). Second Amendment changes applied from April 29, 2024 (500.22(c)).
Section 500.11 covers vendors that can access or hold your nonpublic information. Third-party service provider has a specific meaning in 500.1(s): not an affiliate, not a governmental entity, provides services to you, and maintains, processes or is permitted access to nonpublic information through those services.
The Second Amendment kept the structure of 500.11 but removed the old limited exception in 500.11(c) for agents and representatives who were themselves covered entities. It also points the MFA and encryption guidelines in 500.11(b) at the amended 500.12 and 500.15.
What Does 23 NYCRR 500.11 Require?
The following is the text of 23 NYCRR 500.11 Third-Party Service Provider Security Policy as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability.
- (a) Each covered entity shall implement written policies and procedures designed to ensure the security of information systems and nonpublic information that are accessible to, or held by, third-party service providers. Such policies and procedures shall be based on the risk assessment of the covered entity and shall address to the extent applicable:
- (1) the identification and risk assessment of third-party service providers;
- (2) minimum cybersecurity practices required to be met by such third-party service providers in order for them to do business with the covered entity;
- (3) due diligence processes used to evaluate the adequacy of cybersecurity practices of such third-party service providers; and
- (4) periodic assessment of such third-party service providers based on the risk they present and the continued adequacy of their cybersecurity practices.
- (b) Such policies and procedures shall include relevant guidelines for due diligence and/or contractual protections relating to third-party service providers including to the extent applicable guidelines addressing:
- (1) the third-party service provider’s policies and procedures for access controls, including its use of multi-factor authentication as required by section 500.12 of this Part, to limit access to relevant information systems and nonpublic information;
- (2) the third-party service provider’s policies and procedures for use of encryption as required by section 500.15 of this Part to protect nonpublic information in transit and at rest;
- (3) notice to be provided to the covered entity in the event of a cybersecurity event directly impacting the covered entity’s information systems or the covered entity’s nonpublic information being held by the third-party service provider; and
- (4) representations and warranties addressing the third-party service provider’s cybersecurity policies and procedures that relate to the security of the covered entity’s information systems or nonpublic information.
Source: NY DFS, Second Amendment to 23 NYCRR 500 (text).
How Does 23 NYCRR 500.11 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.11 to 15 SCF controls through 34 relationships (4 "subset of", 30 "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.
- GOV-04 Publishing Security, Compliance & Resilience Documentation. Subset of (strength 10): 500.11(a). SCF control: Mechanisms exist to establish, maintain and disseminate policies, standards and procedures necessary for secure, compliant and resilient capabilities.
- TPM-02 Third-Party Management. Subset of (strength 10): 500.11(a)(1), 500.11(b). Intersects with (strength 5): 500.11(a). SCF control: Mechanisms exist to facilitate the implementation of third-party management controls.
- IAC-37 Multi-Factor Authentication (MFA). Subset of (strength 10): 500.11(b)(1). SCF control: Automated mechanisms exist to enforce Multi-Factor Authentication (MFA) for: (1) Remote network access; (2) Third-party Technology Assets, Applications and/or Services (TAAS); and/ or (3) Non-console access to critical TAAS that store, transmit and/or process sensitive and/or regulated data.
- TPM-08 Third-Party Inventories. Intersects with (strength 5): 500.11(a)(1). SCF control: Mechanisms exist to maintain a current, accurate and complete list of External Service Providers (ESPs) that can potentially impact the Confidentiality, Integrity, Availability and/or Safety (CIAS) of the organization's Technology Assets, Applications, Services and/or Data (TAASD).
- TPM-09 Third-Party Criticality Assessments. Intersects with (strength 5): 500.11(a)(1), 500.11(a)(4). SCF control: Mechanisms exist to identify, prioritize and assess suppliers and partners of critical Technology Assets, Applications and/or Services (TAAS) using a supply chain risk assessment process relative to their importance in supporting the delivery of high-value services.
- TPM-10 Third-Party Risk Assessments & Approvals. Intersects with (strength 5): 500.11(a)(1), 500.11(a)(3). SCF control: Mechanisms exist to conduct a risk assessment prior to the acquisition or outsourcing of technology-related Technology Assets, Applications and/or Services (TAAS).
- TPM-12 Third-Party Services. Intersects with (strength 5): 500.11(a)(1). SCF control: Mechanisms exist to mitigate the risks associated with third-party access to the organization's Technology Assets, Applications, Services and/or Data (TAASD).
- TPM-14 Third-Party Contract Requirements. Intersects with (strength 5): 500.11(a)(1), 500.11(a)(2), 500.11(b), 500.11(b)(1), 500.11(b)(2), 500.11(b)(3), 500.11(b)(4). SCF control: Mechanisms exist to require contractual requirements for applicable security, compliance and resilience requirements with third-parties, reflecting the organization's needs to protect its Technology Assets, Applications, Services and/or Data (TAASD).
- TPM-14.1 Contract Flow-Down Requirements. Intersects with (strength 5): 500.11(a)(1), 500.11(a)(2), 500.11(b), 500.11(b)(1), 500.11(b)(2), 500.11(b)(3), 500.11(b)(4). SCF control: Mechanisms exist to ensure applicable security, compliance and resilience requirements are included in contracts that flow-down to applicable sub-contractors and suppliers.
- TPM-15 Review of Third-Party Services. Intersects with (strength 5): 500.11(a)(3), 500.11(a)(4). SCF control: Mechanisms exist to monitor, regularly review and assess External Service Providers (ESPs) for compliance with established contractual requirements for security, compliance and resilience controls.
- TPM-16 Third-Party Scope Review. Intersects with (strength 5): 500.11(a)(3), 500.11(a)(4). SCF control: Mechanisms exist to perform recurring validation of the Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix, or similar documentation, to ensure security, compliance and resilience control assignments accurately reflect current: (1) Contractual obligations for the External Service Provider (ESP); (2) Business practices; (3) Applicable stakeholders; and (4) Deployed Technology Assets, Applications and/or Services (TAAS).
- TPM-22 First-Party Declaration (1PD). Intersects with (strength 5): 500.11(a)(3), 500.11(b)(4). SCF control: Mechanisms exist to obtain a First-Party Declaration(1PD) from applicable External Service Providers (ESPs) that provides assurance of compliance with specified statutory, regulatory and contractual obligations for security, compliance and resilience controls, including any flow-down requirements to subcontractors.
- TPM-12.3 Third-Party Authentication Practices. Intersects with (strength 5): 500.11(b)(1). SCF control: Mechanisms exist to ensure External Service Providers (ESPs) use unique authentication factors for each of its customers.
- CRY-02 Use of Cryptographic Controls. Intersects with (strength 5): 500.11(b)(2). SCF control: Mechanisms exist to facilitate the implementation of cryptographic protections controls using known public standards and trusted cryptographic technologies.
- TPM-21.1 Security Compromise Notification Agreements. Intersects with (strength 5): 500.11(b)(3). SCF control: Mechanisms exist to compel External Service Providers (ESPs) to provide notification of actual or potential compromises in the supply chain that can potentially affect or have adversely affected Technology Assets, Applications and/or Services (TAAS) that the organization utilizes.
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.11
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Vendor list does not match the definition. A provider list built from accounts payable often misses providers with access to nonpublic information and includes vendors that do not meet 500.1(s).
- One-time due diligence. 500.11(a)(4) requires periodic assessment based on the risk the provider presents and the continued adequacy of its practices.
- Contracts without event notice. 500.11(b)(3) calls for guidelines on notice to the covered entity of cybersecurity events directly affecting its systems or the nonpublic information the provider holds. This feeds the 72-hour clock in 500.17(a), which now includes incidents at third-party service providers.
- Not addressing MFA and encryption. 500.11(b)(1) and (2) call for guidelines on the provider's access controls, including MFA as required by 500.12, and encryption as required by 500.15.
What Is Reasonable Evidence for 23 NYCRR 500.11?
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.11 include:
- E-GOV-01.31 Third-Party Management Policy. Documented evidence of a third-party management policy.
- 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-IAC-16 Multi-Factor Authentication (MFA) Configuration. Documented evidence of Multi-Factor Authentication (MFA) enforcement, including replay-resistant and phishing-resistant authenticators for privileged and non-privileged network access.
- E-RSK-02 Supply Chain Risk Management (SCRM) Plan. Documented evidence of a Supply Chain Risk Management (SCRM) Plan. This is program-level documentation in the form of a playbook, concept of operations or a similar format provides guidance on organizational practices that support existing policies and standards.
- E-TPM-01 Third-Party Contracts. Documented evidence of third-party contractual obligations for cybersecurity & data privacy protections.
- E-TPM-03 Third-Party Service Reviews. Documented evidence of a formal, annual stakeholder review of third-party services for each External Service Provider (ESP).
- E-TPM-02 Third-Party Criticality Assessment. Documented evidence of third-party criticality assessment that evaluates the critical nature of each third-party the organization works with.
Records specific to 23 NYCRR 500.11 that typically show the requirement is designed and operating:
- Third-party service provider policy and procedures. Written documents covering each item in 500.11(a) and (b).
- Provider inventory with risk ratings. Providers meeting 500.1(s), with the risk assessment for each.
- Minimum security requirements. The cybersecurity practices providers must meet to do business with you.
- Due diligence and periodic assessment records. Questionnaires, reports, certifications and review dates.
- Contract clauses. Provisions for MFA, encryption, event notification and representations and warranties.
Which ComplianceForge Documents Support 23 NYCRR 500.11?
The following ComplianceForge documents can help you document and implement 23 NYCRR 500.11 Third-Party Service Provider Security Policy:
Frequently Asked Questions (FAQ)
What must a 23 NYCRR 500.11 third-party service provider policy address? To the extent applicable: identification and risk assessment of third-party service providers; minimum cybersecurity practices they must meet; due diligence processes used to evaluate their practices; and periodic assessment based on the risk they present and the continued adequacy of their practices.
What contract or due diligence guidelines does 500.11(b) require? Guidelines addressing the provider's access controls, including multi-factor authentication as required by 500.12; its use of encryption as required by 500.15; notice to the covered entity of cybersecurity events directly impacting the covered entity's systems or nonpublic information held by the provider; and representations and warranties about the provider's cybersecurity policies and procedures.
Does the limited exemption in 500.19(a) cover 500.11? No. 500.11 is not waived by the 500.19(a), (c) or (d) exemptions.
Was the 500.11(c) limited exception removed? Yes. The Second Amendment deleted the 500.11(c) exception that let an agent, employee, representative or designee who was itself a covered entity follow the covered entity's third-party policy instead of developing its own. 500.19(b) still addresses entities covered by another covered entity's cybersecurity program.
Bottom Line on 23 NYCRR 500.11 Third-Party Service Provider Security Policy
500.11 applies to almost every covered entity, including small ones. Build the provider inventory from the 500.1(s) definition, assess providers by risk and keep reassessing them, and put MFA, encryption, event notice and warranties into due diligence and contracts.
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.10 Cybersecurity Personnel and Intelligence. Next section: 500.12 Multi-Factor Authentication. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.