What is a detective control that does not ensure the integrity of data in a database?

The correct answer is that read/write access log controls are a type of detective control but do not ensure the integrity of data in a database. Detective controls are designed to identify security breaches or compliance failures after they occur, providing an audit trail that can help in detecting unauthorized access or changes to data. While access logs can show who accessed or modified data and when, they do not actively modify or protect the data itself.

In contrast, other controls mentioned play different roles in maintaining data integrity. Authentication controls are focused on verifying the identity of users before granting access, thereby preventing unauthorized actions that could compromise data integrity. Commitment and rollback controls are mechanisms used in database transactions to ensure that either all parts of a transaction are completed successfully or none at all, which is crucial for maintaining data integrity. Data normalization involves organizing data efficiently in a database to reduce redundancy and dependency, contributing to consistent and reliable data integrity.

Thus, while read/write access log controls provide valuable insights and a means to detect issues, they do not implement measures that protect or ensure the integrity of the data itself.