Commentary

George Crump
 

Data Theft

The ability to steal company data is no more real today than it was five years ago, but the volume of data that can be stolen is.

The ability to steal company data is no more real today than it was five years ago, but the volume of data that can be stolen is.This Labor Day weekend I was strolling through the local discount computer store and was reminded of one of the biggest concerns I have been hearing from CIO's lately -- data theft. There are 1-TB USB external hard drives floating around $300 and small, pocket 250-GB drives at around $150.

The real issue is would you rather block or tackle? In yesterday's entry I discussed file auditing and one of its capabilities to know who copied a file and to where. If someone were to copy company-sensitive data you could be alerted to that and stop them before they got out the door ... tackling. You would be better served had that copy never happened in the first place ... blocking. The ultimate would be to have both auditing and blocking integrated so the two applications could work together, sharing policies and metadata... data supervision. One of the challenges is most people don't see this as stealing, they see it as more the data equivalent of taking home a box of pens from the supply closet. Actually, the office supplies are held in higher regard, probably because they are tangible. People just don't hold digital content in as high regard as cash. A person that would never take a $100 bill off your desk might very well rip a copy of the latest CD or DVD, or might also take home a customer list, a prospect database, Excel, or Word templates. The attitude is that this is not "really stealing." It falls on the shoulders of the IT professional to lock this data down, while not making the environment too cumbersome to work with. This makes the more draconian approaches, like disabling all USB devices, impractical, and it is the void that data blocking tools could fill. These products allow you to set policies that only allow certain types of users to copy certain types of files to certain types of devices. They can have full access to the files as long as they stay on the network, but allow you to restrict their movement beyond that. I think they are becoming a key requirement in the enterprise. Data supervision integrates auditing with blocking (among other capabilities) to allow shared policy and common metadata databases. Doing so simplifies the process and allows further examination of what is happening in your enterprise. Say, for example, an executive in your organization has full access and can copy virtually anything to USB devices. You can still have an alert that warns if anyone in the organization is copying a large amount of data to a device in a short period of time -- blocking could then step in and stop the transfer.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

For example, if you are in the oil and gas market and suddenly 500 GB of SEG-Y data is being copied to a local USB drive, that could be legitimate, but it also could be theft. With data supervision you will be able to suspend the transfer, investigate who is making the transfer, and why. Then you can make an informed decision as to if that transfer should be allowed to continue. There is a significant amount of corporate assets that only see life in digital form. Don't let that data walk out the door on a pocket hard drive.

Track us on Twitter: http://twitter.com/storageswiss.

Subscribe to our RSS feed.

George Crump is founder of Storage Switzerland, an analyst firm focused on the virtualization and storage marketplaces. It provides strategic consulting and analysis to storage users, suppliers, and integrators. An industry veteran of more than 25 years, Crump has held engineering and sales positions at various IT industry manufacturers and integrators. Prior to Storage Switzerland, he was CTO at one of the nation's largest integrators.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links