Scribd
Upload
40 views15 pages

Data Leakage Detection: Team Members

The document discusses a proposed system for detecting data leakage when sensitive data is distributed to agents. The system would allocate sensitive data and fake objects to agents, with the goal of identifying which agent leaked the data if a leak occurs. Key aspects of the system include a data allocation module to intelligently distribute real and fake data objects, a fake object module to generate fake objects, and an agent guilt module to analyze any leaks and identify the responsible agent. The system is aimed at problems where data distributors need to share sensitive information with third parties they cannot fully trust.

Uploaded by

GobigopsRulz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
40 views15 pages

Data Leakage Detection: Team Members

The document discusses a proposed system for detecting data leakage when sensitive data is distributed to agents. The system would allocate sensitive data and fake objects to agents, with the goal of identifying which agent leaked the data if a leak occurs. Key aspects of the system include a data allocation module to intelligently distribute real and fake data objects, a fake object module to generate fake objects, and an agent guilt module to analyze any leaks and identify the responsible agent. The system is aimed at problems where data distributors need to share sensitive information with third parties they cannot fully trust.

Uploaded by

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

Data leakage detectioN

Team Guide :
B.Sivanandhan
(AP/CSE)

Team members:
S.VIJAYAKUMAR
T.DINESHCHANDRAN
R.GOBINATH
K.BARATHKUMAR

DATA LEAKAGE DETECTION


ABSTRACT:
A data distributor has given sensitive data to a set of supposedly trusted agents.
Sometimes data is leaked and found in unauthorized place e.g., on the web or on
somebody's laptop. For example, a hospital may give patient records to researchers who will
devise new treatments. Similarly, a company may have partnerships with other companies
that require sharing customer data. Another enterprise may outsource its data processing,
so data might be given to various other companies. The owner of the data are called as
distributors and the trusted third parties are called as agents.
Data leakage happens every day when confidential business information such as customer
or patient data, company secrets, budget information etc..are leaked out. when these
information are leaked out, then the companies are at serious risk. Most probably data are
being leaked from agents side. So , company have to very careful while distributing such a
data to an agents. The Goal of Our project is to analyze how the distributer can allocate the
confidential data to the Agents so that the leakage of data would be minimized to a
GreaterExtent by finding an guilty agent.

DATA LEAKAGE DETECTION

INTRODUCTION
EXISTING SYSTEM
PROPOSED SYSTEM
ARCHITECTURE DIAGRAM
IMPLEMENTATIONS
CONCLUSION

INTRODUCTIO
N
In the course of doing
business, sometimes
sensitive data must be
handed over to supposedly
trusted third parties.
Our goal is to detect when
the distributor's sensitive
data has been leaked by
agents, and if possible to
identify the agent that
leaked the data.

EXISTING SYSTEM
WATERMARKING

PROPOSED SYSTEM

PROPOSED SYSTEM

. In the course of doing business,

sometimes sensitive data must be


handed over to supposedly trusted third
parties.
Our goal is to detect when the
distributor's sensitive data has been
leaked by agents, and if possible to
identify the agent that leaked the data.

MODULES
Data Allocation Module
Fake Object Module
Optimization Module
Data Distributor Module
Agent Guilt Module

DATA ALLOCATION MODULE


The main focus of our project is the data
allocation problem as how can the distributorintelligently give
data to agents in order to improve thechances of detecting a
guilty agent, Admin can send thefiles to the authenticated
user, users can edit their accountdetails etc. Agent views the
secret key details throughmail. In order to increase the
chances of detecting agentsthat leak data.

FAKE OBJECT MODULE


The distributor creates and adds fake objects to
the data that he distributes to agents. Fake objects are
objects generated by the distributor in order to increase
the chances of detecting agents that leak data. The
distributor may be able to add fake objects to the
distributed data in order to improve his effectiveness in
detecting guilty agents. Our use of fake objects is
inspired by the use of trace records in mailing lists. In
case we give the wrong secret key to download the file,
the duplicate file is opened, and that fake details also
send the mail. Ex: The fake object details will display

Optimization Module
The Optimization Module is the distributors
data allocation to agents has one constraint and one
objective. The agents constraint is to satisfy distributors
requests, by providing them with the number of objects
they request or with all available objects that satisfy their
conditions. His objective is to be able to detect an agent
who leaks any portion of his data. User can able to lock
and unlock the files for secure.

ARCHITECTURE DIAGRAM:
The Sent e-mail
dont contains fake
Object/Watermarks.

Internet

Agent tries to leak the


sensitive data
Forwarded
to the
outside
world

The Sent e-mail


contains fake
Object/Watermarks.

Internet

Agent tries to leak the


sensitive data
Infected
e-mail
containing
fake
object

Implementation
The system has the following

Data Allocation
-- approach same as watermarking
-- less sensitive
-- add fake object in some cases

Fake Object
-- Are real looking object
-- Should not affect data
-- Limit on fake object insertion(e-mail inbox)
-- CREATEFAKEOBJECT (Ri, Fi, CONDi)

CONCLUSION
In the real scenario there is no need to hand over the sensitive data
to the agents who will unknowingly or maliciously leak it.
However, in many cases, we must indeed work with agents that may
not be 100 percent trusted, and we may not be certain if a leaked
object came from an agent or from some other source.
In spite of these difficulties, it is possible to assess the likelihood that
an agent is responsible for a leak, based on the overlap of his data
with the leaked data .
The algorithms we have presented implement a variety of data
distribution strategies that can improve the distributors chances of
identifying a leaker.

You might also like