Details

Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. Associating information about where the event occurred within the application 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 where events occurred, such as application components, modules, session identifiers, filenames, host names, and functionality.

Solution

Edit the ‘named.conf’ file.

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

Configure the ‘print-category’ 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-000132
• Rule-ID|SV-207545r612253_rule
• STIG-ID|BIND-9X-001032
• STIG-Legacy|SV-87013
• STIG-Legacy|V-72389
• Vuln-ID|V-207545

Source

• Tenable.com/audits