Commentary

George Hulme
 

DLP Market Continues Its Consolidation

CA's data loss prevention (DLP) vendor acquisition today clinches it: DLP vendors must either forge partnerships or be acquired to survive.

CA's data loss prevention (DLP) vendor acquisition today clinches it: DLP vendors must either forge partnerships or be acquired to survive.Today, CA publicized its intention to acquire DLP vendor Orchestria. Orchestria (other than having a rather silly name that I hope CA fades with the acquisition) makes software that helps stop information from seeping through e-mails, instant messaging, and Web forms, as well as lock down the printing of sensitive files and the use of USB drives.

In its announcement, CA said it will integrate Orchestria's line with its identity and access management solutions, which the company said will help companies improve security within the process of managing users and their level of access privileges based on their roles.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

This strikes me as an interesting approach -- rather than tying access and system usage rights to the machine, they could follow the user. I'll have to see more details on how such a tactic would be put into practice.

While blocking protected or regulated data from slippage through e-mail or inappropriate storage on USB devices is interesting, I'm much more intrigued by the concept of embedding security into the data itself so that no matter where a file travels, its security and access privileges go with it -- as in who can print, forward, or even view the file. I covered recent trends in the enterprise DRM space in this story in our sister Web site Byte and Switch.


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