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

4/22/2012
08:36 PM
Dark Reading
Dark Reading
Quick Hits
50%
50%

How To Secure Large Data Warehouses

As more businesses consolidate sensitive data in high-capacity warehouses, the question becomes how to properly secure these potential treasure-houses. Here are some tips

[Excerpted from "Securing the Data Warehouse," a new report posted this week on Dark Reading's Database Security Tech Center.]

Sony. RSA. Epsilon. Aside from major security breaches, what do these companies have in common? They were all victimized by hackers looking to access large storehouses of corporate data.

Shielding such data from attacks must be a chief priority for any enterprise security team. That means guarding the house in which data resides: the database -- or, in a growing number of instances, the data warehouse.

With the amount of data in organizations increasing daily, many enterprises are building data warehouses to centralize the information flowing through their business into useful repositories. From a business and IT standpoint, this makes perfect sense and simplifies data management.

From a security standpoint, however, the model opens up a new set of challenges that requires smart planning and the effective implementation of many of the same security best practices used with databases.

But there are new lessons to be learned, as well, and the wrong set of security constraints can hurt the productivity of your warehouse just as surely as an attack.

Among its predictions for 2012, analyst firm IDC predicted the volume of digital data would jump to 2.7 billion Tbytes, up 48 percent from 2011. By 2015, the firm predicts, that figure will reach 8 billion Tbytes. In many enterprises, much of this data makes its way into a data warehouse, where it can be pulled out by business intelligence (BI) tools and aggregated into reports that can be leveraged by a business to enable better analysis. The goal of making massive amounts of data available to users is a lofty one, but it is also one that requires erecting protections to keep data safe and block unauthorized access.

At its heart, data warehouse security revolves around the areas of data classification, data protection, and identity and access management.

During the planning phase, organizations should develop their security process by doing the following:

* Identify the data to be migrated; * Determine the data’s business value; and * Classify the data according to its sensitivity.

To discover more about the process of classifying sensitive data -- and to find out about best practices for securing that data and building the right access methodology -- download the free report.

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...