Today, AWS Payments Cryptography announces support for hybrid post-quantum (PQ) TLS to secure API calls. With this launch, customers can future-proof transmissions of sensitive data and commands using ML-KEM post-quantum cryptography.
Enterprises operating highly regulated workloads wish to reduce post-quantum risks from “harvest now, decrypt later”. Long-lived data-in-transit can be recorded today, then decrypted in the future when a sufficiently capable quantum computer becomes available. With today’s launch, AWS Payment Cryptography joins data protection services such as AWS Key Management Service (KMS) in addressing this concern by supporting PQ-TLS.
To get started, simply ensure that your application depends on a version of AWS SDK or browser that supports PQ-TLS. For detailed guidance by language and platform, visit the PQ-TLS enablement documentation. Customers can also validate that ML-KEM was used to secure the TLS session for an API call by reviewing tlsDetails for the corresponding CloudTrail event in the console or a configured CloudTrail trail.
These capabilities are generally available in all AWS Regions at no added cost. To get started with PQ-TLS and Payment Cyptography, see our post-quantum TLS guide. For more information about PQC at AWS, please see PQC shared responsibility.
Categories: marketing:marchitecture/quantum-technologies,marketing:marchitecture/security-identity-and-compliance
Source: Amazon Web Services
Latest Posts
- MC1461157: Microsoft Teams Rooms Adds Proximity Join for Attendees in Teams Events on Windows and Android
- AWS DataSync launches a monitoring dashboard for tracking task executions across your account
- AWS Elastic Disaster Recovery now supports AWS Graviton-based source servers
- MC1442614: Microsoft Teams Rooms Adds AI Data Channel to Enhance IntelliFrame for Intelligent Cameras
