Professional Documents
Culture Documents
Database Security PDF
Database Security PDF
UNIT-1
UNIT 1 Page 1
Database Security IV CSE
UNIT I SYLLABUS
UNIT 1 Page 2
Database Security IV CSE
UNIT 1 OUTCOME
Students can explain the importance and fundamentals of the databases.
Students can discuss the issues in data security.
Students can describe the problems in database security
Students Can Analyze and design different security models.
Students can describe Distributed Databases
Students can design modles for distributed databases
DATABASE:
A Database is an Organized Collection of Integrated files.A company
database might include files of all past and current employees of all the
department.
DATABASE SECURITY:
Database Security contains policies and mechanisms to protect
the data and ensure that it is not accessed,altered or deleted without proper
authorization.Database security methods focus on preventing unauthorized
users from accessing the database because DBMS features that make the
database easy to access and manipulate ,also open doors to intruders,most
DBMS’s include security features that allow only authorized persons or
programs to access data and then restrict the types of processing that can
be accomplished once access is made.
IMPORTANCE OF DATA
Bank/Demat Accounts
Credit card,Salary,Income tax data
University Admissions,marks/grades.
Land records,Licenses
Medical Records
UNIT 1 Page 3
Database Security IV CSE
OBJECTIVES
UNIT 1 Page 4
Database Security IV CSE
It implements encryption,decryption,firewalls,antivirus
software,database backups,physical and logical security on the
database.
Threats:
People
Natural disasters
Malicious code
TechnologicalDisaster
UNIT 1 Page 5
Database Security IV CSE
1.People:
Example:Employees,Contractors,Consultants,Visitors,Hackers,Terrorists
2.Malicious Code:
Software code that in most cases is intentionally written to damage or violate one or
more of the database environment components .
Example:Hurricanes,Tornados,Earthquakes,Flood,Fire
UNIT 1 Page 6
Database Security IV CSE
3.Integrity of Database:
UNIT 1 Page 7
Database Security IV CSE
UNIT 1 Page 8
Database Security IV CSE
OS security
DB security
The access matrix model is the policy for user authentication, and has
several implementations such as access control lists (ACLs) and
capabilities. It is used to describe which users have access to what objects.
The access matrix model consists of four major parts:
A list of objects
A list of subjects
A function T which returns an object's type
The matrix itself, with the objects making the columns and the subjects
making the rows In the cells where a subject and object meet lie the rights
the subject has on that object. Some example access rights are read, write,
execute, list and delete
EXAMPLE ACCESS MATRIX
Objects
index.html JavaVM
Subjects
file Virtual Machine
John Doe rwld x
Sally Doe rl -
UNIT 1 Page 9
Database Security IV CSE
• v. Removal of a subject
• The two most used implementations are access control lists and capabilities.
Access control lists are achieved by placing on each object a list of users and their
associated rights to that object. An interactive demonstration of access control lists
can be seen here. For example, if we have file1, file2 and file3, and users
(subjects) John and Sally, an access control list might look like:
Objects (Files)
Users File1 File2 File3
John RWX R-X RW-
Sally --- RWX R--
• The rights are R (Read), W (Write) and X (Execute). A dash indicates the user
does not have that particular right. Thus, John does not have permission to
execute File3, and Sally has no rights at all on File1.
• Capabilities are accomplished by storing on each subject a list of rights the
subject has for every object. This effectively gives each user a keyring. To remove
UNIT 1 Page 10
Database Security IV CSE
access to a particular object, every user (subject) that has access to it must be
"touched". A touch is an examanition of a user's rights to that object and potentially
removal of rights. This brings back the problem of sweeping changes in access
rights. Here is what an implementation of capabilities might look like, using the
above example:
Users
John file1:RWX file2:R-X file3:RW-
Sally file1:--- file2:RWX file3:R--
• Access restrictions such as access control lists and capabilities sometimes are
not enough. In some cases, information needs to be tightened further, sometimes
by an authority higher than the owner of the information. For example, the owner
of a top secret document in a government office might deem the information
available to many users, but his manager might know the information should be
restricted further than that. In this case, the flow of information needs to be
controlled -- secure information cannot flow to a less secure user.
TAKE-GRANT MODEL:
The take-grant protection model is a formal model used in the field of computer
security to establish the safety of a given computer system that follows specific
rules.
The model represents a system as directed graph, where vertices are either
subjects or objects.
The edges between them are labelled and the label indicates the rights that
the source of the edge has over the destination.
Two rights occur in every instance of the model: take and grant.
They play a special role in the graph rewriting rules describing admissible
changes of the graph.
Take rule allows a subject to take rights of another object (add an edge
originating at the subject)
UNIT 1 Page 11
Database Security IV CSE
Grant rule allows a subject to grant own rights to another object (add an
edge terminating at the subject)
Create rule allows a subject to create new objects (add a vertex and an
edge from the subject to the new vertex)
TAKE RULE
GRANT RULE
fig. 1.
(a) take rewriting rule. (b) grant rewriting rule.
Predicates on authorizations:
(conditions to be satisfied for access to be allowed)
Access modes:
Use: typical for application programs: this right means the program can be
executed.
Read/Update/Create/Delete: access/modify an entity, or add/remove entities
to/from the system.
Grant/Revoke: the privilege allows an entity Ei to grant (resp. revoke) a static
access mode m on an entity Ek to an entity Ej.
Delegate/Abrogate: this privilege allows an entity Ei to grant (resp. revoke) the
dynamic authorization grant related to access mode m on entity Ek to an entity
Ej.
UNIT 1 Page 13
Database Security IV CSE
Aij/k = a ~ {pij}
Entity Ei may grant Ej the right to grant others access right a on entity Ek if pij is
met.
Authorization state Sa of entity Ei: Sa(Ei) is the set of all authorizations Ei holds
on all the other system entities.
Classification of Entities:
UNIT 1 Page 14
Database Security IV CSE
The X READ
UNIT 1 Page 15
Database Security IV CSE
E6 Delegate update
{10,9}
E8 E7
Grant E6
read
PN MODEL
Synchronization
Sequentially
Concurrency
Conflict
UNIT 1 Page 16
Database Security IV CSE
P1
P
P2
T T
T
P3 P4
FIG:PETRINET
In the Diagram above the transition ‘T’ is fired only if the places P1 and P4 contain tokens.Upon
triggering of transition ,these tokens are removed and new tokens are placed on P2 and P3
UNIT 1 Page 17
Database Security IV CSE
UNIT 1 Page 18
Database Security IV CSE
FERNANDEZ’S MODEL
Fernandez proposed an authorization model for object oriented database ,which
consists of following elements.
Set of policies
The purpose of designing authorization model for object oriented databases ,is
the addition of semantic relationship ,due to which performing authorization
became a complex problem.
Security Policies:
UNIT 1 Page 20
Database Security IV CSE
UNIT 1 Page 21
Database Security IV CSE
1.What is Database?
2.Define DataBase Security .
3.What is the need for DataBase Security .
4.List types of Threats in DataBase Security .
5.List the elements in PN model
6.List the elements in Hartson and Hasiao’s model. 7.List the elements in
Fernandez’s model.
8.What is Authorization Rule.
9.List the Components in Secure Distributed Process(SDP).
10.Write a short notes on Entity classification in Acten Model.
PRACTICE BITS
UNIT 1 Page 22
Database Security IV CSE
UNIT 1 Page 23