23 NYCRR Part 500 Cybersecurity Regulation

What the authority record establishes

Part 500 establishes cybersecurity requirements for covered entities and has phased requirements under its second amendment.

Binding within scope

The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.

Why it matters to this market

Insurance systems handling policy, claim, payment, producer, health, or identity data need explicit ownership, access, asset, testing, incident, continuity, third-party, and evidence controls where the rule applies.

Affected operating stages

• Governance
• Asset Inventory
• Access
• Monitoring
• Incident Response
• Continuity
• Third Parties
• Filing

Capabilities to examine

Policy Administration And Policy Lifecycle Control

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for policy administration and policy lifecycle control.

Premium Billing Invoicing And Receivables

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for premium billing invoicing and receivables.

Payments Disbursements And Reconciliation

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for payments disbursements and reconciliation.

First Notice Of Loss Or Event Intake

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for first notice of loss or event intake.

Documents Correspondence And Evidence Management

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for documents correspondence and evidence management.

Insurance Data Model Quality And Governance

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for insurance data model quality and governance.

API Event And Ecosystem Integration

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for API event and ecosystem integration.

Identity Security Privacy And Operational Controls

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for identity security privacy and operational controls.

Audit Trail Reason Code And Decision Reconstruction

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for audit trail reason code and decision reconstruction.

Affected buyer audiences

• New York covered entities
• security
• technology
• legal
• operations

Implementation questions

• Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
• What is binding, what is guidance, and what is a technical or consensus standard?
• Which publication, adoption, effective, application, transition, and enforcement dates differ?
• Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
• How will a source revision affect open work and historical decisions?

Interpretation boundary

The publication does not determine covered-entity status, exemptions, filing obligations, control sufficiency, or compliance.