tls

3 posts

cloudflare

Why we cannot wait for better post-quantum signature algorithms (opens in new tab)

RSA and elliptic-curve signatures will eventually be vulnerable to sufficiently powerful quantum computers, so organizations cannot delay migration until ideal post-quantum algorithms arrive. ML-KEM already protects much of Cloudflare’s traffic from “harvest now, decrypt later” attacks, while ML-DSA is currently the practical choice for post-quantum signatures despite its larger keys and signatures. Better schemes are being developed, but they will not be standardized and deployable in time for the initial transition. ## The urgency of post-quantum migration - NIST standardized ML-KEM encryption and ML-DSA signatures in 2024 after an eight-year international competition. - Cloudflare reports that most of its traffic already uses ML-KEM. - Post-quantum signatures are still needed to protect authentication systems from quantum-enabled attacks. - Cloudflare aims to be fully post-quantum secure by 2029. - The authors argue that deployment must begin with currently available algorithms: - “You go to war with the algorithms you have, not the ones you wish you had.” - Future signature research remains important because current options have substantial performance, size, and implementation drawbacks. ## Comparing the candidate signature algorithms - The candidates include: - Existing classical algorithms such as RSA and elliptic-curve signatures, which are quantum-vulnerable. - ML-DSA and other already standardized or soon-to-be-standardized post-quantum schemes. - Nine candidates advancing to the third round of NIST’s signatures on-ramp. - Comparisons focus on variants relevant to TLS at the 128-bit security level. - The measurements cover: - Public-key and signature sizes. - Signing and verification speed. - Implementation concerns and side-channel resistance. - Some algorithms have important operational limitations: - FN-DSA and SQIsign are difficult to implement with fast, timing-safe signing. - LMS requires state to be maintained securely between signatures. - Certain SLH-DSA variants are intended for only a limited number of signatures. ## No single post-quantum “all-star” - Ed25519 remains the strongest all-around performer when quantum resistance is ignored. - It offers particularly favorable: - Public-key size. - Signature size. - Signing speed. - Its verification is slower than some alternatives but remains fast enough for most applications. - Post-quantum schemes instead fall into two broad groups: - **Specialists:** Excellent on particular metrics but unsuitable for general use because of other weaknesses. - **Generalists:** More balanced schemes such as ML-DSA, which avoid extreme weaknesses but do not match elliptic curves overall. ## SQIsign: compact signatures with slow signing - SQIsign is attractive for bandwidth-sensitive applications: - 148-byte signatures. - 65-byte public keys. - Smaller than RSA-2048 and close to elliptic-curve sizes. - Its disadvantages include: - High mathematical and implementation complexity. - Slow signing and verification. - Difficulty achieving efficient, timing-side-channel-resistant signing. - Progress since 2024 has significantly simplified SQIsign and improved verification speed. - Secure signing is still unlikely to become fast enough for common online uses such as TLS handshakes. - It may be better suited to offline applications where signing is infrequent and verification matters more, including: - Certificate-authority signatures. - DNSSEC. - SQIsign is based on isogenies, a category that attracted concern after SIKE was catastrophically broken. - The authors distinguish the schemes: - SIKE already had known security concerns and used problematic torsion points. - SQIsign does not use those torsion points. - The best known SQIsign attacks are generic brute-force attacks, resembling attacks against well-chosen elliptic curves. - Isogeny mathematics still has a large attack surface, but the authors consider SQIsign’s security outlook stronger than that of structured multivariate schemes. - The authors see significant promise in SQIsign but caution against standardizing it prematurely. The practical recommendation is to begin the post-quantum transition with ML-DSA rather than waiting for smaller or faster alternatives. New schemes such as SQIsign may eventually serve specialized use cases, but they must undergo further cryptanalysis, standardization, implementation work, and deployment before they can replace today’s available algorithms.

aws

AWS Weekly Roundup: Claude Sonnet 5 on AWS, Amazon WorkSpaces for AI agents, AWS service availability updates, and more (July 6, 2026) | Amazon Web Services (opens in new tab)

