Title

The DNS server implementation must follow procedures to re-role a secondary name server as the master name server should the master name server permanently lose functionality. (Cat II impact)

Discussion

Failing to an unsecure condition negatively impacts application security and can lead to system compromise. Failure conditions include, for example, loss of communications among critical system components or between system components and operational facilities. Fail-safe procedures include, for example, alerting operator personnel and providing specific instructions on subsequent steps to take (e.g., do nothing, reestablish system settings, shut down processes, restart the system, or contact designated organizational personnel). If a component such as the DNSSEC or TSIG/SIG(0) signing capabilities were to fail, the DNS server should shut itself down to prevent continued execution without the necessary security components in place. Transactions such as zone transfers would not be able to work correctly anyway in this state.

Check Content

Review the DNS server implementation operating documentation to determine if procedures exist to promote a secondary name server to the master in the event the master DNS name server permanently loses functionality. If procedures do not exist to promote a secondary name server to the master in the event the master DNS name server permanently loses functionality, this is a finding.

Fix Text

Develop internal procedures to ensure a secondary name server to the master in the event the master DNS name server permanently loses functionality.

Additional Identifiers

Rule ID: SV-205221r879822_rule

Vulnerability ID: V-205221

Group Title: SRG-APP-000451

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.