Database Security and Access Control
Uploaded by
elshaday desalegnDatabase Security and Access Control
Uploaded by
elshaday desalegnCommon questions
Powered by AIRole-based access control (RBAC) represents an improvement over discretionary access control (DAC) by aligning permissions with defined roles within an organization, ensuring that users have the minimum necessary access rights based on their function. This reduces the complexity involved in managing individual permissions and the security risks associated with users holding excessive rights due to multiple roles. While DAC involves subjects directly controlling object permissions, RBAC structures permissions hierarchically and is often seen as more scalable and easier to audit within large organizations .
The benefits of using views in the SQL security model include their flexibility in defining access control at a level appropriate to the application and their capability to enforce context and data-dependent policies. Views can help in reclassifying data easily. However, the drawbacks include the potential complexity of access checking, issues with ensuring the correctness and consistency of views, and the risk of security-relevant parts of the DBMS growing excessively large .
The SQL security model implements discretionary access control (DAC) by checking user identity during the login process and managing access to database objects based on privileges granted to specific users or to "Public". Users have control over the objects they own and can grant access to others, with privileges managed using GRANT and REVOKE operations. The challenges in managing these privileges within large organizations include difficulty in security administration due to each grant of privileges being either to an individual or to "Public", and the potential for individuals with multiple roles to have excessive privileges for certain roles .
Field checks ensure element integrity by allowing only acceptable values, thus maintaining the correctness or accuracy of data. Access controls limit updates to authorized users only, preventing unauthorized changes. Change logs maintain a history of modifications to data, which can be used to undo changes made in error, thereby preserving the integrity of specific database elements .
Views can enforce data-dependent security policies by presenting data tailored according to specific criteria, such as user roles or contextual parameters. For instance, views can ensure that managers only see data relevant to their department. However, the reliance on views can lead to complex access management due to the need for a wide variety of views, verification for policy compliance, and potential overlap or omissions in views which could compromise security. Additionally, maintaining and updating these views to align with evolving security policies can be cumbersome .
The inherent weakness of discretionary access control (DAC) is that it allows a subject to write to any other object that can be written by the subject, creating a vulnerability to Trojan horses. This means that a malicious program could copy information from one object to another, potentially breaching data security by making unauthorized disclosures or modifications .
Physical database integrity ensures the database's immunity to physical catastrophes, such as power failures or media failures, through measures like securing hardware, using uninterruptible power supplies (UPS), and performing regular backups. Logical database integrity refers to the database's ability to be accurately reconstructed to a stable state in case of errors, achieved through transaction logs and the ability to replay these logs to restore systems .
Security labels are critical in enforcing mandatory access control (MAC) in database systems. Each piece of data is assigned a security level through such labels, which are also assigned to users. The database management system (DBMS) enforces MAC by granting access to a database row based on the comparison of the user's security clearance with the label of the data row. This ensures that users cannot read data above their clearance level or write data to a lower security level, maintaining data integrity and security compliance .
Mandatory access control (MAC) differs from discretionary access control (DAC) in that MAC enforces rules that prohibit reading higher-tier data (no read up) and writing to lower tiers (no write down), assigned through security labels to both data and users. Traditional MAC implementations in relational database management systems (RDBMS) have focused on multilevel security (MLS). By contrast, DAC relies on user-specific permissions that can be transferred at the user's discretion, raising issues with Trojan horse vulnerabilities .
Application views provide row-level security using discretionary access control (DAC) by allowing specific views to be created, which filter data based on certain criteria (e.g., user roles). For example, a view might be defined to allow managers to see client records for their department only without being able to update them. However, the challenges include the large number of views required as applications evolve, the management burden of directing application users to correct views, and increasing application complexity due to unforeseen security requirements .
