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

OpenSSF Best Practices Badge Criteria silver.crypto_weaknesses: crypto_weaknesses (Silver, MUST)

Silver criterion crypto_weaknesses (MUST; group Security, Use basic good cryptographic practices). Criterion text: The default security mechanisms within the software produced by the project MUST NOT depend on cryptographic algorithms or modes with known serious weaknesses (e.g., the SHA-1 cryptographic hash algorithm or the CBC mode in SSH). This raises the passing criterion of the same name (there SHOULD) to MUST at the silver level.

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 Silver 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.