HIDING SENSITIVE DATA USING

ASSOCIATION RULE WITH

LIMITED SIDE EFFECTS

SUBMITTED BY,
JISHA JOSE(26)
MERLIN SEBASTIAN(34)
RENI ELIZABETH REJI(43)
RINTU MARY THOMAS(44)
GROUP NO :10
ABSTRACT

Data mining techniques have been widely used in various applications.

However, the misuse of these techniques may lead to the disclosure of sensitive
information. Researchers have recently made efforts at hiding sensitive association
rules. Nevertheless, undesired side effects, e.g., non sensitive rules falsely hidden and
spurious rules falsely generated, may be produced in the rule hiding process. In this
paper, we present a novel approach that strategically modifies a few transactions in
the transaction database to decrease the supports or confidences of sensitive rules
without producing the side effects. Since the correlation among rules can make it
impossible to achieve this goal, in this paper, we propose heuristic methods for
increasing the number of hidden sensitive rules and reducing the number of modified
entries. The experimental results show the effectiveness of our approach, i.e.,
undesired side effects are avoided in the rule hiding process. The results also report
that in most cases, all the sensitive rules are hidden without spurious rules falsely
generated. Moreover, the good scalability of our approach in terms of database size
and the influence of the correlation among rules on rule hiding are observed.
INTRODUCTION

2.1 ABOUT HIDING SENSITIVE:

Large repositories of data contain sensitive information which must be

protected against unauthorized access. Here, we are going to hide sensitive
information in large database in order to reduce modifications in database and reduce
unwanted side effects. e.g., no sensitive rules falsely hidden and spurious rules falsely
generated may be produced in the rule hiding process. Here, we investigate
confidentiality issues of a broad category of rules, which are called association rules.
If the disclosure risks of some of these rules are above a certain privacy threshold,
those rules must be characterized as sensitive. Sometimes, sensitive rules should not
be disclosed to the public since, among other things, they may be used for inferencing
sensitive data, or they may provide business competitors with an advantage.

2.2 BENEFITS OF HIDING SENSITIVE:

The experimental results show that the undesired side effects are avoided by
using our approach. The results also report that in most cases, all the sensitive rules
are hidden without generating false rules. Moreover, the good scalability of our
approach in terms of database size and the influence of the correlation among rules on
rule hiding are observed.
LITERATURE SURVEY

3.1 EXISTING SYSTEM:

Although a business might use a set of programs that it knows and trusts, and
might train its administrators and Help Desk personnel to support those programs,
administrators lose control as soon as users begin running unknown code. The
increasing role of the Internet in business puts your network at a greater risk than ever
before.

Such user-installed programs can conflict with other installed programs,

change critical configuration data, or introduce a virus. Users often cannot make safe
or informed choices about what software to run because viruses intentionally conceal
the malicious purpose of the program. Also, the problems that are associated with
running unknown code can increase support costs substantially because they lead to
more system maintenance, more help desk time, and lost user productivity

3.2 LIMITATIONS:

All the items in a sensitive rule do not appear in any other sensitive rule. With
this assumption, hiding a sensitive rule will not affect any other sensitive rule and,
therefore, hiding them one at a time or all together will not make any difference.
Thus, their algorithms hide one rule at a time and decrease the supports or
confidences one unit at a time. Since this work aims at hiding all sensitive rules, it
cannot avoid the undesired side effects.
PROPOSED SYSTEM

Sensitive rules are the major advantage of the proposed system. We can
get the copy of the database without affecting the original database. For this purpose
we are using the sensitive rules. For example, in one organization a salesman always
giving the good production means remaining staff those who want to get a good profit
can use his database from him. If some one made any changes in that original
database means we cannot retrieve the original data again.
Because of that purpose we are building the project to get the copy of database
using the sensitive rules. It does not affect the original database forever. It provides
restricting access to sensitive data and Security to End user.
We remove the assumption and allow the user to select sensitive rules from all
strong rules such as Minimum support threshold (MST) and Minimum Confidence
Threshold (MCT).

REQUIREMENT SPECIFICATION

5.1 HARDWARE SPECIFICATION:

Hardware:
 Pentium IV Processor
 256MB RAM
 40GB Hard disk

5.2 SOFTWARE SPECIFICATION:

Operating System : Win 2000 and above versions

Jdk Kit : Jdk 1.5
Web Server : Apache Tomcat Server
Database : MS-SQL Server
Web Technologies : JSP
PRELIMINARY DESIGN METHODOLOGY

1. Problem Formulation

2. Modification Schemes for Rule Hiding

3. System Framework

4. Properties for Rule Hiding

FEATURES

• Analysis the performance of proposed system heuristic methods for increasing

the number of hidden sensitive rules and reducing the number of modified
entries. The project results show the effectiveness of our approach, i.e.,
undesired side effects is avoided in the rule hiding process.

• The project results also report that in most cases, all the sensitive rules are
hidden without spurious rules falsely generated. Moreover, the good
scalability of our approach in terms of database size and the influence of the
correlation among rules on rule hiding are observed.

• This project contains following major modules to fulfill the need for

finding the association of data using Market – Basket Analysis:

1. Administrator Module

2. Retail Outlet Module

3. Analyzer Module

CONCLUSION
 In this paper, we present a novel approach that modifies the database to
hide sensitive rules with limited side effects. We propose to classify all the valid
modifications such that every class of modifications is related with the sensitive rules,
non-sensitive rules, and spurious rules that can be affected after the modifications.
With the methods proposed in this paper, we can modify the transactions in an order
so that both the numbers of hidden sensitive rules and modified entries are considered.
The experimental results show that our approach is scalable in terms of database size.
Moreover, our approach to the avoidance of undesired side effects in rule hiding is
effective in two well-designed experiments. In most cases, all the sensitive rules are
hidden without false rules generated. In addition, it is observed that the common items
and the overlapping degrees among sensitive rules have a great impact on the
performance of rule hiding.