Title

The print-time variable for the configuration of BIND 9.x server logs must be configured to establish when (date and time) the events occurred. (Cat II impact)

Discussion

Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. Associating event types with detected events in the application and audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured application. To compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know when events occurred (date and time).

Check Content

For each logging channel that is defined, verify that the "print-time" substatement is listed. Inspect the "named.conf" file for the following: logging { channel channel_name { print-time yes; }; }; If the "print-time" statement is missing, this is a finding. If the "print-time" statement is not set to "yes", this is a finding.

Fix Text

Edit the "named.conf" file. Add the "print-time" substatement to the "channel" statement. Configure the "print-time" sub statement to "yes". Restart the BIND 9.x process.

Additional Identifiers

Rule ID: SV-272369r1082296_rule

Vulnerability ID: V-272369

Group Title: SRG-APP-000096-DNS-000007

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.