{"id":18118,"date":"2024-11-11T11:28:33","date_gmt":"2024-11-11T16:28:33","guid":{"rendered":"https:\/\/www.thesslstore.com\/blog\/?p=18118"},"modified":"2024-11-11T11:28:35","modified_gmt":"2024-11-11T16:28:35","slug":"tls-1-0-inches-closer-to-full-retirement","status":"publish","type":"post","link":"https:\/\/www.thesslstore.com\/blog\/tls-1-0-inches-closer-to-full-retirement\/","title":{"rendered":"TLS 1.0 Inches Closer to Full Retirement (Nearly a Decade Later)"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\"><a href=\"https:\/\/azure.microsoft.com\/en-us\/updates\/v2\/update-retirement-tls1-0-tls1-1-versions-azure-services\">Microsoft Azure has pushed back<\/a> its TLS 1.0 and 1.1 end-of-life date to Aug. 31, 2025. This delay is another example of how long it takes to upgrade the protocols the internet runs on.<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">It\u2019s been more than half a decade since websites were told to start migrating from the TLS 1.0 protocol due to its vulnerability issues (and <a href=\"https:\/\/datatracker.ietf.org\/doc\/rfc8996\/\">3+ years since TLS 1.0 and 1.1 were officially deprecated<\/a>). But it\u2019s taking longer than expected to fully switch from TLS 1.0\/1.1 to TLS 1.2 as a minimum. What\u2019s the holdup?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Moving the entire internet from these early protocols isn\u2019t easy \u2014 many systems depend on them. We\u2019ll examine why these real-world security upgrades, TLS 1.2 and 1.3, are taking so long and what exactly these changes entail.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Plus, the internet is beginning an even bigger (and more challenging) migration: <a href=\"https:\/\/www.thesslstore.com\/blog\/nist-pqc-standards-are-out-where-do-we-go-from-here\/\">moving SSL\/TLS to post quantum cryptography<\/a>. Lessons from the past can smooth our path to the future.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s hash it out.<span id=\"newline\"><\/span><\/p>\n\n\n<span style=\"--tl-form-height-m:150.25px;--tl-form-height-t:121.4583px;--tl-form-height-d:121.4583px;\" class=\"tl-placeholder-f-type-shortcode_12753 tl-preload-form\"><span><\/span><\/span>\n\n\n<h2 class=\"wp-block-heading\">TL;DR: A Look at the Timeline of TLS Protocol Migrations<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s a quick overview of the timeline of when these <a href=\"https:\/\/www.ietf.org\/process\/rfcs\/\">Internet Engineering Task Force\u2019s requests for comments (RFCs)<\/a> were originally published and their current statuses:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>TLS 1.0 came out in 1999 as a replacement for SSL 2.0 and 3.0.<\/strong> It was published as <a href=\"https:\/\/datatracker.ietf.org\/doc\/rfc2246\/\"><strong>RFC 2246<\/strong><\/a> and was deprecated by <a href=\"https:\/\/datatracker.ietf.org\/doc\/rfc8996\/\"><strong>RFC 8996<\/strong><\/a> (published in June 2018) in March 2021.<\/li>\n\n\n\n<li><strong>TLS 1.1 was released in 2006 as <\/strong><a href=\"https:\/\/datatracker.ietf.org\/doc\/rfc4346\/\"><strong>IETF RFC 4346<\/strong><\/a><strong>.<\/strong> This protocol, meant to be a minimal upgrade to TLS 1.0, was also deprecated by RFC 8996.<\/li>\n\n\n\n<li><strong>TLS 1.2 was released in 2008 as <\/strong><a href=\"https:\/\/datatracker.ietf.org\/doc\/rfc5246\/\"><strong>IETF RFC 5246<\/strong><\/a><strong> and has been in use since.<\/strong> It\u2019s technically been obsoleted by RFC 8446, but it\u2019s currently still the most widely used protocol. &nbsp;<\/li>\n\n\n\n<li><strong>TLS 1.3 was published in 2018 as <\/strong><a href=\"https:\/\/datatracker.ietf.org\/doc\/rfc8446\/history\/\"><strong>IETF RFC 8446<\/strong><\/a><strong>.<\/strong> It\u2019s still in use today, although it\u2019s not as widely adopted as TLS 1.2.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s a visual representation of the establishment of the TLS 1.0 and 1.1 protocols and the migrations from them:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"583\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-0_1-1_1-2_1-3_timeline-1024x583.png\" alt=\"TLS 1.0 and 1.1 end of life timeline: A timeline for TLS protocol migration to eliminate TLS vulnerability issues\" class=\"wp-image-18120\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-0_1-1_1-2_1-3_timeline-1024x583.png 1024w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-0_1-1_1-2_1-3_timeline-300x171.png 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-0_1-1_1-2_1-3_timeline-768x437.png 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-0_1-1_1-2_1-3_timeline.png 1214w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\"><em>Image caption: The timeline illustrates the introduction and eventual deprecation of the TLS 1.0 and TLS 1.1 protocols and migration to current TLS security protocols.<\/em><\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">A 90-Second Review: Why Migrating from TLS 1.0 &amp; TLS 1.1 Is a Must<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s start with a quick review of why the shift to TLS 1.2 as a minimum is necessary (ideally, use TLS 1.3 instead):<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>TLS 1.0 is old enough to get a break on car insurance.<\/strong> Launched 25 years ago, this protocol supports outdated and weak <a href=\"https:\/\/www.thesslstore.com\/blog\/cipher-suites-algorithms-security-settings\/\">cipher suites<\/a> that leave systems vulnerable to exploitation.<\/li>\n\n\n\n<li><strong>TLS 1.1 was released in 2006 as a minor upgrade but was never fully adopted. <\/strong>The goal was to rectify some of the issues identified in version 1.0. However, TLS 1.1 also has issues (namely, its use of weak ciphers), which is why industry leaders have since deprecated both protocols.<\/li>\n\n\n\n<li><strong>PQC algorithms don\u2019t work with earlier protocols.<\/strong> While some TLS 1.3 implementations support quantum-resistant algorithms, the same can\u2019t be said about TLS 1.2 or earlier protocols. According to NIST\u2019s Migration to Post-Quantum Cryptography Quantum Readiness: Testing Draft Standards preliminary draft, <a href=\"https:\/\/www.nccoe.nist.gov\/sites\/default\/files\/2023-12\/pqc-migration-nist-sp-1800-38c-preliminary-draft.pdf\">PQC algorithms aren\u2019t retrofitted<\/a> to work with the 1.2 protocol.&nbsp;<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">What Are the Challenges of Migrating from TLS 1.0 and 1.1?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Think of moving from <a href=\"https:\/\/www.thesslstore.com\/blog\/what-does-ssl-stand-for-secure-sockets-layer\/\">secure sockets layer (SSL)<\/a> to transport layer security (TLS). Migrating from old internet security protocols is no small or easy task. The process is incredibly time-consuming and challenging, and we\u2019re already nearly a decade into that process for TLS 1.0 and 1.1. \u00a0<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, simply<em> stating<\/em> that these outdated standards need to be deprecated and <em>actually transitioning<\/em> every system, server, and other elements to eliminate these dependencies are two different things. For starters, there are many moving parts involved, some examples of which include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Standards and regulatory requirements (<a href=\"https:\/\/www.ietf.org\/\">IETF<\/a>, <a href=\"https:\/\/www.pcisecuritystandards.org\/\">PCI DSS<\/a>, <a href=\"https:\/\/www.nist.gov\/\">NIST<\/a>, etc.)<\/li>\n\n\n\n<li>Development libraries, frameworks, and services (<a href=\"https:\/\/www.openssl.org\/\">OpenSSL<\/a>, <a href=\"https:\/\/dotnet.microsoft.com\/en-us\/learn\/dotnet\/what-is-dotnet-framework\">.NET<\/a>, Microsoft, etc.)<\/li>\n\n\n\n<li>Devices and hardware components<\/li>\n\n\n\n<li>Web server software<\/li>\n\n\n\n<li>Content Delivery Networks (CDNs)<\/li>\n\n\n\n<li>Web hosting management software like cPanel, etc.<\/li>\n\n\n\n<li>Your organization\u2019s internal network(s) and endpoint devices<\/li>\n\n\n\n<li>Semi-separate networks (e.g., banking, payment services, IoT, etc.)<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Many of these parts require cascading changes \u2014 for example, software can\u2019t be upgraded until the libraries it uses and the servers it runs on have been upgraded.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What if these protocols had critical vulnerabilities that couldn\u2019t be patched? Would upgrading still take a decade? Things would likely be different. The migrations from both protocols would have been better prioritized and likely wouldn\u2019t have been pushed to the back burner by some organizations. But it still would have taken a long time.<\/p>\n\n\n<span style=\"--tl-form-height-m:861.156px;--tl-form-height-t:899.625px;--tl-form-height-d:899.625px;\" class=\"tl-placeholder-f-type-shortcode_12653 tl-preload-form\"><span><\/span><\/span>\n\n\n<h2 class=\"wp-block-heading\">How Many Websites Still Use TLS 1.0\/1.1?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">As of May 2, 2024, <a href=\"https:\/\/www.ssllabs.com\/ssl-pulse\/\">Qualys\u2019s SSL Labs SSL Pulse dashboard<\/a> showed that 27.9% of surveyed websites still supported the outdated protocol. Slightly higher still (30%) still supported TLS 1.1. Compare this to TLS 1.2 (99.9%) and 1.3 (70.1%), which are supported by most websites.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Our smaller but more recent internal data set shows a similar story with only 23% supporting TLS 1.0 and 24% supporting TLS 1.1.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Why do browsers and operating systems support multiple protocols, even when some of them are outdated? Because some users rely on legacy systems that may not support the newer, more secure protocols. These companies would have some pretty irked customers and users if they suddenly just \u201cpulled the plug\u201d on supporting the older protocols.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Which Browsers Do and Don\u2019t Support TLS 1.0 and 1.1<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Using the <a href=\"https:\/\/caniuse.com\/\">Can I Use search tool<\/a>, I checked the TLS 1.0 protocol to see which web clients, if any, still support it. Here\u2019s a quick look at what I found:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"343\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-0-1024x343.jpg\" alt=\"A screenshot the browser versions for which TLS 1.0 is deprecated to eliminate TLS 1.0 vulnerability issues\" class=\"wp-image-18121\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-0-1024x343.jpg 1024w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-0-300x100.jpg 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-0-768x257.jpg 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-0.jpg 1452w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\"><em>Image caption: A screenshot from caniuse.com\u2019s search tool.<\/em><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s a quick look at which browsers either fully or partially support the TLS 1.1 protocol and which ones don\u2019t on various desktop and mobile platforms:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"539\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-1-1024x539.jpg\" alt=\"A screenshot of caniuse.com's search tool that shows which browsers have TLS 1.1 deprecated or display warning messages.\" class=\"wp-image-18122\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-1-1024x539.jpg 1024w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-1-300x158.jpg 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-1-768x404.jpg 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-1.jpg 1470w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\"><em>Image caption: A screenshot from caniuse.com\u2019s search tool. Red blocks mean that the protocol isn\u2019t supported; green blocks mean it\u2019s fully supported; and the brownish color indicates that it\u2019s partially supported in those browser versions.<\/em><\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">How to Tell Whether Your Browser Is Using an Old Protocol<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wondering which protocols your web client supports? Here\u2019s a quick example of what came back when I tested my browser\u2019s SSL\/TLS capabilities using Qualys\u2019s SSL Labs SSL Client Test tool:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"761\" height=\"1024\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/ssl-tls-capabilities-browser-761x1024.jpg\" alt=\"This shows the user agents that support TLS 1.2 minimum because TLS 1.0 or TLS 1.1 are deprecated\" class=\"wp-image-18123\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/ssl-tls-capabilities-browser-761x1024.jpg 761w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/ssl-tls-capabilities-browser-223x300.jpg 223w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/ssl-tls-capabilities-browser-768x1034.jpg 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/ssl-tls-capabilities-browser.jpg 1041w\" sizes=\"auto, (max-width: 761px) 100vw, 761px\" \/><figcaption class=\"wp-element-caption\"><em>Image caption: A screenshot from Qualys\u2019 SSL Labs SSL Client Test user agent data, which shows that my browser does not support the insecure protocols SSL 3, SSL 2, TLS 1.0, or TLS 1.1.<\/em><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This tool will also show you which strong and weak cipher suites your browser supports (listed in order of preference) and whether it supports TLS compression.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">6 Examples of the Industry\u2019s Migration Journeys<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">So, what\u2019s the process of migrating away from TLS 1.0 and 1.1 look like? For some, it\u2019s been a long journey that we\u2019d either wished had gone a bit more smoothly or would like to see wrap up sooner than later:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>GitHub<\/strong> \u2014 My former colleague enlightened you about <a href=\"https:\/\/www.thesslstore.com\/blog\/deprecation-tls-1-0-1-1-underway\/\">GitHub\u2019s challenges<\/a> while deprecating the two protocols in February 2018. It temporarily disabled TLS 1.0 and 1.1 for an hour as a precursor to its full shutdown of the protocols two weeks later. Unfortunately, those still using the protocols apparently didn\u2019t get the message, and the official change over created some issues.&nbsp;<\/li>\n\n\n\n<li><strong>Google Chrome<\/strong> \u2014 It was originally planned for Chrome version 72 but the <a href=\"https:\/\/www.thesslstore.com\/blog\/google-chrome-72-deprecates-support-for-tls-1-0-tls-1-1\/\">browser officially began its move from TLS 1.0 and 1.1<\/a> to TLS 1.2 as a minimum by displaying a warning in Dev Tools. This warning shifted to displaying a full-page warning in Chrome 81, then Chrome 91; eventually, Chrome 98 made the error non-bypassable. However, it fully <a href=\"https:\/\/chromestatus.com\/feature\/5759116003770368\">kicked the outdated protocols to the curb once and for all in Chrome 84<\/a>.<\/li>\n\n\n\n<li><strong>PCI DSS<\/strong> \u2014 The Payment Card Industry Data Security Standards (PCI DSS) implemented a June 30, 2018 <a href=\"https:\/\/blog.pcisecuritystandards.org\/migrating-from-ssl-and-early-tls\">deadline to disable all SSL protocols and TLS 1.0<\/a> in favor of TLS 1.1+. This replaced the earlier June 2016 deadline that got pushed back. The only exception for the mandatory change to TLS 1.1+ was for payment terminals that could be verified as \u201cnot being susceptible to any known exploits for SSL and early TLS.\u201d Now, the PCI Standards Council (PCI SSC) recommends <a href=\"https:\/\/www.pcisecuritystandards.org\/faq\/articles\/Frequently_Asked_Question\/Does-PCI-DSS-define-which-versions-of-TLS-must-be-used\/\">moving away from \u201cearly TLS\u201d versions<\/a> as security controls for everything else and <a href=\"https:\/\/blog.pcisecuritystandards.org\/are-you-ready-for-30-june-2018-sayin-goodbye-to-ssl-early-tls\">strongly encourages the use of TLS 1.2<\/a>.<\/li>\n\n\n\n<li><strong>NIST<\/strong> \u2014 The National Institute of Standards and Technology, the standards body for U.S. federal agencies and contractors, has published multiple versions of SP 800-52 to migrate through the various TLS protocols. The latest, <a href=\"https:\/\/csrc.nist.gov\/pubs\/sp\/800\/52\/r2\/final\">SP 800-52 Rev. 2<\/a>, requires TLS 1.2 and support for TLS 1.3.<\/li>\n\n\n\n<li><strong>Microsoft<\/strong> \u2014 As of Oct. 31, 2018, <a href=\"https:\/\/learn.microsoft.com\/en-us\/purview\/tls-1.0-and-1.1-deprecation-for-office-365\">Microsoft deprecated TLS 1.0 and 1.1 support<\/a> in its Office 365 services. While many Microsoft services and systems have migrated to TLS 1.2 or higher, others are taking more time. The company provides a list of the Microsoft Azure offerings that still <a href=\"https:\/\/techcommunity.microsoft.com\/blog\/microsoftsecurityandcompliance\/support-for-legacy-tls-protocols-and-cipher-suites-in-azure-offerings\/3952099\">support legacy TLS protocols<\/a>.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Final Thoughts: A Few Tips to Help You Migrate Away From TLS 1.0 &amp; 1.1<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Removing TLS 1.0 and 1.1 dependencies is a must to eliminate security risks and compliance issues. Here are some of the ways you can do it within your organization\u2019s ecosystem:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Create a TLS migration plan.<\/strong> This document will outline the necessary steps to keep you on track and provide any specifics you might need to carry out the migration.<\/li>\n\n\n\n<li><strong>Check your endpoint devices and servers for deprecated protocols.<\/strong> This includes SSL (any version), TLS 1.0, and TLS 1.1. On Windows Servers, you can check the Secure Channel (SCHANNEL) to see <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows\/win32\/secauthn\/protocols-in-tls-ssl--schannel-ssp-\">which protocols are supported<\/a>.<\/li>\n\n\n\n<li><strong>Scan your network traffic to identify any pre-TLS 1.2 protocols in use.<\/strong> You can do this using OpenSSL, NMAP, or a tool like WireShark for data packet capture and analysis.<\/li>\n\n\n\n<li><strong>Check your apps for hard-coded outdated protocols.<\/strong> Analyze your web apps and software code for any hardcoded uses of any of these insecure protocols. Be sure to implement regression testing after disabling the outdated protocols.<\/li>\n\n\n\n<li><strong>Update your software and web clients. <\/strong>You can\u2019t run the newer protocols on systems and apps that haven\u2019t been updated since the TV show \u201cFirefly\u201d got canceled.&nbsp;<\/li>\n\n\n\n<li><strong>Communicate protocol changes to your users, employees, partners, and other stakeholders.<\/strong> Prepare them in advance by communicating about the changes to eliminate any protocols earlier than TLS 1.2. Keep them informed as needed throughout and after the migration. &nbsp;<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Needless to say, kowtowing to the insecure protocol requirements of legacy systems is a surefire way for sensitive data to become breached.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bad guys are always looking for a way into your network and systems. They want to get their hands on your data. Don\u2019t give them the opportunity \u2014 eliminate vulnerable, outdated TLS protocols within your IT ecosystem now and save yourself the headaches later.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It\u2019s not too early to start planning your migration to post-quantum cryptography&#8230;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.thesslstore.com\/blog\/nist-pqc-standards-are-out-where-do-we-go-from-here\/\">NIST\u2019s 3 PQC Standards Are Out \u2014 Where Do We Go From Here?<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.thesslstore.com\/blog\/key-takeaways-from-the-second-pki-consortium-post-quantum-cryptography-conference\/\">Key Takeaways from the Second PKI Consortium Post-Quantum Cryptography Conference<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.thesslstore.com\/blog\/post-quantum-cryptography-data-security-in-a-post-quantum-world\/\">Post Quantum Cryptograph: Data Security in a Post Quantum World<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.thesslstore.com\/blog\/post-quantum-cryptography-10-things-you-need-to-know\/\">Post Quantum Cryptography: 10 Things You Need to Know<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft Azure has pushed back its TLS 1.0 and 1.1 end-of-life date to Aug. 31, 2025. This delay is another example of how long it takes to upgrade the protocols&#8230;<\/p>\n","protected":false},"author":17,"featured_media":18125,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":"","tve_updated_post":"","tve_custom_css":"","tve_user_custom_css":"","tve_globals":{},"tcb2_ready":0,"tcb_editor_enabled":0,"tve_landing_page":"","_tve_header":"","_tve_footer":""},"categories":[13107,16],"tags":[13302,13303,7639,8998],"class_list":["post-18118","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-beyond-hashed-out","category-hashing-out-cyber-security","tag-outdated-tls","tag-protocol-deprecation","tag-tls-1-0","tag-tls-1-1","post-with-tags"],"views":7299,"jetpack_featured_media_url":"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2024\/11\/tls_1-0_tls_1-1-feature.jpg","_links":{"self":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/18118","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/comments?post=18118"}],"version-history":[{"count":0,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/18118\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media\/18125"}],"wp:attachment":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media?parent=18118"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/categories?post=18118"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/tags?post=18118"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}