Details

Protection of log data includes assuring log data is not accidentally lost or deleted. Backing up audit records to a different system or onto separate media than the system being audited on a defined frequency helps to assure, in the event of a catastrophic system failure, the audit records will be retained.

This helps to ensure a compromise of the information system being audited does not also result in a compromise of the audit records.

Solution

Configure the ‘logging’ statement to send audit logs to the syslog daemon.

logging {
channel {
syslog ;
};
category { ; };
};

Note: It is recommended to use a local syslog facility (i.e. local0 -7) when configuring the syslog channel.

Restart the BIND 9.x process.

Configure the (r)syslog daemon to send audit logs to a remote server.

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_BIND_9-x_V2R2_STIG.ziphttps://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_BIND_9-x_V2R2_STIG.ziphttps://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-9(2)
• CAT|III
• CCI|CCI-001348
• Rule-ID|SV-207546r744225_rule
• STIG-ID|BIND-9X-001040
• STIG-Legacy|SV-87015
• STIG-Legacy|V-72391
• Vuln-ID|V-207546

Source

• Tenable.com/audits