Title: The DBMS must produce audit records containing sufficient information to establish when (date and time) the events occurred.
Vulnerability ID: V-32369
IA Controls: None
Description: Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes: time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked.
Database software is capable of a range of actions on data stored within the database. It’s important, for accurate forensic analysis, to know exactly when specific actions were performed. This requires the date and time an audit record is referring to. If date and time information is not recorded and stored with the audit record, the record itself is of very limited use.
Check Text: Check DBMS settings and existing audit records to verify information specific to the date and time of the event is being captured and stored with the audit records. If audit records exist without the date and time of the event, this is a finding.
Fix Text: Modify DBMS audit settings to include the date and time of the occurrence of the event as part of the audit record.
In my opinion, it doesn’t really make a lot of sense to capture information in an audit without knowing when it happened. Just be sure if you are using SQL Audit, policy manager, PowerShell, or any other tools with SQL Server that you are capturing the date and time of the audit activity. This is a pretty straight forward check, and you can quickly go through any audits you have setup, or even the logs to make sure that appropriate time and date information is being captured.