Quality, Expert-Derived Cybersecurity Documentation To Keep Organizations Secure, Compliant & Resilient  |  Got Questions? +1-307-241-8740
ComplianceForge

How Do You Comply With NY DFS 23 NYCRR 500.14 Monitoring and Training?

Short Answer

23 NYCRR 500.14 requires risk-based monitoring of authorized user activity to detect unauthorized access, use or tampering with nonpublic information, risk-based controls against malicious code including web and email filtering, and cybersecurity awareness training that includes social engineering for all personnel at least annually. Class A companies also need endpoint detection and response and centralized logging and security event alerting.

23 NYCRR 500.14 Monitoring and Training at a Glance

  • Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
  • Section: 23 NYCRR 500.14 Monitoring and Training.
  • Status: Amended by the Second Amendment, effective November 1, 2023.
  • Who it applies to: Every covered entity unless exempt under 500.19(c) or (d). Entities with a 500.19(a) limited exemption must still meet 500.14(a)(3) training.
  • Class A companies: 500.14(b): Class A companies must implement endpoint detection and response to monitor anomalous activity, including lateral movement, and a solution that centralizes logging and security event alerting, unless the CISO approves reasonably equivalent or more secure compensating controls in writing.
  • Limited exemption (500.19(a)): Partly exempt. 500.19(a) waives 500.14(a)(1), (a)(2) and (b), but not the annual awareness training in 500.14(a)(3).
  • Compliance dates: The annual training requirement in 500.14(a)(3) applied from April 29, 2024 (500.22(c)). The malicious code controls in 500.14(a)(2) and the Class A requirements in 500.14(b) applied from May 1, 2025, 18 months after the effective date (500.22(d)(3)).

Section 500.14 was retitled Monitoring and Training and reordered so that monitoring comes first. It now has three parts for all covered entities: user activity monitoring, malicious code protection with web and email filtering, and annual awareness training that includes social engineering.

Class A companies have extra technical requirements in 500.14(b): endpoint detection and response that monitors anomalous activity such as lateral movement, and centralized logging with security event alerting. The CISO can approve compensating controls in writing instead.

What Does 23 NYCRR 500.14 Require?

The following is the text of 23 NYCRR 500.14 Monitoring and Training as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability.

  • (a) As part of its cybersecurity program, each covered entity shall:
  • (1) implement risk-based policies, procedures and controls designed to monitor the activity of authorized users and detect unauthorized access or use of, or tampering with, nonpublic information by such authorized users;
  • (2) implement risk-based controls designed to protect against malicious code, including those that monitor and filter web traffic and electronic mail to block malicious content; and
  • (3) provide periodic, but at a minimum annual, cybersecurity awareness training that includes social engineering for all personnel that is updated to reflect risks identified by the covered entity in its risk assessment.
  • (b) Each class A company shall implement, unless the CISO has approved in writing the use of reasonably equivalent or more secure compensating controls:
  • (1) an endpoint detection and response solution to monitor anomalous activity, including but not limited to lateral movement; and
  • (2) a solution that centralizes logging and security event alerting.

Source: NY DFS, Second Amendment to 23 NYCRR 500 (text).

How Does 23 NYCRR 500.14 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.14 to 13 SCF controls through 14 relationships (1 "subset of", 13 "intersects with").

How to read the mapping: each relationship runs from the Part 500 text to the SCF control. "Subset of" means the Part 500 requirement is fully contained within 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.

  • SAT-02 Security, Compliance & Resilience-Minded Workforce. Subset of (strength 10): 500.14(a)(3). SCF control: Mechanisms exist to facilitate the implementation of security workforce development and awareness controls.
  • GOV-04 Publishing Security, Compliance & Resilience Documentation. Intersects with (strength 5): 500.14(a)(1). SCF control: Mechanisms exist to establish, maintain and disseminate policies, standards and procedures necessary for secure, compliant and resilient capabilities.
  • MON-16 Anomalous Behavior. Intersects with (strength 5): 500.14(a)(1). SCF control: Mechanisms exist to utilize User & Entity Behavior Analytics (UEBA) and/or User Activity Monitoring (UAM) solutions to detect and respond to anomalous behavior that could indicate account compromise or other malicious activities.
  • SAT-06.2 Suspicious Communications & Anomalous System Behavior. Intersects with (strength 5): 500.14(a)(1). SCF control: Mechanisms exist to provide training to personnel on organization-defined indicators of malware to recognize suspicious communications and anomalous behavior.
  • END-03 Endpoint Protection Mechanisms. Intersects with (strength 5): 500.14(a)(2), 500.14(b)(1). SCF control: Mechanisms exist to protect the confidentiality, integrity, availability and safety of endpoint devices.
  • END-04 Malicious Code Protection (Antimalware). Intersects with (strength 5): 500.14(a)(2). SCF control: Mechanisms exist to utilize antimalware, or similar technologies, to detect and eradicate malicious code.
  • NET-02 Network Security Controls (NSC). Intersects with (strength 5): 500.14(a)(2). SCF control: Mechanisms exist to develop, govern & update procedures to facilitate the implementation of Network Security Controls (NSC).
  • NET-17 DNS & Content Filtering. Intersects with (strength 5): 500.14(a)(2). SCF control: Mechanisms exist to force Internet-bound network traffic through a proxy device (e.g., Policy Enforcement Point (PEP)) for URL content filtering and DNS filtering to limit a user's ability to connect to dangerous or prohibited Internet sites.
  • NET-40.2 Phishing & Spam Protection. Intersects with (strength 5): 500.14(a)(2). SCF control: Mechanisms exist to utilize anti-phishing and spam protection technologies to detect and take action on unsolicited messages transported by electronic mail.
  • END-09 Endpoint Detection & Response (EDR). Intersects with (strength 5): 500.14(b)(1). Applies to Class A companies. SCF control: Mechanisms exist to utilize Endpoint Detection & Response (EDR) capabilities to detect, investigate and respond to anomalous and/or malicious activity.
  • END-12 Host Intrusion Detection and Prevention Systems (HIDS / HIPS). Intersects with (strength 5): 500.14(b)(1). Applies to Class A companies. SCF control: Mechanisms exist to utilize Host-based Intrusion Detection / Prevention Systems (HIDS / HIPS), or similar technologies, to monitor for and protect against anomalous host activity, including lateral movement across the network.
  • MON-05 Centralized Collection of Event Logs & Security-Relevant Telemetry. Intersects with (strength 5): 500.14(b)(2). Applies to Class A companies. 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.
  • MON-05.4 Automated Tools for Real-Time Event Log & Security-Relevant Telemetry Analysis. Intersects with (strength 5): 500.14(b)(2). Applies to Class A companies. SCF control: Mechanisms exist to utilize a Security Incident Event Manager (SIEM), or similar automated tool, to support near real-time event log and security-relevant telemetry analysis and incident escalation.

