Enforcing Secure and Privacy-Preserving
Information Brokering in Distributed
Information
Sharing
ABSTRACT
To facilitate extensive
collaborations, today’s organizations raise increasing needs for information
sharing via on-demand information access. Information Brokering System (IBS)
atop a peer-to-peer overlay has been proposed to support information sharing
among loosely federated data sources. It consists of diverse data servers and
brokering components, which help client queries to locate the data servers.
However, many existing IBSs adopt server side access control deployment and
honest assumptions on brokers, and shed little attention on privacy of data and
metadata stored and exchanged within the IBS.
In this
article, we study the problem of privacy protection in information brokering
process. We first give a formal presentation of the threat models with a focus
on two attacks: attribute-correlation attack and inference attack. Then, we
propose a broker-coordinator overlay, aa well as two schemes, automaton
segmentation scheme and query segment encryption scheme, to share the secure
query routing function among a set of brokering servers. With comprehensive
analysis on privacy, endto- end performance, and scalability, we show that the
proposed system can integrate security enforcement and query routing while
preserving system-wide privacy with reasonable overhead.
EXISTING
SYSTEM:
The
existing system supposes Alice owns a k-anonymous database and needs to
determine whether her database, when inserted with a tuple owned by Bob, is
still k-anonymous. Also, suppose that access to the database is strictly
controlled, because data are used for certain experiments that need to be
maintained confidential. Clearly, allowing Alice to directly read the contents
of the tuple breaks the privacy of Bob; on the other hand, the confidentiality
of the database managed by Alice is violated once Bob has access to the
contents of the database. Thus, the problem is to check whether the database
inserted with the tuple is still k-anonymous, without letting Alice and Bob
know the contents of the tuple and the database respectively.
Disadvantage:
- The database with the tuple data does not be maintained confidentially.
- The existing systems another person to easily access database.
PROPOSED
SYSTEM:
In the current paper,
we present two efficient protocols, one of which also supports the private
update of a generalization-based anonymous database. We also provide security
proofs and experimental results for both protocols. So far no experimental
results had been reported concerning such type of protocols; our results show
that both protocols perform very efficiently.
Advantage:
- The anonymity of DB is not affected by inserting the records.
- We provide security proofs and experimental results for both protocols.
MODULES
1.
Co-Ordinator Module.
2.
Broker Module.
3. User
Module.
4. Admin
Module.
Co-Ordinator Module:
In this module, the co-coordinator performs the global service between
the two end users. Initially the Data Owner needs to submit the details of the
patient in the server.
Data Users needs to search the data which is stored in the servers and
they give request for the data and the co-Ordinator sends the key to the Data
users and the Data will be passed by the broker Way.
Broker Module:
In this module, the
broker performs the role who can act between the Co-coordinator and the data
Users. The request which are all submitted from the data user will be verified
and thus it will be passed to the co-coordinator.
The data will be passed
from the co-coordinator and thus it will be submitted to the End Users(Data
Users).
User Module:
In this module, the
Users are classified into two types they are, Data Users and Data Owner Depends
on the restriction the data will be passed to the Co-coordinator.
The co-coordinator pass the details
via broker and the data will be checked with the secret key and thus it will
display for the users.
Admin Module:
In this module, to arrange the database based
on the patient and doctor details and records. The admin needs to register and
register the Organization and Users Forms.
Hardware Requirements:
•
System : Pentium IV 2.4 GHz.
•
Hard Disk : 40 GB.
•
Floppy Drive : 1.44 Mb.
•
Monitor : 14’ Colour Monitor.
•
Mouse : Optical Mouse.
•
Ram : 512 Mb.
•
Keyboard : 101 Keyboard.
Software Requirements:
•
Operating system : Windows 7 Ultimate. (32-bit os)
•
Coding Language : ASP.Net with C#
•
Front End : VS 2010 Professional
•
Data Base : SQL Server 2008.
No comments:
Post a Comment