Database security

Database security concerns the use of a broad range of information security controls to protect databases against compromises of their confidentiality, integrity and availability. It involves various types or categories of controls, such as technical, procedural or administrative, and physical. 
Security risks to database systems include, for example:

<ul><li>Unauthorized or unintended activity or misuse by authorized database users, database administrators, or network/systems managers, or by unauthorized users or hackers (e.g. inappropriate access to sensitive data, metadata or functions within databases, or inappropriate changes to the database programs, structures or security configurations);</li>
<li>Malware infections causing incidents such as unauthorized access, leakage or disclosure of personal or proprietary data, deletion of or damage to the data or programs, interruption or denial of authorized access to the database, attacks on other systems and the unanticipated failure of database services;</li>
<li>Overloads, performance constraints and capacity issues resulting in the inability of authorized users to use databases as intended;</li>
<li>Physical damage to database servers caused by computer room fires or floods, overheating, lightning, accidental liquid spills, static discharge, electronic breakdowns/equipment failures and obsolescence;</li>
<li>Design flaws and programming bugs in databases and the associated programs and systems, creating various security vulnerabilities (e.g. unauthorized <a href="/facts/Privilege_escalation/STzSAaf5">privilege escalation</a>), data loss/corruption, performance degradation etc.;</li>
<li>Data corruption and/or loss caused by the entry of invalid data or commands, mistakes in database or system administration processes, sabotage/criminal damage etc.</li></ul>
<a href="/facts/Ross_J._Anderson/hIq4z659">Ross J. Anderson</a> has often said that by their nature large databases will never be free of abuse by breaches of security; if a large system is designed for ease of access it becomes insecure; if made watertight it becomes impossible to use. This is sometimes known as Anderson's Rule.
Many layers and types of information security control are appropriate to databases, including:

<ul><li><a href="/facts/Access_control/08zE5Pz8">Access control</a></li>
<li><a href="/facts/Database_audit/nW3mhnSv">Auditing</a></li>
<li><a href="/facts/Authentication/64y4S69b">Authentication</a></li>
<li><a href="/facts/Encryption/16q29Fdv">Encryption</a></li>
<li><a href="/facts/Data_integrity/g3XGbKIH">Integrity</a> controls</li>
<li><a href="/facts/Backups/ldV72CkU">Backups</a></li>
<li><a href="/facts/Application_security/L2DWzCfG">Application security</a></li></ul>

Databases have been largely secured against hackers through <a href="/facts/Network_security/09f8YxwD">network security</a> measures such as <a href="/facts/Firewall_(networking)/Et2RkJaU">firewalls</a>, and network-based <a href="/facts/Intrusion_detection/mAw24Fyo">intrusion detection</a> systems. While network security controls remain valuable in this regard, securing the database systems themselves, and the programs/functions and data within them, has arguably become more critical as networks are increasingly opened to wider access, in particular access from the Internet. Furthermore, system, program, function and data access controls, along with the associated user identification, authentication and rights management functions, have always been important to limit and in some cases log the activities of authorized users and administrators. In other words, these are complementary approaches to database security, working from both the outside-in and the inside-out as it were.
Many organizations develop their own "baseline" security standards and designs detailing basic security control measures for their database systems. These may reflect general information security requirements or obligations imposed by corporate information security policies and applicable laws and regulations (e.g. concerning privacy, financial management and reporting systems), along with generally accepted good database security practices (such as appropriate hardening of the underlying systems) and perhaps security recommendations from the relevant database system and software vendors. The security designs for specific database systems typically specify further security administration and management functions (such as administration and reporting of user access rights, log management and analysis, database replication/synchronization and backups) along with various business-driven information security controls within the database programs and functions (e.g. data entry validation and <a href="/facts/Audit_trail/s3nQzrF4">audit trails</a>). Furthermore, various security-related activities (manual controls) are normally incorporated into the procedures, guidelines etc. relating to the design, development, configuration, use, management and maintenance of databases.

Database security open-in-new

Database security