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 Domain Name System (DNS) Security Requirements Guide

V-205161

CAT II (Medium)

The DNS server implementation must produce audit records containing information to establish what type of events occurred.

Rule ID

SV-205161r960891_rule

STIG

Domain Name System (DNS) Security Requirements Guide

Version

V4R2

CCIs

CCI-000130

Discussion

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.

Check Content

Review the DNS system configuration to determine if it is configured to log sufficient information to establish what type of events has occurred on the system. 

If the logging function is not configured to produce log records with information regarding the type of event, this is a finding.

Fix Text

Configure the DNS server to log events with enough information to determine what type of event has occurred on the system.