23 NYCRR 500.10 Cybersecurity Personnel and Intelligence at a Glance
- Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
- Section: 23 NYCRR 500.10 Cybersecurity Personnel and Intelligence.
- 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.10.
- Compliance dates: The section has applied since the original regulation. The Second Amendment mainly updated terminology and cross-references; any new requirements applied from April 29, 2024 (500.22(c)).
Section 500.10 is about the people who run the program. It works alongside the CISO requirement in 500.4(a) and requires enough qualified personnel to manage cybersecurity risk and to perform or oversee each of the core functions in 500.2(b).
Personnel can come from the covered entity, an affiliate or a third-party service provider. If you use an affiliate or provider to help comply with Part 500, the oversight rules in 500.4 and the third-party requirements in 500.11 apply.
What Does 23 NYCRR 500.10 Require?
The following is the text of 23 NYCRR 500.10 Cybersecurity Personnel and Intelligence as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability.
- (a) In addition to the requirements set forth in section 500.4(a) of this Part, each covered entity shall:
- (1) utilize qualified cybersecurity personnel of the covered entity, an affiliate or a third-party service provider sufficient to manage the covered entity’s cybersecurity risks and to perform or oversee the performance of the core cybersecurity functions specified in section 500.2(b)(1)-(6) of this Part;
- (2) provide cybersecurity personnel with cybersecurity updates and training sufficient to address relevant cybersecurity risks; and
- (3) verify that key cybersecurity personnel take steps to maintain current knowledge of changing cybersecurity threats and countermeasures.
- (b) A covered entity may choose to utilize an affiliate or qualified third-party service provider to assist in complying with the requirements set forth in this Part, subject to the requirements set forth in sections 500.4 and 500.11 of this Part.
Source: NY DFS, Second Amendment to 23 NYCRR 500 (text).
How Does 23 NYCRR 500.10 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.10 to 18 SCF controls through 21 relationships (2 "subset of", 19 "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.
- HRS-02 Human Resources Security Management. Subset of (strength 10): 500.10(a)(1). SCF control: Mechanisms exist to facilitate the implementation of personnel security controls.
- SAT-02 Security, Compliance & Resilience-Minded Workforce. Subset of (strength 10): 500.10(a)(2). SCF control: Mechanisms exist to facilitate the implementation of security workforce development and awareness controls.
- HRS-03.2 Competency Requirements for Security, Compliance & Resilience-Related Positions. Intersects with (strength 5): 500.10(a)(1). SCF control: Mechanisms exist to ensure that all security, compliance and resilience-related positions are staffed by qualified individuals who have the necessary skill set.
- HRS-04 Defined Roles & Responsibilities. Intersects with (strength 5): 500.10(a)(1). SCF control: Mechanisms exist to define cybersecurity roles & responsibilities for all personnel.
- HRS-05.1 Roles With Special Protection Measures. Intersects with (strength 5): 500.10(a)(1). SCF control: Mechanisms exist to ensure that individuals accessing a system that stores, transmits or processes information requiring special protection satisfy organization-defined personnel screening criteria.
- TPM-11 Responsible, Accountable, Supportive, Consulted & Informed (RASCI) Matrix. Intersects with (strength 5): 500.10(a)(1), 500.10(b). SCF control: Mechanisms exist to document and maintain a Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix, or similar documentation, to delineate assignment for security, compliance and resilience controls between internal stakeholders and External Service Providers (ESPs).
- TPM-14 Third-Party Contract Requirements. Intersects with (strength 5): 500.10(a)(1), 500.10(b). 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.10(a)(1). 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.
- HRS-04.1 Assigned Roles & Responsibilities Awareness. Intersects with (strength 5): 500.10(a)(2). SCF control: Mechanisms exist to communicate with users about their roles and responsibilities to maintain a safe and secure working environment.
- HRS-08.1 Formal Indoctrination. Intersects with (strength 5): 500.10(a)(2). SCF control: Mechanisms exist to formally educate authorized users on proper data handling practices for all the relevant types of data to which they have access.
- SAT-04 Security, Compliance & Resilience Awareness Training. Intersects with (strength 5): 500.10(a)(2). SCF control: Mechanisms exist to provide all employees and contractors appropriate security, compliance and resilience awareness education and training that is relevant for their job function.
- SAT-05 Role-Based Security, Compliance & Resilience Training. Intersects with (strength 5): 500.10(a)(2). SCF control: Mechanisms exist to provide role-based security, compliance and resilience-related training: (1) Before authorizing access to the system or performing assigned duties; (2) When required by system changes; and (3) Annually thereafter.
- SAT-05.1 Sensitive / Regulated Data Storage, Handling & Processing. Intersects with (strength 5): 500.10(a)(2). SCF control: Mechanisms exist to ensure that every user accessing a system processing, storing or transmitting sensitive and/or regulated data is formally trained in data handling requirements.
- SAT-05.2 Privileged User Training. Intersects with (strength 5): 500.10(a)(2). SCF control: Mechanisms exist to provide specific training for privileged users to ensure privileged users understand their unique roles and responsibilities
- SAT-06 Cyber Threat Environment Situational Awareness. Intersects with (strength 5): 500.10(a)(2). SCF control: Mechanisms exist to provide role-based security, compliance and resilience awareness training that is current and relevant to the cyber threats that users might encounter in day-to-day business operations.
- THR-02 Threat Intelligence Program. Intersects with (strength 5): 500.10(a)(2), 500.10(a)(3). SCF control: Mechanisms exist to implement a threat intelligence program that includes a cross-organization information-sharing capability that can influence the development of the system and security architectures, selection of security solutions, monitoring, threat hunting, response and recovery activities.
- SAT-07 Continuing Professional Education (CPE) - Security, Compliance & Resilience Personnel. Intersects with (strength 5): 500.10(a)(3). SCF control: Mechanisms exist to ensure security, compliance and resilience personnel receive Continuing Professional Education (CPE) training to maintain currency and proficiency with industry-recognized secure practices that are pertinent to their assigned roles and responsibilities.
- TPM-13 Third-Party Personnel Security. Intersects with (strength 5): 500.10(b). SCF control: Mechanisms exist to control personnel security requirements including security roles and responsibilities for third-party providers.
The STRM records "no relationship" for the lead-in text of 500.10(a); the numbered paragraphs under it are mapped individually.
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.10
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Staffing with no link to the core functions. Personnel must be sufficient to perform or oversee each core function in 500.2(b)(1) to (6). Gaps, such as nobody owning recovery, are visible in a function-by-function review.
- Training that is generic. 500.10(a)(2) requires updates and training sufficient to address relevant cybersecurity risks for cybersecurity personnel, separate from the all-staff awareness training in 500.14.
- No verification of current knowledge. 500.10(a)(3) requires the covered entity to verify that key cybersecurity personnel take steps to stay current.
- Outsourcing without 500.11 controls. Managed security providers are third-party service providers, so 500.11 applies to them.
What Is Reasonable Evidence for 23 NYCRR 500.10?
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.10 include:
- E-SAT-06 Training Materials. Documented evidence of security awareness training materials (e.g., curriculum, course work, presentations, etc.)
- E-HRS-01 Position Categorization. Documented evidence of a discrete roles for cybersecurity & data privacy functions (e.g., position categorization).
- E-SAT-05 Role-Based Training. Documented evidence of specialized user training for privileged users, executives, individuals who handle sensitive/regulated data, etc.
- E-TPM-01 Third-Party Contracts. Documented evidence of third-party contractual obligations for cybersecurity & data privacy protections.
- E-HRS-13 Defined Cybersecurity & Data Privacy Responsibilities. Documented evidence of a role-based cybersecurity & data privacy responsibilities to ensure personnel are both educated on the role and are responsible for the associated control execution.
- E-SAT-02 Initial User Training. Documented evidence of initial user training for security, compliance and/or resilience topics.
- E-SAT-04 Recurring User Training. Documented evidence of recurring (e.g., annual) user training for security, compliance and/or resilience topics.
- E-CPL-03 Shared Responsibility Matrix (SRM) / Controls Responsibility Matrix (CRM). Documented evidence of a Controls Responsibility Matrix (CRM), or similar documentation, that identifies the stakeholder involved in executing assigned controls (e.g., Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix).
Records specific to 23 NYCRR 500.10 that typically show the requirement is designed and operating:
- Roles and responsibilities. A matrix mapping personnel or providers to each core function in 500.2(b).
- Qualifications. Resumes, certifications or provider qualification records.
- Training records. Cybersecurity training and update records for cybersecurity personnel.
- Verification records. Evidence that key personnel maintain current knowledge, such as continuing education or threat intelligence participation.
- Provider oversight. Contracts and oversight records for affiliates or providers used under 500.10(b).
Which ComplianceForge Documents Support 23 NYCRR 500.10?
The following ComplianceForge documents can help you document and implement 23 NYCRR 500.10 Cybersecurity Personnel and Intelligence:
- 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)
Can a covered entity outsource its cybersecurity staff under 23 NYCRR 500.10? Yes. Qualified cybersecurity personnel may be employed by the covered entity, an affiliate or a third-party service provider, and 500.10(b) allows an affiliate or qualified provider to assist with Part 500, subject to the requirements of 500.4 and 500.11.
What training does 500.10 require? Cybersecurity updates and training for cybersecurity personnel sufficient to address relevant cybersecurity risks, plus verification that key cybersecurity personnel take steps to maintain current knowledge of changing threats and countermeasures.
How is 500.10 different from the training in 500.14? 500.10 covers cybersecurity personnel and their specialist knowledge. 500.14(a)(3) covers cybersecurity awareness training, including social engineering, for all personnel at least annually.
Are small entities with a limited exemption required to meet 500.10? No. 500.10 is one of the sections waived for entities that qualify for the 500.19(a) limited exemption.
Bottom Line on 23 NYCRR 500.10 Cybersecurity Personnel and Intelligence
500.10 asks whether you have enough qualified people, in-house or outsourced, to run every core function and keep their skills current. Map people to functions, keep training and verification records, and apply 500.11 to any outsourced provider.
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.9 Risk Assessment. Next section: 500.11 Third-Party Service Provider Security Policy. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.