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

6/23/2006
05:15 AM
50%
50%

Data Loss Epidemic

Data losses at major corporations and government agencies are being reported almost every day now

1:25 PM -- As an IT security journalist, I'm amazed. As an ordinary consumer, I'm downright frightened.

In the last week alone, five major insurance and financial services companies and one government agency have admitted to losing or exposing the personal information of their customers through lax or careless security behavior. Most of these losses occurred not through the ingenuity of attackers, but through the boneheaded behavior of corporate employees – and, in some cases, their IT departments.

We started off the week with the news that ING had lost the names, Social Security numbers, and other data of 13,000 District of Columbia employees when a laptop was stolen from an ING agent living in the D.C. area. (See DC Workers' Personal Data Stolen.)

The laptop was not password-protected, and the data was not encrypted. That loss came just weeks after a similar theft resulted in the loss of 26.5 million veterans' personal information from a laptop owned by a D.C.-area employee of the Department of Veterans Affairs. (See VA Data Loss Worse Than Expected.)

(Note to myself, a D.C.-area resident: Buy new locks for the doors.)

Then, a day later, insurance giant AIG admitted that a break-in back in March had resulted in the loss of a file server containing personal data on some 970,000 of its customers. The data on the server was not encrypted, and AIG said most of the data shouldn't have been given to the company anyway. (See Thieves Nab AIG Customer Records.)

Was that the end of the wave? Not by a longshot. By Thursday, three more companies – Visa, Wachovia, and Equifax – had notified customers of laptop thefts or security violations that may have resulted in the loss of personal data for thousands more customers.

Aside from the sheer coincidence of these major data losses, the most amazing thing about the week's events is the lack of security policy enforcement that occurred (or didn't occur) to create the problems in the first place: Users walking out of the office with thousands of customer records on completely unprotected laptops; and huge caches of data that were never encrypted – or even known about.

How many more hits do companies have to take before IT wises up and gets tough on enforcing security policies?

Apparently, at least a few more. Many of the companies violated this week said they are only just embarking on policy enforcement and training programs to clean up the problem. Credit card vendors report that as many as 90 percent of retailers still aren't complying with guidelines for securing user credit information. (See Retailers Lag on Security Standard.) This thing is likely to get worse before it gets better.

Before you click to the next page, ask yourself the question: Is my customers' data truly safe? The answer may amaze you – or even frighten you.

— Tim Wilson, Site Editor, Dark Reading

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
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...