Welcome Guest. | Log In | Register | Membership Benefits
Dark Reading's evil-bytes Weblog

Topics:   Evil Bytes
  • |   Email this page E-mail
  • |  Print Print
  • |   Bookmark and Share

DLP: An Important Tool In Protecting Data During Mergers & Acquisitions

Data loss prevention (DLP) is a topic I've covered in the past because it's important in these times of targeted attacks and accidental data loss. It also tends to be a controversial topic since many people view it differently due to the variation in definitions of what the technology really is. For example, DLP vendors have solutions that range from basic content filtering at the network gateway to complex network- and host-based monitoring solutions, leaving the definition up to the vendor who is selling the solution.

Jan 02, 2009 | 03:12 PM | 

By John H. Sawyer
Dark Reading
Data loss prevention (DLP) is a topic I've covered in the past because it's important in these times of targeted attacks and accidental data loss. It also tends to be a controversial topic since many people view it differently due to the variation in definitions of what the technology really is. For example, DLP vendors have solutions that range from basic content filtering at the network gateway to complex network- and host-based monitoring solutions, leaving the definition up to the vendor who is selling the solution.Since the current state of the economy is in flux, some companies are closing doors while others are opening new doors through mergers and acquisitions. This could easily spell a quick uptick in business for DLP vendors. I read a blog related to this over at eWeek written by a senior manager from Websense (a DLP vendor) that not only makes a case for having DLP (which you'd expect since it is vendor-written) but also drives home the three things I've said before are necessary for companies wanting to protect their data.

Businesses have to monitor, discover, and implement policy to protect the sensitive information resources. I usually think of the data discovery process as coming before the monitoring step, and it can arguably be done either way effectively as long as both processes are used to enhance one another. For example, if you start monitoring for sensitive data first, you won't fully understand what data needs to be monitored before discovering it. Initial monitoring will be for generic things such as Social Security numbers and credit card numbers until data discovery is done and what needs to be monitored is refined.

If data discovery takes place first, then more specific rules can be put into the monitoring system; however, generic rules should still be kept in the monitoring system to help identify systems and data that may have been missed. Once the data is discovered and is being monitored, policies need to be implemented that define what systems should be using the data and what users should have access to, and the monitoring system should be updated again to reflect those policies in order to detect, and hopefully, prevent violations.

In nearly every security book and class I've taken that covers the attack process, the first step is enumeration of the target's resources in order to find the best avenue for attack. One of the more common areas to target is a new merger or subsidiary of the target because their network is less likely to be secure and could end up being a back door into the target through a hastily set-up VPN.

With the eWeek blogger writing, "with current economic conditions greasing the skids for a merger frenzy," I think we're looking at the potential for a number of companies to get hacked due to poor due diligence in securing the networks of the merged/acquired companies' resources in addition to intentional data theft and accidental data loss.

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark 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

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading 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. Dark Reading 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.
Subscribe to RSS









  1. Cookies, Social Media And FireSheep
  2. SMB Guide To Credit Card Regulations, Part 2: The Low-Hanging Fruit
  3. HP And The Scary Corporate Fifth Column Concept
  4. Taking USB Attacks To The Next Level
  5. NoSQL: Not Much, Anyway
  1. Taking Cybersecurity Lessons To The Bank
  2. Researchers See Real-Time Phishing Jump
  3. 'BlackSheep' Sniffs Out Firesheep WiFi-Hacking
  4. Slideshow: Ten Free Security Monitoring Tools
  5. A Different Spin On Sleuthing Stuxnet
  6. M&A Activity Muddles Database Security
  1. Secure Managed Web Hosting Saves 960.gs from Malicious Hackers
  2. Access Governance as a Business Service: An Integrated Strategy for Automation with ITSM
  3. Business Driven Access Management and Governance: Simplifying the Delivery and Governance of Access Throughout
 
 


 
  Ars Technica
Boing Boing
Channel 9 Forums
CRN Blogs
Dr.Dobb's Portal: Blogs
Engadget
Gizmodo
GrokLaw
  Lifehacker
Schneier on Security
Slashdot
TechCrunch
Techdirt
Techmeme
Valleywag
 
  February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
  May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008