Leading browsers are required to use 2,048-bit length keys by the end of the year, but what effect does this have on security?
Google is changing the length of its encryption keys from 1,024-bit to 2,048-bit, including the root certificates that sign all SSL certificates. What are the practical effects of such a switch from a security perspective, including how enterprises can plan for the switch?
The Certificate Authority/Browser Forum requires all certificate authorities (CAs) to start issuing certificates with a minimum 2,048-bit length by Jan. 1, 2014, and leading browser vendors will require websites to use 2,048-bit keys by the end of 2013.
Many websites have already upgraded their certificates, but because Google services are so ubiquitous, the search giant is flagging its changes to ensure a smooth migration. While most users will not notice anything different (client software like browsers will automatically update to accept the new certificates), some software and hardware -- such as games consoles, phones and cameras -- that rely on hard-coded lists of root certificates will not update automatically.
Ask the expert
SearchSecurity expert Michael Cobb is standing by to answer your questions about enterprise application security and platform security. Submit your question via email. (All questions are anonymous.)
Enterprises using software built in-house that makes SSL connections to Google, must check to see if it relies on hard-coded SSL trust lists and should plan to update the lists, or better still, build SSL certificate flexibility into the software. Google has produced a frequently asked question (FAQ) page covering issues with the changes they are making along with examples of workarounds.
The future of 2,048-bit encryption
Although it's estimated that a 1,024-bit RSA key won't be broken within the next five years (768 bits is the largest RSA key known to have been cracked), it's only considered equivalent to 80 bits of security. Starting at the end of 2013, the U.S. National Institute of Standards and Technology (NIST) will not allow security strengths below 112 to be used within the federal government; those of 112 bits and above will be valid until the end of 2030.
While doubling key strength delivers an exponential increase in protection -- encryption strength is directly tied to key size -- the computational power required to process 2,048-bit certificates is five to 30 times greater than that for 1,024-bit certificates. Enterprises that operate high-volume sites and services need to ensure their infrastructure can handle larger key sizes. To avoid significant performance degradation, one potential option is to offload SSL processing to high-performance application delivery controllers (ADCs). These dedicated network devices include hardware-based SSL acceleration capable of handling far more SSL transactions per second than a general-purpose server.
Google began switching to the new 2,048-bit certificates on Aug. 1, and all certificates will be upgraded by the end of 2013. This includes the root certificate used to sign its SSL certificates, as it only has a 1,024-bit key.
Barring an unforeseen breakthrough in quantum computing, it should be some years before another upgrade is required.
Next Steps
What can elliptic curve cryptography do for the enterprise?
Are there specific encryption requirements under HIPAA?
Array Networks targets SaaS providers with its 2,048-bit SSL-compatible appliances
Learn specifications for backup software-based encryption
Comparing Diffie-Hellman and RSA key exchange algorithms
Is encryption a security cure?
Get information on 2.048-bit SSL keys
Which public key algorithm is used for encrypting emails?
Related Resources
- Aligning Enterprise Identity and Access Management with CIO Priorities–TechTarget Security
- New SaaS Identity Access Management Tools Emerge, Outdo Legacy IAM–TechTarget Security
- Making Sure Your Identity and Access Management Program is Doing What You Need–TechTarget Security
- How to tackle cloud, IAM, and digital certificate problems in your organization–TechTarget Security
Dig Deeper on Identity and access management
Related Q&A from Michael Cobb
Symmetric vs. asymmetric encryption: What's the difference?
Explore the differences between symmetric vs. asymmetric encryption, including how they work and common algorithms, as well as their pros and cons.Continue Reading
What is shellcode and how is it used?
Shellcode is a set of instructions that executes a command in software to take control of or exploit a compromised machine. Read up on the malware ...Continue Reading
Is bitcoin safe? How to secure your bitcoin wallet
As bitcoin use increases, so too have the number of cyber attacks on cryptocurrency exchanges and wallets. Learn how to keep bitcoin use secure.Continue Reading
As an expert in the field of encryption and cybersecurity, my extensive knowledge allows me to delve into the details of the article you provided. The article discusses Google's transition from 1,024-bit to 2,048-bit encryption keys, mandated by the Certificate Authority/Browser Forum. Let's break down the key concepts:
-
Transition to 2,048-Bit Encryption Keys: Google is upgrading its encryption keys from 1,024 bits to 2,048 bits, and this includes the root certificates that sign all SSL certificates. This shift is in compliance with the requirements set by the Certificate Authority/Browser Forum.
-
Security Implications: The move to 2,048-bit keys enhances security. While a 1,024-bit RSA key is considered secure for the next few years, doubling the key strength provides an exponential increase in protection. The U.S. National Institute of Standards and Technology (NIST) mandates a minimum security strength of 112 bits, which will be valid until the end of 2030.
-
Computational Power Requirements: However, it's important to note that the computational power required to process 2,048-bit certificates is significantly higher than that for 1,024-bit certificates. It ranges from five to 30 times greater. This has implications for enterprises, especially those with high-volume sites and services.
-
Performance Considerations: To mitigate the impact on performance, enterprises can consider offloading SSL processing to high-performance application delivery controllers (ADCs). These devices come with hardware-based SSL acceleration, capable of handling a larger number of SSL transactions per second compared to general-purpose servers.
-
Migration Challenges: While most users won't notice a difference (as client software automatically updates to accept new certificates), certain devices like games consoles, phones, and cameras relying on hard-coded lists of root certificates may not update automatically. Enterprises using in-house software that makes SSL connections to Google must ensure compatibility and plan for necessary updates.
-
Google's Migration Strategy: Google initiated the switch to 2,048-bit certificates on August 1, with the goal of completing the upgrade for all certificates by the end of the year. Google acknowledges the widespread use of its services and provides a FAQ page with information on the changes and potential workarounds.
In summary, this transition represents a proactive step in enhancing cybersecurity, aligning with industry standards, and ensuring the continued security of online communications. Enterprises are encouraged to be mindful of the computational requirements and potential performance impacts, taking appropriate measures to facilitate a smooth transition.
