By Jack Hewitt
Jack Hewitt is a partner in the firm of Pastore and Dailey and is a seasoned securities lawyer that focuses his practice on securities litigation and regulatory advice and counsel to broker-dealers, investment advisers and private funds. He is a recognized national authority in cybersecurity, advises firms on their development of information security programs, guides them through cyber-incidents and represents them in the event of a regulatory inquiry. Mr. Hewitt is the author of Cybersecurity in the Federal Securities Markets, a Bloomberg BNA publication.
By Jack Hewitt
The New York State Department of Financial Services (DFS) proposed on September 13, 2016 a cybersecurity regulation that was to be effective on January 1, 2017 (Regulation) (New York State Department of Financial Services, Proposed 23 NYCRR 500, Cybersecurity Requirements for Financial Services Companies).
After considerable adverse commentary about the Regulation during the comment period, the DFS revised the regulation and reset its effective date to March 1, 2017. DFS stated in a December 28 press release that it “carefully considered all comments submitted regarding the proposed regulation during the 45-day comment period . . . and has incorporated those suggestions that DFS deemed appropriate in an updated draft that will be subject to an additional final 30-day comment period.”
The DFS regulates mortgage banks, life insurance companies, savings and loans, charitable foundations and other financial services firms (Firms) and, with certain limited exemptions, all such entities will be subject to the Regulation. In its proposal, the DFS notes that it has been closely monitoring the increasingly serious cybersecurity problems experienced in the financial services industry and is proposing the Regulation to address this situation. It applauds the many firms that have developed and implemented cybersecurity programs (Programs) and directs those who have not to begin the development of one.
The Regulation is designed to provide a basic foundation upon which Firms can develop a Program and requires them initially to assess their risk profile and then to design a robust program to address any identified risks. The Regulation provides flexibility for each Firm to develop a Program that is designed to assess and control a Firm’s specific risks as well as any new technological developments. The DFS emphasizes in the Regulation that senior management must take an active role in a Firm’s Program and take direct responsibility for it.
The Regulation is extensive, as it has 23 sections addressing such subjects as cybersecurity programs and policies, the necessity of appointing a Chief Information Security Officer, penetration testing, audits, risk assessment, third party service providers, multi-factor authentication, training, encryption, incident response plans, notice and exemptions. These topics are similar to those contained in the regulations and guidelines issued by the Securities and Exchange Commission, FINRA and certain states such as Massachusetts. (201 Mass. Code of Regs. 17.01; OCIE 2015 Cybersecurity Examination Initiative (September 2015) and FINRA 2015 Report on Cybersecurity Practices (February 2015)).
Significant changes were made between the initial proposal and the revised Regulation, including the addition of the defined terms “risk assessment” and “third party service provider,” an allowance for the Chief Information Security Officer to have additional Firm responsibilities, modified policies and procedures regarding the handling of nonpublic information by third parties, modification to the requirements for notice of a cybersecurity event and revised exemptions to the Regulation. The initial proposal also had an all-inclusive transitional period of 180 days from the effective date, while the revised version retains the 180 period but now includes additional transition periods of one, one and a half and two years for particular requirements such as risk assessments (one year), multi-factor authentication (one year), audit trials (1 ½ years) and encryption (1 ½ years).
The following provides an overview of the Regulation, as revised.
The Definitions section contains 13 key terms that are specifically applicable to the Regulation. This includes the definitions of Cybersecurity Event, which is any act or attempt to gain unauthorized access to a Firm’s Information System, and Multi-Factor Authentication, that is an authentication through at least two of the following three factors: knowledge (something the user knows such as a password), possession (something s/he possesses such as a token) or inherence (a biometric). The Regulation uses a rather broad definition of Nonpublic Information (Nonpublic Information), as it includes any business-related information the tampering with which would cause a materially adverse impact on a Firm’s business; and information concerning an individual that can be used to identify such individual in combination with elements such as social security numbers, drivers license numbers or financial account numbers or codes. A Covered Entity (CE) is one that operates under or is required to operate under a DFS license, charter, registration or similar state authorization and an Information System (System) is a discrete set of electronic resources organized to provide a certain technological service.
The Regulation requires each CE to maintain a cybersecurity program designed to protect the confidentiality, integrity and availability of its Information Systems. The Program should be based on the CE’s Risk Assessment. It must identify and assess internal and external cybersecurity risks that could threaten the security or integrity of Nonpublic Information stored on the CE’s Information Systems. This must protect the information in these Systems from unauthorized access, use or other malicious acts and be designed to detect Cybersecurity Events. Finally, it must establish an incident response plan (IRP) to ensure that the Firm mitigates the effects of a Cybersecurity Event. A CE may use an Affiliate’s cybersecurity program to meet these requirements.
A CE’s written cybersecurity policy (Cybersecurity Policy) shall be implemented and set forth its policies and procedures to protect its Systems and any Nonpublic Information stored on these Systems. The policy must be based on the CE’s Risk Assessment and address the following areas to the extent applicable to the CE’s operations: information security, data governance and classification, asset inventory and device management, access controls and identity management, business continuity and disaster recovery planning and resources, systems operations and availability concerns, systems and network security, systems and network monitoring, systems and application development and quality assurance, physical security and environmental controls, customer data privacy, vendor and Third Party Service Provider Management, risk assessment, and incident response. These written policies must be approved by a Senior Officer or the CE’s board of directors or equivalent governing body.
Each CE shall designate a Chief Information Security Officer (CISO) or the equivalent to be responsible for implementing, overseeing and enforcing the CE’s cybersecurity program and policy. The CISO responsibility may be handled by a Third Party Service Provider, but the CE shall still be responsible for the CISO’s responsibilities and shall designate a senior Firm member to ensure that the Third Party Service Provider complies with the CISO requirements. The CISO shall develop and file a report at least annually with the CE’s board of directors or equivalent governing body, but, if no such governing body exists, then to the Senior Officer of the CE responsible for its cybersecurity program. The CISO report shall address the integrity and security of the CE’s systems, the policies and procedures, material risks, effectiveness of the Firm’s systems, and material cybersecurity events in the reported period.
Each Program shall include monitoring and testing of the Program, which shall include annual penetration testing of a Firm’s Systems and bi-annual vulnerability assessments of them. The Firm is required to securely maintain systems designed to reconstruct material financial transactions to support normal business, include audit trails to detect and respond to Cybersecurity Events which could materially harm the business operations and maintain records required by this Section for not fewer than five years. Each Firm shall employ the principal of least privilege by limiting System access privileges solely to those who require such access and periodically reviewing such access privileges.
In developing its own applications or in using externally developed applications, a Firm must have written procedures, guidelines and standards designed to ensure the use of secure development practices and for evaluating, assessing and testing the security of them. All procedures, guidelines and standards shall be reviewed, assessed and updated as deemed necessary by the CISO.
Each Firm shall conduct a periodic documented risk assessment of its Systems which shall be updated as reasonably necessary to address changes to the CE’s Information Systems, Nonpublic Information or business operations. The assessment shall include criteria for the evaluation and categorization of identified risks and for the assessment of the confidentiality, integrity and availability of its Systems. This shall include documentation describing risks mitigation or acceptance.
Each CE shall employ sufficient personnel to effectively execute its cybersecurity responsibilities and this personnel shall be properly trained and maintain current knowledge of changing cybersecurity threats and countermeasures. An Affiliate or qualified Third Party Service Provider may assist in complying with these requirements, subject to Section 500.11, Third Party Information Security Policy.
Each CE must develop policies and procedures designed to address the cybersecurity responsibilities of all third parties including the security of Systems that are accessible to, or held by, Third Party Service Providers. Such policies and procedures shall address the identification and risk assessment of these Third Party Service Providers and establish minimum cybersecurity practices required to be met by them to do business with the CE. This must include due diligence procedures to evaluate their cybersecurity practices and a periodic assessment of such entities and the adequacy of their practices.
These policies and procedures shall include requirements for Third Party contract provisions and/or due diligence including the Third Party Service Provider’s policies and procedures for access controls and use of encryption, notice to the CE in the event of a Cybersecurity Event impacting the CE’s Information systems or Nonpublic Information held by the Third Party Service Provider.
Each CE shall use effective controls in order to protect against unauthorized access to Nonpublic Information or Information Systems. Any individual accessing the CE’s internal networks from an external network shall use Multi-Factor Authentication unless the CE’s CISO approves at least reasonably equivalent access controls.
Each CE shall have policies and procedures for the secure disposal on a periodic basis of any Nonpublic Information that is no longer necessary for its business, except where such information is otherwise required to be retained by law or regulation or disposal is not reasonably feasible.
Each CE’s Program shall implement risk-based policies and procedures designed to monitor authorized users, detect unauthorized access, use or tampering with Nonpublic Information and provide regular updated cybersecurity awareness training sessions.
The Regulation requires the encryption of all Nonpublic Information both in transit and at rest. If this proves infeasible, CEs may employ alternative compensating controls that are approved by the CISO and reviewed at least annually.
Each CE shall establish a written IRP that shall effectively respond to and allow the Firm to recover from any Cybersecurity Event materially affecting the confidentiality, integrity or availability of its Systems or the continuity of its business. The IRP shall address, at a minimum, the CE’s response to the incident and the IRP’s goals. It must also clearly define roles, responsibilities and levels of decision-making authority, closely coordinate internal and external communications, identify requirements for remediation of any identified weakness in Information Systems and associated controls, document and report Cybersecurity Events and evaluate and improve the IRP after an event. It must also ensure that all required reports are filed with the appropriate regulatory authorities.
CEs are required to provide a notice to the DFS Superintendent of a Cybersecurity Event where notice is required to be provided to any government body, self-regulatory agency or any other supervisory body or where there is a reasonable likelihood of material harm to the normal operations of the CE. Notice is to be given as soon as possible, but no later than 72 hours after the event.
A CE must also file a written statement on a DFS form by February 15 annually certifying that it is complying with the Regulation’s requirements and these statements shall be maintained as well as all documents supporting it for five years. If the CE notes anything for improvement or redesign, it must document this and retain it for the DFS Superintendent’s inspection.
The Regulation contains an exemption from certain Sections of this Regulation for a CE with fewer than 10 employees or independent contractors, less than $5 million in gross annual revenue in each of the last three fiscal years, or less than $10 million in year-end total assets.
Employees, agents, representatives or designees of a CE, who is itself a CE, are exempt from developing its own Program to the extent that s/he is covered by the CE’s Program.
Further, a CE that does not operate, maintain, utilize or control any Information Systems and that does not, and is not required to, control, own, access, generate, receive or possess Nonpublic Information is exempt from certain Sections of this Regulation.
If a CE ceases to qualify for an exemption, such CE will have 180 days from the effective date to comply with the Regulation’s requirements.
Copyright © 2017 The Bureau of National Affairs, Inc. All Rights Reserved.
All Bloomberg BNA treatises are available on standing order, which ensures you will always receive the most current edition of the book or supplement of the title you have ordered from Bloomberg BNA’s book division. As soon as a new supplement or edition is published (usually annually) for a title you’ve previously purchased and requested to be placed on standing order, we’ll ship it to you to review for 30 days without any obligation. During this period, you can either (a) honor the invoice and receive a 5% discount (in addition to any other discounts you may qualify for) off the then-current price of the update, plus shipping and handling or (b) return the book(s), in which case, your invoice will be cancelled upon receipt of the book(s). Call us for a prepaid UPS label for your return. It’s as simple and easy as that. Most importantly, standing orders mean you will never have to worry about the timeliness of the information you’re relying on. And, you may discontinue standing orders at any time by contacting us at 1.800.960.1220 or by sending an email to email@example.com.
Put me on standing order at a 5% discount off list price of all future updates, in addition to any other discounts I may quality for. (Returnable within 30 days.)
Notify me when updates are available (No standing order will be created).
This Bloomberg BNA report is available on standing order, which ensures you will all receive the latest edition. This report is updated annually and we will send you the latest edition once it has been published. By signing up for standing order you will never have to worry about the timeliness of the information you need. And, you may discontinue standing orders at any time by contacting us at 1.800.372.1033, option 5, or by sending us an email to firstname.lastname@example.org.
Put me on standing order
Notify me when new releases are available (no standing order will be created)