Table 2: Comparable strengths Bits of security Symmetric key algorithms 80 2TDEA 19 FFC (e.g., DSA, D-H) L = 1024 N = 160 112 3TDEA L = 2048 N = 224 128 AES-128 L = 3072 N = 256 192 AES-192 L = 7680 N = 384 256 AES-256 L = 15360 N = 512 IFC (e.g., RSA) March, 2007 ECC (e.g., ECDSA) k = 1024 f = 160-223 k = 2048 f = 224-255 k = 3072 f = 256-383 k = 7680 f = 384-511 k = 15360 f = 512+ For hash functions, the size of the hash function will be determined by the algorithm or scheme in which the hash function is used. For this reason, the standard for the algorithm must specify the appropriate hash size or security strength to use. For example, the appropriate hash algorithm for a digital signature algorithm depends upon the chosen key and parameter size, and the security strength to be provided by the digital signature. To further illustrate this concept, Table 3 indicates the hash size with comparable strength for the listed parameter and key sizes for digital signatures, HMAC, key derivation functions, and random number generation. 19 The assessment of at least 80-bits of security for 2TDEA is based on the assumption that an attacker has at most 2 40 matched plaintext and ciphertext blocks (see [ANSX9.52], Annex B). 63
March, 2007 Table 3: Hash function security strengths for cryptographic applications Bits of Digital HMAC Key Random Other (To <strong>Security</strong> Signatures and Derivation hash-only applications Functions 20 Number Generation 21 Be Determined) 80 SHA-1 22 , SHA-224, SHA-256, SHA-384, SHA-512 SHA-1, SHA-224, SHA-256, SHA-384, SHA-512 SHA-1, SHA-224, SHA-256, SHA-384, SHA-512 SHA-1, SHA-224, SHA-256, SHA-384, SHA-512 112 SHA-224, SHA-1, SHA-1, SHA-1, SHA-256, SHA-224, SHA-224, SHA-224, SHA-384, SHA-256, SHA-256, SHA-256, SHA-512 SHA-384, SHA-384, SHA-384, SHA-512 SHA-512 SHA-512 128 SHA-256, SHA-1, SHA-1, SHA-1, To Be SHA-384, SHA-224, SHA-224, SHA-224, Determined SHA-512 SHA-256, SHA-256, SHA-256, SHA-384, SHA-384, SHA-384, SHA-512 SHA-512 SHA-512 192 SHA-384, SHA-224, SHA-224, SHA-224, SHA-512 SHA-256, SHA-256, SHA-256, SHA-384, SHA-384, SHA-384, SHA-512 SHA-512 SHA-512 256 SHA-512 SHA-256, SHA-384, SHA-512 SHA-256, SHA-384, SHA-512 SHA-256, SHA-384, SHA-512 20 The security strength for key derivation assumes that the shared secret contains sufficient entropy to support the desired security strength. 21 The security strength assumes that the random number generator has been provided with adequate entropy to support the desired security strength. 22 SHA-1 has recently been demonstrated to provide less than 80 bits of security for digital signatures; at the publication of this Recommendation, the security strength against collisions is assessed at 69 bits. The use of SHA-1 is not recommended for the generation of digital signatures in new systems; new systems should use one of the larger hash functions. For the present time, SHA-1 is included here to reflect it's widespread use in existing systems, for which the reduced security strength may not be of great concern when only 80-bits of security are required. 64
- Page 1 and 2:
ARCHIVED PUBLICATION The attached p
- Page 3 and 4:
Abstract March, 2007 This Recommend
- Page 5 and 6:
Authority March, 2007 This document
- Page 7 and 8:
March, 2007 key validation, account
- Page 9 and 10:
March, 2007 4.2.4.1 DSA............
- Page 11 and 12:
March, 2007 8 KEY MANAGEMENT PHASES
- Page 13 and 14: March, 2007 10.2.9 Compromise Manag
- Page 15 and 16: March, 2007 Figure 3: Key states an
- Page 17 and 18: March, 2007 1.2 Audience The audien
- Page 19 and 20: March, 2007 1. Section 1, Introduct
- Page 21 and 22: March, 2007 Backup A copy of inform
- Page 23 and 24: March, 2007 Digital signature The r
- Page 25 and 26: Key Management Policy Key Managemen
- Page 27 and 28: Proof of possession (POP) Pseudoran
- Page 29 and 30: March, 2007 Split knowledge A proce
- Page 31 and 32: March, 2007 3 Security Services Cry
- Page 33 and 34: March, 2007 However, it is often th
- Page 35 and 36: March, 2007 4 Cryptographic Algorit
- Page 37 and 38: March, 2007 operates on blocks (chu
- Page 39 and 40: March, 2007 minimum key size 7 of 1
- Page 41 and 42: March, 2007 2. The protocols trigge
- Page 43 and 44: March, 2007 7. Symmetric key wrappi
- Page 45 and 46: March, 2007 9. Random numbers: The
- Page 47 and 48: March, 2007 In general, where stron
- Page 49 and 50: March, 2007 a. When a symmetric key
- Page 51 and 52: March, 2007 information. For less s
- Page 53 and 54: 8. Symmetric and Asymmetric RNG key
- Page 55 and 56: 15. Private ephemeral key agreement
- Page 57 and 58: Key Type 12. Symmetric Key Agreemen
- Page 59 and 60: March, 2007 establishment keys, see
- Page 61 and 62: March, 2007 c. Restricting plaintex
- Page 63: March, 2007 algorithms completely i
- Page 67 and 68: Table 4: Recommended algorithms and
- Page 69 and 70: March, 2007 size is available, the
- Page 71 and 72: Security life of data up to 4 years
- Page 73 and 74: March, 2007 6 Protection Requiremen
- Page 75 and 76: Table 5: Protection requirements fo
- Page 77 and 78: Key Type Security Service Private e
- Page 79 and 80: March, 2007 Crypto. Security Securi
- Page 81 and 82: March, 2007 may be applied only to
- Page 83 and 84: March, 2007 All cryptographic infor
- Page 85 and 86: March, 2007 8. Domain parameters (e
- Page 87 and 88: March, 2007 6. Destroyed Compromise
- Page 89 and 90: March, 2007 a. A private signature
- Page 91 and 92: 2 Pre-Operational Phase 3 7 1 4 Ope
- Page 93 and 94: March, 2007 8.1 Pre-operational Pha
- Page 95 and 96: 8.1.5.1.1 Distribution of Static Pu
- Page 97 and 98: March, 2007 and then provide eviden
- Page 99 and 100: March, 2007 listed in Section 8.1.5
- Page 101 and 102: March, 2007 encrypting key or publi
- Page 103 and 104: March, 2007 8.1.5.3.5 Intermediate
- Page 105 and 106: March, 2007 of keying material and
- Page 107 and 108: March, 2007 2. The application in w
- Page 109 and 110: March, 2007 and the key derivation
- Page 111 and 112: March, 2007 Type of Key Archive? Re
- Page 113 and 114: March, 2007 All records of the enti
- Page 115 and 116:
March, 2007 other cryptographic inf
- Page 117 and 118:
March, 2007 access to information e
- Page 119 and 120:
March, 2007 1. Private key used to
- Page 121 and 122:
March, 2007 10.2 Content of the Key
- Page 123 and 124:
March, 2007 Management Specificatio
- Page 125 and 126:
March, 2007 is the same value as th
- Page 127 and 128:
March, 2007 If the decision is made
- Page 129 and 130:
March, 2007 only, and then shall be
- Page 131 and 132:
March, 2007 may be stored in backup
- Page 133 and 134:
March, 2007 and the method of key r
- Page 135 and 136:
March, 2007 ephemeral key pairs, an
- Page 137 and 138:
B.3.14.7 Key Control Information Ma
- Page 139 and 140:
March, 2007 to be saved. Keys for t
- Page 141 and 142:
[HAC] Handbook of Applied Cryptogra
- Page 143:
March, 2007 the owner by the CA tha