Information Leak Detection and Prevention System
In today’s regulated business environment, the loss of data records carries heavy penalties which can be expressed in terms of lost time, money, customer relations and ultimately lost profits. It may be obvious that a data security product should increase data protection and not decrease it; therefore it is important to detect the information leakage and more important to prevent it. A comprehensive information leak protection system is as vital for anyone to who needs to prevent the data from unauthorized persons.
PROJECT OUTPUT VIDEO:
- 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.
DISADVANTAGES OF EXISTING SYSTEMS:
- 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. g. A hospital may give patient records to researchers who will devise new treatments.
- There is no proper existing system to detect the information leaking in secured manner.
- 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.
- 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.
- Login / Registration
- Data Distributor:
- Data Allocation Module:
- Fake Object Module:
- Data Leakage protection Module:
- Finding Guilty Agents Module:
- Mobile Alert:
1. Login / Registration
This is a module mainly designed to provide the authority to a user/agent in order to access the other modules of the project. Here a user/agent can have the accessibility authority after the registration.
A data Distributor part is developed in this module. 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 somebody’s 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.
3.Data Allocation Module:
The main focus of our project is the data allocation problem as how can the distributor “intelligently” give data to agents in order to improve the chances of detecting a guilty agent.
4.Fake Object Module:
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.
5.Data Leakage protection Module:
In this module, to protect the data leakage, a secret key is sent to the agent who requests for the files. The secret key is sent through the email id of the registered agents. Without the secret key the agent cannot access the file sent by the distributor.
6. Finding Guilty Agents Module:
The Optimization Module is the distributor’s data allocation to agents has one constraint and one objective. The distributor’s constraint is to satisfy agents’ 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. This module is designed using the agent – guilt model. Here a count value (also called as fake objects) are incremented for any transfer of data occurrence when agent transfers data. Fake objects are stored in database.
In this module, an alert is sent to the distributor mobile, regarding the guilty agents who leaked the files. It is developed using NOKIA SDK 5100. Its only manual process, not an automatic triggered process.
- System : Pentium IV 2.4 GHz
- Hard Disk : 40 GB
- Floppy Drive : 44 MB
- Monitor : 15 VGA colour
- Mouse : Logitech
- Keyboard : 110 keys enhanced.
- RAM : 256 MB
- O/S : Windows XP.
- Front End : Net, C#, Nokia SDK 5100.
- Data Base : SQL Server 2005.
- Browser : IE / Firefox with Internet connection