Skip to main content
Regulator guide · New York

NYDFS 500: what an external record puts in the file

The NYDFS cybersecurity regulation, 23 NYCRR Part 500, asks covered entities for an asset inventory, vulnerability management, oversight of third-party service providers and prompt notice of incidents. This page quotes four of its sections and sets beside each what outside-in monitoring contributes, and what stays with you.

Scope of this page

Four sections, quoted, and nothing read into them

This is a description of monitoring evidence. It does not say who is a covered entity, which exemptions apply to you or what satisfies the Department. Those are questions for your compliance function and its advisers.

The quotations come from the consolidated text of Part 500 published by the New York State Department of Financial Services, read on 18 November 2026. The Department marks that document as not an official version.

Section by section

What the regulation says, and what the record adds

§ 500.13(a)

Asset management

As part of its cybersecurity program, each covered entity shall implement written policies and procedures designed to produce and maintain a complete, accurate and documented asset inventory of the covered entity’s information systems.

What an outside-in record adds

An inventory of the internet-facing part of the estate, built from a single apex domain and rebuilt every 24 hours without a seed list. It can be set against the register you keep, and the differences are dated.

What stays with you

The inventory itself, its policies, and the fields the section lists for each asset, such as owner, location, classification and recovery time objectives. Systems that are not reachable from the internet are outside what discovery can see.

Attack Surface Management

§ 500.5

Vulnerability management

automated scans of information systems, and a manual review of systems not covered by such scans, for the purpose of discovering, analyzing and reporting vulnerabilities at a frequency determined by the risk assessment, and promptly after any material system changes

What an outside-in record adds

Continuous assessment of the external estate, with each finding dated, assigned and carried to a disposition. Where it is safe and authorised, Continuous Automated Red-Teaming tests whether an exposure can be used and attaches the evidence.

What stays with you

Internal scanning, and the annual penetration test the same section calls for. That test is to be carried out by a qualified internal or external party, and automated validation is not a substitute for it.

Continuous Automated Red-Teaming

§ 500.11(a)

Third-party service provider security policy

periodic assessment of such third-party service providers based on the risk they present and the continued adequacy of their cybersecurity practices

What an outside-in record adds

An outside-in read of the providers you nominate, produced with the methodology applied to your own estate and dated on every run. It needs nothing from the provider.

What stays with you

The written policy, the due diligence and the contractual protections the section describes. A provider’s systems are observed from outside and are not tested, and what is not reachable from the internet is not seen.

Third-Party Risk Management

§ 500.17(a)(1)

Notices to superintendent

Each covered entity shall notify the superintendent electronically in the form set forth on the department’s website 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.

What an outside-in record adds

A dated record of what was externally observable before and during an event: which hosts were exposed, which credentials attributed to your domains were in circulation, and when each was first seen. It is retrieved from the record and does not have to be reconstructed.

What stays with you

The determination that an incident has occurred, and the notice. ShadowMap does not file, submit or report anything on your behalf.

Dark Web Monitoring

The record

What the monitoring record holds

One dated, outside-in record across your estate and your providers As of November 2026
  • Each discovery run carries its date and the inventory it covered, so a change is tied to the day it became observable.
  • Each finding carries an owner, a disposition and a change history.
  • Validation runs only where it is safe and authorised, and every finding states whether it was tested.
  • Third-party service providers are read with the methodology applied to your own estate, from the names and apex domains you nominate.

Deliberately excluded

  • No reading of Part 500, and no view on whether it applies to you.
  • No certification, approval or endorsement by the Department of Financial Services.
  • No internal scanning, and no replacement for the annual penetration test.
  • No notice, certification or filing made on your behalf.

Questions on NYDFS 500 and external monitoring

Does ShadowMap make a covered entity compliant with 23 NYCRR 500?

No. Part 500 sets out a cybersecurity programme with governance, policies, access controls, testing and notices, and no monitoring product discharges it. ShadowMap contributes a dated, outside-in record to the parts of that programme that concern the external estate and third-party service providers. Whether the record is sufficient for any section is a judgement for the covered entity and its advisers.

Is Continuous Automated Red-Teaming the penetration test section 500.5 refers to?

No. Section 500.5 calls for penetration testing from both inside and outside the information systems’ boundaries by a qualified internal or external party at least annually. Continuous Automated Red-Teaming is controlled, non-destructive validation of external findings between those tests. Security Brigade, the company behind ShadowMap, carries out penetration tests as a separate engagement.

Do you test our third-party service providers?

No. A provider’s estate is observed from the public internet and nothing on it is probed, because authorisation to test another company’s systems is not yours to give. Findings arrive as observations with a date, for the provider to confirm and fix.

Which version of the regulation does this page quote?

The text of Part 500 as amended by the Second Amendment, in the consolidated PDF the Department of Financial Services publishes on its website, read on 18 November 2026. The Department marks that PDF as not an official version. Check the current official text before relying on any quotation.

Other regimes: MAS TRM Guidelines, APRA CPS 234, DORA.

Start the record with one apex domain

A 30-minute demo walks through the four records described above. Or send one apex domain and receive a written exposure snapshot in two business days.