Details
Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is being performed on the system, where an event occurred, when an event occurred, and by whom the event was triggered, in order to compile an accurate risk assessment. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply identify an improperly configured DNS implementation. Without log records that aid in the establishment of what types of events occurred and when those events occurred, there is no traceability for forensic or analytical purposes, and the cause of events is severely hindered.
Solution
Edit the ‘named.conf’ file.
Add the ‘print-severity’ sub statement to the ‘channel’ statement.
Configure the ‘print-severity’ sub statement to ‘yes’
Restart the BIND 9.x process.
Supportive Information
The following resource is also helpful.
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-000130
- Rule-ID|SV-207543r612253_rule
- STIG-ID|BIND-9X-001030
- STIG-Legacy|SV-87009
- STIG-Legacy|V-72385
- Vuln-ID|V-207543