NYDFS Updates FAQs to Clarify Cybersecurity Regulations

by Ballard Spahr LLP
Contact

Ballard Spahr LLP

The New York Department of Financial Services (NYDFS) recently updated frequently asked questions (FAQs) about its cybersecurity regulations, 23 NYCRR 500, to address four new issues. NYDFS published its initial set of FAQs on April 24, 2017. Please see prior Ballard Spahr Alerts on the NYDFS' cybersecurity regulations here and here.

In addition to FAQs, the NYDFS also released a timeline of key deadlines through March 1, 2019, for compliance with different requirements imposed by the regulations. These deadlines include:

  • August 28, 2017: Cybersecurity program (Section 500.12), cybersecurity policy (500.03), chief information security officer (500.04(a)), access privileges (500.07), cybersecurity personnel and intelligence (500.10); and incident response plan (500.16)

  • September 27, 2017: Filing of Notice of Exemptions (500.19(e))

  • February 15, 2018: All "Covered Entities" are required to submit their first annual certifications

  • March 1, 2018: Chief Information Security Officer reporting to the board of directors (500.04(b)), penetration testing and vulnerability assessments (500.05), risk assessments (500.09), multi-factor authentication (500.12), and cybersecurity awareness training (500.14(a)(2))

  • September 3, 2018: Audit trails (500.06), application security (500.08), data retention (500.13), policies and procedures to monitor the activity of authorized users (500.14(a)(1)), and encryption (500.15)

  • March 1, 2019: Third-party service provider security policy (500.11)

As these compliance deadlines draw closer, financial institutions should review all of the FAQs to confirm that they have aligned their policies, procedures, and practices with the NYDFS' interpretation of the regulations.

Below are a list of the new FAQs and summaries of each entry:

1. When is an unsuccessful attack a Cybersecurity Event that has or had "a reasonable likelihood of materially harming any material part of the normal operation(s) of the Covered Entity" under the reporting requirements of 23 NYCRR Section 500.17(a)(2)?

This first new FAQ instructs organizations to use good judgment when deciding whether to report unsuccessful attacks. Because it seeks to gather and share information about "especially serious unsuccessful attacks," NYDFS encourages organizations to assess whether the response to the incident required measures or resources beyond their usual procedures, such as "exceptional attention by senior personnel or the adoption of extraordinary non-routine precautionary steps." The NYDFS says it does not intend to penalize Covered Entities that were acting in good faith when making judgments about which unsuccessful events to report.

2. Are the New York branches of out-of-state domestic banks required to comply with 23 NYCRR Part 500?

This second new FAQ clarifies that the home state of a state-chartered bank is primarily responsible for its supervision, and NYDFS defers to the home state supervisors in the examination of New York branches, but encourages all financial institutions to adopt cybersecurity protections.

3. How must a Covered Entity address cybersecurity issues with respect to its subsidiaries and other affiliates?

This third new FAQ addresses the need to evaluate any risks to Covered Entities' information systems or any nonpublic information stored on a subsidiary's or affiliate's systems. In conducting the required risk assessment and creating its cybersecurity program and policy, a Covered Entity must address the risks posed by their subsidiaries and affiliates.

4. If a Covered Entity qualifies for a limited exemption, does it need to comply with 23 NYCRR Part 500?

This fourth new FAQ explains that Covered Entities that qualify for exemptions are only exempt from complying with certain provisions. The Covered Entity still must comply with the applicable provisions listed in the designated exemption. The exceptions were designed to be tailored for particular circumstances, not to allow Covered Entities to avoid all cybersecurity requirements.

These four new FAQs join the existing set of questions, which are listed below:

  • Under 23 NYCRR 500.17(a), is a Covered Entity required to give notice to the Department when a Cybersecurity Event involves harm to consumers?

  • Is a Covered Entity required to give notice to consumers affected by a Cybersecurity Event?

  • May a Covered Entity adopt portions of an Affiliate's cybersecurity program without adopting all of it?

  • May the certification requirement of 23 NYCRR 500.17(b) be met by an Affiliate?

  • To the extent a Covered Entity uses an employee of an Affiliate as its Chief Information Security Officer ("CISO"), is the Covered Entity required to satisfy the requirements of 23 NYCRR 500.04(a)(2)-(3)?

  • Are the DFS-authorized New York branches, agencies and representative offices of out-of-country foreign banks required to comply with 23 NYCRR Part 500?

  • Where interrelated requirements under 23 NYCRR Part 500 are subject to different transitional periods, when and to what extent are Covered Entities required to comply with currently applicable requirements that are impacted by separate requirements for which the applicable transitional period has not yet ended?

  • Is a Covered Entity required to certify compliance with all the requirements of 23 NYCRR 500 on February 15, 2018?

  • May a Covered Entity submit a certification under 23 NYCRR 500.17(b) if it is not yet in compliance with all applicable requirements of Part 500?

  • What constitutes "continuous monitoring" for purposes of 23 NYCRR 500.05?

  • When is a Covered Entity required to report a Cybersecurity Event under 23 NYCRR 500.17(a)?

  • How should a Covered Entity submit Notices of Exemption, Certifications of Compliance, and Notices of Cybersecurity Events?

  • Can an entity be both a Covered Entity and a Third-Party Service Provider under 23 NYCRR Part 500?

  • Are all Third Party Service Providers required to implement Multi-Factor Authentication and encryption when dealing with a Covered Entity?

 

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Ballard Spahr LLP | Attorney Advertising

