23 NYCRR 500.7 Access Privileges and Management at a Glance
- Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
- Section: 23 NYCRR 500.7 Access Privileges and Management.
- Status: Amended by the Second Amendment, effective November 1, 2023.
- Who it applies to: Every covered entity unless exempt under 500.19(c) or (d). Entities with a 500.19(a) limited exemption must still meet 500.7.
- Class A companies: 500.7(c): Class A companies must monitor privileged access activity, implement a privileged access management solution, and automatically block commonly used passwords, with a CISO-approved written alternative where blocking is infeasible.
- Limited exemption (500.19(a)): Not exempt under 500.19(a). Entities exempt under 500.19(c) or (d) do not need to meet 500.7.
- Compliance dates: The new requirements in 500.7 applied from May 1, 2025, 18 months after the Second Amendment took effect (500.22(d)(3)).
Section 500.7 was expanded and retitled Access Privileges and Management in the Second Amendment. The old requirement to periodically review access became a minimum annual review of all user access privileges, and new requirements cover privileged account limits, remote control protocols and prompt termination.
Class A companies have extra obligations in 500.7(c): monitoring privileged access activity, a privileged access management solution, and an automated method of blocking commonly used passwords. Where blocking is infeasible, the CISO may approve compensating controls in writing, and that approval must be renewed at least annually.
What Does 23 NYCRR 500.7 Require?
The following is the text of 23 NYCRR 500.7 Access Privileges and Management 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, based on the covered entity’s risk assessment each covered entity shall:
- (1) limit user access privileges to information systems that provide access to nonpublic information to only those necessary to perform the user’s job;
- (2) limit the number of privileged accounts and limit the access functions of privileged accounts to only those necessary to perform the user’s job;
- (3) limit the use of privileged accounts to only when performing functions requiring the use of such access;
- (4) periodically, but at a minimum annually, review all user access privileges and remove or disable accounts and access that are no longer necessary;
- (5) disable or securely configure all protocols that permit remote control of devices; and
- (6) promptly terminate access following departures.
- (b) To the extent passwords are employed as a method of authentication, the covered entity shall implement a written password policy that meets industry standards.
- (c) Each class A company shall monitor privileged access activity and shall implement:
- (1) a privileged access management solution; and
- (2) an automated method of blocking commonly used passwords for all accounts on information systems owned or controlled by the class A company and wherever feasible for all other accounts. To the extent the class A company determines that blocking commonly used passwords is infeasible, the covered entity’s CISO may instead approve in writing at least annually the infeasibility and the use of reasonably equivalent or more secure compensating controls.
Source: NY DFS, Second Amendment to 23 NYCRR 500 (text).
How Does 23 NYCRR 500.7 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.7 to 19 SCF controls through 25 relationships (1 "equal", 1 "subset of", 23 "intersects with").
How to read the mapping: each relationship runs from the Part 500 text to the SCF control. "Equal" means the Part 500 requirement and the SCF control are semantically equivalent. "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.
- IAC-10 Privileged Account Management (PAM). Equal (strength 10): 500.7(c)(1). Intersects with (strength 5): 500.7(a)(1), 500.7(a)(3). SCF control: Mechanisms exist to restrict and control privileged access rights for users and Technology Assets, Applications and/or Services (TAAS).
- IAC-02 Identity & Access Management (IAM). Subset of (strength 10): 500.7(a)(1). Intersects with (strength 5): 500.7(b). SCF control: Mechanisms exist to facilitate the implementation of Identification and Access Management (IAM) controls.
- IAC-12 Periodic Review of Individual & Service Account Privileges. Intersects with (strength 8): 500.7(a)(4). Intersects with (strength 5): 500.7(a)(1). SCF control: Mechanisms exist to periodically-review the privileges assigned to individuals and service accounts to validate the need for such privileges and reassign or remove unnecessary privileges, as necessary.
- IAC-06 Role-Based Access Control (RBAC). Intersects with (strength 5): 500.7(a)(1). SCF control: Mechanisms exist to enforce Role-Based Access Control (RBAC) for Technology Assets, Applications, Services and/or Data (TAASD) to restrict access to individuals assigned specific roles with legitimate business needs.
- IAC-30 Least Privilege. Intersects with (strength 5): 500.7(a)(1), 500.7(a)(2). SCF control: Mechanisms exist to utilize the concept of least privilege, allowing only authorized access to processes necessary to accomplish assigned tasks in accordance with organizational business functions.
- IAC-08.4 Disable Inactive Accounts. Intersects with (strength 5): 500.7(a)(4). SCF control: Automated mechanisms exist to disable inactive accounts after an organization-defined time period.
- IAC-10.1 Privileged Account Inventories. Intersects with (strength 5): 500.7(a)(4). SCF control: Mechanisms exist to inventory all privileged accounts and validate that each person with elevated privileges is authorized by the appropriate level of organizational management.
- IAC-12.1 System Account Reviews. Intersects with (strength 5): 500.7(a)(4). SCF control: Mechanisms exist to review all system accounts and disable any account that cannot be associated with a business process and owner.
- CFG-04 Secure Baseline Configurations. Intersects with (strength 5): 500.7(a)(5). SCF control: Mechanisms exist to develop, document and maintain secure baseline configurations for Technology Assets, Applications and/or Services (TAAS) that are consistent with industry-accepted hardening standards.
- IAC-26 Use of Privileged Utility Programs. Intersects with (strength 5): 500.7(a)(5). SCF control: Mechanisms exist to restrict and tightly control utility programs that are capable of overriding system and application controls.
- HRS-11 Personnel Transfer. Intersects with (strength 5): 500.7(a)(6). SCF control: Mechanisms exist to adjust logical and physical access authorizations to Technology Assets, Applications and/or Services (TAAS) and facilities upon personnel reassignment or transfer, in a timely manner.
- HRS-12 Personnel Termination. Intersects with (strength 5): 500.7(a)(6). SCF control: Mechanisms exist to govern the termination of individual employment.
- GOV-04 Publishing Security, Compliance & Resilience Documentation. Intersects with (strength 5): 500.7(b). SCF control: Mechanisms exist to establish, maintain and disseminate policies, standards and procedures necessary for secure, compliant and resilient capabilities.
- IAC-14 Authenticator Management. Intersects with (strength 5): 500.7(b). SCF control: Mechanisms exist to: (1) Securely manage authenticators for users and devices; and (2) Ensure the strength of authentication is appropriate to the classification of the data being accessed.
- IAC-15 Password-Based Authentication. Intersects with (strength 5): 500.7(b), 500.7(c)(2). SCF control: Mechanisms exist to enforce complexity, length and lifespan considerations to ensure strong criteria for password-based authentication.
- MON-09 Content of Event Logs. Intersects with (strength 5): 500.7(c). Applies to Class A companies. SCF control: Mechanisms exist to configure Technology Assets, Applications and/or Services (TAAS) to produce event logs that contain sufficient information to, at a minimum: (1) Establish what type of event occurred; (2) When (date and time) the event occurred; (3) Where the event occurred; (4) The source of the event; (5) The outcome (success or failure) of the event; and (6) The identity of any user/subject associated with the event.
- MON-14 Privileged Functions Logging. Intersects with (strength 5): 500.7(c). Applies to Class A companies. SCF control: Mechanisms exist to log and review the actions of users and/or services with elevated privileges.
- MON-14.2 Privileged User Oversight. Intersects with (strength 5): 500.7(c). Applies to Class A companies. SCF control: Mechanisms exist to implement enhanced activity monitoring for privileged users.
- IAC-15.1 Automated Support For Password Strength. Intersects with (strength 5): 500.7(c)(2). Applies to Class A companies. SCF control: Automated mechanisms exist to determine if password authenticators are sufficiently strong enough to satisfy organization-defined password length and complexity requirements.
The STRM records "no relationship" for the lead-in text of 500.7(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.7
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Reviewing only privileged access. 500.7(a)(4) requires a review of all user access privileges at least annually, with removal of accounts and access no longer needed.
- Standing privileged access. 500.7(a)(3) limits use of privileged accounts to when functions require it. Admins who use privileged accounts for daily work fall short.
- Remote control protocols left open. 500.7(a)(5) requires all protocols that permit remote control of devices to be disabled or securely configured.
- Slow offboarding. 500.7(a)(6) requires prompt termination of access following departures. Track the time between departure and deprovisioning.
- Class A password blocking without a written exception. If blocking common passwords is infeasible for some accounts, the CISO approval must be in writing and renewed at least annually under 500.7(c)(2).
What Is Reasonable Evidence for 23 NYCRR 500.7?
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.7 include:
- E-GOV-01.16 Identification & Authentication Policy. Documented evidence of a identification and authentication policy.
- E-IAC-03 Privileged User Inventory. Documented evidence of an inventory of privileged users across Technology Assets, Applications and/or Services (TAAS) (internal and external).
- E-IAC-05 Identity & Access Management (IAM) Function. Documented evidence of an Identity & Access Management (IAM), or similar function, that facilitates the implementation of identification and access management controls.
- E-IAC-01 Access Permission Review. Documented evidence of periodic access permission reviews.
- E-HRS-12 Role Review. Documented evidence of a formal review process to ensure personnel roles currently reflect business needs.
- E-HRS-29 Personnel Actions Documentation. Documented evidence of notifications or records of recently transferred, separated, or terminated employees.
- E-IAC-02 Defined Roles & Authorizations (RBAC). Documented evidence of defined access control-specific roles (e.g., Role Based Access Control (RBAC)) that affect both logical and physical access authorizations.
- E-IAC-13 Authenticator Types. Documented evidence of system authenticator types.
Records specific to 23 NYCRR 500.7 that typically show the requirement is designed and operating:
- Access control and password policies. Written policies, including a password policy that meets industry standards where passwords are used.
- Annual access review records. Dated reviews covering all user access, with removals.
- Privileged account inventory. The list of privileged accounts with owners and justification.
- Termination records. HR departure dates matched to account disablement dates.
- Remote control protocol configuration. Evidence that RDP, VNC and similar protocols are disabled or securely configured.
- Class A records. PAM tool coverage, privileged activity monitoring, common-password blocking settings, and any annual CISO infeasibility approval.
Which ComplianceForge Documents Support 23 NYCRR 500.7?
The following ComplianceForge documents can help you document and implement 23 NYCRR 500.7 Access Privileges and Management:
- 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)
How often must access privileges be reviewed under 23 NYCRR 500.7? Periodically, but at a minimum annually. The review covers all user access privileges, and accounts and access that are no longer necessary must be removed or disabled.
What does 500.7(c) require from Class A companies? Class A companies must monitor privileged access activity and implement a privileged access management solution and an automated method of blocking commonly used passwords for all accounts on information systems they own or control, and wherever feasible for all other accounts. If blocking is infeasible, the CISO may approve in writing, at least annually, the infeasibility and reasonably equivalent or more secure compensating controls.
Does 500.7 require a password policy? Yes, to the extent passwords are used for authentication. 500.7(b) requires a written password policy that meets industry standards.
Does the limited exemption in 500.19(a) cover 500.7? No. 500.7 is not among the sections waived by the 500.19(a) limited exemption, so small covered entities must still meet it.
Bottom Line on 23 NYCRR 500.7 Access Privileges and Management
500.7 now spells out least privilege, annual reviews and prompt offboarding for every covered entity, and adds privileged access tooling for Class A companies. Inventory privileged accounts, review all access every year, lock down remote control protocols and document the password policy.
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.6 Audit Trail. Next section: 500.8 Application Security. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.