OpenSSF Best Practices Badge Criteria
Passing level: Security – OpenSSF Best Practices Badge Criteria

OpenSSF Best Practices Badge Criteria passing.crypto_random: crypto_random (Passing, MUST)

Passing criterion crypto_random (MUST; group Security, Use basic good cryptographic practices). Criterion text: The security mechanisms within the software produced by the project MUST generate all cryptographic keys and nonces using a cryptographically secure random number generator, and MUST NOT do so using generators that are cryptographically insecure.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-218 · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Passing level: Security – OpenSSF Best Practices Badge Criteria

Query this from an agent

The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.