Details

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. In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know when events occurred (date and time).

Solution

Edit the ‘named.conf’ file.

Add the ‘print-time’ sub statement to the ‘channel’ statement.

Configure the ‘print-time’ sub statement to ‘yes’

Restart the BIND 9.x process.

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_BIND_9-x_V2R2_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Unix.

References

• 800-53|AU-3
• CAT|III
• CCI|CCI-000131
• Rule-ID|SV-207544r612253_rule
• STIG-ID|BIND-9X-001031
• STIG-Legacy|SV-87011
• STIG-Legacy|V-72387
• Vuln-ID|V-207544

Source

• Tenable.com/audits