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

OpenSSF Best Practices Badge Criteria silver.crypto_used_network: crypto_used_network (Silver, SHOULD)

Silver criterion crypto_used_network (SHOULD; group Security, Use basic good cryptographic practices). Criterion text: The software produced by the project SHOULD support secure protocols for all of its network communications, such as SSHv2 or later, TLS1.2 or later (HTTPS), IPsec, SFTP, and SNMPv3. Insecure protocols such as FTP, HTTP, telnet, SSLv3 or earlier, and SSHv1 SHOULD be disabled by default, and only enabled if the user specifically configures it. If the software produced by the project does not support network communications, select "not applicable" (N/A).

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.