DAY 8 (Database Security and Authorization

Database Security
and
Authorization
Mr. Sumit Gupta
Department of Computer Science and Engineering
University Institute of Technology
The University of Burdwan
Database Security Issues
• Goal:
• Protecting the database against persons who are not authorized to
access either certain parts of a database or the whole database.
• Types of security
• Legal and ethical issues
• Some information may be private and cannot be accessed by unauthorized
person.
• Policy issues
• What kind of information should not be made publicly available (from the
govt. or institutional point of view).
• System-related issues
• Security functions should be handled at: physical h/w level; OS level or DBMS
level.
• Multilevel security & categorization of data and users
11/30/2022 Sumit Gupta @ UIT, BU 2

A DBMS typically includes a database security and

authorization subsystem that is responsible for ensuring the
security portions of a database against unauthorized access.
Two types of database security mechanisms:
• Discretionary security mechanisms

• Grants privileges to users, including the capability to access specific dat files,
records or fields etc. with specific mode like, read, insert, update, etc.
• Mandatory security mechanisms
• This mechanism is used to ensure the multilevel security by classifying the
data and users.

• The security mechanism of a DBMS must include provisions

for restricting access to the database as a whole; this
function is called access control and is handled by creating
user accounts and passwords to control login process by the
DBMS.
• Another aspect of the security
• sensitive information such as employee salaries should
be kept confidential from most of the users.

• Another security is that of flow control, which prevents
information from flowing in such a way that it reaches
unauthorized users.
• A final security issue is data encryption, which is used to
protect sensitive data (such as credit card numbers) that is
being transmitted via some type communication network.
• The data is encoded using some coding algorithm. An
unauthorized user who access encoded data will have
difficulty deciphering it, but authorized users are given
decoding or decrypting algorithms (or keys) to decipher
data.

Database Security and the DBA
The database administrator (DBA) is the central authority for

managing a database system. The DBA’s responsibilities
include granting privileges to users who need to use the
system and classifying users and data in accordance with the
policy of the organization. The DBA has a DBA account in the
DBMS, sometimes called a system or superuser account,
which provides powerful capabilities :

Database Security and the DBA
1. Account creation
2. Privilege granting
3. Privilege revocation
4. Security level assignment
The DBA is responsible for the overall security of the database

system.
Action 1 is access control, whereas 2 and 3 are discretionary
and 4 is used to control mandatory authorization.

Access Protection, User Accounts, and
Database Audits
Whenever a person or group of person s need to access a
database system, the individual or group must first apply for
a user account. The DBA will then create a new account
number and password for the user if there is a legitimate
need to access the database.
The user must log in to the DBMS by entering account

number and password whenever database access is needed.

Access Protection, User Accounts, and
Database Audits
The database system must also keep track of all operations on the
database that are applied by a certain user throughout each login
session.
To keep a record of all updates applied to the database and of the

particular user who applied each update, we can modify system log,
which includes an entry for each operation applied to the database that
may be required for recovery from a transaction failure or system crash.
If any tampering with the database is suspected, a database audit is
performed, which consists of reviewing the log to examine all accesses
and operations applied to the database during a certain time period.
A database log that is used mainly for security purposes is sometimes
called an audit trail.

Discretionary Access Control
The typical method of enforcing discretionary access control
in a database system is based on the granting and revoking
privileges.

Types of Discretionary Privileges
• The account level: the DBA specifies the particular privileges that each
account holds independently of the relations in the database.
• The relation (or table level): the DBA can control the privilege to access each
individual relation or view in the database.
• The privileges at the account level
• CREATE SCHEMA or CREATE TABLE privilege to create a schema or base
relation
• CREATE VIEW privilege; the ALTER privilege, to apply schema changes
such adding or removing attributes from relations
• DROP privilege, to delete relations or views
• MODIFY privilege, to insert, delete, or update tuples
• SELECT privilege, to retrieve information from the database by using a
SELECT query

The privileges at the relation level

applied on the base relations or virtual (view) relations.
The granting and revoking of privileges can be represented by

the access matrix (M)
where the rows of matrix M represents subjects (users,
accounts, programs), and
the columns represent objects (relations, records, columns,
views, operations).
Each position M(i,j) in the matrix represents the types of
privileges (read, write, update) that subject i holds on object j.
• To control the granting and revoking of relation privileges,

each relation R in a database is assigned an owner
account, which is typically the account that was used
when the relation was created in the first place.
• The owner of a relation is given all privileges on that
relation.
• The owner account holder can pass privileges on any of
the owned relation to other users by granting privileges.

Propagation of Privileges using the
GRANT OPTION
• Whenever the owner A of a relation R grants a privilege on R
to another account B, privilege can be given to B with or
without the GRANT OPTION.
• If the GRANT OPTION is given, this means that B can also
grant that privilege on R to other accounts.
• Suppose that B is given the GRANT OPTION by A and that B
then grants the privilege on R to a third account C, also with
GRANT OPTION.
• In this way, privileges on R can propagate to other accounts
without the knowledge of the owner of R.
• If the owner account A now revokes the privilege granted to
B, all the privileges that B propagated based on that privilege
should automatically be revoked by the system.
Granting of Privileges
• The passage of authorization from one user to another may be
represented by an authorization graph.
• The nodes of this graph are the users.
• The root of the graph is the database administrator.
• Consider graph for update authorization on loan.
• An edge Ui  Uj indicates that user Ui has granted update
authorization on loan to Uj.

Authorization Grant Graph
• Requirement: All edges in an authorization graph must be part
of some path originating with the database administrator
• If DBA revokes grant from U1:
• Grant must be revoked from U4 since U1 no longer has
authorization
• Grant must not be revoked from U5 since U5 has another
authorization path from DBA through U2
• Must prevent cycles of grants with no path from the root:
• DBA grants authorization to U7
• U7 grants authorization to U8
• U8 grants authorization to U7
• DBA revokes authorization from U7
• Must revoke grant U7 to U8 and from U8 to U7 since there is no
path from DBA to U7 or to U8 anymore.
Security Specification in SQL
• The grant statement is used to confer authorization
grant <privilege list>
on <relation name or view name> to <user list>
• <user list> is:
• a user-id
• public, which allows all valid users the privilege granted
• A role (more on this later)
• Granting a privilege on a view does not imply granting any
privileges on the underlying relations.
• The grantor of the privilege must already hold the privilege on
the specified item (or be the database administrator).

Privileges in SQL
• select: allows read access to relation, or the ability to query
using the view
• Example: grant users U1, U2, and U3 select authorization on
the branch relation:
grant select on branch to U1, U2, U3
• insert: the ability to insert tuples
• update: the ability to update using the SQL update statement
• delete: the ability to delete tuples.
• references: ability to declare foreign keys when creating
relations.
• usage: In SQL-92; authorizes a user to use a specified domain
• all privileges: used as a short form for all the allowable
privileges

Privilege To Grant Privileges
• with grant option: allows a user who is

granted a privilege to pass the privilege on to
other users.
• Example:
grant select on branch to U1 with grant option
gives U1 the select privileges on branch and allows U1 to
grant this
privilege to others

Specifying Limits on Propagation of
Privileges
Techniques to limit the propagation of privileges have been
developed, although they have not yet been implemented
in most DBMSs and are not a part of SQL.
Limiting horizontal propagation to an integer number i

means that an account B given the GRANT OPTION can
grant the privilege to at most i other accounts.
Vertical propagation is more complicated; it limits the depth

of the granting of privileges.

Authorization on Views
• Creation of view does not require resources authorization

since no real relation is being created
• The creator of a view gets only those privileges that provide
no additional authorization beyond that he already had.
• e.g. if creator of view cust-loan had only read authorization
on borrower and loan, he gets only read authorization on
cust-loan

View Example
• Suppose a bank clerk needs to know the names of the
customers of each branch, but is not authorized to see specific
loan information.
• Approach: Deny direct access to the loan relation, but grant
access to the view cust-loan, which consists only of the
names of customers and the branches at which they have a
loan.
• The cust-loan view is defined in SQL as follows:
create view cust-loan as
select branchname, customer-name
from borrower, loan
where borrower.loan-number = loan.loan-number

View Example (Cont.)
• The clerk is authorized to see the result of the query:

select * from cust-loan
• When the query processor translates the result into a query on
the actual relations in the database, we obtain a query on
borrower and loan.
• Authorization must be checked on the clerk’s query before
processing the query.

Specifying Privileges Using Views
• Users can be given authorization on views, without being given
any authorization on the relations used in the view definition
• Ability of views to hide data serves both to simplify usage of
the system and to enhance security by allowing users access
only to data they need for their job
• A combination of relational-level security and view-level
security can be used to limit a user’s access to precisely the
data that user needs.
• For example, if the owner A of a relation R wants another account B to
be able to retrieve only some fields of R, then A can create a view V of R
that includes only those attributes and then grant SELECT on V to B.
• The same applies to limiting B to retrieving only certain tuples of R; a
view V’ can be created by defining the view by means of a query that
selects only those tuples from R that A wants to allow B to access.

Revoking Privileges
In some cases it is desirable to grant a privilege to a user

temporarily.
For example, the owner of a relation may want to grant the

SELECT privilege to a user for a specific task and then revoke
that privilege once the task is completed. Hence, a
mechanism for revoking privileges is needed. In SQL, a
REVOKE command is included for the purpose of canceling
privileges.

Revoking Authorization in SQL
• The revoke statement is used to revoke authorization.
revoke<privilege list>
on <relation name or view name> from <user list> [restrict|
cascade]
• Example:
revoke select on branch from U1, U2, U3 cascade
• Revocation of a privilege from a user may cause other users
also to lose that privilege; referred to as cascading of the
revoke.
• We can prevent cascading by specifying restrict:
revoke select on branch from U1, U2, U3 restrict
With restrict, the revoke command fails if cascading revokes
are required.

Revoking Authorization in SQL (Cont.)
• <privilege-list> may be all to revoke all privileges the
revokee may hold.
• If <revokee-list> includes public all users lose the privilege
except those granted it explicitly.
• If the same privilege was granted twice to the same user by
different grantees, the user may retain the privilege after
the revocation.
• All privileges that depend on the privilege being revoked are
also revoked.

Limitations of SQL Authorization
• SQL does not support authorization at a tuple level

• E.g. we cannot restrict students to see only (the tuples
storing) their own grades

An Example
Suppose that the DBA creates four accounts --A1, A2, A3, and A4-- and
wants only A1 to be able to create base relations; then the DBA must
issue the following GRANT command in SQL:
GRANT CREATE TAB TO A1;
In SQL 2 the same effect can be accomplished by having the DBA issue a
CREATE SCHEMA command as follows:
CREATE SCHEMA EXAMPLE AUTHORIZATION A1;

An Example
User account A1 can create tables under the schema called EXAMPLE.
Suppose that A1 creates the two base relations EMPLOYEE and

DEPARTMENT; A1 is then owner of these two relations and hence all the
relation privileges on each of them.
Suppose that A1 wants to grant A2 the privilege to insert and delete tuples
in both of these relations, but A1 does not want A2 to be able to
propagate these privileges to additional accounts:
GRANT INSERT, DELETE ON EMPLOYEE, DEPARTMENT TO A2;

An Example
Suppose that A1 wants to allow A3 to retrieve information from either of

the two tables and also to be able to propagate the SELECT privilege to
other accounts.
A1 can issue the command:
GRANT SELECT ON EMPLOYEE, DEPARTMENT TO A3 WITH GRANT OPTION;
A3 can grant the SELECT privilege on the EMPLOYEE relation to A4 by

issuing:
GRANT SELECT ON EMPLOYEE TO A4;
(Notice that A4 can not propagate the SELECT privilege because GRANT
OPTION was not given to A4.)

An Example
Suppose that A1 decides to revoke the SELECT privilege on the

EMPLOYEE relation from A3; A1 can issue:
REVOKE SELECT ON EMPLOYEE FROM A3;
(The DBMS must now automatically revoke the SELECT
privilege on EMPLOYEE from A4, too, because A3 granted
that privilege to A4 and A3 does not have the privilege any
more.)

An Example
Suppose that A1 wants to give back to A3 a limited capability to SELECT from the
EMPLOYEE relation and wants to allow A3 to be able to propagate the privilege.
The limitation is to retrieve only the NAME, BDATE, and ADDRESS attributes and
only for the tuples with DNO=5.
A1 then create the view:
CREATE VIEW A3EMPLOYEE AS
SELECT NAME, BDATE, ADDRESS
FROM EMPLOYEE
WHERE DNO = 5;
After the view is created, A1 can grant SELECT on the view A3EMPLOYEE
to A3 as follows:
GRANT SELECT ON A3EMPLOYEE TO A3 WITH GRANT OPTION;

An Example
Finally, suppose that A1 wants to allow A4 to update only the

SALARY attribute of EMPLOYEE;
A1 can issue:
GRANT UPDATE ON EMPLOYEE (SALARY) TO A4;
(The UPDATE or INSERT privilege can specify particular

attributes that may be updated or inserted in a relation.
Other privileges (SELECT, DELETE) are not attribute specific.)

Mandatory Access Control and Role-Based Access
Control for Multilevel Security
The discretionary access control techniques of granting and
revoking privileges on relations has traditionally been the main
security mechanism for relational database systems.
This is an all-or-nothing method: A user either has or does not have
a certain privilege.
In many applications, and additional security policy is needed that
classifies data and users based on security classes. This approach
as mandatory access control, would typically be combined with
the discretionary access control mechanisms.
Typical security classes are top secret (TS), secret (S), confidential
(C), and unclassified (U), where TS is the highest level and U the
lowest: TS ≥ S ≥ C ≥ U

Introduction to Statistical Database Security
• Statistical databases are used mainly to produce statistics on various

populations.
• A population is a set of tuples of a relation (table) that satisfy some selection
condition.
• Statistical queries involve applying statistical functions to a population of tuples.
• The database may contain confidential data on individuals, which should be
protected from user access.
• Users are permitted to retrieve statistical information on the populations, such
as averages, sums, counts, maximums, minimums, and standard deviations.
• Statistical database security techniques must prohibit the retrieval of individual
data.
• This can be achieved by prohibiting queries that retrieve attribute values and by
allowing only queries that involve statistical aggregate functions such as COUNT, SUM,
MIN, MAX, AVERAGE, and STANDARD DEVIATION.

Introduction to Statistical Database Security
• It is DBA’s responsibility to ensure confidentiality of information
about individuals, while still providing useful statistical
summaries of data about those individuals to users.
• In some cases it is possible to infer the values of individual
tuples from a sequence statistical queries. This is particularly
true when the conditions result in a population consisting of a
small number of tuples.

Encryption and Public Key Infrastructures
• Encryption is a means of maintaining secure data in an

insecure environment.
• Encryption consists of applying an encryption algorithm to
data using some prespecified encryption key.
• the resulting data has to be decrypted using a decryption key to
recover the original data.

The Data and Advanced Encryption
Standards
• The Data Encryption Standard (DES) is a system developed
by the U.S. government for use by the general public. It has
been widely accepted as a cryptographic standard both in
the United States and abroad.
• DES can provide end-to-end encryption on the channel
between the sender A and receiver B.

Public Key Encryption
In 1976 Diffie and Hellman proposed a new kind of

cryptosystem, which they called public key encryption.
• Public key algorithms are based on mathematical functions

rather than operations on bit patterns.
• They also involve the use of two separate keys, in contrast to
conventional encryption, which uses only one key.
• The use of two keys can have profound consequences in the areas of
confidentiality, key distribution, and authentication.

• The two keys used for public key encryption are referred to
as the public key and the private key.
• the private key is kept secret, but it is referred to as private key rather
than a secret key (the key used in conventional encryption) to avoid
confusion with conventional encryption.

A public key encryption scheme, or infrastructure, has six ingredients:
1. Plaintext : This is the data or readable message that is fed into the
algorithm as input.
2. Encryption algorithm: The encryption algorithm performs various
transformations on the plaintext.
3. and
4. Public and private keys : These are pair of keys that have been selected
so that if one is used for encryption, the other is used for decryption.
The exec transformations performed by the encryption algorithm
depend on the public or private key that is provided as input.
5. Ciphertext : This is the scrambled message produced as output. It
depends on the plaintext and the key. For a given message, two
different keys will produce two different ciphertexts.
6. Decryption algorithm : This algorithm accepts the ciphertext and the
matching key and produces the original plaintext.

Public key is made for public and private key is known only by owner.
A general-purpose public key cryptographic algorithm relies on one key for
encryption and a different but related one for decryption. The
essential steps are as follows:
1. Each user generates a pair of keys to be used for the encryption and
decryption of messages.
2. Each user places one of the two keys in a public register or other
accessible file. This is the public key. The companion key is kept
private.
3. If a sender wishes to send a private message to a receiver, the sender
encrypts the message using the receiver’s public key.
4. When the receiver receives the message, he or she decrypts it using
the receiver’s private key. No other recipient can decrypt the message
because only the receiver knows his or her private key.
The RSA Public Key Encryption algorithm, one of the first public key schemes
was introduced in 1978 by Ron Rivest, Adi Shamir, and Len Adleman at
MIT and is named after them as the RSA scheme.
The RSA encryption algorithm incorporates results from number theory,
combined with the difficulty of determining the prime factors of a
target.
The RSA algorithm also operates with modular arithmetic – mod n.

• Two keys, d and e, are used for decryption and encryption.

• An important property is that d and e can be interchanged.
• n is chosen as a large integer that is a product of two large distinct prime
numbers, a and b.
• The encryption key e is a randomly chosen number between 1 and n that is
relatively prime to (a-1) x (b-1).
• The plaintext block P is encrypted as Pe mod n.
• Because the exponentiation is performed mod n, factoring Pe to uncover the
encrypted plaintext is difficult.
• However, the decryption key d is carefully chosen so that (Pe)d mod
n = P.
• The decryption key d can be computed from the condition that dx
e= 1 mod ((a-1)x(b-1)).
• Thus, the legitimate receiver who knows d simply computes (Pe)d
mod n = P and recovers P without having to factor Pe .

Digital Signatures
A digital signature is an example of using encryption techniques to provide
authentication services in e-commerce applications.
• A digital signature is a means of associating a mark unique to an individual
with a body of text.
• The mark should be unforgettable, meaning that others should be able to check
that the signature does come from the originator.
• A digital signature consists of a string of symbols.
• Signature must be different for each use. This can be achieved by making each
digital signature a function of the message that it is signing, together with a time
stamp.
• Public key techniques are the means creating digital signatures.

DAY 8 (Database Security and Authorization

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DAY 8 (Database Security and Authorization

Uploaded by

Copyright:

Available Formats

Database Security

11/30/2022 Sumit Gupta @ UIT, BU 2

A DBMS typically includes a database security and

• Discretionary security mechanisms

11/30/2022 Sumit Gupta @ UIT, BU 3

• The security mechanism of a DBMS must include provisions

11/30/2022 Sumit Gupta @ UIT, BU 4

11/30/2022 Sumit Gupta @ UIT, BU 5

The database administrator (DBA) is the central authority for

11/30/2022 Sumit Gupta @ UIT, BU 6

The DBA is responsible for the overall security of the database

11/30/2022 Sumit Gupta @ UIT, BU 7

The user must log in to the DBMS by entering account

11/30/2022 Sumit Gupta @ UIT, BU 8

To keep a record of all updates applied to the database and of the

11/30/2022 Sumit Gupta @ UIT, BU 9

11/30/2022 Sumit Gupta @ UIT, BU 10

11/30/2022 Sumit Gupta @ UIT, BU 11

The privileges at the relation level

The granting and revoking of privileges can be represented by

• To control the granting and revoking of relation privileges,

11/30/2022 Sumit Gupta @ UIT, BU 13

11/30/2022 Sumit Gupta @ UIT, BU 15

11/30/2022 Sumit Gupta @ UIT, BU 17

11/30/2022 Sumit Gupta @ UIT, BU 18

• with grant option: allows a user who is

11/30/2022 Sumit Gupta @ UIT, BU 19

Limiting horizontal propagation to an integer number i

Vertical propagation is more complicated; it limits the depth

11/30/2022 Sumit Gupta @ UIT, BU 20

• Creation of view does not require resources authorization

11/30/2022 Sumit Gupta @ UIT, BU 21

11/30/2022 Sumit Gupta @ UIT, BU 22

• The clerk is authorized to see the result of the query:

11/30/2022 Sumit Gupta @ UIT, BU 23

11/30/2022 Sumit Gupta @ UIT, BU 24

In some cases it is desirable to grant a privilege to a user

For example, the owner of a relation may want to grant the

11/30/2022 Sumit Gupta @ UIT, BU 25

11/30/2022 Sumit Gupta @ UIT, BU 26

11/30/2022 Sumit Gupta @ UIT, BU 27

• SQL does not support authorization at a tuple level

11/30/2022 Sumit Gupta @ UIT, BU 28

GRANT CREATE TAB TO A1;

CREATE SCHEMA EXAMPLE AUTHORIZATION A1;

11/30/2022 Sumit Gupta @ UIT, BU 29

Suppose that A1 creates the two base relations EMPLOYEE and

GRANT INSERT, DELETE ON EMPLOYEE, DEPARTMENT TO A2;

11/30/2022 Sumit Gupta @ UIT, BU 30

Suppose that A1 wants to allow A3 to retrieve information from either of

GRANT SELECT ON EMPLOYEE, DEPARTMENT TO A3 WITH GRANT OPTION;

A3 can grant the SELECT privilege on the EMPLOYEE relation to A4 by

11/30/2022 Sumit Gupta @ UIT, BU 31

Suppose that A1 decides to revoke the SELECT privilege on the

11/30/2022 Sumit Gupta @ UIT, BU 32

11/30/2022 Sumit Gupta @ UIT, BU 33

Finally, suppose that A1 wants to allow A4 to update only the

GRANT UPDATE ON EMPLOYEE (SALARY) TO A4;

(The UPDATE or INSERT privilege can specify particular

11/30/2022 Sumit Gupta @ UIT, BU 34

11/30/2022 Sumit Gupta @ UIT, BU 35

• Statistical databases are used mainly to produce statistics on various

11/30/2022 Sumit Gupta @ UIT, BU 36