NYDFS Part 500 access reviews and privileged access
NYDFS 23 NYCRR 500.7 requires covered entities to limit access to what each job needs, review all user access at least once a year, and promptly end access when people leave, with privileged access monitoring for Class A companies. Examiners look for annual review sign-offs, privileged account inventories and termination records behind the April 15 certification; Autharva supports that evidence by showing what every identity can reach and naming its owner.
Who it applies to: Any person operating, or required to operate, under a license, registration, charter or similar authorization under the New York Banking Law, Insurance Law or Financial Services Law, with added duties for Class A companies.
What the rule asks for
- § 500.7(a)(1)Least privilege for user access. Limit user access privileges to information systems that provide access to nonpublic information to only those necessary to perform the user's job.
- § 500.7(a)(2)-(3)Limit and restrict privileged accounts. Limit the number of privileged accounts and their access functions to what is necessary, and use privileged accounts only when performing functions that require them.
- § 500.7(a)(4)Annual access review. Review all user access privileges at least annually and remove or disable accounts and access that are no longer necessary.
- § 500.7(a)(6)Prompt termination on departure. Promptly terminate access following personnel departures.
- § 500.7(c)Class A privileged access monitoring. Class A companies must monitor privileged access activity, implement a privileged access management solution, and use an automated method of blocking commonly used passwords.
- § 500.12(a)Multi-factor authentication. Use MFA for any individual accessing any information system of the covered entity. Entities with a limited exemption must still use MFA for remote access to their systems and to third-party applications with nonpublic information, and for all privileged accounts other than service accounts that prohibit interactive login.
- § 500.17(b)Annual certification. By April 15 each year, the highest-ranking executive and the CISO sign a certification of material compliance, or an acknowledgment of noncompliance, for the prior calendar year. Supporting records must be kept for five years.
Dates that matter
- Second amendment to Part 500 takes effect, with requirements phased in through November 2025.
- Enhanced § 500.7 access privilege requirements take effect, including the annual access review, prompt termination on departure and Class A privileged access monitoring.
- § 500.12 MFA for all individuals accessing information systems and § 500.13(a) asset inventory requirements take effect.
Where access evidence usually falls short
- Annual reviews cover only applications connected to the IGA tool, so access in other systems is never reviewed.
- Service accounts that can perform privileged functions are missing from the privileged account inventory, even though the Part 500 definition of a privileged account includes service accounts.
- Departures are closed in the identity provider, but accounts inside individual applications stay active.
- Vendor logins and OAuth grants have no named owner, so no one can say whether the access is still necessary.
- Evidence for the April 15 certification is assembled at year end instead of being kept as the year runs.
How Autharva helps
- Shows what every employee, contractor, service account, OAuth grant and AI agent can actually reach, including through the apps it administers, the accounts it owns and the keys it holds.
- Assigns a named owner to every identity, so each privileged and service account has someone accountable for it.
- Closes access no one should still have, only with the owner's approval, and hands exceptions back to your IGA certification campaigns.
- Produces continuous access-control evidence for Part 500 that supports, but does not replace, your annual certification.
- Runs as a container in your data center or VPC, starts read-only, and keeps your data inside your network.
Autharva produces evidence that supports these controls. It does not by itself make an organization compliant; your auditor or examiner decides.
Evidence your examiner or auditor will ask for
- Annual user access review records with reviewer sign-off and removal of unnecessary access
- Inventory of privileged accounts, including service accounts, with the business need for each
- Termination records showing access removed after each personnel departure
- Class A privileged access monitoring records and PAM coverage
- MFA coverage records and any CISO-approved compensating controls
- Documentation supporting the § 500.17(b) certification, retained for five years
Questions.
Are service accounts in scope of § 500.7?+
Yes. Part 500 defines a privileged account as any authorized user account or service account that can perform security-relevant functions ordinary users cannot. Those accounts fall under the limits on number, use and review in § 500.7.
When did the amended access requirements take effect?+
The enhanced § 500.7 requirements took effect on May 1, 2025. Universal MFA under § 500.12 followed on November 1, 2025.
Does Autharva make us compliant with Part 500?+
No. Autharva produces access-control evidence and supports your cybersecurity program. Compliance, and the annual certification, rest on your whole program.
Does Autharva replace our IGA tool?+
No. Your IGA keeps running its review campaigns. Autharva covers systems it does not reach and hands exceptions back to those campaigns.
Sources
- NYDFS, 23 NYCRR Part 500 Cybersecurity Requirements for Financial Services Companies (as amended), 2023-11-01
- NYDFS, Cybersecurity Implementation Timeline for Covered Entities, 2023-11-01
Summaries are in our own words for orientation, not legal advice. Read the official text and check with your counsel.
Have a requirement we haven't covered?
Describe your environment, a system you're unsure about, or an audit finding. An Autharva SME reads every message and replies by email.
- Answered by a person, not a script.
- Please don't include passwords, customer data or account numbers.
What can your identities really reach?
Find out before an attacker or an examiner does.