STIGQter: STIG Summary: BIND 9.x Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 22 Jan 2021:

The print-severity variable for the configuration of BIND 9.x server logs must be configured to produce audit records containing information to establish what type of events occurred.

DISA Rule

SV-207543r612253_rule

Vulnerability Number

V-207543

Group Title

SRG-APP-000095-DNS-000006

Rule Version

BIND-9X-001030

Severity

CAT III

CCI(s)

• CCI-000130 - The information system generates audit records containing information that establishes what type of event occurred.

Weight

10

Fix Recommendation

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.

Check Contents

For each logging channel that is defined, verify that the "print-severity" sub statement is listed:

Inspect the "named.conf" file for the following:

logging {
channel channel_name {
print-severity yes;
};
};

If the "print-severity" statement is missing, this is a finding.

If the "print-severity" statement is not set to "yes", this is a finding.

Vulnerability Number

V-207543

Documentable

False

Rule Version

BIND-9X-001030

Severity Override Guidance

For each logging channel that is defined, verify that the "print-severity" sub statement is listed:

Inspect the "named.conf" file for the following:

logging {
channel channel_name {
print-severity yes;
};
};

If the "print-severity" statement is missing, this is a finding.

If the "print-severity" statement is not set to "yes", this is a finding.

Check Content Reference

M

Target Key

2926

Comments