AWS Security ChangesHomeSearch

AWS payment-cryptography high security documentation change

Service: payment-cryptography · 2025-11-16 · Security-related high

File: payment-cryptography/latest/userguide/data-protection.md

Summary

Updated TLS requirements to remove support for TLS 1.0-1.1, now requiring TLS 1.2-1.3

Security assessment

Removing deprecated TLS 1.0/1.1 mitigates known vulnerabilities (e.g., BEAST, POODLE). This directly addresses security by enforcing stronger encryption standards.

Diff

diff --git a/payment-cryptography/latest/userguide/data-protection.md b/payment-cryptography/latest/userguide/data-protection.md
index 0d464c151..f4346ef6b 100644
--- a//payment-cryptography/latest/userguide/data-protection.md
+++ b//payment-cryptography/latest/userguide/data-protection.md
@@ -69 +69 @@ Key material that AWS Payment Cryptography generates or loads for payment keys i
-However, some AWS Payment Cryptography API operations export keys encrypted by a previously shared or asymmetric key exchange key. Also, customers can use API operations to import encrypted key material for payment keys.
+However, some API operations export keys encrypted by a previously shared or asymmetric key exchange key. Also, customers can use API operations to import encrypted key material for payment keys.
@@ -71 +71 @@ However, some AWS Payment Cryptography API operations export keys encrypted by a
-All AWS Payment Cryptography API calls must be signed and be transmitted using Transport Layer Security (TLS). AWS Payment Cryptography requires TLS versions and cipher suites defined by PCI as "strong cryptography". All service endpoints support TLS 1.0—1.3 and hybrid post-quantum TLS.
+All AWS Payment Cryptography API calls must be signed and be transmitted using Transport Layer Security (TLS). AWS Payment Cryptography requires TLS versions and cipher suites defined by PCI as "strong cryptography". All service endpoints support TLS 1.2—1.3 and hybrid post-quantum TLS.