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-279959

CAT II (Medium)

An authoritative name server must be configured to enable DNSSEC Resource Records.

Rule ID

SV-279959r1156986_rule

STIG

Domain Name System (DNS) Security Requirements Guide

Version

V4R2

CCIs

CCI-001663

Discussion

The specification for a digital signature mechanism in the context of the DNS infrastructure is in IETF's DNSSEC standard. In DNSSEC, trust in the public key (for signature verification) of the source is established not by going to a third party or a chain of third parties (as in public key infrastructure [PKI] chaining), but by starting from a trusted zone (such as the root zone) and establishing the chain of trust down to the current source of response through successive verifications of signature of the public key of a child by its parent. The public key of the trusted zone is called the trust anchor. After authenticating the source, the next process DNSSEC calls for is to authenticate the response. DNSSEC mechanisms involve two main processes: sign and serve, and verify signature. Before a DNSSEC-signed zone can be deployed, a name server must be configured to enable DNSSEC processing.

Check Content

Check the DNS configuration to ensure DNSSEC Resource Records has been enabled.

If the name server is not configured with DNSSEC enabled, this is a finding.

Fix Text

Configure the name server with DNSSEC enabled.