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

8/26/2008
11:59 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Security Breach: More Laws Needed. Let's Add Health Care

Earlier this week, colleague Thomas Claburn covered the unfortunate trend that the tally of data breaches this year already has surpassed all breaches recorded for the entire year in 2007. This isn't entirely bad news, as I'll explain.

Earlier this week, colleague Thomas Claburn covered the unfortunate trend that the tally of data breaches this year already has surpassed all breaches recorded for the entire year in 2007. This isn't entirely bad news, as I'll explain.From the story, "This Year's Data Breaches Surpass 2007 Totals":

With four months to go in 2008, the number of data breaches on the Identity Theft Resource Center's 2008 breach list has already surpassed the 446 breaches reported by the organization for all of 2007.

As of the morning of Aug. 22, the number of data breaches reported had reached 449.

I agree with much of what the story goes on to say, especially that auditors are finding more breaches today than ever before. There are more eyes looking at IT systems now: internal security teams and auditors, as well as external auditors and business partners. And, as a result of this first database breach disclosure law, and the many similar state laws that followed, the public finally got a view into the severity of the data security program, and how poorly the applications, networks, and systems that store and manage their information are designed, coded, and maintained.

Yet, these publicly disclosed breaches are like light waves: we're only seeing a small part of the spectrum of breaches occurring every year.

From the same story:

The Identity Theft Resource Center points out that the actual number of breaches this year is probably higher than 449 so far because of underreporting and because breaches affecting multiple businesses tend to be reported as a single event. According to the ITRC, in 40% of breach events, the number of records affected is not reported or fully disclosed.

In June, following the release of a Verizon Business Security survey about data breaches, Bryan Sartin, VP of investigative response at Verizon, told InformationWeek that publicly reported breaches are "just the tip of iceberg." He said that less than 5% of the more than 500 cases covered in the Verizon study involved some form of disclosure.

In any event, it appears that hard numbers about data breaches are hard to come by. According to survey of about 300 attendees at this year's RSA Conference, more than 89% of security incidents went unreported in 2007.

This is why we need more data breach disclosure laws -- laws that go beyond financial account information. For instance, health care-related information is much more sensitive than financial information, and it would be great if Web sites had to report to visitors (as many as they can) that their site was compromised and spreading malware, like password sniffing Trojans. But under current law, there's no reason for them to tell anyone.

But let's just stick to health care. More than 1.5 million patient records at hospitals have been exposed by data breaches during 2006 and 2007, according to the 2008 HIMSS Analytics Report: Security of Patient Data, commissioned by Kroll Fraud Solutions. That begs the question: is the health care industry doing enough to protect the privacy of medical records?

The symptoms point to a diagnosis of no. According to the HIMSS report, those 1.5 million data leak victims don't include breaches at other health care companies, home care providers, physician offices, or pharmaceutical companies. So this report is likely only giving us a peak at a sliver of the problem.

If that doesn't send your blood pressure up, consider this: the hospitals surveyed are probably only aware of a small percentage of how many patients have been affected by lax hospital security, as only about 44% of hospitals that suffered a breach failed to let the patients know their records could be at risk to snoops.

Even more disturbing is what the hospitals didn't say: all of the hospitals that disclosed being breached mostly cited unauthorized use of information and wrongful access of paper records. None reported having been hacked. The odds are that that's simply not the reality: "Noticeably absent are breach sources associated with malicious intent, such as stolen laptops/computers, deliberate acts by unscrupulous employees, etc., supporting the lack of industry focus on fraudulent data breaches that masks the frequency and severity of the problem," the report states.

No doubt. The trouble is, without proper intrusion detection and prevention systems in place, access and database log monitoring, and other controls, most hospitals probably wouldn't know if they were successfully hacked.

There was plenty of silence when it came to financial breaches, prior to July 2003. That's not because banks, credit unions, and retailers weren't being hacked. It's because they weren't required to report any breaches until California enacted SB 1386, which required any company, where California residents were involved, to notify each of these victims if the firm suffered a security incident where certain kinds of financial information was, or could have been, exposed. Today, most states have similar laws in force.

Perhaps it's time the health care industry was forced to do the same.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
9 Tips to Prepare for the Future of Cloud & Network Security
Kelly Sheridan, Staff Editor, Dark Reading,  9/28/2020
Attacker Dwell Time: Ransomware's Most Important Metric
Ricardo Villadiego, Founder and CEO of Lumu,  9/30/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-2019-20902
PUBLISHED: 2020-10-01
Upgrading Crowd via XML Data Transfer can reactivate a disabled user from OpenLDAP. The affected versions are from before version 3.4.6 and from 3.5.0 before 3.5.1.
CVE-2019-20903
PUBLISHED: 2020-10-01
The hyperlinks functionality in atlaskit/editor-core in before version 113.1.5 allows remote attackers to inject arbitrary HTML or JavaScript via a Cross-Site Scripting (XSS) vulnerability in link targets.
CVE-2020-25288
PUBLISHED: 2020-09-30
An issue was discovered in MantisBT before 2.24.3. When editing an Issue in a Project where a Custom Field with a crafted Regular Expression property is used, improper escaping of the corresponding form input's pattern attribute allows HTML injection and, if CSP settings permit, execution of arbitra...
CVE-2020-25781
PUBLISHED: 2020-09-30
An issue was discovered in file_download.php in MantisBT before 2.24.3. Users without access to view private issue notes are able to download the (supposedly private) attachments linked to these notes by accessing the corresponding file download URL directly.
CVE-2020-25830
PUBLISHED: 2020-09-30
An issue was discovered in MantisBT before 2.24.3. Improper escaping of a custom field's name allows an attacker to inject HTML and, if CSP settings permit, achieve execution of arbitrary JavaScript when attempting to update said custom field via bug_actiongroup_page.php.