OpenControls Logo

STIG Viewer

STIGViewer Support

The BIND 9.x server implementation must be configured with a channel to send audit records to at least two remote syslogs.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-272432BIND-9X-001910SV-272432r1123950_ruleCCI-001348high
Description
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 ensure, 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.
STIGDate
BIND 9.x Security Technical Implementation Guide2026-02-25

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

MON-08.1Event Log Backup on Separate Physical Systems / Components
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (21) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(1)Monitoring and Control
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(4)Automated Audit Actions
1.00
AU-10Non-repudiation
1.00
AU-11Audit Record Retention
1.00
AU-12Audit Record Generation
1.00
AU-12(1)System-wide and Time-correlated Audit Trail
1.00
AU-12(3)Changes by Authorized Individuals
1.00
AU-4(1)Transfer to Alternate Storage
1.00
AU-5Response to Audit Logging Process Failures
1.00

+11 more (top 10 by confidence shown)

CCI1 mapping
CCI-001348
1.00

Details

Check Text (C-272432r1123950_chk)

Verify that the BIND 9.x server is configured to send audit logs to at least two syslog servers. Note: syslog and local file channel must be defined for every defined category. Inspect the "named.conf" file for the following: logging { channel <syslog_channel> { syslog <syslog_facility>; }; category <category_name> { <syslog_channel>; }; logging { channel <syslog_channel> { syslog <syslog_facility>; }; category <category_name> { <syslog_channel>; }; If a logging channel is not defined for each syslog, this is a finding. If a category is not defined to send messages to the syslog channels, this is a finding.

Fix Text (F-76389r1123949_fix)

Configure the "logging" statement to send audit logs to the syslog daemons. logging { channel <syslog_channel> { syslog <syslog_facility>; }; category <category_name> { <syslog_channel>; }; }; logging { channel <syslog_channel> { syslog <syslog_facility>; }; category <category_name> { <syslog_channel>; }; }; 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.