Recommendation for Random Number Generation Using Deterministic Random Bit Generators
Open accessAbstract
AuthorityThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3541 et seq., Public Law (P.L.) 113-283.NIST is responsible for developing information security standards and guidelines, including minimum requirements for Federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems.This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems, as analyzed in Circular A-130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources.Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority.Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other Federal official.This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States.Attribution would, however, be appreciated by NIST.
AI snapshot
Written from the paper’s full text.
TL;DR
NIST SP 800-90A Rev. 1 specifies approved Deterministic Random Bit Generators (DRBGs) — Hash_DRBG, HMAC_DRBG, and CTR_DRBG — along with the requirements for instantiating, reseeding, generating from, and health-testing them. It defines the security strengths, entropy requirements, and output limits under which these mechanisms are considered secure.
Key findings
- The Recommendation supports exactly four security strengths: 112, 128, 192, or 256 bits; the security strength of output is `min(output_length, DRBG_security_strength)`, and concatenating outputs cannot exceed the instantiated strength.
- Approved mechanisms are hash-based (Hash_DRBG, HMAC_DRBG) and block-cipher-based (CTR_DRBG using TDEA, AES-128, AES-192, or AES-256). All were judged to provide acceptable security when published, and diversity of mechanisms allows transition if attacks are found on one class.
- Output constraints: hash-based DRBGs permit up to 2^48 generate requests of up to 2^19 bits each; AES CTR_DRBG the same; TDEA CTR_DRBG is limited to 2^32 requests of 2^13 bits. These limits exist to avoid a theoretical distinguishing attack (probability of distinguishing AES CTR_DRBG from ideal random at maximum output ≈ 2^-57; TDEA case ≈ 2^-6 in the described game).
- All DRBG mechanisms in the Recommendation are designed to provide backtracking resistance; prediction resistance requires reseeding with fresh entropy (at least the security strength) between consecutive requests.
- Dual_EC_DRBG was removed in Revision 1, along with the elliptic-curve appendices.
Methods
- This is a specification/standards document, not an empirical study: it defines DRBG mechanisms via pseudocode "envelopes" (instantiate, reseed, generate, uninstantiate, health test) around underlying algorithms, plus auxiliary derivation functions (Hash_df, Block_Cipher_df) and BCC/Block_Encrypt primitives.
- Conformance testing is to be conducted within the CMVP and CAVP frameworks; requirements are indicated by "shall," and some are out of scope for CMVP/CAVP validation.
- Informative appendices provide conversion routines (Appendix A), worked pseudocode examples for each mechanism (Appendix B), and DRBG mechanism selection guidance with a cost/constraint summary table (Appendix C).
Limitations
- Stated: "The precise structure, design and development of a random bit generator is outside the scope of this document"; entropy source design/validation is deferred to SP 800-90B and RBG construction to SP 800-90C.
- Stated: Hash_DRBG has known problems when instantiated with insufficient entropy for the requested strength and later supplied enough entropy via additional input during a generate request — though these do not affect security when instantiated with the entropy specified in the Recommendation.
- Stated: the CTR_DRBG distinguishing attack is "theoretical — it poses no practical threat to any real-world application of the DRBG"; the output limits are nonetheless required.
Model-written summary. Check it against the paper before relying on it.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
0 of 6 cited sources checked · 0 supported · 0 flagged
- Interpretationreasoning
The actual security strength supported by a given instantiation depends on the DRBG implementation and on the amount of entropy provided to the instantiate function.
“The actual security strength supported by a given instantiation depends on the DRBG implementation and on the amount of entropy provided to the instantiate function.”
Quote in the paperSubstantial claim - Interpretationreasoning
A concatenation of bit strings resulting from multiple calls to a DRBG will not provide a security strength for the concatenated string that is greater than the instantiated security strength of the DRBG.
“A concatenation of bit strings resulting from multiple calls to a DRBG will not provide a security strength for the concatenated string that is greater than the instantiated security strength of the DRBG.”
Quote in the paperSubstantial claim - Interpretationreasoning
If there is an undetected failure in the randomness source of an already properly seeded DRBG instantiation, the DRBG instantiation will still retain any previous entropy when the reseed operation fails to introduce new entropy.
“However, if there is an undetected failure in the randomness source of an already properly seeded DRBG instantiation, the DRBG instantiation will still retain any previous entropy when the reseed operation fails to introduce new entropy.”
Quote in the paperSubstantial claim - Interpretationnone given
The simple modular method produces a random value with a negligible skew, that is, the probability that a_i = w for any particular value of w (0 ≤ w ≤ r-1) is not exactly 1/r.
“This method produces a random value with a negligible skew, that is, the probability that a i =w for any particular value of w (0 ≤ w ≤ r-1) is not exactly 1/r.”
Quote in the paperNot a substantial claim - Interpretationreasoning
The claimed security strength for CTR_DRBG depends on limiting the total number of generate requests and the bits provided per generate request according to Table 3.
“Note that the claimed security strength for CTR_DRBG depends on limiting the total number of generate requests and the bits provided per generate request according to the table above.”
Quote in the paperSubstantial claim
- Interpretationreasoning
The introduction of fresh entropy via reseeding will also make the DRBG less susceptible to cryptanalytic attack.
“The introduction of fresh entropy via reseeding will also make the DRBG less susceptible to cryptanalytic attack.”
Quote in the paperSubstantial claim - Interpretationnone given
For a large enough value of s, the difference between the probability that a_i = w for any particular value of w and 1/r is negligible.
“However, for a large enough value of s, the difference between the probability that a i =w for any particular value of w and 1/r is negligible.”
Quote in the paperNot a substantial claim - Interpretationnone given
Without the limits on the total number of generate requests and the bits provided per generate request, it becomes possible, in principle, for an attacker to observe enough outputs from CTR_DRBG to distinguish its outputs from ideal random bits.
“Without these limits, it becomes possible, in principle, for an attacker to observe enough outputs from CTR_DRBG to distinguish its outputs from ideal random bits.”
Quote in the paperSubstantial claim - Premisecitation
The maximum security strength that can be supported by each DRBG based on a hash function is the security strength of the hash function for pre-image resistance.
“The maximum security strength that can be supported by each DRBG based on a hash function is the security strength of the hash function for pre-image resistance; these security strengths are provided in [SP 800-107].”
Quote in the paperSubstantial claim0 of 1 sources checked- cites [SP 800-107]
Not checked in the free run.
- Interpretationnone given
For TDEA CTR_DRBG, the DRBG generates a maximum of 128 64-bit blocks per generate request, thus providing 2^13 bits per request.
“The DRBG generates a maximum of 128 64-bit blocks per generate request, thus providing 2 13 bits per request.”
Quote in the paperSubstantial claim - Interpretationcitation
The maximum security strength that can be supported by the DRBG depends on the block cipher and key size used.
“The maximum security strength that can be supported by the DRBG depends on the block cipher and key size used; the security strengths that can be supported by the block ciphers and key sizes are provided in [SP 800-57].”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites SP 800-57
Not checked in the free run.
- Interpretationreasoning
An attacker given a sequence of 2^13 * 2^32 = 2^45 bits from an ideal random source has about a 2^-19 probability of seeing an event happen that could never happen from TDEA CTR_DRBG.
“This provides a distinguisheran attacker, given a sequence of 2 13 2 32 = 2 45 bits from an ideal random source, has about a 2 -19 probability of seeing an event happen that could never happen from TDEA CTR_DRBG.”
Quote in the paperSubstantial claim - Interpretationreasoning
These output constraints apply to the use of CTR_DRBG for any single purpose, regardless of how many times the DRBG is reseeded.
“These output constraints apply to the use of CTR_DRBG for any single purpose, regardless of how many times the DRBG is reseeded.”
Quote in the paperSubstantial claim - Interpretationown data
For each of the three AES key sizes, up to 2^48 generate requests may be made, each of up to 2^19 bits, with a negligible chance of any weakness that does not represent a weakness in AES.
“As shown in Table 3 of Section 10.2.1, for each of the three AES key sizes, up to 2 48 generate requests may be made, each of up to 2 19 bits, with a negligible chance of any weakness that does not represent a weakness in AES.”
Quote in the paperSubstantial claim - Interpretationreasoning
The block cipher is rekeyed between generate requests, so duplicate blocks can appear in different generate request outputs.
“(The block cipher is rekeyed between generate requests, so duplicate blocks can appear in different generate request outputs.)”
Quote in the paperSubstantial claim - Interpretationcitation
The output constraints are necessary to avoid a distinguishing attack on CTR_DRBG, described in [Campagna], in which the fact that a single generate call can never produce a duplicate block from the block cipher is used to build a distinguisher for the DRBG's outputs.
“The output constraints are necessary to avoid a distinguishing attack on the CTR_DRBG, described in [Campagna], in which the fact that a single generate call can never produce a duplicate block from the block cipher is used to build a distinguisher for the DRBG's outputs.”
Quote in the paperSubstantial claim0 of 1 sources checked- cites Campagna
Not checked in the free run.
- Interpretationreasoning
These problems do not affect Hash_DRBG's security when Hash_DRBG is instantiated with the amount of entropy specified in this Recommendation.
“However, these problems do not affect the DRBG's security when Hash_DRBG is instantiated with the amount of entropy specified in this Recommendation.”
Quote in the paperSubstantial claim - Interpretationreasoning
HMAC_DRBG requires far less demanding properties of the underlying hash function than Hash_DRBG.
“Note that the pseudorandomness of HMAC is a widely used assumption in designs, and the HMAC_DRBG requires far less demanding properties of the underlying hash function than Hash_DRBG.”
Quote in the paperSubstantial claim- The authors state this as an assumption: The pseudorandomness of HMAC is a widely used assumption in designs.
- Interpretationnone given
Hash_DRBG's security depends on the underlying hash function's behavior when processing a series of sequential input blocks.
“Hash_DRBG's security depends on the underlying hash function's behavior when processing a series of sequential input blocks.”
Quote in the paperSubstantial claim - Interpretationreasoning
AES CTR_DRBG permits up to 2^48 generate requests, so an attacker seeing the maximum length of output permitted (2^67 bits) from either an AES CTR_DRBG instance or an ideal random sequence will have a 2^-57 probability of being able to distinguish the two.
“AES CTR_DRBG permits up to 2 48 generate requests, so an attacker seeing the maximum length of output permitted (2 67 bits) from either an AES CTR_DRBG instance or an ideal random sequence will have a 2 -57 probability of being able to distinguish the two.”
Quote in the paperSubstantial claim
- Classified as probably not a substantial claim. 91
- May combine two claims. 28
Probably not a substantial claim: may not pass S3 (load-bearing).
Findingnone givenEach DRBG mechanism has restrictions on the security strength it can support, based on its design.
“Each DRBG mechanism has restrictions on the security strength it can support, based on its design (see Section 10).”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Findingnone givenThis Recommendation specifies several DRBG mechanisms, all of which provided acceptable security when this Recommendation was published.
“This Recommendation specifies several DRBG mechanisms, all of which provided acceptable security when this Recommendation was published.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Findingnone givenThe DRBG mechanisms specified in this Recommendation support four security strengths: 112, 128, 192 or 256 bits.
“The DRBG mechanisms specified in this Recommendation support four security strengths: 112, 128, 192 or 256 bits.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Findingnone givenEach DRBG mechanism includes one or more cryptographic primitives (i.e., a hash function or block cipher algorithm).
“Each DRBG mechanism includes one or more cryptographic primitives (i.e., a hash function or block cipher algorithm).”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
FindingreasoningThe DRBG mechanisms have been specified so that input with full entropy is not required.
“Ideally, the entropy input would have full entropy; however, the DRBG mechanisms have been specified so that input with full entropy is not required.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenA nonce may be required in the construction of a seed during instantiation to provide a security cushion to block certain attacks.
“A nonce may be required in the construction of a seed during instantiation in order to provide a security cushion to block certain attacks.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Premisenone givenThe intent of a personalization string is to introduce additional input into the instantiation of a DRBG.
“The intent of a personalization string is to introduce additional input into the instantiation of a DRBG.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Premisenone givenA DRBG does not provide output until a seed is available, and the internal state has been initialized.
“Note that a DRBG does not provide output until a seed is available, and the internal state has been initialized (see Section 10).”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationnone givenA DRBG does not rely on a personalization string to provide entropy.
“Note that a DRBG does not rely on a personalization string to provide entropy, even though entropy could be provided in the personalization string”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
InterpretationreasoningThe nonce provides greater assurance that the DRBG provides security_strength bits of security to the consuming application.
“The nonce provides greater assurance that the DRBG provides security_strength bits of security to the consuming application.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S4 (based).
Premisenone givenRandom number generation does not require interoperability between two entities; communicating entities may use different DRBG mechanisms without affecting their ability to communicate.
“Random number generation does not require interoperability between two entities, i.e., communicating entities may use different DRBG mechanisms without affecting their ability to communicate.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S4 (based).
Interpretationnone givenIn some consuming applications, a single DRBG compromise could reveal long-term secrets (e.g., a compromise of the DSA per-message secret could reveal the signing key).
“In some consuming applications, a single DRBG compromise could reveal long-term secrets (e.g., a compromise of the DSA per-message secret could reveal the signing key).”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
InterpretationreasoningA DRBG produces pseudorandom bits, rather than random bits, because of the deterministic nature of the process.
“Because of the deterministic nature of the process, a DRBG is said to produce pseudorandom bits, rather than random bits.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S2 (checkable), S4 (based). May combine two claims.
Interpretationnone givenThe security provided by an RBG that uses a DRBG mechanism is a system implementation issue; both the DRBG mechanism and its randomness source must be considered when determining whether the RBG is appropriate for use by consuming applications.
“The security provided by an RBG that uses a DRBG mechanism is a system implementation issue; both the DRBG mechanism and its randomness source must be considered when determining whether the RBG is appropriate for use by consuming applications.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
InterpretationreasoningReseeding is a means of restoring the secrecy of the output of the DRBG if a seed or the internal state becomes known.
“Reseeding is a means of restoring the secrecy of the output of the DRBG if a seed or the internal state becomes known.”
Quote in the paperSubstantial claimClassified as probably not a substantial claim.
Premisenone givenThe secrecy of the entropy input and the seed provides the basis for the security of the DRBG.
“The secrecy of this information provides the basis for the security of the DRBG.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S4 (based).
Interpretationnone givenIf the seed is kept secret and the algorithm is well designed, the bits output by the DRBG will be unpredictable, up to the instantiated security strength of the DRBG.
“If the seed is kept secret, and the algorithm is well designed, the bits output by the DRBG will be unpredictable, up to the instantiated security strength of the DRBG.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S4 (based).
Interpretationnone givenGenerating too many outputs from a seed (and other input information) may provide sufficient information for successfully predicting future outputs.
“Generating too many outputs from a seed (and other input information) may provide sufficient information for successfully predicting future outputs (see Section 8.8).”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable).
InterpretationreasoningThe presence of more entropy than is required, especially during the instantiation, will provide a higher level of assurance than the minimum required entropy.
“The presence of more entropy than is required, especially during the instantiation, will provide a higher level of assurance than the minimum required entropy.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductnone givenThe DRBG reseed specifications within this Recommendation are designed to produce a new seed that is determined by both the old seed and newly obtained entropy input that will support the desired security strength.
“The DRBG reseed specifications within this Recommendation are designed to produce a new seed that is determined by both the old seed and newly obtained entropy input that will support the desired security strength.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
Interpretationnone givenIf a DRBG were instantiated many times without a nonce, a compromise could become more likely.
“If a DRBG were instantiated many times without a nonce, a compromise could become more likely.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationnone givenThe security of the DRBG itself does not rely on the secrecy of other inputs (nonce, personalization string, additional input).
“This information may or may not be required to be kept secret by a consuming application; however, the security of the DRBG itself does not rely on the secrecy of this information.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable).
InterpretationreasoningIn the event that new attacks are found on a particular class of DRBG mechanisms, a diversity of approved mechanisms will allow a timely transition to a different class of DRBG mechanism.
“However, in the event that new attacks are found on a particular class of DRBG mechanisms, a diversity of approved mechanisms will allow a timely transition to a different class of DRBG mechanism.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S4 (based).
Interpretationnone givenIf a DRBG instantiation was initially seeded with sufficient entropy, and the randomness source subsequently fails without being detected, then a new instantiation using the same (failed) source would not have sufficient entropy to operate securely.
“If a DRBG instantiation was initially seeded with sufficient entropy, and the randomness source subsequently fails without being detected, then a new instantiation using the same (failed) source would not have sufficient entropy to operate securely.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim. May combine two claims.
InterpretationreasoningPeriodic reseeding will reduce security risks, reducing the likelihood of a compromise of the data that is protected by cryptographic mechanisms that use the DRBG.
“Periodic reseeding will reduce security risks, reducing the likelihood of a compromise of the data that is protected by cryptographic mechanisms that use the DRBG.”
Quote in the paperSubstantial claimClassified as probably not a substantial claim. May combine two claims.
Premisenone givenSeeds have a finite seedlife (i.e., the number of outputs that are produced during a seed period); the maximum seedlife is dependent on the DRBG mechanism used.
“Seeds have a finite seedlife (i.e., the number of outputs that are produced during a seed period); the maximum seedlife is dependent on the DRBG mechanism used.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenKnowledge of the personalization string by an adversary does not degrade the security strength of a DRBG instantiation, as long as the entropy input is unknown.
“knowledge of the personalization string by an adversary does not degrade the security strength of a DRBG instantiation, as long as the entropy input is unknown.”
Quote in the paperNot a substantial claim- Rests on an assumption: The security of the DRBG depends on the secrecy of the entropy input.
Classified as probably not a substantial claim. May combine two claims.
InterpretationreasoningHaving more entropy than the assessed amount is acceptable; having less entropy than the assessed amount could be fatal to security.
“Having more entropy than the assessed amount is acceptable; having less entropy than the assessed amount could be fatal to security.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenValidations by a NVLAP-accredited laboratory provide a higher level of assurance that the DRBG mechanism is correctly implemented.
“Such validations provide a higher level of assurance that the DRBG mechanism is correctly implemented.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S4 (based).
Interpretationnone givenThe simple discard method produces a random number a with no skew (no bias).
“This method produces a random number a with no skew (no bias).”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationnone givenWhen the reseed function returns an error, the indicated instantiation will not have been reseeded (i.e., the internal state will not have been injected with fresh entropy).
“When the reseed function returns an error (see Section 9.2), the indicated instantiation will not have been reseeded (i.e., the internal state will not have been injected with fresh entropy).”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
InterpretationreasoningSince SHA-224 is based on SHA-256, there is no efficiency benefit when using SHA-224 rather than SHA-256.
“Note that since SHA-224 is based on SHA-256, there is no efficiency benefit when using SHA-224, rather than SHA-256.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenThe complex discard method may have better overall performance than the simple discard method if many random numbers are needed.
“The complex discard method may have better overall performance than the simple discard method if many random numbers are needed.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
InterpretationreasoningAn amount of entropy that is sufficient to support the security strength of the DRBG being reseeded (i.e., an amount that is at least equal to the security strength) must be provided to the DRBG in a way that ensures that knowledge of the current DRBG internal state does not allow an adversary any useful knowledge about future DRBG internal states or outputs.
“That is, an amount of entropy that is sufficient to support the security strength of the DRBG being reseeded (i.e., an amount that is at least equal to the security strength) must be provided to the DRBG in a way that ensures that knowledge of the current DRBG internal state does not allow an adversary any useful knowledge about future DRBG internal states or outputs.”
Quote in the paperSubstantial claim- The authors state this as an assumption: The adversary is incapable of performing work that matches the claimed security strength of the RBG.
Probably not a substantial claim: may not pass S3 (load-bearing).
InterpretationreasoningSince SHA-384, SHA-512/224 and SHA-512/256 are based on SHA-512, there is no efficiency benefit for using these three SHA mechanisms rather than using SHA-512.
“Also note that since SHA-384, SHA-512/224 and SHA-512/256 are based on SHA-512, there is no efficiency benefit for using these three SHA mechanisms, rather than using SHA-512.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationnone givenThe complex discard method coincides with the simple discard method when t = 1.
“The complex discard method coincides with the simple discard method when t = 1.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenIf the additional input is kept secret and has sufficient entropy, the input can provide more assurance when recovering from the compromise of the entropy input, the seed or one or more DRBG internal states.
“If the additional input is kept secret and has sufficient entropy, the input can provide more assurance when recovering from the compromise of the entropy input, the seed or one or more DRBG internal states.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
InterpretationreasoningA possible disadvantage of the simple discard method, in general, is that the time needed to generate such a random a is not a fixed length of time because of the conditional loop.
“A possible disadvantage of this method, in general, is that the time needed to generate such a random a is not a fixed length of time because of the conditional loop.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim. May combine two claims.
Interpretationnone givenThe hash-based DRBG mechanisms specified in this Recommendation have been designed to use any approved hash function and may be used by consuming applications requiring various security strengths, providing that the appropriate hash function is used and sufficient entropy is obtained for the seed.
“The hash-based DRBG mechanisms specified in this Recommendation have been designed to use any approved hash function and may be used by consuming applications requiring various security strengths, providing that the appropriate hash function is used and sufficient entropy is obtained for the seed.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationIn accordance with Table 2 in Section 10.1, security strengths of 112, 128, 192 and 256 bits may be instantiated.
“In accordance with Table 2 in Section 10.1, security strengths of 112, 128, 192 and 256 bits may be instantiated.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Table 2 in Section 10.1
Not checked in the free run.
Classified as probably not a substantial claim.
Study design and conductreasoningEntropy input used for testing shall not be used for normal operational use.
“Therefore, entropy input used for testing shall not be used for normal operational use.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenAny entropy input used for testing (either for validation testing or health testing) may be publicly known.
“Note that any entropy input used for testing (either for validation testing or health testing) may be publicly known.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S4 (based).
Interpretationnone givenReseeding will insert additional entropy into the generation of pseudorandom bits.
“Reseeding will insert additional entropy into the generation of pseudorandom bits.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based). May combine two claims.
Interpretationnone givenThe Get_entropy_input call could return a status of ERROR_FLAG to indicate that entropy is currently unavailable, and could return CATASTROPHIC_ERROR_FLAG to indicate that an entropy source failed.
“The Get_entropy_input call could return a status of ERROR_FLAG to indicate that entropy is currently unavailable, and could return CATASTROPHIC_ERROR_FLAG to indicate that an entropy source failed.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationIn accordance with Table 2 in Section 10.1, the 112-and 128-bit security strengths may be instantiated.
“In accordance with Table 2 in Section 10.1, the 112-and 128-bit security strengths may be instantiated.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Table 2 in Section 10.1
Not checked in the free run.
Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Study design and conductnone givenA DRBG implementation shall perform self-tests to obtain assurance that the DRBG continues to operate as designed and implemented (health testing).
“A DRBG implementation shall perform self-tests to obtain assurance that the DRBG continues to operate as designed and implemented (health testing).”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
InterpretationreasoningIf r/2^m is close to 1, then the simple discard method is simple and efficient.
“If r/2 m is close to 1, then the above method is simple and efficient.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based). May combine two claims.
Interpretationnone givenThe error codes may provide information about the reason for the error; for example, when ERROR_FLAG is returned because of an incorrect input parameter, the ERROR_FLAG may indicate the problem.
“The error codes may, in fact, provide information about the reason for the error; for example, when ERROR_FLAG is returned because of an incorrect input parameter, the ERROR_FLAG may indicate the problem.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S4 (based).
Interpretationnone givenThe complex discard method produces random numbers (a0, a1, ..., at-1) with no skew.
“This method produces random numbers (a 0 , a 1 , … , a t-1 ) with no skew.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationnone givenA possible disadvantage of the complex discard method, in general, is that the time needed to generate these numbers is not a fixed length of time because of the conditional loop.
“A possible disadvantage of this method, in general, is that the time needed to generate these numbers is not a fixed length of time because of the conditional loop.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenThe simple modular method can be coded to take constant time.
“The simple modular method can be coded to take constant time.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationnone givenA DRBG does not rely on additional input to provide entropy.
“Note that a DRBG does not rely on additional input to provide entropy, even though entropy could be provided in the additional input”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationnone givenThe use of additional input may be a means of providing more entropy for the DRBG internal state that will increase assurance that the entropy requirements are met.
“The use of additional input may be a means of providing more entropy for the DRBG internal state that will increase assurance that the entropy requirements are met.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based). May combine two claims.
Interpretationnone givenThe ratio r/2^m is a measure of the efficiency of the simple discard technique, and this ratio will always satisfy 0.5 < r/2^m ≤ 1.
“The ratio r/2 m is a measure of the efficiency of the technique, and this ratio will always satisfy 0.5 < r/2 m ≤ 1.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
InterpretationreasoningPrediction resistance can be provided when the randomness source is or has direct or indirect access to an entropy source or an NRBG.
“Prediction resistance can be provided when the randomness source is or has direct or indirect access to an entropy source or an NRBG (see Section 8.6.5).”
Quote in the paperSubstantial claim- The authors state this as an assumption: The adversary is incapable of performing work that matches the claimed security strength of the RBG.
May combine two claims.
Interpretationnone givenThe ratio r^t/2^m is a measure of the efficiency of the complex discard technique, and this ratio will always satisfy 0.5 < r^t/2^m ≤ 1.
“The ratio r t /2 m is a measure of the efficiency of the technique, and this ratio will always satisfy 0.5 < r t /2 m ≤ 1.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing), S4 (based). May combine two claims.
Interpretationnone givenA personalization string might contain values unknown to an attacker, or values that tend to differentiate this DRBG instantiation from all others.
“This personalization string might contain values unknown to an attacker, or values that tend to differentiate this DRBG instantiation from all others.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Interpretationnone givenWithout the explicit prediction resistance request, the entropy input could be provided from either a DRBG with no access to an entropy source (i.e., fresh entropy would not be provided), or the entropy input could be provided by an entropy source or by an RBG with access to an entropy source (i.e., fresh entropy would be provided in these cases).
“Without the explicit prediction resistance request, the entropy input could be provided from either a DRBG with no access to an entropy source (i.e., fresh entropy would not be provided), or the entropy input could be provided by an entropy source or by an RBG with access to an entropy source (i.e., fresh entropy would be provided in these cases).”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S4 (based).
Interpretationnone givenBacktracking resistance can be provided by ensuring that the DRBG generation algorithm is a one-way function.
“Backtracking resistance can be provided by ensuring that the DRBG generation algorithm is a one-way function.”
Quote in the paperNot a substantial claim- The authors state this as an assumption: The adversary is incapable of performing the work required to negate the claimed security strength of the DRBG.
Classified as probably not a substantial claim.
InterpretationreasoningPrediction resistance can be provided only by ensuring that a DRBG is effectively reseeded with fresh entropy between producing output for consecutive DRBG requests.
“Prediction resistance can be provided only by ensuring that a DRBG is effectively reseeded with fresh entropy between producing output for consecutive DRBG requests.”
Quote in the paperSubstantial claim- The authors state this as an assumption: The adversary is incapable of performing work that matches the claimed security strength of the RBG.
Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Study design and conductnone givenAll DRBG mechanisms in this Recommendation have been designed to provide backtracking resistance.
“All DRBG mechanisms in this Recommendation have been designed to provide backtracking resistance.”
Quote in the paperNot a substantial claim- The authors state this as an assumption: The adversary is incapable of performing the work required to negate the claimed security strength of the DRBG.
Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Study design and conductnone givenHealth tests on the DRBG mechanism shall be implemented within a DRBG mechanism boundary or sub-boundary in order to determine that the process continues to operate as designed and implemented.
“Health tests on the DRBG mechanism shall be implemented within a DRBG mechanism boundary or sub-boundary in order to determine that the process continues to operate as designed and implemented.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
InterpretationreasoningIf r/2^m is close to 0.5, then the simple discard method is less efficient.
“However, if r/2 m is close to 0.5, then the simple discard method is less efficient”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationnone givenEach HMAC_DRBG generate request involves additional overhead equivalent to processing 2048 extra bits with SHA-256.
“Each generate request also involves additional overhead equivalent to processing 2048 extra bits with SHA-256.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenA general-purpose hash function implementation can always be used to implement HMAC.
“However, a general-purpose hash function implementation can always be used to implement HMAC.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
InterpretationreasoningWhen instantiation is performed using this method, a nonce is required, whereas using the method in Section 10.2.1.3.1 does not require a nonce, since full entropy is provided when using that method.
“When instantiation is performed using this method, a nonce is required, whereas using the method in Section 10.2.1.3.1 does not require a nonce, since full entropy is provided when using that method.”
Quote in the paperNot a substantial claimMay combine two claims.
InterpretationreasoningFor an attacker who sees 2^64 bits of output from TDEA CTR_DRBG across at least one reseed, the TDEA CTR_DRBG received 2^45 generate requests; an ideal random sequence has a probability of about 2^-6 of having a duplicate block in one of the generate outputs, while CTR_DRBG outputs will never have one.
“In this case, the TDEA CTR_DRBG received 2 45 generate requests.An ideal random sequence has a probability of about 2 -6 of having a duplicate block in one of the generate outputs; the CTR_DRBG outputs will never have one.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenIf the hash function is replaced by a random oracle, Hash_DRBG is secure.
“If the hash function is replaced by a random oracle, Hash_DRBG is secure.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenCTR_DRBG is parallelizable.
“Furthermore, CTR_DRBG is parallelizable.”
Quote in the paperNot a substantial claimMay combine two claims.
InterpretationreasoningFor AES CTR_DRBG, each generate request may produce no more than 2^19 bits, which means 2^12 128-bit blocks; in an ideal random sequence of 2^12 128-bit blocks, the probability that any two blocks will be the same is approximately 2^-105; AES CTR_DRBG will never provide a generate output with duplicate blocks.
“The case for AES CTR_DRBG is similar: each generate request may produce no more than 2 19 bits, which means 2 12 128-bit blocks.In an ideal random sequence of 2 12 128-bit blocks, the probability that any two blocks will be the same is approximately 2 -105 ; AES CTR_DRBG will never provide a generate output with duplicate blocks.”
Quote in the paperSubstantial claimMay combine two claims.
InterpretationreasoningTDEA CTR_DRBG permits the use of up to 2^32 generate requests; an ideal random source providing 2^32 sequences of 128 64-bit blocks would have a probability of about 2^-19 of having a duplicate block in one of those sequences, while CTR_DRBG will never have such a duplicate block.
“TDEA CTR_DRBG permits the use of up to 2 32 generate requests.An ideal random source, providing 2 32 sequences of 128 64-bit blocks, would have a probability of about 2 -19 of having a duplicate block in one of those sequences of 128 64-bit blocks; the CTR_DRBG will never have such a duplicate block.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S4 (based).
Interpretationnone givenThe security of CTR_DRBG is directly based on the security of the underlying block cipher algorithm, in the sense that, as long as some limits on the total number of outputs are observed, any attack on CTR_DRBG represents an attack on the underlying block cipher algorithm.
“The security of CTR_DRBG is directly based on the security of the underlying block cipher algorithm, in the sense that, as long as some limits on the total number of outputs are observed, any attack on CTR_DRBG represents an attack on the underlying block cipher algorithm.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Interpretationnone givenWhen a derivation function is used, CTR_DRBG can process the personalization string and any additional input in the same way as any other DRBG mechanism, but at a cost in performance because of the use of the derivation function.
“When a derivation function is used, CTR_DRBG can process the personalization string and any additional input in the same way as any other DRBG mechanism, but at a cost in performance because of the use of the derivation function (as opposed to not using the derivation function; see below).”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Interpretationnone givenThe block cipher DRBG mechanism specified in this Recommendation has been designed to use any approved block cipher algorithm and may be used by consuming applications requiring various security strengths, providing that the appropriate block cipher algorithm and key length are used, and sufficient entropy is obtained for the seed.
“The block cipher DRBG mechanism specified in this Recommendation has been designed to use any approved block cipher algorithm and may be used by consuming applications requiring various security strengths, providing that the appropriate block cipher algorithm and key length are used, and sufficient entropy is obtained for the seed.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Interpretationnone givenWithin a Hash_DRBG generate request, each outlen-bit block of output requires one hash function computation and several addition operations, and an additional hash function computation is required to provide backtracking resistance.
“Within a generate request, each outlen-bit block of output requires one hash function computation and several addition operations; an additional hash function computation is required to provide the backtracking resistance.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductreasoningHash_DRBG updates the secret value V at the end of each generate request before returning the pseudorandom output to the consuming application in order to prevent backtracking.
“At the end of the generate request, and before the pseudorandom output is returned to the consuming application, the secret value V is updated in order to prevent backtracking.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenHash_DRBG produces pseudorandom output bits in about half the time required by HMAC_DRBG.
“Hash_DRBG produces pseudorandom output bits in about half the time required by HMAC_DRBG.”
Quote in the paperNot a substantial claimMay combine two claims.
InterpretationreasoningAn ideal random source would have a very small probability (about 2^-51) of producing a pair of identical 64-bit blocks within that generate request output; each generate request from CTR_DRBG is generated by running the block cipher in counter mode, so there can never be a duplicate block produced within a generate request output.
“An ideal random source would have a very small probability (about 2 -51 ) of producing a pair of identical 64-bit blocks within that generate request output; each generate request from the CTR_DRBG is generated by running the block cipher in counter mode, so there can never be a duplicate block produced within a generate request output.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenFor large generate requests, CTR_DRBG produces outputs at the same speed as the underlying block cipher algorithm encrypts data.
“For large generate requests, CTR_DRBG produces outputs at the same speed as the underlying block cipher algorithm encrypts data.”
Quote in the paperNot a substantial claimMay combine two claims.
InterpretationreasoningAn attacker looking at the sequence will not be able to determine that it came from CTR_DRBG, though he would have a pretty large advantage in a distinguishing game.
“An attacker looking at the sequence will not be able to determine that it came from the CTR_DRBG, though he would have a pretty large advantage in a distinguishing game.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing), S4 (based).
Interpretationnone givenIt is difficult to relate the properties of the hash function required by Hash_DRBG with common properties such as collision resistance, pre-image resistance, or pseudorandomness.
“It is difficult to relate the properties of the hash function required by Hash_DRBG with common properties, such as collision resistance, pre-image resistance, or pseudorandomness.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenIn general, even relatively weak hash functions seem to be quite strong when used in the HMAC construction.
“In general, even relatively weak hash functions seem to be quite strong when used in the HMAC construction.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based). May combine two claims.
Interpretationnone givenWhen instantiation is performed using this method, the entropy input may or may not have full entropy; in either case, a nonce is required.
“When instantiation is performed using this method, the entropy input may or may not have full entropy; in either case, a nonce is required.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing).
InterpretationreasoningFew if any consuming applications are expected to need output bits faster than HMAC_DRBG can provide them.
“Note, however, that hash functions are typically quite fast; few if any consuming applications are expected to need output bits faster than HMAC_DRBG can provide them.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Study design and conductnone givenAt the end of a generation request, HMAC_DRBG generates a new Key and V, each requiring one HMAC computation.
“At the end of a generation request, the HMAC_DRBG generates a new Key and V, each requiring one HMAC computation.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
InterpretationreasoningSuch an implementation may be seeded by any approved randomness source that may or may not provide full entropy.
“Such an implementation may be seeded by any approved randomness source that may or may not provide full entropy.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Interpretationnone givenFor TDEA, the input and output block lengths are 64 bits, and for AES, the lengths are 128 bits.
“Note that for TDEA, the input and output block lengths are 64 bits, and for AES, the lengths are 128 bits.”
Quote in the paperNot a substantial claimMay combine two claims.
InterpretationreasoningFor TDEA CTR_DRBG, each generate request is limited to 2^13 bits, and at most 2^32 such requests may be made.
“However, the smaller block size of TDEA imposes more constraints: each generate request is limited to 2 13 bits, and at most, 2 32 such requests may be made.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenAt the end of each CTR_DRBG generate request, work equivalent to two, three or four encryptions is performed, depending on the choice of underlying block cipher algorithm, to generate new keys and counters for the next generate request.
“At the end of each generate request, work equivalent to two, three or four encryptions is performed, depending on the choice of underlying block cipher algorithm, to generate new keys and counters for the next generate request.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Interpretationnone givenHMAC_DRBG produces pseudorandom outputs considerably more slowly than the underlying hash function processes inputs; for SHA-256, a long generate request produces output bits at about 1/4 of the rate that the hash function can process input bits.
“HMAC_DRBG produces pseudorandom outputs considerably more slowly than the underlying hash function processes inputs; for SHA-256, a long generate request produces output bits at about 1/4 of the rate that the hash function can process input bits.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
Interpretationnone givenWhen a derivation function is not used, CTR_DRBG is more efficient when the personalization string and any additional input are provided, but is less flexible because the lengths of the personalization string and additional input cannot exceed seedlen bits.
“When a derivation function is not used, CTR_DRBG is more efficient when the personalization string and any additional input are provided, but is less flexible because the lengths of the personalization string and additional input cannot exceed seedlen bits.”
Quote in the paperNot a substantial claimMay combine two claims.
Interpretationnone givenThere is not a reduction proof from the hash function's collision resistance properties to the security of the DRBG; the security of HMAC_DRBG ultimately relies on the pseudorandomness properties of the underlying hash function.
“On the other hand, there is not a reduction proof from the hash function's collision resistance properties to the security of the DRBG; the security of HMAC_DRBG ultimately relies on the pseudorandomness properties of the underlying hash function.”
Quote in the paperSubstantial claim- The authors state this as an assumption: An approved hash function used in the HMAC construction is a pseudorandom function family.
Classified as probably not a substantial claim.
InterpretationreasoningSuch implementations must be seeded by a randomness source that provides full entropy (e.g., an approved entropy source that has full entropy output or an approved NRBG).
“Such implementations must be seeded by a randomness source that provides full entropy (e.g., an approved entropy source that has full entropy output or an approved NRBG).”
Quote in the paperSubstantial claimClassified as probably not a substantial claim.
Interpretationnone givenThere are known problems with Hash_DRBG when it is instantiated with insufficient entropy for the requested security strength and later provided with enough entropy via additional input during a generate request.
“There are known problems with Hash_DRBG when the DRBG is instantiated with insufficient entropy for the requested security strength, and then later provided with enough entropy to attain the amount of entropy required for the security strength, via the inclusion of additional input during a generate request.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
InterpretationreasoningHash_DRBG's Generate function is parallelizable because it uses counter mode.
“The Generate function is parallelizable, since it uses the counter mode.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationnone givenThe DRBG mechanisms specified in this Recommendation have different performance characteristics, implementation issues, and security assumptions.
“The DRBG mechanisms specified in this Recommendation have different performance characteristics, implementation issues, and security assumptions.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based). May combine two claims.
Interpretationnone givenThe distinguishing attack is theoretical and poses no practical threat to any real-world application of the DRBG.
“However, the distinguishing attack is theoretical -it poses no practical threat to any real-world application of the DRBG.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
Interpretationown dataFor each hash function, up to 2^48 generate requests may be made, each of up to 2^19 bits.
“As shown in Table 2 of Section 10.1, for each hash function, up to 2 48 generate requests may be made, each of up to 2 19 bits.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationIn accordance with Table 3 in Section 10.2.1, security strengths of 112 and 128 bits may be supported.
“In accordance with Table 3 in Section 10.2.1, security strengths of 112 and 128 bits may be supported.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Table 3 in Section 10.2.1
Not checked in the free run.
The authors state this as an assumption.
The adversary is incapable of performing the work required to negate the claimed security strength of the DRBG.
“This assumes that the adversary is incapable of performing the work required to negate the claimed security strength of the DRBG.”
The authors state this as an assumption.
The adversary is incapable of performing work that matches the claimed security strength of the RBG.
“incapable of performing work that matches the claimed security strength of the RBG”
The paper relies on this without support.
The security of the DRBG depends on the secrecy of the entropy input.
“The security of the DRBG depends on the secrecy of the entropy input.”
The authors state this as an assumption.
An approved hash function used in the HMAC construction is a pseudorandom function family.
“The security of HMAC_DRBG is based on the assumption that an approved hash function used in the HMAC construction is a pseudorandom function family.”
The authors state this as an assumption.
The pseudorandomness of HMAC is a widely used assumption in designs.
“Note that the pseudorandomness of HMAC is a widely used assumption in designs, and the HMAC_DRBG requires far less demanding properties of the underlying hash function than Hash_DRBG.”
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Weaknesses in random number generation have historically led to severe security breaches.
“Weaknesses in random number generation (RNG) have historically led to severe security breaches1.”
From Raw QPP-RNG randomness via system jitter across platforms: a NIST SP 800-90B evaluation (2025) · cites this paper as [1]
Section 8.6.3 (page not provided) says that insufficient entropy could be fatal to security, supporting the claim that weak random-number generation poses a serious risk. The passages do not report historical security breaches caused by such weaknesses, so the claim of breaches having occurred is unsupported. (LLM, conf=0.83)
Experimental — accuracy not yet measured
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
Each contradiction between two passages listed here was confirmed by an independent check.
HMAC_DRBG example names a nonexistent state value
MinorThe example lists Key, not C, in its internal state, but then identifies V and C as its bitstrings.
“The internal state contains the values for V, Key, reseed_counter, and security_strength, where V and C are bitstrings, and reseed_counter and security_strength are integers.”
“The values of V and Key are the critical values of the internal state upon which the security of this DRBG mechanism depends (i.e., V and Key are the "secret values" of the internal state).”
CTR_DRBG example checks a prediction-resistance flag it says is absent
MinorThe example says it does not store a prediction_resistance_flag, but its generate-function pseudocode tests that flag to decide whether to reseed. It should instead act on the request parameter described in the example.
“Since prediction resistance is known to be supported, there is no need for prediction_resistance_flag in the internal state.”
“If ((reseed_required_flag = 1) OR (prediction_resistance_flag = 1)), then 7.1 status = CTR_DRBG_Reseed_function (state_handle, prediction_resistance_request, additional_input).”
TDEA request count cannot produce the stated output length
MinorAt the stated maximum of 2^13 bits per request, producing 2^64 bits requires 2^51 requests, not 2^45. The stated 2^45 requests would produce only 2^58 bits.
“an attacker who sees 2 64 bits of output from the TDEA CTR_DRBG across at least one reseed”
“In this case, the TDEA CTR_DRBG received 2 45 generate requests.”
Cites
1 retracted
Recommendation for Random Bit Generator (RBG) Constructions
Barker, E. B., Kelsey, J. M., McKay, K. A., Roginsky, A. L., & Turan, M. S. (2022) · doi:10.6028/nist.sp.800-90c.3pd · Cited by 56 · see citing works
Self-citationRetractedRecommendation for the Entropy Sources Used for Random Bit Generation
Turan, M. S., Barker, E., Kelsey, J., McKay, K. A., Baish, M. L., & Boyle, M. (2018) · NIST Special Publication 800-90B · doi:10.6028/nist.sp.800-90b · Cited by 489 · see citing works
Self-citationRecommendation for applications using approved hash algorithms
Dang, Q. H. (2012) · doi:10.6028/nist.sp.800-107r1 · Cited by 137 · see citing works
Security Bounds for the NIST Codebook-based Deterministic Random Bit Generator.Preprint
Campagna, M. (2006) · IACR Cryptology ePrint Archive · Cited by 12 · see citing works
Flagged first, then by citations
Cited by
Sorted by citations
Internet of Things: A survey on the security of IoT frameworks
Ammar, M., Russello, G., & Bruno Crispo, A. (2017) · Journal of Information Security and Applications · doi:10.1016/j.jisa.2017.11.002 · Cited by 874 · see citing works
Recommendation for the Entropy Sources Used for Random Bit Generation
Turan, M. S., Barker, E., Kelsey, J., McKay, K. A., Baish, M. L., & Boyle, M. (2018) · NIST Special Publication 800-90B · doi:10.6028/nist.sp.800-90b · Cited by 489 · see citing works
Self-citationRecommendation for Key Management Part 1: General
Barker, E. B. (2016) · doi:10.6028/nist.sp.800-57pt1r4 · Cited by 396 · see citing works
Self-citationRecommendation for key management: part 1 - general
Barker, E. (2020) · doi:10.6028/nist.sp.800-57pt1r5 · Cited by 271 · see citing works
Self-citationDigital identity guidelines: authentication and lifecycle management
Grassi, P. A., Fenton, J. L., Newton, E. M., Perlner, R. A., Regenscheid, A. R., Burr, W. E., Richer, J. P., Lefkovitz, N. B., Danker, J. M., Choong, Y.-Y., et al. (2017) · doi:10.6028/nist.sp.800-63b · Cited by 261 · see citing works
Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths
Barker, E. B., & Roginsky, A. L. (2015) · doi:10.6028/nist.sp.800-131ar1 · Cited by 191 · see citing works
Self-citationTransitioning the use of cryptographic algorithms and key lengths
Barker, E. B., & Roginsky, A. L. (2019) · doi:10.6028/nist.sp.800-131ar2 · Cited by 179 · see citing works
Self-citationDigital Signature Standard (DSS)
(2023) · doi:10.6028/nist.fips.186-5 · Cited by 169 · see citing works
Stateless Hash-Based Digital Signature Standard
National Institute of Standards and Technology (US) (2024) · doi:10.6028/nist.fips.205 · Cited by 131 · see citing works
ZRTP: Media Path Key Agreement for Unicast Secure RTP
Zimmermann, P. R., & Callas, J. (2011) · doi:10.17487/rfc6189 · Cited by 112 · see citing works
Recommendation for Stateful Hash-Based Signature Schemes
Cooper, D. A., Apon, D., Dang, Q. H., Davidson, M. S., Dworkin, M. J., & Miller, C. A. (2020) · doi:10.6028/nist.sp.800-208 · Cited by 106 · see citing works
Digital Signature Standard (DSS)Preprint
Regenscheid, A. (2019) · doi:10.6028/nist.fips.186-5-draft · Cited by 102 · see citing works
Module-Lattice-Based Key-Encapsulation Mechanism Standard
(2023) · doi:10.6028/nist.fips.203.ipd · Cited by 92 · see citing works
RetractedPadgette, J., Bahr, J., Batra, M., Holtmann, M., Smithbey, R., Chen, L., & Scarfone, K. A. (2017) · doi:10.6028/nist.sp.800-121r2 · Cited by 86 · see citing works
Recommendation for password-based key derivation :
Turan, M. S., Barker, E. B., Burr, W. E., & Chen, L. (2010) · doi:10.6028/nist.sp.800-132 · Cited by 85 · see citing works
Self-citationRecommendation for key derivation using pseudorandom functions
Chen, L. (2022) · doi:10.6028/nist.sp.800-108r1 · Cited by 82 · see citing works
Recommendation for pair-wise key establishment using integer factorization cryptography
Barker, E., Chen, L., Roginsky, A., Vassilev, A., Davis, R., & Simon, S. (2019) · doi:10.6028/nist.sp.800-56br2 · Cited by 81 · see citing works
Self-citationModule-Lattice-Based Digital Signature Standard
(2023) · doi:10.6028/nist.fips.204.ipd · Cited by 78 · see citing works
RetractedCompressive Diffusion Strategies Over Distributed Networks for Reduced Communication Load
Sayin, M. O., & Kozat, S. S. (2014) · IEEE Transactions on Signal Processing · doi:10.1109/tsp.2014.2347917 · Cited by 77 · see citing works
Recommendation for Key Management Part 3: Application-Specific Key Management Guidance
Barker, E. B., & Dang, Q. H. (2015) · doi:10.6028/nist.sp.800-57pt3r1 · Cited by 77 · see citing works
Self-citationBanerjee, U., Wright, A., Juvekar, C., Waller, M., Arvind, A., & Chandrakasan, A. P. (2019) · IEEE Journal of Solid-State Circuits · doi:10.1109/jssc.2019.2915203 · Cited by 69 · see citing works
Machine Learning Cryptanalysis of a Quantum Random Number Generator
Truong, N. D., Haw, J. Y., Assad, S. M., Lam, P. K., & Kavehei, O. (2018) · IEEE Transactions on Information Forensics and Security · doi:10.1109/tifs.2018.2850770 · Cited by 66 · see citing works
Fan, X., & Chai, Q. (2018) · EAI International Conference on Mobile and Ubiquitous Systems: Computing, Networking and Services (MobiQuitous) · doi:10.1145/3286978.3287023 · Cited by 66 · see citing works
Recommendation for Key Derivation Using Pseudorandom Functions, Revision 1 (Draft)Preprint
Chen, L. (2021) · doi:10.6028/nist.sp.800-108r1-draft · Cited by 60 · see citing works
McKay, K. A., & Cooper, D. A. (2019) · doi:10.6028/nist.sp.800-52r2 · Cited by 66 · see citing works
Recommendation for Random Bit Generator (RBG) Constructions
Barker, E. B., Kelsey, J. M., McKay, K. A., Roginsky, A. L., & Turan, M. S. (2022) · doi:10.6028/nist.sp.800-90c.3pd · Cited by 56 · see citing works
Self-citationRetractedMeteor: Cryptographically Secure Steganography for Realistic Distributions
Kaptchuk, G., Jois, T. M., Green, M., & Rubin, A. D. (2021) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/3460120.3484550 · Cited by 58 · see citing works
Recommendation for Cryptographic Key Generation
Barker, E. B., & Roginsky, A. L. (2012) · doi:10.6028/nist.sp.800-133 · Cited by 54 · see citing works
Self-citationStateless Hash-Based Digital Signature Standard
(2023) · doi:10.6028/nist.fips.205.ipd · Cited by 52 · see citing works
RetractedCao, Y., Liu, W., Qin, L., Liu, B., Chen, S., Ye, J., Xia, X., & Wang, C. (2022) · Entropy · doi:10.3390/e24111566 · Cited by 46 · see citing works
Long-Term Test of a Fast and Compact Quantum Random Number Generator
Marangon, D. G., Plews, A., Lucamarini, M., Dynes, J. F., Sharpe, A. W., Yuan, Z., & Shields, A. J. (2018) · Journal of Lightwave Technology · doi:10.1109/jlt.2018.2841773 · Cited by 42 · see citing works
NIST First Call for Multi-Party Threshold Schemes
Peralta, R., & Brandão, L. T. A. N. (2023) · doi:10.6028/nist.ir.8214c.ipd · Cited by 41 · see citing works
RetractedRandom Number Generators: Principles and Applications
Bikos, A. N., Nastou, P. E., Petroudis, G., & Stamatiou, Y. C. (2023) · Cryptography · doi:10.3390/cryptography7040054 · Cited by 40 · see citing works
PUF-Based Authentication-Oriented Architecture for Identification Tags
Rullo, A., Felicetti, C., Vatalaro, M., Rose, R. D., Lanuzza, M., Crupi, F., & Saccà, D. (2024) · IEEE Transactions on Dependable and Secure Computing · doi:10.1109/tdsc.2024.3387568 · Cited by 38 · see citing works
Performance Analysis of Cryptographic Pseudorandom Number Generators
Aljohani, M. D., Ahmad, I., Basheri, M., & Alassafi, M. O. (2019) · IEEE Access · doi:10.1109/access.2019.2907079 · Cited by 37 · see citing works
An Asynchronous and Low-Power True Random Number Generator Using STT-MTJ
Perach, B., & Kvatinsky, S. (2019) · IEEE Transactions on Very Large Scale Integration (VLSI) Systems · doi:10.1109/tvlsi.2019.2927816 · Cited by 37 · see citing works
Kornaros, G., Tomoutzoglou, O., Mbakoyiannis, D., Karadimitriou, N., Coppola, M., Montanari, E., Deligiannis, I., & Gherardi, G. (2020) · Journal of Systems Architecture · doi:10.1016/j.sysarc.2020.101761 · Cited by 37 · see citing works
Cryptographically Secure Pseudo-Random Number Generator IP-Core Based on SHA2 Algorithm
Baldanzi, L., Crocetti, L., Falaschi, F., Bertolucci, M., Belli, J., Fanucci, L., & Saponara, S. (2020) · Sensors · doi:10.3390/s20071869 · Cited by 37 · see citing works
Quantum Cryptography—A Simplified Undergraduate Experiment and Simulation
Bloom, Y., Fields, I., Maslennikov, A., & Rozenman, G. G. (2022) · Physics · doi:10.3390/physics4010009 · Cited by 37 · see citing works
DNSSEC Operational Practices, Version 2
Kolkman, O., Mekking, W., & Gieben, R. (2012) · doi:10.17487/rfc6781 · Cited by 35 · see citing works
Recommendation for cryptographic key generation
Barker, E. B., & Roginsky, A. L. (2019) · doi:10.6028/nist.sp.800-133r1 · Cited by 36 · see citing works
Self-citationRecommendation for applications using approved hash algorithms
Dang, Q. H. (2009) · doi:10.6028/nist.sp.800-107 · Cited by 34 · see citing works
Combined Pseudo-Random Sequence Generator for Cybersecurity
Maksymovych, V., Shabatura, M., Гарасимчук, О. І., Shevchuk, R., Sawicki, P., & Zając, T. (2022) · Sensors · doi:10.3390/s22249700 · Cited by 28 · see citing works
A Profile for U. S. Federal Cryptographic Key Management Systems
Barker, E. B., Smid, M. E., & Branstad, D. K. (2015) · doi:10.6028/nist.sp.800-152 · Cited by 32 · see citing works
Self-citationEntropy as a Service: Unlocking Cryptography's Full Potential
Vassilev, A. T., & Staples, R. (2016) · Computer · doi:10.1109/mc.2016.275 · Cited by 27 · see citing works
Recommendation for Pair-Wise Key-Establishment Schemes Using Integer Factorization Cryptography
Barker, E. B., Chen, L., & Moody, D. (2014) · doi:10.6028/nist.sp.800-56br1 · Cited by 26 · see citing works
Self-citationSoK: Security Models for Pseudo-Random Number Generators
Ruhault, S. (2017) · IACR Transactions on Symmetric Cryptology · doi:10.46586/tosc.v2017.i1.506-544 · Cited by 25 · see citing works
Ganesh, R., Khan, B. U. I., Khan, A. R., & Kamsin, A. (2025) · International Journal of Information Security · doi:10.1007/s10207-025-01116-x · Cited by 24 · see citing works
Asynchronous Probabilistic Couplings in Higher-Order Separation Logic
Gregersen, S. O., Aguirre, A., Haselwarter, P. G., Tassarotti, J., & Birkedal, L. (2024) · Proceedings of the ACM on Programming Languages · doi:10.1145/3632868 · Cited by 24 · see citing works
NIST roadmap toward criteria for threshold schemes for cryptographic primitives
Brandão, L. T. A. N., Davidson, M. S., & Vassilev, A. T. (2020) · doi:10.6028/nist.ir.8214a · Cited by 24 · see citing works
Chaotic Encryption Applied to Optical Ethernet in Industrial Control Systems
Pérez-Resa, A., Garcia-Bosque, M., Sánchez‐Azqueta, C., & Celma, S. (2019) · IEEE Transactions on Instrumentation and Measurement · doi:10.1109/tim.2019.2896550 · Cited by 23 · see citing works
An Analysis of NIST SP 800-90A
Woodage, J., & Shumow, D. (2019) · Lecture notes in computer science · doi:10.1007/978-3-030-17656-3_6 · Cited by 23 · see citing works
An Improved Authentication Scheme for BLE Devices with No I/O Capabilities
Gupta, C., & Varshney, G. (2023) · Computer Communications · doi:10.1016/j.comcom.2023.01.001 · Cited by 21 · see citing works
Recommendation for cryptographic key generation
Barker, E. B., Roginsky, A. L., & Davis, R. (2020) · doi:10.6028/nist.sp.800-133r2 · Cited by 35 · see citing works
Self-citationRecommendation for Stateful Hash-Based Signature SchemesPreprint
Cooper, D. A. (2019) · doi:10.6028/nist.sp.800-208-draft · Cited by 21 · see citing works
POCA: First Power-on Chip Authentication in Untrusted Foundry and Assembly
Sami, M. S. U. I., Rahman, F., Cron, A., Donchin, D. R., Borza, M., Farahmandi, F., & Tehranipoor, M. M. (2021) · IEEE International Symposium on Hardware Oriented Security and Trust (HOST) · doi:10.1109/host49136.2021.9702285 · Cited by 20 · see citing works
Gewehr, C. G. D. A., Luza, L., & Moraes, F. (2024) · IEEE Access · doi:10.1109/access.2024.3416812 · Cited by 20 · see citing works
On The Study of EEG-based Cryptographic Key Generation
Nguyen, D., Tran, D., Sharma, D. K., & Ma, W. (2017) · Procedia Computer Science · doi:10.1016/j.procs.2017.08.126 · Cited by 20 · see citing works
Randomized hashing for digital signatures
Dang, Q. H. (2009) · doi:10.6028/nist.sp.800-106 · Cited by 19 · see citing works
Hales, T. (2014) · Notices of the American Mathematical Society · doi:10.1090/noti1078 · Cited by 18 · see citing works
SecuCode: Intrinsic PUF Entangled Secure Wireless Code Dissemination for Computational RFID Devices
Su, Y., Gao, Y., Chesser, M., Kavehei, O., Sample, A. P., & Ranasinghe, D. C. (2019) · IEEE Transactions on Dependable and Secure Computing · doi:10.1109/tdsc.2019.2934438 · Cited by 18 · see citing works
A Novel Secure Root Key Updating Scheme for LoRaWANs Based on CTR_AES DRBG 128
Hayati, N. Q., Ramli, K., Windarta, S., & Suryanegara, M. (2022) · IEEE Access · doi:10.1109/access.2022.3150281 · Cited by 17 · see citing works
Efficient Polar Code-Based Physical Layer Encryption Scheme
Hooshmand, R., & Aref, M. R. (2017) · IEEE Wireless Communications Letters · doi:10.1109/lwc.2017.2735401 · Cited by 17 · see citing works
Padgette, J., Bahr, J., Batra, M., Holtmann, M., Smithbey, R., Chen, L., & Scarfone, K. A. (2022) · doi:10.6028/nist.sp.800-121r2-upd1 · Cited by 16 · see citing works
Aging-Resilient SRAM-based True Random Number Generator for Lightweight Devices
Wang, W., Guin, U., & Singh, A. D. (2020) · Journal of Electronic Testing · doi:10.1007/s10836-020-05881-6 · Cited by 15 · see citing works
Digital Random Number Generator Hardware Accelerator IP-Core for Security Applications
Baldanzi, L., Crocetti, L., Falaschi, F., Belli, J., Fanucci, L., & Saponara, S. (2020) · Lecture notes in electrical engineering · doi:10.1007/978-3-030-37277-4_14 · Cited by 14 · see citing works
Firmware Integrity Protection: A Survey
Marchand, A., Imine, Y., Ouarnoughi, H., Tarridec, T., & Gallais, A. (2023) · IEEE Access · doi:10.1109/access.2023.3298833 · Cited by 14 · see citing works
Toward All-Optical Layered Encryption: A Feasibility Analysis of Optical Stream Cipher
Engelmann, A., & Jukan, A. (2019) · IEEE Transactions on Information Forensics and Security · doi:10.1109/tifs.2019.2904793 · Cited by 14 · see citing works
Enabling Ubiquitous Hardware Security via Energy-Efficient Primitives and Systems : (Invited Paper)
Alioto, M., & Taneja, S. (2019) · Custom Integrated Circuits Conference · doi:10.1109/cicc.2019.8780123 · Cited by 14 · see citing works
PLCrypto: A Symmetric Cryptographic Library for Programmable Logic Controllers
Yang, Z., Bao, Z., Jin, C., Liu, Z., & Zhou, J. (2021) · IACR Transactions on Symmetric Cryptology · doi:10.46586/tosc.v2021.i3.170-217 · Cited by 14 · see citing works
Hands-On Quantum Cryptography: Experimentation with the B92 Protocol Using Pulsed Lasers
Gandelman, S. P., Maslennikov, A., & Rozenman, G. G. (2025) · Photonics · doi:10.3390/photonics12030220 · Cited by 13 · see citing works
SP 800–22 and GM/T 0005–2012 Tests: Clearly Obsolete, Possibly Harmful
Saarinen, M.-J. O. (2022) · IEEE European Symposium on Security and Privacy Workshops (EuroS&PW) · doi:10.1109/eurospw55150.2022.00011 · Cited by 12 · see citing works
In-depth energy analysis of security algorithms and protocols for the Internet of Things
Winderickx, J., Braeken, A., Singelée, D., & Mentens, N. (2021) · Journal of Cryptographic Engineering · doi:10.1007/s13389-021-00274-7 · Cited by 12 · see citing works
On Entropy and Bit Patterns of Ring Oscillator Jitter
Saarinen, M.-J. O. (2021) · Asian Hardware Oriented Security and Trust Symposium (AsianHOST) · doi:10.1109/asianhost53231.2021.9699508 · Cited by 11 · see citing works
Low Randomness Masking and Shuffling: An Evaluation Using Mutual Information
Papagiannopoulos, K. (2018) · IACR Transactions on Cryptographic Hardware and Embedded Systems · doi:10.46586/tches.v2018.i3.524-546 · Cited by 11 · see citing works
On the Additional Chi-Square Tests for the IID Assumption of NIST SP 800-90B
Kang, J.-S., Park, H., & Yeom, Y. (2017) · Conference on Privacy, Security and Trust · doi:10.1109/pst.2017.00051 · Cited by 10 · see citing works
Modelling cryptographic distinguishers using machine learning
Brunetta, C., & Picazo‐Sanchez, P. (2021) · Journal of Cryptographic Engineering · doi:10.1007/s13389-021-00262-x · Cited by 10 · see citing works
A New Look at Blockchain Leader Election: Simple, Efficient, Sustainable and Post-Quantum
Esgin, M. F., Ersoy, O., Kuchta, V., Loss, J., Sakzad, A., Steinfeld, R., Yang, X., & Zhao, R. K. (2023) · ACM Asia Conference on Computer and Communications Security (ASIA CCS) · doi:10.1145/3579856.3595792 · Cited by 10 · see citing works
Hydrogenated VO2 Bits for Probabilistic Computing
Deng, S., Park, T. J., Yu, H., Saha, A., Islam, A. N. M. N., Wang, Q., Sengupta, A., & Ramanathan, S. (2023) · IEEE Electron Device Letters · doi:10.1109/led.2023.3303875 · Cited by 10 · see citing works
Ciphertext-Only Attack on Linear Feedback Shift Register-Based Esmaeili-Gulliver Cryptosystem
Lee, Y., Kim, Y.-S., & No, J. (2017) · IEEE Communications Letters · doi:10.1109/lcomm.2017.2654238 · Cited by 10 · see citing works
A Secure Exception Mode for Fault-Attack-Resistant Processing
Yuce, B., Deshpande, C., Ghodrati, M., Bendre, A., Nazhandali, L., & Schaumont, P. R. (2018) · IEEE Transactions on Dependable and Secure Computing · doi:10.1109/tdsc.2018.2823767 · Cited by 9 · see citing works
TrustNet: Ensuring Normal-world and Trusted-world CAN-bus Networking
Kornaros, G., Bakoyiannis, D., Tomoutzoglou, O., Coppola, M., & Gherardi, G. (2019) · IEEE International Conference on Communications, Control, and Computing Technologies for Smart Grids (SmartGridComm) · doi:10.1109/smartgridcomm.2019.8909715 · Cited by 9 · see citing works
Enabling Second Factor Authentication for Drones in 5G using Network Slicing
Abdel-Malek, M. A., Akkaya, K., Bhuyan, A., Cebe, M., & Ibrahim, A. S. (2020) · IEEE Globecom Workshops (GC Wkshps) · doi:10.1109/gcwkshps50303.2020.9367441 · Cited by 9 · see citing works
Modern random number generator design – Case study on a secured PLL-based TRNG
Fischer, V., Bernard, F., & Bochard, N. (2019) · it - Information Technology · doi:10.1515/itit-2018-0025 · Cited by 9 · see citing works
Recommendation for Cryptographic Key GenerationPreprint
Barker, E. B., Roginsky, A. L., & Davis, R. (2020) · doi:10.6028/nist.sp.800-133r2-draft · Cited by 9 · see citing works
Self-citationTemoshok, D., Fenton, J. L., Choong, Y., Lefkovitz, N. B., Regenscheid, A., & Richer, J. P. (2022) · doi:10.6028/nist.sp.800-63b-4.ipd · Cited by 9 · see citing works
RetractedIn-line rate encrypted links using pre-shared post-quantum keys and DPUs
Aguilera, A. C., García, C. R., Lawo, D. C., Imaña, J. L., Monroy, I. T., & Olmos, J. J. V. (2024) · Scientific Reports · doi:10.1038/s41598-024-71861-x · Cited by 8 · see citing works
Pulsar: Secure Steganography for Diffusion Models
Jois, T. M., Beck, G., & Kaptchuk, G. (2024) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/3658644.3690218 · Cited by 8 · see citing works
Implementation of the Binary Random Number Generator Using the Knight Tour Problem
Mahmood, A. S., Rahim, M. S. M., & Othman, N. Z. S. (2016) · Modern Applied Science · doi:10.5539/mas.v10n4p35 · Cited by 8 · see citing works
Recommendation for Key ManagementPreprint
Barker, E. B. (2019) · doi:10.6028/nist.sp.800-57pt1r5-draft · Cited by 8 · see citing works
Self-citationAssessing the quality of random number generators through neural networks
Crespo, J. L., González‐Villa, J., Gutiérrez, J., & Valle, A. (2024) · Machine Learning Science and Technology · doi:10.1088/2632-2153/ad56fb · Cited by 9 · see citing works
Using a Chaotic Cipher to Encrypt Ethernet Traffic
Pérez-Resa, A., Garcia-Bosque, M., Sánchez‐Azqueta, C., & Celma, S. (2018) · IEEE International Symposium on Circuits and Systems proceedings · doi:10.1109/iscas.2018.8351203 · Cited by 7 · see citing works
Enhancing non-profiled side-channel attacks by time-frequency analysis
Jin, C., & Zhou, Y. (2023) · Cybersecurity · doi:10.1186/s42400-023-00149-w · Cited by 7 · see citing works
Improved Performance of SRAM-Based True Random Number Generator by Leveraging Irradiation Exposure
Zhang, X., Jiang, C., Dai, G., Zhong, L., Fang, W., Gu, K., Xiao, G., Ren, S., Liu, X., & Zou, S. (2020) · Sensors · doi:10.3390/s20216132 · Cited by 7 · see citing works
Symmetric Key Cryptosystem Based on Randomized Block Cipher
Aruljothi, S., & Venkatesulu, M. A. (2010) · International Conference on Future Information Technology · doi:10.1109/futuretech.2010.5482692 · Cited by 7 · see citing works
Melosik, M., & Marszałek, W. (2021) · IEEE Access · doi:10.1109/access.2021.3131969 · Cited by 7 · see citing works
A Robust and Sponge-Like PRNG with Improved Efficiency
Hutchinson, D. (2017) · Lecture notes in computer science · doi:10.1007/978-3-319-69453-5_21 · Cited by 7 · see citing works
Duda, C. K., Meier, K. A., & Newell, R. (2023) · Entropy · doi:10.3390/e25050731 · Cited by 6 · see citing works
Secure Noise Sampling for DP in MPC with Finite Precision
Keller, H., Möllering, H., Schneider, T. H., Tkachenko, O., & Zhao, L. (2024) · International Conference on Availability, Reliability and Security (ARES) · doi:10.1145/3664476.3664490 · Cited by 6 · see citing works
Generation of 1 GB full entropy random numbers with the enhanced-NRBG method
Aggarwal, D., Karthick Balaji, R., Ghatikar, R., Chennuri, S., & Banerjee, A. (2023) · Physica Scripta · doi:10.1088/1402-4896/ad0811 · Cited by 6 · see citing works
- Authors
- Barker, E. B., & Kelsey, J. M.
- Published
- 2015-06
- OpenAlex
- W4298403653
- Cited by
- 304
- References
- 4
- Citations by year
- 2026: 49 · 2025: 53 · 2024: 27 · 2023: 31 · 2022: 22 · 2021: 18 · 2020: 19 · 2019: 26 · 2018: 13 · 2017: 16 · 2016: 8 · 2015: 4 · 2014: 5 · 2012: 5
- Type
- report
- Language
- en
- Open access
- gold
- doi.org
- Funders
- National Institute of Standards and Technology
- Topics
- Physical Sciences › Computer Science › Artificial Intelligence › Cryptographic Implementations and Security
- Physical Sciences › Computer Science › Information Systems › Cryptography and Residue Arithmetic
- Physical Sciences › Computer Science › Artificial Intelligence › Cryptography and Data Security
- Keywords
- random number generation, random bit generation, cryptographic key generation, information security standards
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Claims read by deepseek-v4.1-flash under definition version 3 (extract-v3) on 2026-10-09.
Classified by jev-1.13-20260917 (gold-guideline-v0.2) on 2026-10-09.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review