Which control should an IS auditor recommend for protecting specific sensitive information within a data warehouse?

Implementing column- and row-level permissions is essential for protecting specific sensitive information within a data warehouse because it allows for granular access control over the data stored. This means that even if a user has access to the data warehouse, their ability to view or manipulate sensitive information can be strictly limited based on their role or need to know. By setting permissions at the column and row level, organizations can ensure that only authorized users can view or alter sensitive data, thereby reducing the risk of unauthorized access and protecting the confidentiality and integrity of that data.

In addition, this type of control helps organizations comply with various data protection regulations and industry standards that often mandate strict access controls for sensitive information. It is vital for protecting data in environments where many users might have varying levels of access and responsibilities.

Other approaches, such as enhancing user authentication with strong passwords, are important for securing access to the system in general, but they do not specifically address the need to protect sensitive information at a granular level. Organizing the data warehouse into subject matter-specific databases might improve data management and retrieval but does not inherently protect sensitive data. Logging user access to the data warehouse is an essential practice for auditing and monitoring, but it does not prevent unauthorized access to sensitive information directly. Therefore, the