BIND-9X-001120 - A BIND 9.x server must implement NIST FIPS-validated cryptography for provisioning digital signatures and generating cryptographic hashes - zones


The 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 approved by the federal government since this provides assurance they have been tested and validated.

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:

- Digital Signature Algorithm (DSA)
- Elliptic Curve DSA (ECDSA)

Of these three algorithms, RSA and DSA are more widely available and hence are considered candidates of choice for DNSSEC. In terms of performance, both RSA and DSA have comparable signature generation speeds, but DSA is much slower for signature verification. Hence, RSA is the recommended algorithm as far as this guideline is concerned. It can be expected that name servers and clients will be able to use the RSA algorithm at the minimum.

NIST's Secure Hash Standard (SHS) (FIPS 180-3) specifies SHA-1, SHA-224, SHA-256, SHA-384, and SHA-512 as approved hash algorithms to be used as part of the algorithm suite for generating digital signatures using the digital signature algorithms in NIST's DSS[FIPS186].

Satisfies: SRG-APP-000514-DNS-000075, SRG-APP-000516-DNS-000090

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.


Create new DNSSEC and TSIG keys using a FIPS 180-3 approved cryptographic algorithm that meets or exceeds the strength of SHA256

See Also

Item Details


References: 800-53|SC-13, CAT|I, CCI|CCI-002450, Rule-ID|SV-207567r612253_rule, STIG-ID|BIND-9X-001120, STIG-Legacy|SV-87069, STIG-Legacy|V-72445, Vuln-ID|V-207567

Plugin: Unix

Control ID: e38c553f766a01951c9a0e2a2ca13dd34d98311f13bd04fe7735d9c8208cda07