Commercial National Security Algorithm Suite (CNSA) 2.0
Validation and product acceptance: NIAP, CAVP, CMVP and hardware-backed signing – Commercial National Security Algorithm Suite (CNSA) 2.0

Commercial National Security Algorithm Suite (CNSA) 2.0 VAL-AGILE: VAL-AGILE Cryptographic agility and prefer-then-require configuration through the transition

Equipment purchased before CNSA 2.0 support is mandated should, where possible, have sufficient memory and processing power to run the new algorithms and capacity for future algorithms and protocols so that enhancements arrive by software update; during the transition NSS owners and operators are required, where feasible, to prefer CNSA 2.0 algorithms when configuring systems, all appropriate components should be configured to prefer CNSA 2.0 as validated solutions become available, and as products mature they should be configured to accept only CNSA 2.0 algorithms; NSA encourages responsible testing in vendor and government research environments now to understand the effect of the larger key and signature sizes.

Maintained by Gerard BlokdykControl text last updated

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.

  • AGILITY Build cryptographic agility into technology, processes and policies

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 Validation and product acceptance: NIAP, CAVP, CMVP and hardware-backed signing – Commercial National Security Algorithm Suite (CNSA) 2.0

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.