23 NYCRR 500.1 Definitions at a Glance
- Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
- Section: 23 NYCRR 500.1 Definitions.
- Status: Amended by the Second Amendment, effective November 1, 2023.
- Who it applies to: Every covered entity. The definitions set the scope of every other section of Part 500.
- Class A companies: 500.1(d) defines a Class A company. The Class A obligations themselves sit in 500.2(c), 500.7(c) and 500.14(b).
- Limited exemption (500.19(a)): Not applicable. Definitions apply to every entity, including those claiming an exemption under 500.19.
- Compliance dates: The amended definitions are part of the Second Amendment, effective November 1, 2023. The requirements that use them follow the transitional periods in 500.22.
Section 500.1 is the dictionary for the rest of Part 500. Whether you are a covered entity, whether you qualify as a Class A company, what counts as nonpublic information and when an event becomes a reportable cybersecurity incident all turn on the wording here.
The Second Amendment rewrote several definitions. Cybersecurity incident is now the trigger for the 72-hour notice in 500.17(a), privileged account drives the access limits in 500.7 and the MFA scope in 500.12, and senior governing body replaces the old board-or-equivalent wording throughout the regulation.
What Does 23 NYCRR 500.1 Require?
The following is the text of 23 NYCRR 500.1 Definitions as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability.
- For purposes of this Part only, the following definitions shall apply:
- (a) Affiliate means any person that controls, is controlled by or is under common control with another person. For purposes of this subdivision, control means the possession, direct or indirect, of the power to direct or cause the direction of the management and policies of a person, whether through the ownership of stock of such person or otherwise.
- (b) Authorized user means any employee, contractor, agent or other person that participates in the business operations of a covered entity and is authorized to access and use any information systems and data of the covered entity.
- (c) Chief Information Security Officer or CISO means a qualified individual responsible for overseeing and implementing a covered entity’s cybersecurity program and enforcing its cybersecurity policy.
- (d) Class A company means a covered entity with at least $20,000,000 in gross annual revenue in each of the last two fiscal years from all business operations of the covered entity and the business operations in this State of the covered entity’s affiliates and:
- (1) over 2,000 employees averaged over the last two fiscal years, including employees of both the covered entity and all of its affiliates no matter where located; or
- (2) over $1,000,000,000 in gross annual revenue in each of the last two fiscal years from all business operations of the covered entity and all of its affiliates no matter where located. For purposes of this subdivision, when calculating the number of employees and gross annual revenue, affiliates shall include only those that share information systems, cybersecurity resources or all or any part of a cybersecurity program with the covered entity.
- (e) Covered entity means any person operating under or required to operate under a license, registration, charter, certificate, permit, accreditation or similar authorization under the Banking Law, the Insurance Law or the Financial Services Law, regardless of whether the covered entity is also regulated by other government agencies.
- (f) Cybersecurity event means any act or attempt, successful or unsuccessful, to gain unauthorized access to, disrupt or misuse an information system or information stored on such information system.
- (g) Cybersecurity incident means a cybersecurity event that has occurred at the covered entity, its affiliates, or a third-party service provider that:
- (1) impacts the covered entity and requires the covered entity to notify any government body, self-regulatory agency or any other supervisory body;
- (2) has a reasonable likelihood of materially harming any material part of the normal operation(s) of the covered entity; or
- (3) results in the deployment of ransomware within a material part of the covered entity’s information systems.
- (h) Independent audit means an audit conducted by internal or external auditors free to make decisions not influenced by the covered entity being audited or by its owners, managers or employees.
- (i) Information system means a discrete set of electronic information resources organized for the collection, processing, maintenance, use, sharing, dissemination or disposition of electronic information, as well as any specialized system such as industrial/process controls systems, telephone switching and private branch exchange systems, and environmental control systems.
- (j) Multi-factor authentication means authentication through verification of at least two of the following types of authentication factors:
- (1) knowledge factors, such as a password;
- (2) possession factors, such as a token; or
- (3) inherence factors, such as a biometric characteristic.
- (k) Nonpublic information means all electronic information that is not publicly available information and is:
- (1) business related information of a covered entity the tampering with which, or unauthorized disclosure, access or use of which, would cause a material adverse impact to the business, operations or security of the covered entity;
- (2) any information concerning an individual which because of name, number, personal mark, or other identifier can be used to identify such individual, in combination with any one or more of the following data elements:
- (i) social security number;
- (ii) drivers’ license number or non-driver identification card number;
- (iii) account number, credit or debit card number;
- (iv) any security code, access code or password that would permit access to an individual’s financial account; or
- (v) biometric records;
- (3) any information or data, except age or gender, in any form or medium created by or derived from a health care provider or an individual and that relates to:
- (i) the past, present or future physical, mental or behavioral health or condition of any individual or a member of the individual’s family;
- (ii) the provision of health care to any individual; or
- (iii) payment for the provision of health care to any individual.
- (l) Penetration testing means testing the security of information systems by attempting to circumvent or defeat the security features of an information system by authorizing attempted penetration of databases or controls from outside or inside the covered entity’s information systems.
- (m) Person means any individual or entity, including but not limited to any partnership, corporation, branch, agency or association.
- (n) Privileged account means any authorized user account or service account that can be used to perform security-relevant functions that ordinary users are not authorized to perform, including but not limited to the ability to add, change or remove other accounts, or make configuration changes to information systems.
- (o) Publicly available information means any information that a covered entity has a reasonable basis to believe is lawfully made available to the general public from: Federal, State or local government records; widely distributed media; or disclosures to the general public that are required to be made by Federal, State or local law. A covered entity has a reasonable basis to believe that information is lawfully made available to the general public if the covered entity has taken steps to determine:
- (1) that the information is of the type that is available to the general public; and
- (2) whether an individual can direct that the information not be made available to the general public and, if so, that such individual has not done so.
- (p) Risk assessment means the process of identifying, estimating and prioritizing cybersecurity risks to organizational operations (including mission, functions, image and reputation), organizational assets, individuals, customers, consumers, other organizations and critical infrastructure resulting from the operation of an information system. Risk assessments incorporate threat and vulnerability analyses and consider mitigations provided by security controls planned or in place.
- (q) Senior governing body means the board of directors (or an appropriate committee thereof) or equivalent governing body or, if neither of those exist, the senior officer or officers of a covered entity responsible for the covered entity’s cybersecurity program. For any cybersecurity program or part of a cybersecurity program adopted from an affiliate under section 500.2(d) of this Part, the senior governing body may be that of the affiliate.
- (r) Senior officer(s) means the senior individual or individuals (acting collectively or as a committee) responsible for the management, operations, security, information systems, compliance and/or risk of a covered entity, including a branch or agency of a foreign banking organization subject to this Part.
- (s) Third-party service provider(s) means a person that:
- (1) is not an affiliate of the covered entity;
- (2) is not a governmental entity;
- (3) provides services to the covered entity; and
- (4) maintains, processes or otherwise is permitted access to nonpublic information through its provision of services to the covered entity.
Source: NY DFS, Second Amendment to 23 NYCRR 500 (text).
How Does 23 NYCRR 500.1 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.1 to 1 SCF control through 1 relationship (1 "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.
- GOV-03.2 Standardized Terminology. Intersects with (strength 5): 500.1. SCF control: Mechanisms exist to standardize technology and process terminology to reduce confusion amongst groups and departments.
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.1
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Counting Class A thresholds too narrowly. The Class A test in 500.1(d) counts revenue and employees of affiliates that share information systems, cybersecurity resources or any part of the cybersecurity program. Entities that look only at the licensed entity can miss the test.
- Treating every cybersecurity event as reportable. A cybersecurity event is any attempt, successful or not. Only events that meet the cybersecurity incident definition in 500.1(g) trigger the 72-hour notice in 500.17(a).
- Reading nonpublic information as customer data only. Nonpublic information in 500.1(k) also covers business information whose tampering or disclosure would cause a material adverse impact, and health information.
- Overlooking service accounts. The privileged account definition in 500.1(n) includes service accounts that can perform security-relevant functions, which matters for 500.7 and 500.12.
What Is Reasonable Evidence for 23 NYCRR 500.1?
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 following are examples of records that typically show 23 NYCRR 500.1 is designed and operating:
- Covered entity and license inventory. A list of the DFS licenses, charters or registrations held and the entities in scope.
- Class A determination worksheet. Revenue and employee figures for the last two fiscal years, including the affiliates counted under 500.1(d), with the conclusion and who approved it.
- Nonpublic information inventory. Where each category of nonpublic information in 500.1(k)(1) to (3) is stored and processed.
- Incident classification criteria. Written criteria that map the 500.1(g) definition to your incident response process.
- Third-party service provider list. Vendors that meet all four parts of the 500.1(s) definition.
Which ComplianceForge Documents Support 23 NYCRR 500.1?
The following ComplianceForge documents can help you document and implement 23 NYCRR 500.1 Definitions:
- 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)
What is a Class A company under 23 NYCRR 500.1? A covered entity with at least $20,000,000 in gross annual revenue in each of the last two fiscal years from its business operations and the New York business operations of its affiliates, and either more than 2,000 employees averaged over the last two fiscal years or more than $1,000,000,000 in gross annual revenue in each of the last two fiscal years, counting affiliates that share information systems, cybersecurity resources or program elements.
What is the difference between a cybersecurity event and a cybersecurity incident? A cybersecurity event is any act or attempt, successful or unsuccessful, to gain unauthorized access to, disrupt or misuse an information system or its information. A cybersecurity incident is an event at the covered entity, an affiliate or a third-party service provider that requires notice to a government or supervisory body, is reasonably likely to materially harm normal operations, or results in ransomware deployment within a material part of the information systems.
Does nonpublic information under 500.1 include health information? Yes. 500.1(k)(3) covers information, except age or gender, created by or derived from a health care provider or an individual that relates to physical, mental or behavioral health, the provision of health care, or payment for health care.
Who is a third-party service provider under 500.1? A person that is not an affiliate, is not a governmental entity, provides services to the covered entity, and maintains, processes or otherwise is permitted access to nonpublic information through those services. All four conditions in 500.1(s) must be met.
Bottom Line on 23 NYCRR 500.1 Definitions
500.1 decides how the rest of Part 500 applies to you. Settle your covered entity scope, your Class A status and your nonpublic information inventory first, then align your incident criteria with the cybersecurity incident definition, since that definition drives the 72-hour notice.
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
Next section: 500.2 Cybersecurity Program. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.