NYDFS · United States

NYDFS 500 and US financial services logging, with the evidence on your own storage.

What the NYDFS cybersecurity regulation, the FTC Safeguards Rule and the SEC's disclosure rules ask of your logs: three-year audit trails, centralized logging and alerting, user activity monitoring, and the clocks that start when something goes wrong. nano runs in your own environment, and your logs never reach nano.

Buy nano
Talk to sales
What the rules say

Four rules, rule by rule.

The rules' own words, what they mean in practice, and where nano fits.

NYDFS, 23 NYCRR Part 500 (as amended November 2023)

Binding on DFS-licensed covered entities. Small covered entities under 500.19(a) are exempt from 500.6 and 500.14(b).

Ref What the text says In plain English How nano helps
500.6(a)(2) Systems that "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." dfs.ny.gov · 23 NYCRR 500 Keep audit trails good enough to catch, and respond to, the events that could seriously disrupt the business.
Collects the logs from the sources you choose from the catalog into one store in your environment, and runs detections on them as they arrive.
500.6(b) Records required by paragraph (a)(2) are kept "for not fewer than three years." dfs.ny.gov · 23 NYCRR 500 Keep those audit trails for at least three years.
Retention is a setting on your own event store (365 days by default). Set it to three years or more and tier older data to your own object storage, where it stays searchable.
500.14(b)(2) "Each class A company shall implement, unless the CISO has approved in writing the use of reasonably equivalent or more secure compensating controls: … a solution that centralizes logging and security event alerting." dfs.ny.gov · Second Amendment Class A companies need centralized logging and alerting, in force since 1 May 2025. A CISO can approve equivalent or stronger compensating controls in writing instead.
Centralizes logs from your sources and raises alerts from detection rules, inside your own environment. Related alerts group into cases with the evidence and timeline.
500.17(a)(1) Notify the superintendent "as promptly as possible but in no event later than 72 hours after determining that a cybersecurity incident has occurred at the covered entity, its affiliates, or a third-party service provider." dfs.ny.gov · Second Amendment 72 hours from the moment you determine there was an incident, including one at a third-party service provider.
Detections raise alerts as events arrive, and cases hold the evidence your notice draws on. Notifying DFS stays with you.

FTC Safeguards Rule, 16 CFR Part 314 (GLBA)

Binding on non-bank financial institutions under FTC jurisdiction, such as auto dealers, mortgage brokers, tax preparers and fintechs.

Ref What the text says In plain English How nano helps
314.4(c)(8) "Implement policies, procedures, and controls designed to monitor and log the activity of authorized users and detect unauthorized access or use of, or tampering with, customer information by such users." ecfr.gov · 16 CFR 314 Log what your own users do with customer information, and spot misuse or tampering.
Search across sources by user, host or IP to follow one person's activity in one timeline, and alert on access patterns your rules define.
314.4(j)(1) "if the notification event involves the information of at least 500 consumers, you must notify the Federal Trade Commission as soon as possible, and no later than 30 days after discovery of the event." ecfr.gov · 16 CFR 314 If 500 or more consumers are affected, tell the FTC within 30 days of discovery. In effect since 13 May 2024.
Logs and cases help you work out what was accessed and how many consumers it touched. Notifying the FTC stays with you.

SEC disclosure rules

Form 8-K Item 1.05 binds SEC registrants. Regulation S-P binds broker-dealers, investment companies, registered advisers and transfer agents.

Ref What the text says In plain English How nano helps
8-K Item 1.05 "A report pursuant to Item 1.05 is to be filed within four business days after the registrant determines that it has experienced a material cybersecurity incident." sec.gov · Form 8-K Four business days from the materiality decision, not from the incident itself.
The materiality decision needs facts fast: what happened, which systems, how long. Search and cases put the evidence in one place. Filing stays with you.
17 CFR 248.30(a)(4)(iii) Notice "as soon as practicable, but not later than 30 days, after becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred". ecfr.gov · 17 CFR 248.30 Tell affected customers within 30 days. Larger entities have complied since 3 December 2025, smaller ones since 3 June 2026.
Logs show whose information was reached and when, so you can scope the notice. Notifying customers stays with you.
Notification and disclosure clocks

