Existing System

Traditionally, leakage detection is handled by watermarking, 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. The Existing System can detect the hackers but the total no of
cookies (evidence) will be less and the organization may not be able to proceed legally for
further proceedings due to lack of good amount of cookies and the chances to escape of hackers
are high.

1.5 Proposed System

In the proposed system we study unobtrusive techniques for detecting leakage of a set of objects
or records. Specifically, we study the following scenario: After giving a set of objects to agents,
the distributor discovers some of those same objects in an unauthorized place. (For example, the
data may be found on a website, or may be obtained through a legal discovery process.) At this
point, the distributor can assess the likelihood that the leaked data came from one or more agents,
as opposed to having been independently gathered by other means. In the proposed approach, we
develop a model for assessing the “guilt” of agents. We also present algorithms for distributing
objects to agents, in a way that improves our chances of identifying a leaker. Finally, we also
consider the option of adding “fake” objects to the distributed set. Such objects do not
correspond to real entities but appear realistic to the agents. In a sense, the fake objects act as a
type of watermark for the entire set, without modifying any individual members. If it turns out
that an agent was given one or more fake objects that were leaked, then the distributor can be
more confident that agent was guilty. In the Proposed System the hackers can be traced with
good amount of evidence.
Sl.no Input Expected Output Actual Output Status

A page with A page with

01 Welcome Page distributor login distributor login and Pass
and agent login agent login

Login page with Login Page with user

02 Distributor Login user name and name password Pass
password arrives arrives

The 4 sub models The 4 sub models of

03 Distributor Function Pass
of distributor login distributor login

A sign up page
A sign up page where
where the user has
04 Sign up new agents the user has to enter Pass
to enter personal
personal details
details

A page with a set A page with a set of

Distribute data via
of hosts arrive and hosts arrive and can
05 the distributor to Pass
can send data to send data to various
agents
various agents agents

Before sending
Before sending data
data from the
from the distributor
06 Distributor Server distributor this Pass
this server has to be
server has to be
turned on
turned on

A page with A page with

Return to Welcome
07 distributor login distributor login and Pass
Page
and agent login agent login

A page where the A page where the

08 Login as Agent agent enters the agent enters the Pass
agent details agent details

09 Agent Leaking A page where A page where Pass

 data to different agent can leak agent can leak
agents data arrives data arrives
10 A page with A page with
Return to
distributor login distributor login Pass
Welcome Page
and agent login and agent login
11 Login page with Login page with
Distributor Login user name and user name and Pass
password arrives password arrives
12 Find Guilty A Page for finding A Page for finding
Agents guilty agents guilty agents Pass
arrive arrive
13 Find probability Find the guilty Find the guilty
Pass
of guilty agent agent agent
14 Show the Graph shown Graph shown
Pass
probability graph