STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to BIND 9.x Security Technical Implementation Guide

V-272369

CAT II (Medium)

The print-time variable for the configuration of BIND 9.x server logs must be configured to establish when (date and time) the events occurred.

Rule ID

SV-272369r1123825_rule

STIG

BIND 9.x Security Technical Implementation Guide

Version

V3R2

CCIs

CCI-000131

Discussion

Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. Associating event types with detected events in the application and audit logs provides a means of investigating an attack, recognizing resource utilization or capacity thresholds, or identifying an improperly configured application. To compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know when events occurred (date and time).

Check Content

For each logging channel that is defined, verify that the "print-time" substatement is listed.

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

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

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

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

Fix Text

Edit the "named.conf" file.

Add the "print-time" substatement to the "channel" statement.

Configure the "print-time" sub statement to "yes".

Restart the BIND 9.x process.