Written by:

Ballard Spahr LLP
Contact
more
less

Ballard Spahr LLP on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
Sign up using*

Already signed up? Log in here

*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
Privacy Policy (Updated: October 8, 2015):
hide

JD Supra provides users with access to its legal industry publishing services (the "Service") through its website (the "Website") as well as through other sources. Our policies with regard to data collection and use of personal information of users of the Service, regardless of the manner in which users access the Service, and visitors to the Website are set forth in this statement ("Policy"). By using the Service, you signify your acceptance of this Policy.

Information Collection and Use by JD Supra

JD Supra collects users' names, companies, titles, e-mail address and industry. JD Supra also tracks the pages that users visit, logs IP addresses and aggregates non-personally identifiable user data and browser type. This data is gathered using cookies and other technologies.

The information and data collected is used to authenticate users and to send notifications relating to the Service, including email alerts to which users have subscribed; to manage the Service and Website, to improve the Service and to customize the user's experience. This information is also provided to the authors of the content to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

JD Supra does not sell, rent or otherwise provide your details to third parties, other than to the authors of the content on JD Supra.

If you prefer not to enable cookies, you may change your browser settings to disable cookies; however, please note that rejecting cookies while visiting the Website may result in certain parts of the Website not operating correctly or as efficiently as if cookies were allowed.

Email Choice/Opt-out

Users who opt in to receive emails may choose to no longer receive e-mail updates and newsletters by selecting the "opt-out of future email" option in the email they receive from JD Supra or in their JD Supra account management screen.

Security

JD Supra takes reasonable precautions to insure that user information is kept private. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. However, please note that no method of transmitting or storing data is completely secure and we cannot guarantee the security of user information. Unauthorized entry or use, hardware or software failure, and other factors may compromise the security of user information at any time.

If you have reason to believe that your interaction with us is no longer secure, you must immediately notify us of the problem by contacting us at info@jdsupra.com. In the unlikely event that we believe that the security of your user information in our possession or control may have been compromised, we may seek to notify you of that development and, if so, will endeavor to do so as promptly as practicable under the circumstances.

Sharing and Disclosure of Information JD Supra Collects

Except as otherwise described in this privacy statement, JD Supra will not disclose personal information to any third party unless we believe that disclosure is necessary to: (1) comply with applicable laws; (2) respond to governmental inquiries or requests; (3) comply with valid legal process; (4) protect the rights, privacy, safety or property of JD Supra, users of the Service, Website visitors or the public; (5) permit us to pursue available remedies or limit the damages that we may sustain; and (6) enforce our Terms & Conditions of Use.

In the event there is a change in the corporate structure of JD Supra such as, but not limited to, merger, consolidation, sale, liquidation or transfer of substantial assets, JD Supra may, in its sole discretion, transfer, sell or assign information collected on and through the Service to one or more affiliated or unaffiliated third parties.

Links to Other Websites

This Website and the Service may contain links to other websites. The operator of such other websites may collect information about you, including through cookies or other technologies. If you are using the Service through the Website and link to another site, you will leave the Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We shall have no responsibility or liability for your visitation to, and the data collection and use practices of, such other sites. This Policy applies solely to the information collected in connection with your use of this Website and does not apply to any practices conducted offline or in connection with any other websites.

Changes in Our Privacy Policy

We reserve the right to change this Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our privacy policy will become effective upon posting of the revised policy on the Website. By continuing to use the Service or Website following such changes, you will be deemed to have agreed to such changes. If you do not agree with the terms of this Policy, as it may be amended from time to time, in whole or part, please do not continue using the Service or the Website.

Contacting JD Supra

If you have any questions about this privacy statement, the practices of this site, your dealings with this Web site, or if you would like to change any of the information you have provided to us, please contact us at: info@jdsupra.com.

- hide
*With LinkedIn, you don't need to create a separate login to manage your free JD Supra account, and we can make suggestions based on your needs and interests. We will not post anything on LinkedIn in your name. Or, sign up using your email address.