The host running a BIND 9.x implementation must have DNS cookies enabled.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-275938BIND-9X-002470SV-275938r1156959_ruleCCI-000366medium
Description
DNS cookies can help prevent spoofing and cache poisoning attacks by verifying the identity of both the client and server. They do this by including a cryptographic identifier (the cookie) in DNS messages, which can be verified in future messages. This makes it difficult for an attacker to learn the cookie values and thus spoof them.
STIGDate
BIND 9.x Security Technical Implementation Guide2026-02-25

Related Frameworks

4 paths across 3 frameworks
NIST 800-531 mapping
CM-6
1.00
  • DISA · V3R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.4.1
1.00
  • DISA · V3R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.4.2
1.00
  • DISA · V3R2 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000366
1.00
  • DISA · V3R2 · disa_xccdf · related

Details

Check Text (C-275938r1156959_chk)

Verify answer-cookie is enabled. Inspect the named.conf file for the following: options { answer-cookie yes; If answer-cookie is missing or set to "no", this is a finding.

Fix Text (F-79945r1123967_fix)

Edit the named.conf file: options { answer-cookie yes; }; After making changes, save the named.conf file and restart the BIND service to apply the changes.