Chapter 9 Database Security
Chapter 9 Database Security
1. External level
• It is also called view level. The reason this level is called “view” is
because several users can view their desired data from this level
which is internally fetched from database with the help of
conceptual and internal level mapping.
• The user doesn’t need to know the database schema details such as
data structure, table definition etc. user is only concerned about data
which is what returned back to the view level after it has been
fetched from database (present at the internal level).
3. Internal level
• This level is also known as physical level. This level describes how
the data is actually stored in the storage devices. This level is also
responsible for allocating space to the data. This is the lowest level
of the architecture.
Categorization of data and users
• Primary methods that organizations use to protect against loss of availability are
fault tolerant systems, redundancies, and backups.
– Backups: Important data is backed up and can be restored if the original data
becomes corrupt.
Integrity loss:
Integrity loss occurs when unacceptable operations are performed upon
the database either accidentally or maliciously. This may happen while
creating, inserting, updating or deleting data. It results in corrupted data
leading to incorrect decisions.
• The more complex the database is, the greater the security
implemented in association with it should be.