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.

Perimeter

5/5/2010
03:01 PM
John H. Sawyer
John H. Sawyer
Commentary
50%
50%

DLP Gets An Open-Source Boost

Data loss, or leakage, prevention (a.k.a. DLP) is a product class that includes data discovery, classification, and monitoring to prevent your sensitive data from falling into the wrong hands. Some implementations are configured to alert instead of block, but the basics are the same. You have sensitive data, you don't always know where it is, so you use DLP tools to find it and keep it safe.

Data loss, or leakage, prevention (a.k.a. DLP) is a product class that includes data discovery, classification, and monitoring to prevent your sensitive data from falling into the wrong hands. Some implementations are configured to alert instead of block, but the basics are the same. You have sensitive data, you don't always know where it is, so you use DLP tools to find it and keep it safe.Until last week, there really were no open-source agent-based DLP tools. There have been several open-source discovery tools, including Spider, Senf, and Find_SSN, but they had to be run on individual systems. Workarounds were created to use them in a distributed manner across many desktops, but the attempts were often very specific to a particular environment, kludgy, and required constant care and feeding.

A new agent-based DLP discovery tool was just released to Google Code last week called OpenDLP (follow the project on Twitter). Andrew Gavin made the announcement to various mailing lists and has posted version 0.1 to Google Code. The design is simple. A server runs a Web management interface that allows the deployment and management of agents, securely receives results from the agents, creates scan profiles, and more.

The agents currently run on Microsoft Windows systems and scan for sensitive information using regular expressions. The regular expressions are essentially pattern matching data based on known patterns, such as Social Security and credit card numbers.

Coming from an educational environment, money for security is often scarce, and being able to deploy DLP is difficult due to the high costs associated with the current solutions. I nearly jumped out of my seat when I first started reading about OpenDLP. It has a lot of great potential to help organizations who simply cannot afford commercial DLP solutions.

However, there's a problem. It's a first release, meaning there's a lot of desirable features that just aren't there yet. For example, the agent is limited in the file types it can read. There is no support yet for zip files, Office 2007, and OpenOffice files. It doesn't support data at rest inside databases. And it cannot do agentless scans. BUT those are features listed under "Future Plans" on the site. Of course, that raises the other question of how active is development and what's the time frame for those features?

The future is bright for open-source DLP. For example, combine OpenDLP with the new Sensitive Data preprocessor in Snort, and you're well on your way to detecting sensitive data at rest and in motion. Neither solution is perfect by any means, but it's a lot more than many organizations are already doing. Even with commercial DLP solution, a determined insider is going to get the data out one way or another.

Keep an eye on OpenDLP. And if you can give back to the project in any way, please do so because everyone will benefit.

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.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
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-2021-31769
PUBLISHED: 2021-06-21
MyQ Server in MyQ X Smart before 8.2 allows remote code execution by unprivileged users because administrative session data can be read in the %PROGRAMFILES%\MyQ\PHP\Sessions directory. The "Select server file" feature is only intended for administrators but actually does not require autho...
CVE-2020-20469
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has a SQL injection vulnerability. The vulnerability stems from the log_edit.php files failing to filter the csa_to_user parameter, remote attackers can exploit the vulnerability to obtain database sensitive information.
CVE-2020-20470
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has web site physical path leakage vulnerability.
CVE-2020-20471
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has an unauthorized access vulnerability in default_user_edit.php, remote attackers can exploit this vulnerability to escalate to admin privileges.
CVE-2020-20472
PUBLISHED: 2021-06-21
White Shark System (WSS) 1.3.2 has a sensitive information disclosure vulnerability. The if_get_addbook.php file does not have an authentication operation. Remote attackers can obtain username information for all users of the current site.