Volume: 4 Issue: 3
ISSN: 2321-8169
186 -187
______________________________________________________________________________________
Supriya Sarkar
SKNSITS,Lonavala
manishprabhu812@gmail.com
SKNSITS,Lonavala
supriya.sarkar@rediffmail.com
Abstract The number of data leak instances are increasing day by day. Human mistakes are main cause of data leakage . Data leakage caused
by human mistakes have some solutions. These solutions provide an alert when there is a data leakage. One of the common approach is to give
the contents in the databases and transmitted information over the network to the data leakage detection service provider for getting information
about the leakage ,but this is an open invitation for an outsider to gain the sensitive information about the company or an organization ;because
the detection is based on third party. In this paper, we have done the analysis on various techniques of data leakage detection along with their
privacy issue
INTRODUCTION
COMPARISON OF TECHNIQUES
_______________________________________________________________________________________
ISSN: 2321-8169
186 -187
______________________________________________________________________________________
especially in cases where there is large overlap in the data that
agents must receive. In some cases realistic but fake data
records are injected to improve the chances of detecting
leakage and identifying the guilty party.
In paper [5], authors have done experiment on android
based system. They have found some API which are
susceptible for compromising privacy of the user. They have
analyzed smali source codes from android devices to identify
potential security threats.
In paper [6], authors have implemented privacy preserving
data leakage detection model. For that purpose they used rabin
fingerprint for calculating message digest. Using fingerprint
technique, we can store very large amount of data in small
size. Rabin fingerprints are useful for achieving privacy of
sensitive data. But these methods failed to handle dynamically
changing data.
III.
CONCLUSION
[2]
[3]
[4]
[5]
[6]
[7]
187
IJRITCC | March 2016, Available @ http://www.ijritcc.org
_______________________________________________________________________________________