NYDFS 23 NYCRR 500.06: Audit Trail for Class A Entities

Asqav provides the unaffiliated audit-trail layer for the audit trail that 23 NYCRR § 500.06 requires of covered financial entities under the New York Department of Financial Services cybersecurity regulation, with heightened obligations for Class A entities phased in by November 1, 2025.

NYDFS Part 500 has been in force since 2017. The November 2023 amendment introduced the Class A entity tier and tightened the audit-trail rule. The amended audit-trail and independent-audit obligations land on covered entities in a phased schedule across 2024 and 2025.

What 500.06 requires: systems that reconstruct material financial transactions and audit trails that detect and respond to cybersecurity events.

Where Asqav fits: a signed receipt for each AI-agent action is the audit-trail artefact for both obligations.

Why unaffiliated matters: an NYDFS examiner and a 500.2(c) independent auditor read self-attestation as the entity's own narrative, not as independent evidence.

What the rule says

23 NYCRR § 500.06 (audit trail) reads, in relevant part:

Each covered entity shall securely maintain systems that, to the extent applicable and based on its risk assessment: (a)(1) are designed to reconstruct material financial transactions sufficient to support normal operations and obligations of the covered entity, and (a)(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. 23 NYCRR § 500.06(a)

Subsection (b) requires retention of records produced under (a)(1) for not fewer than five years, and records produced under (a)(2) for not fewer than three years.

The cybersecurity-event detection clause covers actions taken by AI agents on systems within the covered entity's perimeter. A signed receipt for each agent action is the audit-trail artefact that supports both the reconstruction obligation and the detection-and-response obligation.

Class A entity criteria

The November 2023 amendment introduced the Class A entity tier, defined in 23 NYCRR § 500.1(d). A covered entity is Class A if it has, in each of the last two fiscal years:

Class A entities take on heightened obligations across several sections of Part 500, including the audit-trail rule. The full set of Class A obligations phased in on a schedule that completed by November 1, 2025.

How Asqav provides the unaffiliated audit trail

The 500.06 audit-trail rule does not write the unaffiliated-party requirement into the rule text the way SEC 17a-4(f)(3)(v) does. The unaffiliated-party property still matters in practice because inbound NYDFS examination and the 500.2(c) independent-audit requirement both read self-attestation as the covered entity's own narrative rather than as independent evidence.

Asqav fulfils the unaffiliated-party slot for the AI-agent action surface:

The unaffiliated property converts the receipt stream from in-house log to independent evidence. The 500.06(a)(1) reconstruction obligation and the 500.06(a)(2) cybersecurity-event detection obligation both rest on that evidence.

Independent audit (500.2(c)) and Class A obligations

23 NYCRR § 500.2 requires the covered entity to maintain a cybersecurity program, and § 500.4 (cybersecurity governance) requires it to designate a Chief Information Security Officer (CISO) responsible for overseeing and implementing that program. Under § 500.2(c), Class A entities take on the additional obligation to design and conduct independent audits of the cybersecurity program at a frequency the entity's risk assessment establishes.

The independent audit reads the audit-trail evidence produced under 500.06. Asqav's signed-receipt stream is the artefact the auditor reads for the AI-agent slice of the covered entity's perimeter. The published verify key and the IETF-listed wire format let the auditor work offline.

For the CISO's annual written report to senior governing body required under 500.04, the receipt stream produces the numerical evidence the report rests on:

Five-year retention and three-year retention

23 NYCRR § 500.06(b) sets the retention period: five years for records of material financial transactions under (a)(1), three years for cybersecurity-event audit trails under (a)(2). Asqav's signed receipts are retained for the full applicable period and remain independently verifiable across the retention window.

The post-quantum signature algorithm choice (ML-DSA-65, NIST FIPS 204) is driven by the retention window: a receipt signed today must verify as far ahead as the retention rule reaches. Ed25519 is unsafe against a future cryptographically relevant quantum computer. ML-DSA-65 is the NIST-standardised replacement. See Post-quantum signed receipts for the threat model.

How to wire Asqav into a 500.06 compliance posture

  1. Identify the AI agent action surfaces that touch material financial transactions (500.06(a)(1)) or that have reasonable likelihood of materially harming normal operations (500.06(a)(2)). These are the surfaces the audit-trail rule covers.
  2. Wire the Asqav SDK at each surface so every action produces a signed receipt before the action takes effect. The SDK defaults to compliance_mode=True. Receipts that lack the required fields are rejected at the signer.
  3. Add Asqav to the covered entity's third-party service provider security policy (500.11) and complete the diligence required there.
  4. Set the receipt-retention configuration to the longer of the two applicable periods (five years for 500.06(a)(1) records).
  5. Wire the receipt stream into the CISO's annual 500.04 reporting pipeline. The numerical evidence and the verification status are the CISO-report inputs.
  6. On inbound NYDFS examination or 500.2(c) independent audit, produce the receipt set with asqav audit-pack export and direct the examiner or auditor to the public verify key for offline verification.

Customer questions about the third-party service provider diligence: info@asqav.com.

Adjacent surfaces in the 23 NYCRR 500 cluster