| V-58593 | High | The Windows 2012 DNS Servers zone files must have NS records that point to active name servers authoritative for the domain specified in that record. | Poorly constructed NS records pose a security risk because they create conditions under which an adversary might be able to provide the missing authoritative name services that are improperly... |
| V-58599 | High | The Windows 2012 DNS Server must be configured to enable DNSSEC Resource Records. | 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... |
| V-58687 | High | The Windows 2012 DNS Server must protect the authenticity of dynamic updates via transaction signing. | DNS is a fundamental network service that is prone to various attacks, such as cache poisoning and man-in-the middle attacks. If communication sessions are not provided appropriate validity... |
| V-58595 | Medium | All authoritative name servers for a zone must be located on different network segments. | Most enterprises have an authoritative primary server and a host of authoritative secondary name servers. It is essential that these authoritative name servers for an enterprise be located on... |
| V-58597 | Medium | All authoritative name servers for a zone must have the same version of zone information. | The only protection approach for content control of a DNS zone file is the use of a zone file integrity checker. The effectiveness of integrity checking using a zone file integrity checker depends... |
| V-58591 | Medium | NSEC3 must be used for all internal DNS zones. | NSEC records list the resource record types for the name, as well as the name of the next resource record. With this information it is revealed that the resource record type for the name queried,... |
| V-58663 | Medium | The Windows 2012 DNS Server must use DNSSEC data within queries to confirm data integrity to DNS resolvers. | The major threat associated with DNS forged responses or failures is the integrity of the DNS data returned in the response. The principle of DNSSEC is to mitigate this threat by providing data... |
| V-58661 | Medium | WINS lookups must be disabled on the Windows 2012 DNS Server. | The major threat associated with DNS forged responses or failures is the integrity of the DNS data returned in the response. The principle of DNSSEC is to mitigate this threat by providing data... |
| V-58667 | Medium | The Windows 2012 DNS Server must enforce approved authorizations between DNS servers through the use of digital signatures in the RRSet. | A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations,... |
| V-58665 | Medium | The Windows 2012 DNS Server must be configured with the DS RR carrying the signature for the RR that contains the public key of the child zone. | If name server replies are invalid or cannot be validated, many networking functions and communication would be adversely affected. With DNS, the presence of Delegation Signer (DS) records... |
| V-58589 | Medium | The validity period for the RRSIGs covering a zones DNSKEY RRSet must be no less than two days and no more than one week. | The best way for a zone administrator to minimize the impact of a key compromise is by limiting the validity period of RRSIGs in the zone and in the parent zone. This strategy limits the time... |
| V-58697 | Medium | The Windows 2012 DNS Server must restrict individuals from using it for launching Denial of Service (DoS) attacks against other information systems. | Applications and application developers must take the steps needed to ensure users cannot use an authorized application to launch DoS attacks against other systems and networks. For example,... |
| V-58695 | Medium | The Windows 2012 DNS Server must not contain zone records that have not been validated in over a year. | If zone information has not been validated in over a year, then there is no assurance that it is still valid. If invalid records are in a zone, then an adversary could potentially use their... |
| V-58693 | Medium | The Windows 2012 DNS Server must protect secret/private cryptographic keys while at rest. | Information at rest refers to the state of information when it is located on a secondary storage device within an organizational information system. Mobile devices, laptops, desktops, and storage... |
| V-58691 | Medium | The Windows 2012 DNS Server must only allow the use of an approved DoD PKI-established certificate authorities for verification of the establishment of protected transactions. | Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DoD systems or by organizations with insufficient... |
| V-58699 | Medium | The Windows 2012 DNS Server must use DNS Notify to prevent denial of service through increase in workload. | In the case of application DoS attacks, care must be taken when designing the application to ensure the application makes the best use of system resources. SQL queries have the potential to... |
| V-58583 | Medium | The Windows 2012 DNS Server with a caching name server role must restrict recursive query responses to only the IP addresses and IP address ranges of known supported clients. | A potential vulnerability of DNS is that an attacker can poison a name server's cache by sending queries that will cause the server to obtain host-to-IP address mappings from bogus name servers... |
| V-58581 | Medium | Forwarders on an authoritative Windows 2012 DNS Server, if enabled for external resolution, must only forward to either an internal, non-AD-integrated DNS server or to the DoD Enterprise Recursive Services (ERS). | A potential vulnerability of DNS is that an attacker can poison a name server's cache by sending queries that will cause the server to obtain host-to-IP address mappings from bogus name servers... |
| V-58587 | Medium | The Windows 2012 DNS Server must implement cryptographic mechanisms to detect changes to information during transmission unless otherwise protected by alternative physical safeguards, such as, at a minimum, a Protected Distribution System (PDS). | Encrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for... |
| V-58585 | Medium | The Windows 2012 DNS Server with a caching name server role must be secured against pollution by ensuring the authenticity and integrity of queried records. | A potential vulnerability of DNS is that an attacker can poison a name server's cache by sending queries that will cause the server to obtain host-to-IP address mappings from bogus name servers... |
| V-58671 | Medium | The Windows 2012 DNS Server must be configured to validate an authentication chain of parent and child domains via response data. | If name server replies are invalid or cannot be validated, many networking functions and communication would be adversely affected. With DNS, the presence of Delegation Signer (DS) records... |
| V-58673 | Medium | Trust anchors must be exported from authoritative Windows 2012 DNS Servers and distributed to validating Windows 2012 DNS Servers. | If name server replies are invalid or cannot be validated, many networking functions and communication would be adversely affected. With DNS, the presence of Delegation Signer (DS) records... |
| V-58675 | Medium | Automatic Update of Trust Anchors must be enabled on key rollover. | A trust anchor is a preconfigured public key associated with a specific zone. A validating DNS server must be configured with one or more trust anchors in order to perform validation. If the DNS... |
| V-58677 | Medium | The Windows DNS secondary servers must request data origin authentication verification from the primary server when requesting name/address resolution. | If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been... |
| V-58669 | Medium | The Name Resolution Policy Table (NRPT) must be configured in Group Policy to enforce clients to request DNSSEC validation for a domain. | The Name Resolution Policy Table (NRPT) is used to require DNSSEC validation. The NRPT can be configured in local Group Policy for a single computer or domain Group Policy for some or all... |
| V-58645 | Medium | The Windows 2012 DNS Server permissions must be set so that the key file can only be read or modified by the account that runs the name server software. | 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 can also be used for securing other... |
| V-58647 | Medium | The private key corresponding to the ZSK must only be stored on the name server that does support dynamic updates. | The private keys in the KSK and ZSK key pairs must be protected from unauthorized access. If possible, the private keys should be stored off-line (with respect to the Internet-facing, DNSSEC-aware... |
| V-58641 | Medium | The Windows 2012 DNS Server must be configured to enforce authorized access to the corresponding private key. | The cornerstone of the PKI is the private key used to encrypt or digitally sign information. If the private key is stolen, this will lead to the compromise of the authentication and... |
| V-58643 | Medium | The Windows 2012 DNS Server key file must be owned by the account under which the Windows 2012 DNS Server service is run. | 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 can also be used for securing other... |
| V-58649 | Medium | The Windows 2012 DNS Server must implement a local cache of revocation data for PKIauthentication in the event revocation information via the network is not accessible. | Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates).
SIG(0) is used for... |
| V-58579 | Medium | The Windows 2012 DNS Server must prohibit recursion on authoritative name servers for which forwarders have not been configured for external queries. | A potential vulnerability of DNS is that an attacker can poison a name server's cache by sending queries that will cause the server to obtain host-to-IP address mappings from bogus name servers... |
| V-58577 | Medium | The Windows DNS name servers for a zone must be geographically dispersed. | In addition to network-based separation, authoritative name servers should be dispersed geographically as well. In other words, in addition to being located on different network segments, the... |
| V-58575 | Medium | The validity period for the RRSIGs covering the DS RR for a zones delegated children must be no less than two days and no more than one week. | The best way for a zone administrator to minimize the impact of a key compromise is by limiting the validity period of RRSIGs in the zone and in the parent zone. This strategy limits the time... |
| V-58573 | Medium | The Windows 2012 DNS Servers audit records must be backed up at least every seven days onto a different system or system component than the system or component being audited. | Protection of log data includes assuring log data is not accidentally lost or deleted. Backing up audit records to a different system or onto separate media than the system being audited on a... |
| V-58571 | Medium | The Windows 2012 DNS Server log must include identity of individual or process associated with events within the log records. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. The... |
| V-58557 | Medium | The Windows 2012 DNS Server must implement NIST FIPS-validated cryptography for provisioning digital signatures, generating cryptographic hashes, and protecting unclassified information requiring confidentiality. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards... |
| V-58653 | Medium | The Windows 2012 DNS Server must include data origin with authoritative data the system returns in response to external name/address resolution queries. | The underlying feature in the major threat associated with DNS query/response (i.e., forged response or response failure) is the integrity of DNS data returned in the response. The security... |
| V-58651 | Medium | The salt value for zones signed using NSEC3 RRs must be changed every time the zone is completely re-signed. | NSEC records list the resource record types for the name, as well as the name of the next resource record. With this information it is revealed that the resource record type for the name queried,... |
| V-58657 | Medium | The Windows 2012 DNS Server must return data information in responses to internal name/address resolution queries. | The major threat associated with DNS forged responses or failures is the integrity of the DNS data returned in the response. The principle of DNSSEC is to mitigate this threat by providing data... |
| V-58655 | Medium | The Windows 2012 DNS Servers IP address must be statically defined and configured locally on the server. | The major threat associated with DNS forged responses or failures are the integrity of the DNS data returned in the response. The principle of DNSSEC is to mitigate this threat by providing data... |
| V-58659 | Medium | The Windows 2012 DNS Server must use DNSSEC data within queries to confirm data origin to DNS resolvers. | The major threat associated with DNS forged responses or failures are the integrity of the DNS data returned in the response. The principle of DNSSEC is to mitigate this threat by providing data... |
| V-58719 | Medium | The Windows 2012 DNS Server must generate audit records for the success and failure of start and stop of the DNS Server service. | 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... |
| V-58569 | Medium | The Windows 2012 DNS Server log must include results of events within the log records. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. The... |
| V-58713 | Medium | The Windows 2012 DNS Server must perform verification of the correct operation of security functions: upon system start-up and/or restart; upon command by a user with privileged access; and/or every 30 days. | Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data... |
| V-58565 | Medium | The Windows 2012 DNS Server log must include origin of events within the log records. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. The... |
| V-58711 | Medium | The Windows 2012 DNS Server must, when a component failure is detected, activate a notification to the system administrator. | Predictable failure prevention requires organizational planning to address system failure issues. If components key to maintaining systems security fail to function, the system could continue... |
| V-58567 | Medium | The Windows 2012 DNS Server log must include the source of events within the log records. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. The... |
| V-58717 | Medium | The Windows 2012 DNS Server must be configured to notify the ISSO/ISSM/DNS administrator when functionality of DNSSEC/TSIG has been removed or broken. | Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data... |
| V-58561 | Medium | The Windows 2012 DNS Server log must include event types within the log records. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. The... |
| V-58715 | Medium | The Windows 2012 DNS Server must log the event and notify the system administrator when anomalies in the operation of the signed zone transfers are discovered. | Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data... |
| V-58563 | Medium | The Windows 2012 DNS Server log must include time stamps within the log records. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. The... |
| V-58627 | Medium | When IPv6 protocol is installed, the server must also be configured to answer for IPv6 AAAA records. | To prevent the possibility of a denial of service in relation to an IPv4 DNS server trying to respond to IPv6 requests, the server should be configured not to listen on any of its IPv6 interfaces... |
| V-58709 | Medium | The Windows 2012 DNS Server must follow procedures to re-role a secondary name server as the master name server should the master name server permanently lose functionality. | 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... |
| V-58625 | Medium | AAAA addresses must not be configured in a zone for hosts that are not IPv6-aware. | DNS is only responsible for resolving a domain name to an IP address. Applications and operating systems are responsible for processing the IPv6 or IPv4 record that may be returned. With this in... |
| V-58623 | Medium | Non-routable IPv6 link-local scope addresses must not be configured in any zone. | IPv6 link-local scope addresses are not globally routable and must not be configured in any DNS zone. Similar to RFC1918 addresses, if a link-local scope address is inserted into a zone provided... |
| V-58621 | Medium | The Windows 2012 DNS Servers zone files must not include CNAME records pointing to a zone with lesser security for more than six months. | The use of CNAME records for exercises, tests, or zone-spanning aliases should be temporary (e.g., to facilitate a migration). When a host name is an alias for a record in another zone, an... |
| V-58551 | Medium | The Windows 2012 DNS Server logging must be enabled to record events from all DNS server functions. | DNS server performance can be affected when additional logging is enabled, however the enhanced DNS logging and diagnostics feature in Windows Server 2012 R2 is designed to have a very low impact... |
| V-58701 | Medium | The Windows 2012 DNS Server must protect the integrity of transmitted information. | Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered.
Communication... |
| V-58553 | Medium | The Windows 2012 DNS Server logging criteria must only be configured by the ISSM or individuals appointed by the ISSM. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. The... |
| V-58703 | Medium | The Windows 2012 DNS Server must maintain the integrity of information during preparation for transmission. | Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points,... |
| V-58555 | Medium | The Windows 2012 DNS Server must generate audit records for the success and failure of all name server events. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. The... |
| V-58705 | Medium | The Windows 2012 DNS Server must maintain the integrity of information during reception. | Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points,... |
| V-58629 | Medium | The Windows 2012 DNS Server must be configured to prohibit or restrict unapproved ports and protocols. | In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must... |
| V-58707 | Medium | The Windows 2012 DNS Server must be configured to only allow zone information that reflects the environment for which it is authoritative, to include IP ranges and IP versions. | DNS zone data for which a Windows 2012 DNS server is authoritative should represent the network for which it is responsible. If a Windows 2012 DNS server hosts zone records for other networks or... |
| V-58547 | Medium | The Windows 2012 DNS Server must, in the event of an error validating another DNS servers identity, send notification to the DNS administrator. | Failing to act on the validation errors may result in the use of invalid, corrupted, or compromised information. The validation of bindings can be achieved, for example, by the use of... |
| V-58737 | Medium | The DNS Name Server software must be configured to refuse queries for its version information. | Each newer version of the name server software, especially the BIND software, generally is devoid of vulnerabilities found in earlier versions because it has design changes incorporated to take... |
| V-58543 | Medium | The Windows 2012 DNS Server must be configured to record, and make available to authorized personnel, who added/modified/deleted DNS zone information. | Without a means for identifying the individual that produced the information, the information cannot be relied upon. Identifying the validity of information may be delayed or deterred.
This... |
| V-58739 | Medium | The HINFO, RP, TXT and LOC RR types must not be used in the zone SOA. | There are several types of RRs in the DNS that are meant to convey information to humans and applications about the network, hosts, or services. These RRs include the Responsible Person (RP)... |
| V-58549 | Medium | The Windows 2012 DNS Server log must be enabled. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. The... |
| V-58635 | Medium | The secondary Windows DNS name servers must cryptographically authenticate zone transfers from primary name servers. | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Device authentication is a solution enabling an organization to manage... |
| V-58637 | Medium | The Windows DNS primary server must only send zone transfers to a specific list of secondary name servers. | Primary name servers also make outbound connection to secondary name servers to provide zone transfers and accept inbound connection requests from clients wishing to provide a dynamic update.... |
| V-58631 | Medium | The Windows 2012 DNS Server must require devices to re-authenticate for each dynamic update request connection attempt. | Without re-authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity.
In addition to the re-authentication requirements associated with... |
| V-58633 | Medium | The Windows 2012 DNS Server must uniquely identify the other DNS server before responding to a server-to-server transaction. | Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. This applies to server-to-server (zone transfer) transactions only and is... |
| V-58639 | Medium | The Windows 2012 DNS Server must provide its identity with returned DNS information by enabling DNSSEC and TSIG/SIG(0). | Weakly bound credentials can be modified without invalidating the credential; therefore, non-repudiation can be violated.
This requirement supports audit requirements that provide organizational... |
| V-58689 | Medium | The Windows 2012 DNS Server must protect the authenticity of query responses via DNSSEC. | The underlying feature in the major threat associated with DNS query/response (i.e., forged response or response failure) is the integrity of DNS data returned in the response. An integral part of... |
| V-58681 | Medium | The Windows DNS secondary server must validate data integrity verification on the name/address resolution responses received from primary name servers. | If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been... |
| V-58683 | Medium | The Windows DNS secondary server must validate data origin verification authentication on the name/address resolution responses received from primary name servers. | If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been... |
| V-58685 | Medium | The Windows 2012 DNS Server must protect the authenticity of zone transfers via transaction signing. | Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. This applies to server-to-server (zone transfer) transactions and is... |
| V-58601 | Medium | Digital signature algorithm used for DNSSEC-enabled zones must be FIPS-compatible. | The choice of digital signature algorithm will be based on recommended algorithms in well-known standards. NIST's Digital Signature Standard (DSS) [FIPS186] provides three algorithm choices:
*... |
| V-58603 | Medium | For zones split between the external and internal sides of a network, the RRs for the external hosts must be separate from the RRs for the internal hosts. | Authoritative name servers for an enterprise may be configured to receive requests from both external and internal clients.
External clients need to receive RRs that pertain only to public... |
| V-58605 | Medium | In a split DNS configuration, where separate name servers are used between the external and internal networks, the external name server must be configured to not be reachable from inside resolvers. | Instead of having the same set of authoritative name servers serve different types of clients, an enterprise could have two different sets of authoritative name servers.
One set, called external... |
| V-58607 | Medium | In a split DNS configuration, where separate name servers are used between the external and internal networks, the internal name server must be configured to not be reachable from outside resolvers. | Instead of having the same set of authoritative name servers serve different types of clients, an enterprise could have two different sets of authoritative name servers.
One set, called external... |
| V-58609 | Medium | Primary authoritative name servers must be configured to only receive zone transfer requests from specified secondary name servers. | Authoritative name servers (especially primary name servers) should be configured with an allow-transfer access control sub statement designating the list of hosts from which zone transfer... |
| V-58237 | Medium | The Windows 2012 DNS Server must restrict incoming dynamic update requests to known clients. | Limiting the number of concurrent sessions reduces the risk of Denial of Service (DoS) on any system.
A DNS server's function requires it to be able to handle multiple sessions at a time so... |
| V-58619 | Medium | The Windows 2012 DNS Servers zone files must not include resource records that resolve to a fully qualified domain name residing in another zone. | If a name server were able to claim authority for a resource record in a domain for which it was not authoritative, this would pose a security risk. In this environment, an adversary could use... |
| V-58617 | Medium | The DNS name server software must be at the latest version. | Each newer version of the name server software, especially the BIND software, generally is devoid of vulnerabilities found in earlier versions because it has design changes incorporated to take... |
| V-58615 | Medium | The Windows 2012 DNS Server authoritative for local zones must only point root hints to the DNS servers that host the internal root domain. | All caching name servers must be authoritative for the root zone because, without this starting point, they would have no knowledge of the DNS infrastructure and thus would be unable to respond to... |
| V-58613 | Medium | The Windows 2012 DNS Server must implement internal/external role separation. | DNS servers with an internal role only process name/address resolution requests from within the organization (i.e., internal clients). DNS servers with an external role only process name/address... |
| V-58611 | Medium | The Windows 2012 DNS Servers zone database files must not be accessible for edit/write by users and/or processes other than the Windows 2012 DNS Server service account and/or the DNS database administrator. | Discretionary Access Control (DAC) is based on the premise that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in... |
| V-58679 | Medium | The Windows DNS secondary server must request data integrity verification from the primary server when requesting name/address resolution. | If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been... |
