Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Operations

8/28/2017
05:00 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

New York's Historic FinSec Regulation Covers DDoS, Not Just Data

Starting today, New York banks and insurers must report to authorities within 72 hours on any security event that has a 'reasonable likelihood' of causing material harm to normal operations.

As of today, banks, insurers, and other financial services companies in the state of New York must officially report the kind of cybersecurity incidents that until now most organizations have been able to sweep under the carpet.

The new rules will apply to entities covered by the New York Department of Financial Services' (DFS) new cybersecurity regulation, 23 NYCRR 500, which officially went into effect in March, but hit its first compliance deadline today.

Under 23 NYCRR 500, covered entities must report to the DFS Superintendent within 72 hours any cybersecurity incidents "that have a reasonable likelihood of materially harming any material part of the normal operation of the Covered Entity." 

The regulation does not state under what conditions, if any, an incident needs to be reported to law enforcement, customers, or to the general public. "The regulation specifically relates to the authority that DFS has over its regulated entities. A regulated entity may have other reporting obligations depending on the facts and circumstances, " a DFS spokesperson said.

The regulation requires covered entities to report any incident covered by other regulations as well - therefore, a bank that suffers a PII breach that triggered a PCI violation would also now need to tell DFS.   

More importantly, the new rules would capture many of the significant cybersecurity incidents that currently go uncatalogued and unreported because they are not covered by any formal regulation. Disruptions and denials of service caused by WannaCry, NotPetya, Mirai, or the recent attacks on the SWIFT network, for example, would now be covered (as well as smaller incidents that do not make their way into the news cycle).

However, 23 NYCRR 500 extends beyond operational damage. Any cybersecurity incident that could materially damage the business - like a BEC fraud that cost millions of dollars or an intellectual property theft that jeopardizes the company's market advantage - must also be reported, a DFS representative confirmed. 

Last month, DFS launched a new online portal for reporting incidents. Businesses covered by the regulation must also submit to the Superintendent an annual compliance report, due Feb. 15 each year.

The regulation is the first of its kind in the US. It officially went into effect in March with a series of compliance deadlines staged over two years. Today marks the end of the first transitional period. 

As of today, covered organizations must have a cybersecurity program, a cybersecurity policy, a chief information security officer (who could be employed by either the covered entity or a third party), a security incident response plan, and a process to begin limiting user access priviliges. They also must begin reporting incidents.

By March 2018, covered entities must complete a full infosec risk assessment, conduct penetration testing, conduct end-user awareness training, issue an annual cybersecurity report to internal board-level management, and as a risk assessment deems fit, deploy multi-factor authentication. The regulation specifically calls out multi-factor authentication for any individual accessing internal networks from an external network, unless the CISO has approved reasonably equivalent or more secure controls.

More deadlines hit in September 2018. Organizations will need a secure application development program in place for in-house apps and a process for assessing security of commercial software. This is also when processes for maintaining adequate audit trails (some for at least three years, others for at least five years) data retention, end-user monitoring and data encryption must be in place.

The final piece comes in March 2019, two years after the initial enactment of the regulation, when covered entities must have a third-party service provider security policy. The policy must include due diligence when selecting providers, contractional protections with each third party, and minimum cybersecurity baseline requirements for each third party, including use of access controls and encryption.   

See the full text of 23 NYCRR 500 at DFS.ny.gov.

Learn from the industry’s most knowledgeable CISOs and IT security experts in a setting that is conducive to interaction and conversation. Click for more info and to register.

Related Content:

 

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
romeo999
50%
50%
romeo999,
User Rank: Apprentice
5/27/2020 | 5:10:30 AM
Re: Step in the right direction
we have changed our comment system to block all posts that include URLs. We are seeking a longer-term solution that would allow for URLs. 
NicolaiBezsonoff
50%
50%
NicolaiBezsonoff,
User Rank: Author
9/11/2017 | 2:44:32 PM
Step in the right direction
This is a step in the right direction in terms of providing transparency for consumers. Our research shows that organizations of all sizes are getting hit with DDoS attacks, increasing the likelihood that all kinds of financial services firms will be targets. The good news is that these firms are becoming more prepared to mitigate these kinds of attacks, so they do not cause the significant downtime they have caused in the past. 
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17478
PUBLISHED: 2020-08-10
ECDSA/EC/Point.pm in Crypt::Perl before 0.33 does not properly consider timing attacks against the EC point multiplication algorithm.
CVE-2020-15648
PUBLISHED: 2020-08-10
Using object or embed tags, it was possible to frame other websites, even if they disallowed framing using the X-Frame-Options header. This vulnerability affects Thunderbird < 78 and Firefox < 78.0.2.
CVE-2020-15649
PUBLISHED: 2020-08-10
Given an installed malicious file picker application, an attacker was able to steal and upload local files of their choosing, regardless of the actually files picked. *Note: This issue only affected Firefox for Android. Other operating systems are unaffected.*. This vulnerability affects Firefox ESR...
CVE-2020-15650
PUBLISHED: 2020-08-10
Given an installed malicious file picker application, an attacker was able to overwrite local files and thus overwrite Firefox settings (but not access the previous profile). *Note: This issue only affected Firefox for Android. Other operating systems are unaffected.*. This vulnerability affects Fir...
CVE-2020-15651
PUBLISHED: 2020-08-10
A unicode RTL order character in the downloaded file name can be used to change the file's name during the download UI flow to change the file extension. This vulnerability affects Firefox for iOS < 28.