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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
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. 
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8423
PUBLISHED: 2020-04-02
A buffer overflow in the httpd daemon on TP-Link TL-WR841N V10 (firmware version 3.16.9) devices allows an authenticated remote attacker to execute arbitrary code via a GET request to the page for the configuration of the Wi-Fi network.
CVE-2019-14868
PUBLISHED: 2020-04-02
In ksh version 20120801, a flaw was found in the way it evaluates certain environment variables. An attacker could use this flaw to override or bypass environment restrictions to execute shell commands. Services and applications that allow remote unauthenticated attackers to provide one of those env...
CVE-2019-20635
PUBLISHED: 2020-04-02
codeBeamer before 9.5.0-RC3 does not properly restrict the ability to execute custom Java code and access the Java class loader via computed fields.
CVE-2020-11452
PUBLISHED: 2020-04-02
Microstrategy Web 10.4 includes functionality to allow users to import files or data from external resources such as URLs or databases. By providing an external URL under attacker control, it's possible to send requests to external resources (aka SSRF) or leak files from the local system using the f...
CVE-2020-11453
PUBLISHED: 2020-04-02
Microstrategy Web 10.4 is vulnerable to Server-Side Request Forgery in the Test Web Service functionality exposed through the path /MicroStrategyWS/. The functionality requires no authentication and, while it is not possible to pass parameters in the SSRF request, it is still possible to exploit it ...