Skip Links

Network World

  • Social Web 
  • Email 
  • Close

(Comma separation for multiple addresses)
Your Message:

Avoiding data-loss prevention pitfalls

Insider Threat By Rich Mogull , Network World , 02/04/2008
  • Share/Email
  • Tweet This
  • Comment
  • Print

What are the barriers to DLP? I've heard it can take a lot of time and the costs add up. Is there a way to get around this?

It's always daunting to consider deployment of a new security technology, but with the proper preparation Data Loss Prevention (DLP) is less painful to deploy than many of our other tools. The keys to a successful DLP deployment are setting the right expectations, proper planning during the selection process, and a controlled roll-out.

The most common failure in deploying DLP is failing to set appropriate expectations before and during the selection process. Some organizations jump into DLP before they know exactly how they would like to use the technology. They either make a snap purchase to close a single existing problem, or they focus on technology-driven expectations that do not reflect business needs. Before you start product evaluations, pull together a team of major stakeholders - including IT, IT security, legal, risk, compliance, HR, and major business units. Determine what data you want to protect, and the degree of protection you would like.

For example, one organization may focus on detecting credit card numbers on the network, in storage, and on endpoints and on preventing any transfer outside the enterprise. Another organization might be more interested in protecting unstructured sensitive engineering plans, with an emphasis on detection rather than enforcement. Make a prioritized list of the content you want to protect, and map it to a list of desired protective actions. Follow this with a rough outline of workflow so you know which users, technical and non-technical, will need to use the system. This feeds directly into your product selection requirements.

Armed with knowledge of what you would like to protect and how, you then inventory your existing infrastructure and integration requirements. You do not need a detailed assessment of every little device on the network, just an overview of major gateways, data repositories, and endpoint management infrastructure. The combination of your data protection, workflow, and infrastructure integration requirements will form the heart of your product requirements. You will know what kind of content analysis techniques to focus on, whether you will need a point solution (e.g. an endpoint-only solution) or a complete DLP suite, and what your key workflow requirements are.

  • Share/Email
  • Tweet This
  • Comment
  • Print
Comment
Login
Forgot your account info?
Add comment
Anonymous comments subject to approval. Register here for member benefits.
Have a NetworkWorld account? Log in here. Register now for a free account.

Videos

rssRss Feed