MyDLP Blog

As you can see from our previous blog post, we are now developing multi-user version of MyDLP in order deliver product to customer in SaaS model. When working on this task, we have encountered several conceptual challenges.

For example; Network-based DLP solutions should inspect all relevant traffic in order to prevent sensitive data leakage, but in Security-as-a-Service model, applications run on cloud computing data centers. So, situation enforces administrators to redirect all traffic to cloud servers and this was never a good idea because of duplicate bandwidth usage on both client line and server line.

Now, what we should do? What is the solution?

Solution is already presented by several authors. Answer is hybrid SaaS model. An application server runs in the internal network, proxies whole external traffic and sends critical parts to services on clouds for leak prevention analysis.

We have worked on this concept and tried to think of a way to use MyDLP in this model and let me tell you MyDLP was already ready for this model and the answer what we were looking for was ICAP.

In next blog post, I will talk about ICAP and our SaaS model implementation…

Data leak protection is a common concern for all companies nowadays. However not all companies have enough budget to conduct an inbound DLP system. Nowadays, MyDLP developers are working to convert MyDLP to a SaaS.

Previously, we have developed a Bayesian Classifier Engine with Java because of Turkish NLP (zemberek) dependency. But, this engine was introducing us some difficulties in many areas such as distribution, performance and maintenance.

But, a week ago we have decide to develop a very simple Turkish NLP module for MyDLP. This was a good decision because zemberek was too developed for us . We weren’t using most of its features and for every request we have to push a big binary through a thrift bridge. Also, large memory footprint of Java process was a disadvantage.

And now, we are using bayeserl with our own very simple Turkish NLP module. Moreover, results are more accurate and performance is improved.

Try it, use it.

Any comments and questions are very welcome.

You can reach draft version of MyDLP Feature and Help Documentfrom the link below. We are about to make a release for network part of MyDLP over Ubuntu.

http://downloads.medratech.com/help/help.html

MyDLP Windows Endpoint Data Leak Prevention tool has made its first release in today. This release is a test release for community. Please feel free to make any comments or submit bugs.

This release have a little probability to harm your computer. Because of this try it in your virtual machines.

Applicable platforms:

32 bit:
Windows XP/Vista/7

You can download and use MyDLP EP from this url:
http://github.com/mydlp/mydlp-host-win32/downloads

Usage and howto documents are going to be ready for a few days.

Central management over network features and several major bugfixes will be ready for the next release. However the most important thing is your opinions for us.

0.1.0 version of MyDLP have been released. You can access tarball from GitHub page.

Features of the release are listed here.

Also, some basic documentation had been added to wiki.

Comments, critics, recommendations, bug reports, feature requests are all welcome.

This features are expected to be released in 2 weeks after final tests(16.07.2010).

MyDLP is an easy-to-use network based data leak prevention tool. It is under heavy development and you can see MyDLP’s sources over http://github.com/mydlp. Project is licensed under GPLv3. Erlang/OTP is being used in development of MyDLP for concurrency, easy deployment and management.

MyDLP’s main aims are:

- Manage Information Flow
- Detect leak