In your production database, data manipulation language (DML) operations are executed on the SALES table. You have noticed some dubious values in the SALES table during the last few days. You are…

Fine-grained auditing (DBMS_FGA) records which rows a user accessed and what SQL was executed, but it does not capture the before and after column values of DML changes.

Value-based auditing is implemented by creating DML triggers (BEFORE or AFTER INSERT, UPDATE, DELETE) on the target table that reference the :OLD and :NEW pseudo-records to capture the previous and current data values. These triggers also capture user context information such as USER, SYSDATE, and SYS_CONTEXT values, storing all of this into a custom audit table - satisfying the requirement to track both old and new data along with the user.

Standard database auditing of object privileges records the fact that a privilege (such as INSERT or UPDATE) was used and by whom, but it does not capture the actual old or new data values involved in the change.

Standard database auditing of SQL statements records the SQL text and execution metadata, but does not store the specific column values that existed before and after the DML operation was performed.