72 hours, four business days, 30 days.

Each clock starts from a different moment: determining an incident occurred, determining it is material, discovering it, or becoming aware of unauthorized access. All of them need the facts from your logs quickly.

  1. 0 h

    An incident

    Each rule starts its clock at its own trigger, shown below.

  2. 72 h

    NYDFS notice

    After determining a cybersecurity incident occurred (500.17).

  3. 4 business days

    SEC Form 8-K

    After determining the incident is material (Item 1.05).

  4. 30 days

    FTC and customers

    FTC: after discovery, 500+ consumers (314.4(j)). Reg S-P: after becoming aware (248.30).

23 NYCRR 500.17(a)(1), Form 8-K General Instruction B.1, 16 CFR 314.4(j)(1), 17 CFR 248.30(a)(4)(iii).
  1. 13 May 2024 In effect

    FTC breach notice

    16 CFR 314.4(j), the 30-day FTC notice for 500 or more consumers, takes effect.

    ecfr.gov · 16 CFR 314 ↗
  2. 1 May 2025 In effect

    NYDFS Class A logging

    500.14(b), centralized logging and security event alerting for Class A companies, applies.

    dfs.ny.gov · Second Amendment ↗
  3. 3 Dec 2025 In effect

    Reg S-P, larger entities

    Larger covered institutions must comply with the amended Regulation S-P.

    sec.gov · Reg S-P guide ↗
  4. 3 Jun 2026 In effect

    Reg S-P, all entities

    Smaller covered institutions must comply too. The 30-day customer notice now applies to all.

    sec.gov · Reg S-P guide ↗
Where running it yourself matters

One fewer provider. Same clocks.

Unlike CMMC or HIPAA, these rules do not turn a SIEM vendor into an assessment or business associate question. Running the SIEM yourself helps a little with vendor oversight, and not at all with disclosure deadlines.

One fewer service provider

NYDFS 500.11 and FTC 314.4(f)

Both rules make you oversee the service providers that hold your data. A SIEM you run yourself is one fewer provider holding your security logs, and 500.17 counts incidents at a third-party service provider against your own 72 hours.

Evidence and retention

500.6, 500.14(b), 314.4(c)(8)

Three years of audit trails on storage you own, centralized logging and alerting, and a record of what authorized users did. This is where nano does most of its work.

No difference

8-K Item 1.05 and Regulation S-P

Where the logs live does not change a disclosure clock. What helps is how quickly you can find the facts: what happened, to which systems and whose data.

Inside your environment

Three years of audit trails, on storage you own.

nano installs with Docker Compose or with Helm on Kubernetes, on your servers or in your own cloud account. Sources send logs to it over your network, and it parses, stores, searches and runs detections on them there.

Your environment

Your data center, your own AWS, Azure or Google Cloud account, or an air-gapped network

01 · Sources
  • core banking
  • identity provider
  • firewall
  • VPN
  • endpoint
  • cloud audit
02 · nano
  • Collect and parse
  • Detections and alerts
  • Search and cases
03 · Your storage
  • Disks you own
  • Optional object storage tier
  • Retention you set
Optional · AI pivt AI calls your model endpoint directly: any OpenAI-compatible API (including self-hosted models) or the Anthropic Messages API. Off by default; model calls never go through nano.
nano, the vendor

Never receives your logs.

Connected
  • Daily license check-in: deployment ID, install ID, version
  • Hourly content and enrichment-feed updates (no data sent; can be turned off)
  • One number per day: total GB ingested
  • Downloads: log-source catalog, detection rules and SOAR content, enrichment feeds, releases
Air-gapped
  • No connection to nano at all
  • Offline license file, renewed by hand
fig 01 · nano runs inside your environment. Log data is never sent to nano.
Retention

