Page 1430 - (ISC)² CISSP Certified Information Systems Security Professional Official Study Guide
P. 1430

be an “all-or-nothing” affair. If any part of the transaction fails, the
               entire transaction must be rolled back as if it never occurred.

               Consistency All transactions must begin operating in an

               environment that is consistent with all of the database’s rules (for
               example, all records have a unique primary key). When the transaction
               is complete, the database must again be consistent with the rules,
               regardless of whether those rules were violated during the processing
               of the transaction itself. No other transaction should ever be able to

               use any inconsistent data that might be generated during the
               execution of another transaction.

               Isolation The isolation principle requires that transactions operate
               separately from each other. If a database receives two SQL
               transactions that modify the same data, one transaction must be
               completed in its entirety before the other transaction is allowed to
               modify the same data. This prevents one transaction from working

               with invalid data generated as an intermediate step by another
               transaction.

               Durability Database transactions must be durable. That is, once they
               are committed to the database, they must be preserved. Databases
               ensure durability through the use of backup mechanisms, such as
               transaction logs.

               In the following sections, we’ll discuss a variety of specific security
               issues of concern to database developers and administrators.



               Security for Multilevel Databases

               As you learned in Chapter 1, many organizations use data classification
               schemes to enforce access control restrictions based on the security
               labels assigned to data objects and individual users. When mandated
               by an organization’s security policy, this classification concept must

               also be extended to the organization’s databases.

               Multilevel security databases contain information at a number of
               different classification levels. They must verify the labels assigned to
               users and, in response to user requests, provide only information
               that’s appropriate. However, this concept becomes somewhat more
   1425   1426   1427   1428   1429   1430   1431   1432   1433   1434   1435