Jump to content

Support a security strength: Difference between revisions

From Hackerpedia
imported>Unknown user
No edit summary
 
imported>Unknown user
No edit summary
Line 1: Line 1:
{{LanguageHeader|en}}
{{LanguageHeader|en}}
{{CyberTerm|definition=<p>A security strength of <i>s</i> bits is said to be supported by a particular choice of algorithm, primitive, auxiliary function, or parameters for use in the implementation of a cryptographic mechanism if that choice will not prevent the resulting implementation from attaining a security strength of at least <i>s</i> bits.</p><p>In this Recommendation, it is assumed that implementation choices are intended to support a security strength of 112 bits or more (see [SP 800-57] and [SP 800-131A]).</p>|source=NIST SP 800-56C Rev. 2}}
{{CyberTerm|definition=A security strength of s bits is said to be supported by a particular choice of algorithm, primitive, auxiliary function, or parameters for use in the implementation of a cryptographic mechanism if that choice will not prevent the resulting implementation from attaining a security strength of at least s bits.In this Recommendation, it is assumed that implementation choices are intended to support a security strength of 112 bits or more (see [SP 800-57] and [SP 800-131A]).|source=NIST SP 800-56C Rev. 2}}

Revision as of 01:42, 15 January 2026

Languages: English | Français

Support a security strength

A security strength of s bits is said to be supported by a particular choice of algorithm, primitive, auxiliary function, or parameters for use in the implementation of a cryptographic mechanism if that choice will not prevent the resulting implementation from attaining a security strength of at least s bits.In this Recommendation, it is assumed that implementation choices are intended to support a security strength of 112 bits or more (see [SP 800-57] and [SP 800-131A]).


Source: NIST SP 800-56C Rev. 2 | Category: