Database Security Issues
Database Security Issues
An Introduction
Outline
Introduction to Database Security Issues
• Types of Security
• Threats to databases
• Database Security and DBA
• Access Protection, User Accounts, and Database Audits
Discretionary Access Control
• Types of Discretionary Privileges
• Specifying Privileges Using Views
• Revoking Privileges
• Propagation of Privileges Using the GRANT OPTION
• An example
• Weakness
Mandatory Access Control
• Bell-LaPudula Model
• Comparing DAC and MAC
RBAC (Role-Based Access Control)
Encryption & PKI (Public Key Infrastructure)
2
Introduction to Database Security Issues
Types of Security
• Legal and ethical issues
• Policy issues
• System-related issues
• The need to identify multiple security levels
3
Three Basic Concepts
Authentication: a mechanism that determines
whether a user is who he or she claims to be
Authorization: the granting of a right or privilege,
which enables a subject to legitimately have access
to a system or a system’s objects
Access Control: a security mechanism (of a DBMS)
for restricting access to a system’s objects (the
database) as a whole
4
4
Introduction to Database Security Issue(2)
Threats
• Any situation or event, whether intentional or
unintentional, that will adversely affect a system and
consequently an organization
• Threats to:
→Computer systems
→Databases
5
Threats to Computer Systems
6
Scope of Data Security Needs
7
Introduction to Database Security Issues (3)
Threats to databases
• Loss of integrity
• Loss of availability
• Loss of confidentiality
8
Introduction to Database Security Issues (4)
9
Introduction to Database Security Issues 5)
10
Introduction to Database Security Issues (6)
11
Introduction to Database Security Issues (7)
12
Introduction to Database Security Issues (8)
13
Database Security and the DBA
14
Database Security and the DBA (2)
The DBA has a DBA account in the DBMS
• Sometimes these are called a system or superuser account
• These accounts provide powerful capabilities such as:
→1. Account creation
→2. Privilege granting
→3. Privilege revocation
→4. Security level assignment
• Action 1 is access control, whereas 2 and 3 are discretionarym
and 4 is used to control mandatory authorization
15
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 id and
password for the user if he/she deems there is a
legitimate need to access the database
The user must log in to the DBMS by entering
account id and password whenever database
access is needed.
16
Access Protection, User Accounts, and
Database Audits(2)
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.
17
Access Protection, User Accounts, and
Database Audits(3)
If any tampering with the database is suspected, a
database audit is performed
• A database audit 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.
18
Outline
Introduction to Database Security Issues
• Types of Security
• Threats to databases
• Database Security and DBA
• Access Protection, User Accounts, and Database Audits
Discretionary Access Control
• Types of Discretionary Privileges
• Specifying Privileges Using Views
• Revoking Privileges
• Propagation of Privileges Using the GRANT OPTION
• An example
• Weakness
Mandatory Access Control
• Bell-LaPudula Model
• Comparing DAC and MAC
RBAC (Role-Based Access Control)
Encryption & PKI (Public Key Infrastructure)
19
Discretionary Access Control
20
Types of Discretionary Privileges
21
Types of Discretionary Privileges(2)
The privileges at the account level apply to the capabilities
provided to the account itself and can include
• the CREATE SCHEMA or CREATE TABLE privilege, to create
a schema or base relation;
• the CREATE VIEW privilege;
• the ALTER privilege, to apply schema changes such adding or
removing attributes from relations;
• the DROP privilege, to delete relations or views;
• the MODIFY privilege, to insert, delete, or update tuples;
• and the SELECT privilege, to retrieve information from the
database by using a SELECT query.
22
Types of Discretionary Privileges(3)
The second level of privileges applies to the relation level
• This includes base relations and virtual (view) relations.
The granting and revoking of privileges generally follow an
authorization model for discretionary privileges known as the
access matrix model where
• The rows of a matrix M represents subjects (users, accounts,
programs)
• 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.
23
Types of Discretionary Privileges(4)
To control the granting and revoking of relation privileges,
each relation R in a database is assigned and 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.
• In SQL2, the DBA can assign and owner to a whole schema by
creating the schema and associating the appropriate
authorization identifier with that schema, using the CREATE
SCHEMA command.
• The owner account holder can pass privileges on any of the
owned relation to other users by granting privileges to their
accounts.
24
Types of Discretionary Privileges(5)
In SQL the following types of privileges can be granted on
each individual relation R:
• SELECT (retrieval or read) privilege on R:
→Gives the account retrieval privilege.
→In SQL this gives the account the privilege to use the SELECT
statement to retrieve tuples from R.
• MODIFY privileges on R:
→This gives the account the capability to modify tuples of R.
→In SQL this privilege is further divided into UPDATE, DELETE,
and INSERT privileges to apply the corresponding SQL command
to R.
→In addition, both the INSERT and UPDATE privileges can specify
that only certain attributes can be updated by the account.
25
Types of Discretionary Privileges(6)
In SQL the following types of privileges can be
granted on each individual relation R (contd.):
• REFERENCES privilege on R:
→This gives the account the capability to reference relation R when
specifying integrity constraints.
→The privilege can also be restricted to specific attributes of R.
26
Specifying Privileges Using Views
The mechanism of views is an important discretionary
authorization mechanism in its own right. 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.
27
Revoking Privileges
28
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.
29
An Example
Suppose that the DBA creates four accounts
• A1, A2, A3, A4
and wants only A1 to be able to create base relations. Then
the DBA must issue the following GRANT command in SQL
GRANT CREATETAB TO A1;
In SQL2 the same effect can be accomplished by having the
DBA issue a CREATE SCHEMA command as follows:
CREATE SCHAMA EXAMPLE AUTHORIZATION A1;
30
An Example(2)
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;
31
An Example(3)
32
An Example(4)
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’t propagate the SELECT privilege because
GRANT OPTION was not given to A4
33
An Example(5)
34
An Example(6)
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;
35
An Example(7)
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;
36
DAC: Weakness
User X Program P
select * from f1;
commit;
…
Read f1
Write f2
Table f1 Table f2
Owner X Owner Y
(X, write, f2)
37
Outline
Introduction to Database Security Issues
• Types of Security
• Threats to databases
• Database Security and DBA
• Access Protection, User Accounts, and Database Audits
Discretionary Access Control
• Types of Discretionary Privileges
• Specifying Privileges Using Views
• Revoking Privileges
• Propagation of Privileges Using the GRANT OPTION
• An example
• Weakness
Mandatory Access Control
• Bell-LaPudula Model
• Comparing DAC and MAC
RBAC (Role-Based Access Control)
Encryption & PKI (Public Key Infrastructure)
38
Mandatory Access Control
39
Bell-LaPudula Model
41
Mandatory Access Control(3)
42
Mandatory Access Control(4)
43
Comparing DAC and MAC
44
Comparing DAC and MAC (2)
45
Outline
Introduction to Database Security Issues
• Types of Security
• Threats to databases
• Database Security and DBA
• Access Protection, User Accounts, and Database Audits
Discretionary Access Control
• Types of Discretionary Privileges
• Specifying Privileges Using Views
• Revoking Privileges
• Propagation of Privileges Using the GRANT OPTION
• An example
• Weakness
Mandatory Access Control
• Bell-LaPudula Model
• Comparing DAC and MAC
RBAC (Role-Based Access Control)
Encryption & PKI (Public Key Infrastructure)
46
Role-Based Access Control
Role-based access control (RBAC) emerged rapidly in the
1990s as a proven technology for managing and enforcing
security in large-scale enterprisewide systems.
Its basic notion is that permissions are associated with roles,
and users are assigned to appropriate roles.
Roles can be created using the CREATE ROLE and
DESTROY ROLE commands.
• The GRANT and REVOKE commands discussed under DAC
can then be used to assign and revoke privileges from roles.
47
Outline
Introduction to Database Security Issues
• Types of Security
• Threats to databases
• Database Security and DBA
• Access Protection, User Accounts, and Database Audits
Discretionary Access Control
• Types of Discretionary Privileges
• Specifying Privileges Using Views
• Revoking Privileges
• Propagation of Privileges Using the GRANT OPTION
• An example
• Weakness
Mandatory Access Control
• Bell-LaPudula Model
• Comparing DAC and MAC
RBAC (Role-Based Access Control)
Encryption & PKI (Public Key Infrastructure)
48
Encryption
49
Encryption
Encryption key: public key
Decryption key: private key
Asymmetric techniques: more secure but expensive in terms of
computational costs
Encrypted message
using a symmetric key
50
Encryption & PKI (Public Key Infrastructure)
Certificate Authority
(CA)
51
Summary
Introduction to Database Security Issues
• Types of Security
• Threats to databases
• Database Security and DBA
• Access Protection, User Accounts, and Database Audits
Discretionary Access Control
• Types of Discretionary Privileges
• Specifying Privileges Using Views
• Revoking Privileges
• Propagation of Privileges Using the GRANT OPTION
• An example
• Weakness
Mandatory Access Control
• Bell-LaPudula Model
• Comparing DAC and MAC
RBAC (Role-Based Access Control)
Encryption & PKI (Public Key Infrastructure)
52
Q&A
53