OpenControls Logo

STIG Viewer

STIGViewer Support

A unique Transaction Signature (TSIG) key must be generated for each pair of communicating hosts.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-259410WDNS-22-000090SV-259410r1081086_ruleCCI-000186medium
Description
To enable zone transfer (requests and responses) through authenticated messages, it is necessary to generate a key for every pair of name servers. The key also can be used for securing other transactions, such as dynamic updates, DNS queries, and responses. The binary key string generated by most key generation utilities used with DNSSEC is Base64 encoded. TSIG is a string used to generate the message authentication hash stored in a TSIG Resource Record (RR) and used to authenticate an entire DNS message.
STIGDate
Microsoft Windows Server Domain Name System (DNS) Security Technical Implementation Guide2025-02-25

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

IAC-10.2PKI-Based Authentication
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (55) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-10Concurrent Session Control
1.00
AC-12Session Termination
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(4)Discretionary Access Control
1.00

+45 more (top 10 by confidence shown)

CCI1 mapping
CCI-000186
1.00

Details

Check Text (C-259410r1081086_chk)

This check is not applicable for Windows DNS Servers that only host Active Directory-integrated zones or for Windows DNS servers on a classified network. Review the DNS implementation. Verify that each pair of communicating hosts has a unique TSIG key (i.e., a separate key for each secondary name server to authenticate transactions with the primary name server, etc.). If a unique TSIG key has not been generated for each pair of communicating hosts, this is a finding. If using DNSSEC, this requirement is not applicable.

Fix Text (F-63057r939934_fix)

Regenerate a unique TSIG key for each pair of communicating hosts within the DNS architecture.