Transferring from 1024 to 2048 SSL | Symantec Website Security Solutions


Published on

Authorities stop supporting 1024-bit key length RSA certificates for both SSL and code signing by the end of this year (2013). Any Symantec customers with certificates expiring this year (2013) will need to renew by generating a Certificate Signing Request (CSR) of 2048 bits or higher. Any Symantec customers with certificates expiring in 2014 or later will need to replace and upgrade all 1024-bit certificates with 2048-bit RSA/DSA or 256-bit ECC certificates by 1st October 2013. All existing 1024-bit certificates will be discontinued industry-wide in the new year (2014). This is in compliance with NIST Special Publication 800-131A you can read more about the changes here -

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Thanks for joining us today my name is Andrew Horbury I’m a product marketing manager for Symantec and the purpose today is to talk about this year’s industry-wide migration of SSL certificates with 1024-bit RSA keys to higher, stronger keys. This session is meant to be informative and educational, but also actionable so you know what to do in case you need to take action in order to maintain industry-standard security, within your organisation– that is something that you your customers and stakeholders will appreciate.
  • The topic today is very straightforward. This is about the migration of 1024 bit certificates based on the RSA Algorithm.I’ll talk about why this is happening, the timelines involved and where you can get support and more information.The US National Institute of Standards and Technology (NIST) have released their special publication, that calls for the end of 1024-bit RSA keys by the end of December 2013 and advises moving to 2048-bit RSA keys.  NIST advises that 2048-bit keys should be viable until 2030. Based on the NIST recommendations, the CAB Forum and Microsoft have implemented requirements to move from 1024-bit to 2048-bit RSA. The CA browser forum (a group of CA's and Browser manufactures) has seen the need to EOL 1024 for all SSL, Code Signing and other digital certificates by 31 Dec 31 2013. The CAB Forum already requires for 2048 bit keys for Extended Validation Certificates and this good practice has been extended to all SSL Certificates and will be mandated from 31 December 2013As a company Symantec concurs with this and we believe this is the duty of every responsible CA. Symantec is fully supportive of this industry initiative and one that is aimed to stay ahead of the curve with the move and advancement of signing algorithms.
  • To give you some context to see how some of our partners are reacting and handling this. Here is a screen cap from Microsoft. Specifically you can see here what Microsoft are doing. Windows Root Certification Program and they have spelled our some reqs as to how digital certs should be maintained… Microsoft have spelled out their requirements – and we’ve circled the key parts. MS are clearly stating that they will not be supporting 1024 key lengths after 31 December 2013.Circled in Red at the foot of the page is this statement CA’s who issue 1024 bit intermediate and end entity certs with expirations beyond 31 December 2013 do so at their own peril! And this puts CA's on notice.
  • Now lets see what the browsers are talking about:Mozilla in their CA Certificate Maintenance Policy are talking about what they consider to be acceptable and supported in Mozilla products. And as you can see they state that the following algorithms and key sizes are acceptable in Mozilla products. Circled on screen you can see that RSA 1024 bit keys will only be supported until 31 December 2013. So as you can see CA’s, browsers and industry bodies are all working together and moving in the same direction.
  • Changing gears for a few moments… and give some frame of reference and where RSA came from and the technology behind the certificates themselvesRSA is an Internet encryption and authentication system that uses an algorithm developed in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman. And their initials spell out RSA…. And since 1991 there have been 17 different RSA key lengths that have been factored.The RSA algorithmis based on the simple arith-met-ical fact that it is relatively easy to multiply two large prime numbers but extremely difficult to work backward from the product to find those prime numbers. Longer key lengths decrease the possibility of successful attacks by increasing the number of combinations that are possible. For example, for a 40-bit key, there are 240 possible values. By using a personal computer that can try 1 million keys per second, an attacker can try all possible keys in about 13 days. However, an 128-bit key has 2128 possible values. If you could use a computer that would allow you to try 100 billion keys a second and you used 10 million of these computers, it would take about 1013  years to try every possible 128-bit key value. This is nearly 1000 times longer than the estimated age of the universe (15 billion to 20 billion years). Therefore, the longer the key, the more protection you have from attacks. For symmetric key encryption, increasing the key size by one bit doubles the effort that is required for an exhaustive key search attack. Doubling the key size squares the amount of effort required.As computational power has increased its important that the key length be increased to guard against the factoring of the RSA algorithm.Now lets talk through the pace of factoring over the last few years.
  • Lets look at RSA keys that have been factored.In August 1999 512 bit was factored, by Dec 2003 576 bit was also factored. Conversely 768 bit RSA algorithm was factored a few years before 704. So rather than waiting for 1024 to be factored and forcing us (the vendors, the CA’s, the browsers) to be reactive we are taking a proactive approach and making the change sooner rather than later…We predict that 1024 will be factored and we want to act together to advance this and respond to the natural march of technology.Because as I’m showing here… Ending the life of a key size is a natural point in the lifecycle of any algorithm.
  • I want to talk a little bit about our responsibility:Its our duty to help you thru this and we’ve built a number of resources on our site to guide you through this lifecycle end. For us it’s a motivator and we’ve developed a series of resources and you will see this URL throughout this presentation and on these pages you can find out everything you need to know to get through this transition.Everything you need to know is on our site at
  • For certificates expiring this year – there is no action to take. So you follow the normal course of things (bar of course generating a new 2048bit or stronger key CSR for the renewal of the certificate).We have a number of tools available on especially on how you can generate a new CSR.For Certs expiring in 2014 and later we will be initiating a rolling revocation process starting on 1 October 2013. This is a point that bears repeating. If the certificate you have from one of our CA’s expires after 31 December 2013 we will revoke this certificate in advance of the deadline and this process starts on 1 October 2013. Why are we acting so far in advance? – we know our certificates are used to establish drive trust and secure data online so we want to ensure we are acting way in advance so your business will not be impacted in the run up to the Christmas holiday season or indeed to avoid any code freeze coming up towards the end of the year. So by acting as far in advance as we can we hope to avoid any hiccups in your business. Because this is mandated EOL we want to help you through this and so your customers, colleagues, stakeholders will not be impacted in anyway.
  • So what do you need to do? In 2013 if your cert expires not so much but do ensure that you renew your certificate with a new CSR that.If your certificate expires after 31 December 2013 you can revoke and replace your certificate with a valid certificate before the rolling revocation which starts on 1 October 2013.
  • Customers are already acting to steadily move beyond 1024-bit certificate usage, so that they can beat the deadlines. Here’s what you can do, if you haven’t started already.The first thing you should do is go find your 1024-bit certs, you can use the tool here on the link to determine the key length of your certificates. You also need understand when they are expiring and for any certificates expiring after 31 December 2013 take the appropriate steps.For Certificates expiring this year simply generate a new CSR using a 2048bit RSA key and renew the certificate.For Certificates expiring after 31 December 2013 then you can revoke and replace those certificates using a 2048 bit RSA/DSA or a 256 ECC key (I’m not going to talk about our ECC keys today but you can read about it on our blog here).If you are a Symantec™ Managed PKI for SSL customer you can configure any 1024-bit certificates with a customized expiration date before the deadline, if you have questions on how to do this you can reach out to our tech support team who can guide you through this process.To recap: These 3 steps are pretty important. For certificates expiring this year renew them – you can renew 90 days in advance just be certain to generate a 2048bit CSR.For 1024 certs expiring in 2014 or later revoke and replace using a 2048 RSA/DSA key or a 256 ECC key..Again if you need additional information visit
  • On this slide there are a whole host of useful reference that if you want to read up on the subject they provide a real insight into what is happening from an industry perspective. I’ll hold on this slide for a few moments but please do take a screen shot and refer back to this for more information.Save this screen
  • If you use our Trust Centre Product here are the contact
  • Transferring from 1024 to 2048 SSL | Symantec Website Security Solutions

    1. 1. 1024-Bit MigrationInformational WebinarAndrew HorburyProduct Marketing Manager
    2. 2. The Topic• The National Institute of Standards and Technology(NIST) Special Publication 800-131A calls for the endof 1024-bit certificate usage by 31 December 20132• The Certification Authority/Browser (CA/B) Forumrequires the end-of-life for all 1024-bit certificatesand code signing products by 31 December 20131• Symantec fully supports the NIST and CA/B Forumpositions: staying ahead of encryption factoring isthe duty of every responsible CA31024-Bit Migration Webinar1. CA/Browser Forum, Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates v.1.1.3, CA/Browser Forum (21 February2013), Elaine Barker and Allen Roginsky, Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths, NIST (January 2011), Symantec, 2013 Industry Requirements: Ending Support for 1024-bit keys. Upgrade to 2048-bit keys or ECC Certificates, Symantec Corporation (May 2013),
    3. 3. 1024-Bit Migration WebinarMicrosoft, Windows Root Certificate Program - Technical Requirements, Microsoft Corporation (6 April 2011),
    4. 4. 1024-Bit Migration WebinarMozilla, Mozilla CA Certificate Maintenance Policy (Version 2.1), Mozilla (8 May 2013),
    5. 5. The RSA Algorithm• First publically described byRon Rivest, Adi Shamir, andLen Adleman in 1977• Since 1991, 17 RSA keylengths have been factored(hacked)1024-Bit Migration Webinar
    6. 6. Ending the life of a key sizeis a natural pointin the lifecycle of any algorithm.RSA Key Sizes Factored Over Time1024-Bit Migration WebinarAug 1999512Nov 2005640July 2012704Dec 2003576Dec 2009768?1024
    7. 7. Our Responsibility–to the industry, to trust online,and to you• We want to assist you through this key size’s lifecycle end• What you need to know: Migration Webinar
    8. 8. • We have a number of resources to support you through this keysize’s lifecycle end• Ready now:• For certificates expiring this year:– Symantec will allow them to expire naturally– Get help with generating a new Certificate Signing Request (CSR) at• For certificates expiring in 2014 and later:– Symantec is initiating a rolling revocation process, beginning 1 October 2013– Helps customers adopt new encryption levels before year-end IT blackoutperiods and busy holiday online shopping1024-Bit Migration WebinarGenerate a new CSRThis page has every tool you need to generate a new CSR for a compliant certificate.Our Responsibility – to the industry, to trust online,and to you
    9. 9. Keeping It SimpleCertificate expires:2013Certificate expires:2014+Generate a newCertificate SigningRequest with a validkey lengthbefore/when yourcertificate expires.Revoke and replaceyour Certificate witha valid certificatebefore 1 October2013.1024-Bit Migration Webinar
    10. 10. Do Your Part1. Find your 1024-bit certificates– Run a test on your fully qualified domain name (FQDN) to check for keylength.2. For certificates expiring this year:– At renewal, generate a CSR using a 2048-bit RSA key3. For certificates expiring in 2014 and later:– Revoke and replace all 1024-bit certificates with a CSR using a 2048-bitRSA/DSA or 256-bit ECC key (Read more about ECC– Symantec™ Managed PKI for SSL customers can configure 1024-bitcertificates with a customized expiration date before the deadline1024-Bit Migration WebinarCheck your certificate’s encryption strengthEasily determine the key-length of your certificates.
    11. 11. Save This Screen(Windows: “Alt-PrintScreen” or Mac: “Command-Shift-3”)••••••• Migration Webinar
    12. 12. 1024-Bit Migration WebinarTrust Center AccountUnited Kingdom: email: ssltechsupport@symantec.comTel: 0808 234 2897 or 0808 101 3911 (Cable and mobiles)France: email: ssltechsupport_fr@symantec.comTel: 0800 91 40 81Spain: email: ssltechsupport_es@symantec.comTel: 900 99 4142Germany: email: ssltechsupport_de@symantec.comTel: 0800 183 0624Denmark: email: ssltechsupport_dk@symantec.comTel: 80 88 20 30Sweden: email: ssltechsupport_se@symantec.comTel: 020-799270
    13. 13. 1024-Bit Migration WebinarManaged PKI for SSLUnited Kingdom: email: enterprise-sslsupport@symantec.comTel: 0808 234 2897 or 0808 101 3911 (Cable and mobiles)France: email: FRenterprise-sslsupport@symantec.comTel: 0800 91 40 81Spain: email: ESenterprise-sslsupport@symantec.comTel: 900 99 4142Germany: email: DEenterprise-sslsupport@symantec.comTel: 0800 183 0624Denmark: email: DKenterprise-sslsupport@symantec.comTel: 80 88 20 30Sweden: email: SEenterprise-sslsupport@symantec.comTel: 020-799270
    14. 14. Thank you!Copyright © 2013 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates inthe U.S. and other countries. Other names may be trademarks of their respective owners.This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the information in this document, either express or implied,are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice.1024-Bit Migration WebinarAndrew Horbury