Data Leakage Detection

PREPARED BY DEEPIKA.K [081061106005]

Abstract
A data distributor has given sensitive data to a set of supposedly trusted agents (third parties). It has a chance in leakage of data and found in an unauthorized place (e.g., on the web or somebodys laptop).
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 detecting leakage and identify the guilty party.

WATERMARKING
Traditionally, leakage detection is handled by water-marking, e.g., a unique code is embedded in each distributed copy.

If that copy is later discovered in the hands of an unauthorized party, the leaker can be identified. Watermarks can be very useful in some cases, but again, involve some modification of the original data. Furthermore, watermarks can sometimes be destroyed if the data recipient is malicious.

Leakage Problem
Name: Sarah
Sex: Female . Name: Mark

Sex: Male
. Jeremy Sarah App. U1 App. U2 Mark

Other Sources e.g. Sarahs Network

Kathryn

Stanford Infolab

Modules
Problem Description

Guilt Models Distribution Strategies

Data flow diagram

Software Requirements

Front End Back End Operating System

: .NET : SQL Server 2000 : Windows XP

Hardware Requirements
Hard Disk RAM Processor : : : 80GB and Above 512MB and Above Pentium IV and Above

Conclusions

Data Leakage

Modeled as maximum likelihood problem

Data distribution strategies that help identify the guilty agents