I. Introduction
From small companies to major institutions and everything in between, databases are being implemented everywhere. To the ethical person, this might not mean much. However, to some other people, this might mean having more targets to choose from for their next attacks. Some attacks may leave little or no damages. However, in safety and life-critical systems a database attack damage can range from a loss of a huge amount of money to a loss of life. For example, a malicious transaction on a hospital’s database can change someone’s blood type, which can directly result in death [1]. That is an example of how a single transaction can cause death, a malicious attack can spread into the entire database. Another example would be a German serial killer named "Niles Hogel", who killed around 300 patients [2] by giving them different medication that weren’t authorized. This serial killer could be a nurse with good intentions applying a prescription that has been tampered with by some malicious transactions. Employees tend to trust data provided by their computers, and in many cases it is very hard to verify some information as they are private (for example: a client’s IBAN for money transfers, someone’s address, etc) and having to check with the client every time is inconvenient for both sides and can be tampered with (example: a hacker changes the client contact information to his). In almost all cases, people trust the information on the screen and hope they are the correct ones. The only way to decrease an incident happening is by keeping the data in a consistent state. This justifies the need for database security which is an even larger concern in the era of information warfare. Manipulating the victim’s trusted information without them realizing it or simply, an attack to cause a denial of service [3] of the information system could always happen.