| V-205157 | | The DNS implementation must limit the number of concurrent sessions for zone transfers to the number of secondary name servers. | Limiting the number of concurrent sessions reduces the risk of Denial of Service (DoS) to the DNS implementation.
Name servers do not have direct us... |
| V-205158 | | The DNS implementation must limit the number of concurrent sessions client connections to the number of allowed dynamic update clients. | Limiting the number of concurrent sessions reduces the risk of Denial of Service (DoS) to the DNS implementation.
Name servers do not have direct us... |
| V-205159 | | The DNS server implementation must be configured to provide audit record generation capability for DoD-defined auditable events within all DNS server components. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, o... |
| V-205160 | | The DNS server implementation must be configured to provide audit record generation capability for DoD-defined auditable events within all DNS server components. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident, o... |
| V-205161 | | The DNS server implementation must produce audit records containing information to establish what type of events occurred. | Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is being performed on the sy... |
| V-205162 | | The DNS server implementation must produce audit records containing information to establish when (date and time) the events occurred. | Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident.
Associating... |
| V-205163 | | The DNS server implementation must produce audit records containing information to establish where the events occurred. | Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident. Associating ... |
| V-205164 | | The DNS server implementation must produce audit records containing information to establish the source of the events. | Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. ... |
| V-205165 | | The DNS server implementation must produce audit records that contain information to establish the outcome of the events. | Without information about the outcome of events, security personnel cannot make an accurate assessment about whether an attack was successful or if ch... |
| V-205166 | | The DNS server implementation must generate audit records containing information that establishes the identity of any individual or process associated with the event. | Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, sec... |
| V-205167 | | The DNS server implementations 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... |
| V-205168 | | The DNS server implementation 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... |
| V-205169 | | The DNS server implementation 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-ser... |
| V-205170 | | The DNS server implementation, when using PKI-based authentication, must 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 compr... |
| V-205171 | | The key file must be owned by the account under which the name server software 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... |
| V-205172 | | Read/Write access to the key file must be restricted to the account that runs the name server software only. | To enable zone transfer (requests and responses) through authenticated messages, it is necessary to generate a key for every pair of name servers. The... |
| V-205173 | | Only the private key corresponding to the ZSK alone must be kept 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 (wit... |
| V-205174 | | Signature generation using the KSK must be done off-line, using the KSK-private stored off-line. | Security-relevant information is any information within information systems that can potentially impact the operation of security functions or the pro... |
| V-205175 | | The DNS server implementation must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. | If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the system. The act of managing s... |
| V-205176 | | A DNS server implementation must provide additional data origin artifacts along with the 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... |
| V-205177 | | A DNS server implementation must provide the means to indicate the security status of child zones. | If name server replies are invalid or cannot be validated, many networking functions and communication would be adversely affected. With DNS, the pres... |
| V-205178 | | 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 p... |
| V-205179 | | The DNS server implementation must enforce approved authorizations for controlling the flow of information between DNS servers and between DNS servers and DNS clients based on DNSSEC policies. | A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is ... |
| V-205180 | | A DNS server implementation must provide the means to enable verification of a chain of trust among parent and child domains (if the child supports secure resolution services). | If name server replies are invalid or cannot be validated, many networking functions and communication would be adversely affected. With DNS, the pres... |
| V-205182 | | The DNS implementation must protect the authenticity of communications sessions for zone transfers. | DNS is a fundamental network service that is prone to various attacks, such as cache poisoning and man-in-the middle attacks.
If communication sessi... |
| V-205183 | | The DNS implementation must protect the authenticity of communications sessions for dynamic updates. | DNS is a fundamental network service that is prone to various attacks, such as cache poisoning and man-in-the middle attacks. If communication session... |
| V-205184 | | The DNS implementation must protect the authenticity of communications sessions for 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... |
| V-205185 | | The DNS server implementation must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. | Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Ap... |
| V-205186 | | In the event of a system failure, the DNS server implementation must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes. | Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure s... |
| V-205187 | | The DNS server implementation must protect the confidentiality and integrity of secret/private cryptographic keys at rest and the integrity of DNS information 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. M... |
| V-205188 | | The DNS server implementation must prevent unauthorized and unintended information transfer via shared system resources. | Preventing unauthorized information transfers mitigates the risk of information, including encrypted representations of information, produced by the a... |
| V-205189 | | The DNS server implementation must restrict the ability of individuals to use the DNS server to launch Denial of Service (DoS) attacks against other information systems. | A DoS is a condition where a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission o... |
| V-205190 | | The DNS server implementation must manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of Denial of Service (DoS) attacks. | A DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or... |
| V-205191 | | The DNS server implementation must check the validity of all data inputs except those specifically identified by the organization. | Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process ... |
| V-205192 | | The DNS server implementation 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 fa... |
| V-205193 | | The DNS server implementation must be configured to generate audit records for failed security verification tests so that the ISSO and ISSM can be notified of the failures. | Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy... |
| V-205196 | | The DNS server implementation must strongly bind the identity of the DNS server with the DNS information. | Weakly bound credentials can be modified without invalidating the credential; therefore, non-repudiation can be violated.
This requirement supports a... |
| V-205197 | | The DNS server implementation must provide the means for authorized individuals to determine the identity of the source of the DNS server-provided information. | Without a means for identifying the individual that produced the information, the information cannot be relied upon. Identifying the validity of infor... |
| V-205198 | | The DNS server implementation must validate the binding of the other DNS servers identity to the DNS information for a server-to-server transaction (e.g., zone transfer). | Validation of the binding of the information prevents the modification of information between production and review. The validation of bindings can be... |
| V-205199 | | In the event of an error when validating the binding of another DNS servers identity to the DNS information, the DNS server implementation must log the event and 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 ach... |
| V-205201 | | The DNS implementation must prohibit recursion on authoritative name servers. | 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-... |
| V-205203 | | The DNS server implementation must authenticate the other DNS server before responding to a server-to-server transaction. | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Device authentication is a... |
| V-205204 | | The DNS server implementation must authenticate another DNS server before establishing a remote and/or network connection using bidirectional authentication that is cryptographically based. | Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authenticati... |
| V-205205 | | The DNS server implementation, for PKI-based authentication, must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network. | 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... |
| V-205206 | | A DNS server implementation must provide data origin artifacts for 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 i... |
| V-205207 | | A DNS server implementation must provide data integrity protection artifacts for 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 i... |
| V-205208 | | A DNS server implementation must provide additional integrity artifacts along with the authoritative name resolution data the system returns in response to external 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 i... |
| V-205209 | | A DNS server implementation must request data origin authentication verification on the name/address resolution responses the system receives from authoritative sources. | If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poiso... |
| V-205210 | | A DNS server implementation must request data integrity verification on the name/address resolution responses the system receives from authoritative sources. | If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poiso... |
| V-205211 | | A DNS server implementation must perform data integrity verification on the name/address resolution responses the system receives from authoritative sources. | If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poiso... |
| V-205212 | | A DNS server implementation must perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources. | If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poiso... |
| V-205213 | | If the DNS server is using SIG(0), the DNS server implementation must only allow the use of 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 syst... |
| V-205217 | | The DNS server implementation 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 pr... |
| V-205218 | | The DNS server implementation 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 agg... |
| V-205219 | | The DNS server implementation must maintain the integrity of information during reception. | Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protoc... |
| V-205220 | | The DNS server implementation must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received. | A common vulnerability of applications is unpredictable behavior when invalid inputs are received. This requirement guards against adverse or unintend... |
| V-205221 | | 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. | Failing to an unsecure condition negatively impacts application security and can lead to system compromise. Failure conditions include, for example, l... |
| V-205222 | | The DNS server implementation 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... |
| V-205223 | | The DNS server implementation 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... |
| V-205224 | | The DNS implementation must generate audit records for the success and failure of start and stop of the name server service or daemon. | Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is being performed on the sy... |
| V-205225 | | The DNS implementation must generate audit records for the success and failure of all name server events. | Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is being performed on the sy... |
| V-205226 | | The 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 cryptogr... |
| V-205227 | | The salt value for zones signed using NSEC3 RRs must be changed every time the zone is completely re-signed. | NSEC3 RRs contain other options than just the (hashed) next name and RRType bitmap. There are also 2 values associated with the NSEC3 RR: the iteratio... |
| V-205228 | | 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 p... |
| V-205229 | | NSEC3 must be used for all internal DNS zones. | To ensure that RRs associated with a query are really missing in a zone file and have not been removed in transit, the DNSSEC mechanism provides a mea... |
| V-205230 | | The DNS implementation must ensure each NS record in a zone file points to an active name server 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 author... |
| V-205231 | | The two files generated by the dnssec-keygen program must be made accessible only to the server administrator account, or deleted, after they have been copied to the key file in the name server. | To enable zone transfer (requests and responses) through authenticated messages, it is necessary to generate a key for every pair of name servers. The... |
| V-205232 | | 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 nam... |
| V-205233 | | All authoritative name servers for a zone must have the same version of zone information. | The only protection approach for content control of DNS zone file is the use of a zone file integrity checker. The effectiveness of integrity checking... |
| V-205234 | | An authoritative name 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 pu... |
| V-205235 | | 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) [FI... |
| V-205236 | | 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... |
| V-205237 | | 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 authorit... |
| V-205238 | | 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 authorit... |
| V-205239 | | 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 substatement designating the l... |
| V-205240 | | The DNS implementation must be conformant to the IETF DNS specification. | Any DNS implementation must be designed to be able to conform to the Internet Engineering Task Force (IETF) specification. DoD utilizes many different... |
| V-205241 | | The DNS implementation must enforce a Discretionary Access Control (DAC) policy that limits propagation of access rights. | Discretionary Access Control (DAC) is based on the premise that individual users are "owners" of objects and therefore have discretion over who should... |
| V-205242 | | The DNS implementation 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 wit... |
| V-205243 | | The DNS must utilize valid root name servers in the local root zone file. | All caching name servers must be authoritative for the root zone because, without this starting point, they would have no knowledge of the DNS infrast... |
| V-205244 | | 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... |
| V-205245 | | The DNS Name Server software must run with restricted privileges. | Failure to provide logical access restrictions associated with changes to application configuration may have significant effects on the overall securi... |
| V-205246 | | The IP address for hidden master authoritative name servers must not appear in the name servers set in the zone database. | A hidden master authoritative server is an authoritative DNS server whose IP address does not appear in the name server set for a zone. All of the na... |
| V-205247 | | The platform on which the name server software is hosted must be configured to respond to DNS traffic only. | OS configuration practices as issued by the US Computer Emergency Response Team (US CERT) and the National Institute of Standards and Technology's (NI... |
| V-205248 | | The platform on which the name server software is hosted must be configured to send outgoing DNS messages from a random port. | OS configuration practices as issued by the US Computer Emergency Response Team (US CERT) and the National Institute of Standards and Technology's (NI... |
| V-205249 | | The private key corresponding to the ZSK, stored on name servers accepting dynamic updates, must have appropriate directory/file-level access control list-based or cryptography-based protections. | 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 (wit... |
| V-205250 | | The private keys corresponding to both the ZSK and the KSK must not be kept on the DNSSEC-aware primary authoritative name server when the name server does not 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 (wit... |
| V-205251 | | A zone file 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. I... |
| V-205252 | | CNAME records must not point 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 ... |
| V-205253 | | The DNS server implementation must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. | Configuration settings are the set of parameters that can be changed that affect the security posture and/or functionality of the system. Security-rel... |
| V-220316 | | A unique TSIG key must be generated for each pair of communicating hosts. | To enable zone transfer (requests and responses) through authenticated messages, it is necessary to generate a key for every pair of name servers. The... |
| V-220317 | | All authoritative name servers for a zone must be geographically disbursed. | In addition to network-based dispersion, authoritative name servers should be dispersed geographically as well. In other words, in addition to being l... |
| V-263623 | | The DNS server implementation must disable accounts when the accounts have expired. | Disabling expired, inactive, or otherwise anomalous accounts supports the concepts of least privilege and least functionality, which reduce the attack... |
| V-263624 | | The DNS server implementation must disable accounts when the accounts are no longer associated to a user. | Disabling expired, inactive, or otherwise anomalous accounts supports the concepts of least privilege and least functionality, which reduce the attack... |
| V-263625 | | The DNS server implementation must implement the capability to centrally review and analyze audit records from multiple components within the system. | Automated mechanisms for centralized reviews and analyses include Security Information and Event Management products.... |
| V-263626 | | The DNS server implementation must alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information. | Audit information includes all information needed to successfully audit system activity, such as audit records, audit log settings, audit reports, and... |
| V-263627 | | The DNS server implementation must automatically generate audit records of the enforcement actions. | Organizations log system accesses associated with applying configuration changes to ensure that configuration change control is implemented and to sup... |
| V-263628 | | The DNS server implementation must prevent the installation of organization-defined software and firmware components without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization. | Software and firmware components prevented from installation unless signed with recognized and approved certificates include software and firmware ver... |
| V-263629 | | The DNS server implementation must require users to be individually authenticated before granting access to the shared accounts or resources. | Individual authentication prior to shared group authentication mitigates the risk of using group accounts or authenticators.... |
| V-263630 | | The DNS server implementation must implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that one of the factors is provided by a device separate from the system gaining access. | The purpose of requiring a device that is separate from the system to which the user is attempting to gain access for one of the factors during multif... |
| V-263631 | | The DNS server implementation must implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that the device meets organization-defined strength of mechanism requirements. | The purpose of requiring a device that is separate from the system to which the user is attempting to gain access for one of the factors during multif... |
| V-263632 | | The DNS server implementation must, for password-based authentication, maintain a list of commonly used, expected, or compromised passwords on an organization-defined frequency. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-263633 | | The DNS server implementation must, for password-based authentication, update the list of passwords on an organization-defined frequency. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-263634 | | The DNS server implementation must, for password-based authentication, update the list of passwords when organizational passwords are suspected to have been compromised directly or indirectly. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-263635 | | The DNS server implementation must, for password-based authentication, verify when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5 (1) (a). | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-263636 | | The DNS server implementation must, for password-based authentication, store passwords using an approved salted key derivation function, preferably using a keyed hash. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-263637 | | The DNS server implementation must, for password-based authentication, require immediate selection of a new password upon account recovery. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-263638 | | The DNS server implementation must, for password-based authentication, allow user selection of long passwords and passphrases, including spaces and all printable characters. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-263639 | | The DNS server implementation must, for password-based authentication, employ automated tools to assist the user in selecting strong password authenticators. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-263640 | | The DNS server implementation must, for password-based authentication, enforce organization-defined composition and complexity rules. | Password-based authentication applies to passwords regardless of whether they are used in single-factor or multifactor authentication. Long passwords ... |
| V-263641 | | The DNS server implementation must, for public key-based authentication, implement a local cache of revocation data to support path discovery and validation. | Public key cryptography is a valid authentication mechanism for individuals, machines, and devices. For PKI solutions, status information for certific... |
| V-263642 | | The DNS server implementation must protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the system by logically separated communications paths. | Nonlocal maintenance and diagnostic activities are conducted by individuals who communicate through either an external or internal network. Communicat... |
| V-263643 | | The DNS server implementation must include only approved trust anchors in trust stores or certificate stores managed by the organization. | Public key infrastructure (PKI) certificates are certificates with visibility external to organizational systems and certificates related to the inter... |
| V-263644 | | The DNS server implementation must provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store. | A Trusted Platform Module (TPM) is an example of a hardware-protected data store that can be used to protect cryptographic keys.... |
| V-263645 | | The DNS server implementation must synchronize system clocks within and between systems or system components. | Time synchronization of system clocks is essential for the correct execution of many system services, including identification and authentication proc... |
| V-263646 | | The DNS server implementation must compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source. | Synchronization of internal system clocks with an authoritative source provides uniformity of time stamps for systems with multiple system clocks and ... |
| V-205214 | | The DNS server implementation must utilize cryptographic mechanisms to prevent unauthorized modification of DNS zone data. | Applications handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modificati... |
| V-205215 | | The DNS server implementation must utilize cryptographic mechanisms to prevent unauthorized disclosure of non-DNS data stored on the DNS server. | Applications handling data requiring "data-at-rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modificati... |
| V-205216 | | The DNS server implementation must protect the integrity of transmitted information. | Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepte... |