The July 6, 2026 AWS roundup highlights new infrastructure, AI, observability, and developer productivity capabilities. Major announcements include Claude Sonnet 5 on AWS, generally available WorkSpaces for AI agents, faster SageMaker inference scaling, and log-query alarms in CloudWatch. It also details AWS service lifecycle changes and upcoming community events. ## Featured AWS Launches - **Claude Sonnet 5 on AWS** - Anthropic’s latest Sonnet model is available for coding, agentic workflows, and professional tasks. - It can navigate large codebases, use tools accurately, and preserve state across long-running tasks. - **Amazon WorkSpaces for AI agents** - AI agents can securely operate desktop applications in managed WorkSpaces environments. - Organizations can use existing applications without modernization or custom integrations. - **OpenSearch log analytics optimization** - A new engine provides up to four times better price-performance in internal benchmarks. - It combines log aggregation with OpenSearch’s full-text search capabilities. - **Faster SageMaker AI inference scaling** - Container image caching can reduce generative AI scale-out time by up to half. - SageMaker supports up to two times faster end-to-end scaling during demand increases. - **CloudWatch alarms from log queries** - Users can create alarms directly from log query results and define thresholds in one workflow. - This removes the need to create metric filters or custom metrics first. ## Additional Infrastructure and Developer Updates - **EC2 C9g and C9gd instances** - Powered by AWS Graviton5 processors. - Offer up to 25% more compute performance than Graviton4 instances, five times more cache, faster memory, and optional local NVMe storage. - **CloudFormation Express mode** - Provides deployment confirmation within seconds. - Helps developers and AI agents iterate more quickly, at no additional cost in commercial Regions. - **Amazon EKS version rollbacks** - Kubernetes upgrades can be reversed within seven days. - Rollbacks avoid rebuilding clusters and reduce the risk of failed upgrades. - **ACME support in AWS Certificate Manager** - Automates issuance and renewal of public TLS certificates using the standard ACME protocol. ## AWS Service Availability Changes AWS updated its lifecycle guidance on June 30, 2026, including alternatives and migration support. - **Moving to maintenance for new customers from July 30** - Amazon Bedrock Agents becomes Bedrock Agents Classic. - Amazon Cognito Sync, Amazon Kendra, Amazon Q Business, Simple AD, and several other services and features will no longer accept new customers. - A number of SageMaker AI features are affected, including Clarify, Debugger, Ground Truth, Model Monitor, and Studio Lab. - AWS IoT Device Defender Detect changes on August 31, 2026. - **Entering sunset** - Amazon WorkSpaces PCoIP and Pool. - AWS Managed Services Advanced. - AWS re:Post Private. - SageMaker AI Profiler. - **End of support** - Amazon Chime SDK Carrier Voice Focus. - SageMaker AI Ground Truth Plus. ## Upcoming AWS Events - AWS Summits will take place throughout the second half of 2026. - AWS Community Day Belo Horizonte is scheduled for August 22. - The AWS Builder Center offers community discussions, technical content, and information about upcoming virtual and in-person events. Organizations using affected AWS services should review the relevant lifecycle documentation and contact AWS Support to plan migrations before availability or support deadlines.

cloudflare

The post-quantum EO is an important milestone. Now it’s time to get to work (opens in new tab)

The post welcomes Executive Order 14409 as a major step toward post-quantum security, setting federal deadlines of 2030 for encryption and 2031 for authentication. It argues that the threat timeline has accelerated and that organizations must begin migration now, especially to prevent “harvest-now-decrypt-later” attacks. Cloudflare views the order as a strong foundation but believes agencies need clearer guidance and a coordinated migration roadmap. ## Federal Post-Quantum Requirements - The order primarily covers: - **High Value Assets (HVAs)**, such as systems containing sensitive employee records, classified intelligence, or federal financial data. - **High impact systems** rated “high” under FIPS 199, where compromise could cause severe harm. - Key deadlines include: - **July 2026:** Agencies name a post-quantum migration lead. - **September 2026:** Agencies inventory HVAs and high-impact systems, create migration plans, and submit them to OMB and the National Cyber Director. - **December 2030:** Key establishment must use post-quantum cryptography. - **December 2031:** Digital signatures and certificates must use post-quantum cryptography. - National Security Systems are excluded from these deadlines and remain on a separate NSA-managed schedule. - The order directly binds federal agencies, not state and local governments, critical infrastructure, academia, or civil society. ## Encryption and Authentication Are Separate Migrations - **Post-quantum encryption** protects key establishment and should begin immediately. - It prevents attackers from collecting encrypted data now and decrypting it after quantum computers become capable of breaking RSA and elliptic-curve cryptography. - This is especially important for government, financial, healthcare, defense, and telecommunications data with long-term value. - **Post-quantum authentication** protects digital signatures, certificates, software signatures, and system access. - It prevents future quantum computers from impersonating servers or forging trusted signatures. - Its primary threat emerges once a cryptographically relevant quantum computer exists. - The order’s 2031 authentication deadline suggests the U.S. government considers an operational quantum computer around that period a meaningful possibility. ## Standardized Cryptography Over Quantum Key Distribution - The order emphasizes NIST-standardized post-quantum algorithms. - The authors support this focus because Quantum Key Distribution requires specialized hardware and dedicated physical links, making it unsuitable for Internet-scale deployment. - Cloudflare reports that more than two-thirds of browser traffic reaching its network already uses post-quantum encryption. - Its Cloudflare One platform supports post-quantum protection across TLS, MASQUE, and IPsec, while broader post-quantum authentication deployment is still beginning. ## Why Authentication Is More Difficult - Post-quantum ML-DSA signatures are larger than traditional signatures, potentially reducing performance in systems such as short-lived TLS connections. - Cloudflare is working with Google Chrome on Merkle Tree Certificates to reduce this TLS overhead. - Authentication requires coordinated upgrades across a larger ecosystem: - Clients and servers - Certificate authorities - Certificate transparency logs - Root stores - Web browsers - By comparison, post-quantum key establishment is already more widely available and easier to deploy incrementally. Organizations should begin with asset inventories, risk assessments, and post-quantum key-establishment upgrades now rather than waiting for the federal deadlines. Authentication migration should also start early because its broader dependency chain and larger signatures make it the more complex transition.