theDocumentId => 746192 House Bill Would Create Federal Standards for Data ...

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.

Operational Security //

Law

9/19/2018
07:00 AM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

House Bill Would Create Federal Standards for Data Breach Notifications

A bill that has now passed the House Financial Services Committee would create federal standards for how banks and other financial institutions notify customers when a data breach occurs.

A bill that passed the House Financial Services Committee earlier this month would create new federal standards and rules that would require banks and other financial institutions to notify customers following a data breach.

The bill, H.R. 6743, or the "Consumer Information Notification Requirement Act," passed the committee by a vote of 32 to 20. It will now move to the full House for a vote.

US Rep. Rep. Blaine Luetkemeyer (R-Mo.) introduced the bill, which would amend the Gramm-Leach-Bliley Act, a 1999 law that currently regulates how financial institutions handle customers' personal information.

(Source: Pixabay)
(Source: Pixabay)

"It is going to take better cooperation from all my colleagues and the industries that handle consumer data in order to advance additional meaningful changes," according to a Sept. 13 statement from Luetkemeyer's office. "At some point there will be another major breach, and without a comprehensive solution our constituents will pay the price for our inaction."

If passed, the bill would create new requirements that banks and other financial institutions notify customers when a data breach has occurred. The law would also preempt local state laws that regulate the disclosure of data breaches.

Following the massive data breach at Equifax in 2017, where some employees and executives have been charged with insider trading, as well as issues with how Intel disclosed security problems with its chips earlier this year, the US Securities and Exchange Commission has now upgraded its own guidelines on how public companies must disclose data breaches to the public. (See Equifax, Intel Help Spur SEC to Update Cybersecurity Regulations.)

While not law yet, the Luetkemeyer bill drew praise from Steve Durbin, the managing director of the non-profit Information Security Forum. However, in an email to Security Now, Durbin noted that not only banks, but other merchants and businesses, should be required to disclose data breach as well.

Durbin wrote:

Anyone who has been caught up in a breach will know the upset and disruption this can cause. Therefore, having a bill that requires financial institutions to notify consumers of a breach, within a timely period passed, is a positive first step. However, given the complexity of the financial networks today, merchants must also be included to ensure that all ends of the complex purchase chain are covered. This will then go some way to providing consumers with the confidence, not that breaches are a thing of the past, but that they will be issued with timely warnings of the potential damage that a breach may cause them personally and are better placed to take immediate remedial action to reduce the impact that loss of personal and financial details can so often cause.

In addition to advocates like Durbin, organization such as the Credit Union National Association also voiced support for including merchants and other businesses as part of the disclosure process.

Chris Morales, head of security analytics at Vectra, which makes threat management tools, wrote in an email that while these laws are good for consumers, and will help standardized the notification process, they do address the underlying security issues of how these data breaches occur.

"The notification laws only work once an institution even knows there is a problem," Morales wrote. "I don't expect these laws to have any impact on the next major financial breach because financial institutions cannot report on what they do not know. For example, it took Equifax 78 days to even know a problem existed. They responded and reported the breach within 30 days after knowing. The hard part is even knowing the breach exists."

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-23416
PUBLISHED: 2021-07-28
This affects all versions of package curly-bracket-parser. When used as a template library, it does not properly sanitize the user input.
CVE-2021-23417
PUBLISHED: 2021-07-28
All versions of package deepmergefn are vulnerable to Prototype Pollution via deepMerge function.
CVE-2021-23415
PUBLISHED: 2021-07-28
This affects the package elFinder.AspNet before 1.1.1. The user-controlled file name is not properly sanitized before it is used to create a file system path.
CVE-2020-4974
PUBLISHED: 2021-07-28
IBM Jazz Foundation products are vulnerable to server side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks. IBM X-Force ID: 192434.
CVE-2020-5004
PUBLISHED: 2021-07-28
IBM Jazz Foundation products are vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 192957.