23 NYCRR 500.6 Audit Trail at a Glance
- Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
- Section: 23 NYCRR 500.6 Audit Trail.
- Status: Not changed by the Second Amendment (text unchanged since 2017).
- 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. Class A companies also have centralized logging and alerting duties under 500.14(b)(2).
- Limited exemption (500.19(a)): Exempt. 500.19(a) limited-exemption entities do not need to meet 500.6.
- Compliance dates: The Second Amendment did not change 500.6. The requirement has applied since the original regulation, which gave covered entities 18 months from March 1, 2017 to comply (500.22(b)(2)).
Section 500.6 has two parts: systems that can reconstruct material financial transactions, and audit trails that support detecting and responding to serious cybersecurity events. Both are scoped by the risk assessment and apply to the extent applicable to the business.
The Second Amendment left 500.6 unchanged, but the surrounding requirements moved. Class A companies now need centralized logging and security event alerting under 500.14(b)(2), and the incident response plans in 500.16 depend on the audit trails 500.6 produces.
What Does 23 NYCRR 500.6 Require?
The following is the text of 23 NYCRR 500.6 Audit Trail as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability. Text not changed by the Second Amendment (all of 500.6) is shown as published in the New York Codes, Rules and Regulations, which keeps the capitalized defined terms of the original 2017 regulation.
- (a) Each Covered Entity shall securely maintain systems that, to the extent applicable and based on its Risk Assessment:
- (1) are designed to reconstruct material financial transactions sufficient to support normal operations and obligations of the Covered Entity; and
- (2) include audit trails designed to detect and respond to Cybersecurity Events that have a reasonable likelihood of materially harming any material part of the normal operations of the Covered Entity.
- (b) Each Covered Entity shall maintain records required by this section for not fewer than five years.
Source: NY DFS, Second Amendment to 23 NYCRR 500 (text) and 23 NYCRR 500.6 as published in the NYCRR (Cornell LII).
How Does 23 NYCRR 500.6 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.6 to 7 SCF controls through 9 relationships (9 "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.
- CFG-04 Secure Baseline Configurations. Intersects with (strength 5): 500.6(a). 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.
- MON-02 Continuous Monitoring. Intersects with (strength 5): 500.6(a)(1), 500.6(a)(2). SCF control: Mechanisms exist to facilitate the implementation of enterprise-wide monitoring controls.
- MON-09 Content of Event Logs. Intersects with (strength 5): 500.6(a)(1), 500.6(a)(2). 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-05 Centralized Collection of Event Logs & Security-Relevant Telemetry. Intersects with (strength 5): 500.6(a)(2). SCF control: Mechanisms exist to utilize a Security Incident Event Manager (SIEM), or similar automated tool, to support the centralized collection of event logs and security-relevant telemetry.
- DCH-27 Media & Data Retention. Intersects with (strength 5): 500.6(b). SCF control: Mechanisms exist to retain media and data in accordance with applicable statutory, regulatory and contractual obligations.
- IAC-03.2 Retain Access Records. Intersects with (strength 5): 500.6(b). SCF control: Mechanisms exist to retain a record of personnel accountability to ensure there is a record of all access granted to an individual (system and application-wise), who provided the authorization, when the authorization was granted and when the access was last reviewed.
- MON-13 Event Log & Security-Relevant Telemetry Retention. Intersects with (strength 5): 500.6(b). SCF control: Mechanisms exist to retain event logs and security-relevant telemetry for a time period consistent with records retention requirements to provide support for after-the-fact investigations of security incidents and to meet statutory, regulatory and contractual retention requirements.
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.6
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Short log retention. 500.6(b) requires records required by the section to be kept for not fewer than five years. Default log retention in many tools is far shorter.
- Logs that are not protected. The systems must be securely maintained. Audit trails that administrators can alter or delete undermine their value as evidence.
- No link to detection and response. 500.6(a)(2) asks for audit trails designed to detect and respond to cybersecurity events. Logs that nobody reviews or alerts on do not show that design.
- Ignoring transaction reconstruction. 500.6(a)(1) is about reconstructing material financial transactions, which is often owned by finance or operations rather than security.
What Is Reasonable Evidence for 23 NYCRR 500.6?
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.6 include:
- E-MON-01 Event Log Review & Analysis. Documented evidence of a capability to perform security event log review and analysis (e.g., system monitoring records, continuous monitoring strategy, etc.).
- E-MON-09 Event Logs. Documented evidence of event logs being generated by Technology Assets, Applications and/or Services (TAAS).
- E-MON-05 Centralized Event Log Collection. Documented evidence of security-relevant activities being logged and included as part of the centralized event log collection and review/analysis process.
- E-IAC-09 Access Authorization Records. Documented evidence of access authorization records.
- E-AST-11 Data Retention Program. Documented evidence of a formal data retention program that governs the retention and destruction of data types.
- E-AST-12 Secure Baseline Configurations Reviews. Documented evidence of a review process to ensure Secure Baseline Configurations (SBC) are current and applicable (e.g., system configuration settings and associated documentation).
Records specific to 23 NYCRR 500.6 that typically show the requirement is designed and operating:
- Logging standard. A standard that names the systems in scope, the events logged and the retention period.
- Retention configuration. Settings or archive records showing at least five years of retention for required records.
- Log protection controls. Access restrictions and integrity protections for audit records.
- Transaction reconstruction records. Documentation showing how material financial transactions can be reconstructed.
- Use in incident response. Examples of audit trails used in investigations or alert triage.
Which ComplianceForge Documents Support 23 NYCRR 500.6?
The following ComplianceForge documents can help you document and implement 23 NYCRR 500.6 Audit Trail:
- 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 long must audit trail records be kept under 23 NYCRR 500.6? For not fewer than five years, under 500.6(b).
Did the 2023 Second Amendment change 500.6? No. The Second Amendment did not amend 500.6. Related logging duties changed elsewhere, such as the Class A centralized logging and security event alerting requirement in 500.14(b)(2).
Does 500.6 require logging of every system? The requirement applies to the extent applicable and based on the risk assessment. The audit trails must be designed to detect and respond to cybersecurity events that have a reasonable likelihood of materially harming any material part of normal operations.
Are small entities with a limited exemption required to meet 500.6? No. 500.6 is one of the sections waived for entities that qualify for the 500.19(a) limited exemption.
Bottom Line on 23 NYCRR 500.6 Audit Trail
500.6 has not changed since 2017, but examiners still expect to see it working. Scope it through the risk assessment, protect the logs, keep required records for five years, and show that the audit trails actually feed detection and response.
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.5 Vulnerability Management. Next section: 500.7 Access Privileges and Management. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.