22-03-2014, 04:24 PM
Protection of Data Base Security via Collaborative Inference Detection
![Microsoft Word 2007 Document .docx](https://seminarproject.net/images/attachtypes/doc.gif)
Abstract
In many applications like Defense department, Commercial departments and Marketing departments we need a strongly secured database. Database securities are needed in order to protect our identity and authentication process of users. We propose a novel security mechanism to overcome inference problems and risks for securing the database. Our approach is used for the violation inference detection for single users and multi users. An agent is located between the user input query and the database. Our approach can be used for both the single user as well as the multiple users. This process achieves high authorization, communication accuracy and trust in communication and preventing data from leakage by inference. Here Work is focused on employee information access. Probability of each employee goes on increasing on each query request. When a user poses a query, detection system will examine users past query log for last three days and calculates probability. If probability exceeds than the specified threshold, the query will be denied for that day. Also, to monitor activities, security officer can generate log.
Index Terms: knowledge processing; database; inference; probability; protection; security; query;
INTRODUCTION
The restrictions for protecting a database system are generally stated in terms of database views, which can be used by a user to access a relation which he is not authorized to directly access. However, with information flow and inference, a user may acquire additional, unauthorized information, which may be the exact values of attribute or the relationship of attributes. Two inference techniques can be used to derive additional information: (1) analyzing functional dependencies between attributes within a relation or across relations, (2) merging views with the same constraints. On the other hand, information flows are caused by invoking a sequence of queries to indirectly read/write the sensitive data of a relation. Our approach is used to defend users from accessing the secured data from the data source or data centers. But the former techniques are not fulfilled because intruders can acquire the inoffensive information and apply inference techniques to execute sensitive information by the data. We construct a novel technique as inference detection system which is used to identify the inference problem and inference risks. Our approach monitors the trespassers from the database. When a new query is posted, we can compare the query with the query history. Query will be unresponsed if the probability of the query exceeds the threshold of the sensitive information. This actuates us to lead our inquiry from a singleuser case to a multiple-user case, where users may cooperate to each other to collectively deduce conscious data. We have carried a set of researches by using our inference trespass detector as a testbed to understand the characteristics in coactions and the effect on collaborative inference. Thus, coactions inference for a specific task can be derived by tracking the query history of all the users together with their collaboration levels (CLs).
WORK DONE
In analyzing different inference in the database system, researchers have expanded their an inference project on eliminating the issue with varies techniques and persuaders. In recent years, researchers have found a method that prevents inference within databases from recurring in the system. By locating inference channel and preventing any occurrence of these types of problems happening in the system. Some have used semantic data modeling to detect the inference channel. It looks into database design and redesigns it to make sure that this type of inference does not occur in the system. The other technique evaluates the database system, which read, update or both by using database transaction to determine if inference has occurred. The technique will either disable the query or reclassify the query in higher level, only if it discovers an illegal inference. Several techniques have been addressed for the inference problems in the database Rule-based inference schemes were employed in this paradigm to defend the protection, since data modify can regard data inference, a performance that spreads modify to the user history files to assure that no question is refused based on the noncurrent entropy.
INFERENCE INFRACTION DISCOVERY FOR SINGLE USER
IVDS provide an integrated view of the relationships among data attributes, which can be used to detect inference violation for sensitive nodes. In such a graph, the values of the attributes are set according to the answers of the previous posted queries. Based on the list of queries and the user who posted those queries, the value of the inference will be modified accordingly. If the current query answer can infer the sensitive information greater than the pre specified threshold, then the request for accessing the query answer will be denied. The notion of imbedding policies into the database itself and altering these policies to closure every try to determine the land of the database, or to vary its shape in a way that opposes what has been accomplished and fed into the policy by the system owner. These policies can be accomplished at different graininess levels in such a way that the system owner can choose to raise coarse-grained policies to supervise and control the behavior of the database as a whole through the use of global settings, or invoke fine-grained policies that affect specific aspects or configuration settings. But the absolute core principle of our framework is the notion that the security policies, as well as all the database objects and logic that enforces them, are made an integral and inseparable part of the database that they are meant to protect.
INFERENCE INFRACTION DISCOVERY FOR MULTI USER
Generalizing from the single-user collaborative system to the multiuser collaborative system greatly increases the complexity and presents two challenges for building the inference detection system. First, we need to estimate the effectiveness of collaboration among users, which involves such factors as the authoritativeness of the collaborators, the communication mode among collaborators, and the honesty of the collaboration. In addition, we need to properly integrate the knowledge from collaborators on the inference channels for the inference probability computation. Database administrators or power users can alter security configurations in a way that could result in unauthorized access to and compromise of the database. An example would be that of granting privileged access to unprivileged users, or just simply misusing his privileged access. Another example is one that pertains to security scans or audits of the database. Independent auditors are usually hired to perform a security scan of the database and they work with the DBA to get the database to a point where it is hardened enough to pass the scan. However, a database administrator can temporarily (or permanently) set some or all of the configuration parameters back to their original settings in order to achieve certain goals that he thinks are justified. The DBA can easily set that parameter to unlimited, change the password to the same one, and then set that parameter back to what it is supposed to be. By doing so, the DBA would have violated the rule that applies to reusing the same password over and over again. In this paper we describe a policy based approach for enforcing database configurations even to those who have privileged access. We do not advocate minimizing the role of the DBA or restricting his access. However, we do advocate that each action gets verified and approved by system owner embedded, predefined configuration policies before it is applied to the database. Unlike database security frameworks that exist today, which mostly detect imminent problems, generate an alert, and produce a report, our solution, which is an inseparable component of the database that it is meant to protect, mitigates any detected risk on its own without having to wait for human intervention.
COLLABRATION EFFECTIVNESS
We shall define CL as a metric for measuring the percentage of useful information flow from the information source to the recipient. The range of CL is from 0 to 1. CL = 0 and CL = 1 mean that none or all of the information is received by the recipient. By a series of experimental studies, we find that the CL depends on three components: the authoritativeness of the information provider A, the honesty of the collaboration H, and the fidelity of the communication channel between the provider and recipient F. The authoritativeness of the information provider represents how accurate the information is. If a provider is knowledgeable and has high reputation in the field related with the task, then he/she can provide more accurate information. Honesty represents the honesty level of the provider and his/her willingness of releasing his/her knowledge to the recipient. For example, if user A is very knowledgeable, and A and B have a good communication channel, then both the authoritativeness and fidelity of user A are high. However, A is not willing to release his full knowledge to B. As a result, the useful information cannot reach B for inference. Further, A can deceive B with false information. Thus, we shall use the honesty measure as an indication of the honesty in collaboration.