AWS transfer: Move 3DES out of FIPS-compliant algorithms list
Summary
Removes 3DES from the FIPS-compliant (recommended) algorithm section and relocates it to the general 'Other supported algorithms' list, signaling it is legacy and not recommended.
Security assessment
The change demotes 3DES (Triple DES), a weak/legacy cipher, from the FIPS-compliant recommended set to the general supported list, steering users toward stronger algorithms like AES. This is cryptographic hardening guidance rather than a fix for a specific vulnerability.
Evidence
* 3DES, IDEA, CAST5, Blowfish, DES, TwoFish, CAMELLIA-128, CAMELLIA-192, CAMELLIA-256
Diff
diff --git a/transfer/latest/userguide/key-management.md b/transfer/latest/userguide/key-management.md index e215968..3a84c0c 100644 --- a//transfer/latest/userguide/key-management.md +++ b//transfer/latest/userguide/key-management.md @@ -135,2 +134,0 @@ FIPS-compliant algorithms (recommended for regulated environments) - * **3DES** \- Triple Data Encryption Standard (legacy, use AES when possible) - @@ -142 +140 @@ Other supported algorithms - * IDEA, CAST5, Blowfish, DES, TwoFish, CAMELLIA-128, CAMELLIA-192, CAMELLIA-256 + * 3DES, IDEA, CAST5, Blowfish, DES, TwoFish, CAMELLIA-128, CAMELLIA-192, CAMELLIA-256