Policy Patty Newsletter - November 2023
https://policypatty.com/

Policy Patty Newsletter - November 2023

November 30, 2023

Here is a compilation of critical headlines I covered in November 2023.? Click on the headline to access the full article/blog.?

This newsletter does not include all relevant developments that may impact your organization's governance, risk, and compliance controls.? It is provided for informational purposes only and does not offer legal, accounting, or tax advice.

?

??POLICY PATTY POSTS

??REPORTS AND OTHER INFORMATION

I've included below a summary of reports and other developments that, while I did not cover in November, may be relevant to your operations.

??Special News:

NYDFS Part 500 approval

On November 1, 2023, the New York Department of Financial Services (NYDFS or DFS) released the?finalized amendments ?to its?landmark cyber regulation - 23NYCRR Part 500 (Part 500) , first enacted in 2017. The changes represent efforts that began in July 2022 and, following?extensive comments , were finalized on November 1, 2023.?

?

Highlights of the changes:

  • Class A Companies (500.1(d)) - creates a new category of companies called "Class A Companies" for which there are specific additional requirements.?
  • Audits (500.2(c)) - requires independent audits of the covered entity's cybersecurity program based on its risk assessment.
  • Access monitoring (500.7(c)). Requires monitoring of privileged access activity and implementation of: (1) a privileged access management solution; and (2) an automated method of blocking commonly used passwords (CISO-approved compensating controls are permitted so long as they are in writing and approved annually).

  • Endpoint security (500.14(b)) -??Requires this unless the CISO approves reasonably equivalent or more secure compensating controls in writing.

  • Cybersecurity policy (500.3) - requires annual approval of the cybersecurity program policy by a senior officer or the covered entity's senior governing body and adds additional areas to cover.
  • CISO (500.4) -?retains the requirement for a specific CISO for the covered entity while defining CISO as "a qualified individual responsible for overseeing and implementing a covered entity's cybersecurity program and enforcing its cybersecurity policy."?
  • Senior governing body (i.e., board or equivalent) oversight (500.4(d)) -?requires a "senior governing body" of the covered entity to exercise effective cybersecurity-related oversight and clarifies that for any cybersecurity program or part of a cybersecurity program adopted from an affiliate under section 500.2(d), the senior governing body may be that of the affiliate.
  • Vulnerability management (500.5)- requires that vulnerability management policies and procedures require that covered entities conduct, at a minimum, annual penetration testing, automated scans of information systems, and a manual review of the scans. Also adds a requirement that all vulnerabilities must be timely remediated and prioritized by the risk posed to the covered entity.
  • Access and privilege management (500.7) -?requires that, based on the covered entity's risk assessment, the covered entity take specific steps related to access and privilege management (e.g., limiting the number of privileged accounts and access functions of privileged accounts to only those necessary to perform the user's job; periodically, but at a minimum annually, reviewing all user access privileges and removing or deactivating accounts and access that are no longer necessary; etc.).
  • Password policy (500.7) -??requires a written password policy that meets industry standards to the extent that passwords are an authentication method.
  • Application security (500.8) -?requires that application security procedures, guidelines, and standards be reviewed at least annually.
  • Risk assessment (500.9). Specifies that risk assessment must be reviewed and updated at least annually and when a change in the business or technology causes a material change to the covered entity's cyber risk.?
  • Multi-factor authentication (MFA) (500.12)-?requires that MFA be used for any individual accessing the covered entity's information systems unless the entity is eligible for a limited exception. Also specifies that the CISO?may?approve?in writing?compensating controls and that such controls, if applied, must be reviewed annually.
  • Asset management and data retention (500.13(a)) -?requires implementing policies and procedures to maintain a complete and accurate asset management inventory of the covered entity's information systems.?
  • Monitoring (500.14(b)) -?requires covered entities to implement risk-based controls designed to protect against malicious code (which includes controls that monitor and filter web traffic and email to block malicious content).
  • Training (500.14(a)(3)) -?requires training must occur annually and include social engineering training.
  • Encryption (500.15) -?requires a policy requiring encryption that meets industry standards and removes the infeasibility exception for encryption in transit while maintaining the infeasibility exception for encryption at rest (but clarifies that the CISO's annual review and approval of feasibility and compensating controls must be in writing).
  • Incident response and business continuity and disaster recovery (500.16) - requires that incident response plans address disruptive events such as ransomware incidents, recovery from backups, and preparation of root cause analysis, and undergo annual resting.?
  • Notice of cybersecurity incidents and extortion payments (500.17(a); 500.17(c)) -?requires notice of all cybersecurity incidents within 72 hours after determining that the event has occurred. The notice must: le.

  • Include an explanation of extortion payments made in connection with cybersecurity events involving the covered entity within 24 hours of the payment.?

  • Within 30 days of the extortion payment, the covered entity must submit a written description of the reasons payment was necessary, a description of alternatives considered, all diligence performed to find payment alternatives, and all diligence performed to ensure compliance with applicable rules and regulations.

  • Certification (500.17(b)). Revises the certification process to include options for the covered entity regarding their compliance status.
  • Enforcement (500.20). Adds language specifying that violations of Part 500.

?

Key Dates

  • Series of staggered transition periods for various provisions.
  • December 1, 2023 - compliance with section 500.17(a) requires providing NYDFS with notice of cybersecurity events reported to other authorities and ransomware.?
  • April 15, 2024 - compliance with section 500.17(b) requires all entities to submit a Certification of Material Compliance or Acknowledgment of Noncompliance for 2023.?

More Information

DFS guidance is available at the?Cybersecurity Resource Center , which features tools and information.?

?

legalrightsguru.io AI fixes this Policy Patty Newsletter November 2023

回复
Sara Lord

Leveraging the Power of Fun (and data) to Increase Engagement & Productivity

11 个月

These monthly summaries are great. Thanks for these!

Wendy Schoen, MBA, JD

Legal Recruiter ?? I Find Forever Homes for Elite Lawyers ?? Specializing in Partners for Midsize and Specialty Practices?? Career Strategy for GCs and Partners?? Let Me Put My Experience to Work for You

12 个月

WOW! One tends to forget how much actually happens in one month! Thanks Patty P. Tehrani for putting this all together every month! Subscribing to your Newsletter is a MUST DO for any regulatory attorney!

要查看或添加评论,请登录

社区洞察

其他会员也浏览了