The STRM records "no relationship" for the lead-in text of 500.14(a) and 500.14(b); the numbered paragraphs under them are mapped individually.

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.14

The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:

  • Training without social engineering. 500.14(a)(3) requires training that includes social engineering and is updated to reflect risks identified in the risk assessment.
  • Training less than annually. Training must be provided periodically, but at a minimum annually, to all personnel.
  • Email filtering but no web filtering. 500.14(a)(2) calls for controls that monitor and filter web traffic and electronic mail to block malicious content.
  • Class A EDR gaps. EDR coverage that leaves out servers or other endpoints where lateral movement occurs weakens the 500.14(b)(1) control. Document any CISO-approved compensating controls.

What Is Reasonable Evidence for 23 NYCRR 500.14?

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.14 include:

  • E-GOV-01.10 Continuous Monitoring Policy. Documented evidence of a continuous monitoring policy.
  • E-GOV-01.29 Security Awareness & Training Policy. Documented evidence of a security awareness and training policy.
  • E-SAT-06 Training Materials. Documented evidence of security awareness training materials (e.g., curriculum, course work, presentations, etc.)
  • E-END-01 Endpoint Security Tools. Documented evidence of endpoint security tools employed by the organization to ensure secure, compliant and resilient Technology Assets, Applications and/or Services (TAAS) (e.g., antimalware, FIM, etc.).
  • E-MON-02 Malware Activity. Documented evidence of malware activity being logged and included as part of the centralized event log collection and review/analysis process.
  • E-END-03 Antimalware Scanning Results. Documented evidence of scan results from malicious code protection mechanisms.
  • E-GOV-02 Cybersecurity & Data Protection Standards. Documented evidence of an appropriately-scoped cybersecurity & data protection standards. Standards are mandatory requirements regarding processes, actions and configurations. Standards are intended to be granular and prescriptive to ensure Technology Assets, Applications and/or Services (TAAS) are designed and operated to include appropriate cybersecurity & data protection protections
  • E-GOV-04 Cybersecurity & Data Protection Procedures. Documented evidence of an appropriate appropriately-scoped cybersecurity & data protection procedures. Procedures are a documented set of steps necessary to perform a specific task or process in conformance with an applicable standard. Procedures help address the question of how the organization actually operationalizes a policy, standard or control. The result of a procedure is intended to satisfy a specific control. Procedures are also commonly referred to as “control activities.”

Records specific to 23 NYCRR 500.14 that typically show the requirement is designed and operating:

  • Monitoring procedures. Risk-based procedures and controls for monitoring authorized user activity.
  • Malicious code and filtering configuration. Anti-malware, web filtering and email filtering settings and coverage.
  • Training records. Completion records for all personnel within the last year, with social engineering content and updates tied to the risk assessment.
  • Class A records. EDR coverage reports, SIEM or centralized logging scope, alert rules, and any CISO compensating control approvals.

Which ComplianceForge Documents Support 23 NYCRR 500.14?

The following ComplianceForge documents can help you document and implement 23 NYCRR 500.14 Monitoring and Training:

  • 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 often is cybersecurity awareness training required under 23 NYCRR 500.14? Periodically, but at a minimum annually, for all personnel. The training must include social engineering and be updated to reflect risks identified in the risk assessment.

What does 500.14(b) require from Class A companies? Unless the CISO approves reasonably equivalent or more secure compensating controls in writing, an endpoint detection and response solution to monitor anomalous activity, including lateral movement, and a solution that centralizes logging and security event alerting.

Do limited-exemption entities need security awareness training? Yes. The 500.19(a) limited exemption waives 500.14(a)(1), (a)(2) and (b), but not the training requirement in 500.14(a)(3).

When did the 500.14 malicious code and Class A requirements take effect? 500.14(a)(2) and 500.14(b) had an 18-month transitional period from November 1, 2023, so they applied from May 1, 2025 under 500.22(d)(3).

Bottom Line on 23 NYCRR 500.14 Monitoring and Training

500.14 combines user monitoring, malicious code protection and annual social engineering training for everyone, with EDR and centralized logging for Class A companies. Even limited-exemption entities must run the annual training, so keep completion records for all personnel.

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.13 Asset Management and Data Retention Requirements. Next section: 500.15 Encryption of Nonpublic Information. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.