Three years, or longer.

Event retention defaults to 365 days and is yours to set. Keep recent data on fast disk and tier older data to your own object storage, where it stays searchable. Storage and retention

Licensing

Priced per GB/day, not per year kept.

The license is priced on daily ingest, so keeping three years costs you storage, not license. Every license includes every feature.

No standing access

nano never holds your logs.

nano has no standing access to your install. Support sees only what you choose to share. A connected install sends a daily license check-in and one GB/day number; air-gapped installs send nothing. See air-gapped deployment, and the United States guide for the other US rules.

FAQ

Questions we get asked.

What is the NYDFS cybersecurity regulation?

23 NYCRR Part 500, the New York Department of Financial Services' Cybersecurity Requirements for Financial Services Companies. It applies to covered entities licensed or authorized by DFS, and was substantially amended by the Second Amendment of 1 November 2023, whose phased requirements are now all in force.

Does NYDFS 500 require a SIEM?

Not by name. Section 500.14(b) requires Class A companies to implement "a solution that centralizes logging and security event alerting", together with endpoint detection and response, unless the CISO approves reasonably equivalent or more secure compensating controls in writing. A SIEM is the usual way to meet that, but the rule only binds Class A companies.

What is a Class A company under NYDFS?

Under 500.1(d), a covered entity with at least $20,000,000 in gross annual revenue in each of the last two fiscal years from its business and its affiliates' New York business, and either over 2,000 employees averaged over the last two fiscal years or over $1,000,000,000 in gross annual revenue in each of the last two fiscal years, counting affiliates as the rule defines.

How long does NYDFS require logs to be kept?

Section 500.6(b) requires audit trails designed to detect and respond to cybersecurity events to be kept for not fewer than three years, and records that reconstruct material financial transactions for not fewer than five years. Small covered entities that qualify for the 500.19(a) limited exemption are exempt from 500.6.

What is the NYDFS 72-hour notification rule?

Section 500.17(a)(1) requires covered entities to notify the superintendent electronically as promptly as possible, and in no event later than 72 hours after determining that a cybersecurity incident has occurred at the covered entity, its affiliates or a third-party service provider.

What does the FTC Safeguards Rule require for logging?

16 CFR 314.4(c)(8) requires controls designed to monitor and log the activity of authorized users and to detect unauthorized access or use of, or tampering with, customer information by them. Since 13 May 2024, 314.4(j) also requires notifying the FTC within 30 days of discovering a notification event that involves the information of at least 500 consumers.

Is the GLBA Safeguards Rule the same as the FTC Safeguards Rule?

The FTC Safeguards Rule, 16 CFR Part 314, is the FTC's rule under the Gramm-Leach-Bliley Act, so the two names are often used for the same rule. It applies to non-bank financial institutions under FTC jurisdiction, such as auto dealers, mortgage brokers, tax preparers and fintechs.

When must a material cybersecurity incident be disclosed to the SEC?

Within four business days after the registrant determines the incident is material, under Form 8-K Item 1.05. The clock runs from the materiality determination, not from discovery of the incident.

What does Regulation S-P require after a breach?

17 CFR 248.30(a)(4)(iii) requires notice to affected individuals as soon as practicable, and no later than 30 days after becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred. Larger entities had to comply by 3 December 2025 and smaller entities by 3 June 2026.

Does running the SIEM myself help with NYDFS?

Modestly, on the vendor side. Section 500.11 requires a third-party service provider security policy, and 500.17 counts incidents at a third-party service provider. With nano running in your own environment, nano does not hold your security logs. The bigger value is evidence: centralized logging and alerting, and three years of audit trails on storage you own.

Is nano NYDFS compliant or certified?

There is no NYDFS certification for software. nano, LLC holds no certification or authorization for these rules. It is the SIEM you run to collect, keep and search the logs the rules ask for, and to alert on them.

Primary sources

Read the rules yourself.

Start with nano.

From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.

Buy nano
Talk to sales