Scribd
Upload
71 views

Project Title: Data Leakage Detection

The project aims to detect data leakage when a data distributor shares sensitive data with trusted third parties. Some data is leaked and the distributor needs to determine if it came from one of the third parties. The proposal involves strategies for allocating data across agents to improve identifying leakages without altering the data. In some cases, fake but realistic records can be added to further help detect leakage and identify the guilty party. The project uses .NET as the platform, C# as the programming language, and SQL Server 2005 as the backend database.

Uploaded by

Nikhil Dixit
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
71 views

Project Title: Data Leakage Detection

The project aims to detect data leakage when a data distributor shares sensitive data with trusted third parties. Some data is leaked and the distributor needs to determine if it came from one of the third parties. The proposal involves strategies for allocating data across agents to improve identifying leakages without altering the data. In some cases, fake but realistic records can be added to further help detect leakage and identify the guilty party. The project uses .NET as the platform, C# as the programming language, and SQL Server 2005 as the backend database.

Uploaded by

Nikhil Dixit
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Project Title: Data Leakage Detection

We study the following problem: A data distributor has given sensitive data to a set of
supposedly trusted agents (third parties). Some of the data is leaked and found in an
unauthorized place (e.g., on the web or somebodys laptop). The distributor must assess the
likelihood that the leaked data came from one or more agents, as opposed to having been
independently gathered by other means. We propose data allocation strategies (across the
agents) that improve the probability of identifying leakages. These methods do not rely on
alterations of the released data (e.g., watermarks). In some cases we can also inject realistic
but fake data records to further improve our chances of detecting leakage and identifying the
guilty party.

Platform : .Net

Language : C#.net

BackEnd : Microsoft SQL Server 2005

You might also like