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.

Risk //

Compliance

2/14/2018
05:30 PM
50%
50%

Filing Deadline for New Infosec Law Hits NY Finance Firms Thursday

Banks and financial services companies in New York must file by tomorrow to certify they are compliant with the state Department of Financial Services' new cybersecurity regulation, 23 NYCRR 500.

Banks, insurers, and other financial services organizations in New York state have until tomorrow to file for their first annual certification of compliance with 23 NYCRR 500, the New York State Department of Financial Services' historic cybersecurity regulation.

The law officially went into effect March 2017; covered entities must be in compliance with the bulk of the regulation by March 1. This includes sections 500.04(b), 500.05, 500.09, 500.12, and 500.14(b) of the law, which mandate risk assessments, vulnerability assessments, penetration testing, multi-factor authentication, and end-user awareness training. 

Enforcement for the law's security incident reporting rule went into effect in August, requiring companies to report within 72 hours any event that has a "reasonable likelihood" of causing material harm to normal operations - a unique notification rule that goes beyond PII breaches to cover anything from intellectual property leaks to DDoSes.

The next compliance deadline - on rules for data use, data access, security personnel, and more - hits Sep. 18.  

For more information, see here

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
CustomEssay
50%
50%
CustomEssay,
User Rank: Apprentice
3/12/2018 | 5:21:32 AM
Re: Given the state of security
Good work
CustomEssay
50%
50%
CustomEssay,
User Rank: Apprentice
3/12/2018 | 5:21:11 AM
Re: Given the state of security
Really useful blog
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
2/15/2018 | 7:57:46 AM
Given the state of security
I would be surprised if a fraction of financial institutions are in compliance.  Down here in Georgia we have the collapse of Equifax as a prime example of game gone bad.   I work for a firm that DOES have a malware forensics department and a damn good one it is too.  Quite rare.  So - NYState?   Given the total mess that Albany is, I see nothing really changing at all - only getting worse.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...