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

3/1/2017
01:35 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

New Cybersecurity Regulations Begin Today For NY Banks

New York's new security regulations for financial industry viewed as potential model for other states.

Today's the day the much-anticipated new cybersecurity regulations for the financial industry go into effect in the state of New York.

Security experts say the new regulations by the state's Department of Financial Services (DFS) set a minimum baseline for security best practices, and acknowledge that small- to midsized businesses with fewer resources and smaller IT staffs may find compliance more challenging.

The regulations require that banks, insurance companies, and other financial institutions establish and maintain a cybersecurity program. The new rules are widely viewed as the first of their kind and potentially a baseline model for other states.

"These new regulations will push companies to have a basic level of cybersecurity, but it doesn’t create an unfair competitive situation because it's generally applied across the board," says Tim Erlin, senior director, product management and IT risk and security strategist at Tripwire.

The new regulations will be phased in over the next two years. Companies with less than $5 million in revenues and $10 million in assets are exempt from many of the more costly, technical aspects of the regulations, such as pen testing and vulnerability assessments, but still must document that they have implemented a security policy and program.

The vast majority of companies are now on the hook to develop an incident response plan and a training program in the next 180 days. Companies must also notify DFS of a security breach within 72 hours and have a CISO or a similar person responsible for protecting private data. The breach-notification portion requires companies to start the clock on notification from the time they have determined that a breach would cause material harm to the business.

By one year from today, companies must also demonstrate that they have pen testing, risk assessment, and multifactor authentication practices in place. In 18 months, they must have developed audit trail capabilities, application security, data retention (five years for financial, three years for non-financial), and encryption. The DFS requirements for third parties will be phased in over two years.

David Murray, chief business development officer at Corvil, says the vast majority of the large banks and financial institutions are well on their way to having implemented many of the best practices outlined by the DFS regulations.

While smaller hedge funds, retail banks, and credit unions have expressed concerns that implementing these security technologies will be too costly, he points out that many of these companies already have security analytics technologies that provide visibility into their operations.

"What we’re saying is that you can start by getting a better read on what’s happening within your organization and you don’t necessarily have to spend more money and time deploying new technology," Murray says. "We see this as pushing companies to be more proactive, because they are now tracking incidents and attacks versus just looking for a piece of malware."

Tripwire's Erlin adds that the strength of these regulations will be to what extent they are enforced. He points to recent cases where New York’s DFS fined Deutsche Bank $425 million and Mega Bank $180 million for violating state money-laundering laws.

"While those fines are not related to cybersecurity, it does indicate that the agency is capable of imposing those type of fines and that they actually might do it," he says. 

Related Content:

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
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...