Database Security
Database Security
Database Security
Outline
Security:
Database Security:
5
Why need of database security?
6
Concepts of Database Security
2. Integrity
3. Availability
7
SECRECY /
It is protecting the database from unauthorized users.
For examples,
An employee should be able to modify his or her own
information.
9
AVAILABILITY
Restrict the amount of the storage space given to each user in the database.
10
11
SECURITY
PROBLEM
S
Any circumstance or event with the potential to adversely12
impact an IS through unauthorized access, destruction,
disclosure, modification of data, and/or denial of service.
Non-fraudulent Threat
fraudulent Threat
13
1. Non-fraudulent Threat
Natural or accidental disasters.
Errors or bugs in hardware or software.
Human errors. Often this is due to the lack of expertise required to implement security
controls, enforce policies or conduct incident response processes
Excessive privileges. When workers are granted default database privileges that exceed the
requirements of their job functions, these privileges can be abused.
Unmanaged sensitive data. Many companies struggle to maintain an accurate inventory of
their databases and the critical data objects contained within them. “Forgotten databases
may contain sensitive information, and new databases can emerge without visibility to the
security team. Sensitive data in these databases will be exposed to threats if the required
controls and permissions are not implemented.
fraudulent Threat
Authorized users
Those who abuse their privileges and authority.
Hostile agents
Those improper users (outsider or insiders).
who attack the software and/or hardware system, or read or write
data in a database.
Fraudulent attacks……
The most common database threats include:
Legitimate privilege abuse. Users may abuse legitimate database privileges for unauthorized purposes.
Malware. A perennial threat, malware is used to steal sensitive data via legitimate users using infected devices.
Database injection attacks. The two major types of database injection attacks are SQL injections that target
traditional database systems and NoSQL injections that target “big data” platforms.
Fraudulent attacks…..
Storage media exposure. Backup storage media is often completely unprotected from attack. As a result, numerous
security breaches have involved the theft of database backup disks and tapes. Furthermore, failure to audit and
monitor the activities of administrators who have low-level access to sensitive information can put your data at risk.
Taking the appropriate measures to protect backup copies of sensitive data and monitor your most highly privileged
users is not only a data security best practice, but also mandated by many regulations.
Exploitation of vulnerable databases. It generally takes organizations months to patch databases, during which
time they remain vulnerable. Attackers know how to exploit unpatched databases or databases that still have default
accounts and configuration parameters.
DATABASE
PROTECTION 17
REQUIREMENTS
1. Protection from Improper Access
4. User Authentication
5. Multilevel Protection
6. Confinement
15
19
Authentication – passwords.
You do not need to create triggers or views to decrypt data. Data from
tables is decrypted for the database user.
Database users need not be aware of the fact that the data they are
accessing is stored in encrypted form. Data is transparently decrypted for
the database users and does not require any action on their part.
select: allows read access to relation, or the ability to query using the view
Example:
With grant option: grant select on
allows a user who is branch to U1 with
granted a privilege to grant option
gives U1 the select
pass the privilege on privileges on branch and
to other users. allows U1 to grant this
privilege to others