{"id":197882,"date":"2025-09-25T06:47:00","date_gmt":"2025-09-25T05:47:00","guid":{"rendered":"https:\/\/liora.io\/en\/?p=197882"},"modified":"2026-02-06T07:42:15","modified_gmt":"2026-02-06T06:42:15","slug":"all-about-transport-layer-security","status":"publish","type":"post","link":"https:\/\/liora.io\/en\/all-about-transport-layer-security","title":{"rendered":"Transport Layer Security (TLS): What is it?"},"content":{"rendered":"<b>Since 2018, Google has mandated the use of the HTTPS protocol as the security standard for websites. Most likely, your own site has adopted this safeguard. But should you feel completely secure? Not entirely. In truth, HTTPS connections can be vulnerable if they&#8217;re not properly configured. Ideally, the TLS protection they integrate should be robust. Here is more information\u2026<\/b>\n\nThe Internet became widely accessible to the public starting in 1995. The need to establish <b>security standards<\/b> quickly became apparent.\n\nThis concern actually emerged almost 10 years earlier when <b>the Internet<\/b> was mainly used by researchers and academics. In 1986, the U.S. government formed a standards organization\u2014which later became autonomous\u2014called the <b>IETF or Internet Engineering Task Force<\/b>.\n\nIn 1999, recognizing the growing importance of the Web and the security risks it posed, the IETF developed <a href=\"https:\/\/liora.io\/en\/network-protocols-definition-operation-and-types\">a security protocol<\/a> named <b>TLS \u2013 Transport Layer Security<\/b>. Its purpose: to <b>encrypt communications<\/b> between two systems connected to the Internet. The most recent update (TLS 1.3) was released in 2018.\n\nIf you operate a website, it likely complies with the <b>HTTPS standard<\/b>, which is built on the <a href=\"https:\/\/liora.io\/en\/all-about-secure-sockets-layer\">SSL encryption standard<\/a>. Can you assume your website is protected from every threat? Not necessarily.\n\n<a href=\"\/en\/courses\/data-ai\/\">\nLearn about safety protocols\n<\/a>\n\n<style><br \/>\n.elementor-heading-title{padding:0;margin:0;line-height:1}.elementor-widget-heading .elementor-heading-title[class*=elementor-size-]>a{color:inherit;font-size:inherit;line-height:inherit}.elementor-widget-heading .elementor-heading-title.elementor-size-small{font-size:15px}.elementor-widget-heading .elementor-heading-title.elementor-size-medium{font-size:19px}.elementor-widget-heading .elementor-heading-title.elementor-size-large{font-size:29px}.elementor-widget-heading .elementor-heading-title.elementor-size-xl{font-size:39px}.elementor-widget-heading .elementor-heading-title.elementor-size-xxl{font-size:59px}<\/style>\n<h2>HTTPS incorporates TLS<\/h2>\nInitially, <b>websites<\/b> followed the HTTP standard, which lacked security. <b>Data<\/b> was transferred openly from <a href=\"https:\/\/liora.io\/en\/all-about-proxy-servers\">a server<\/a> to a browsing device, making it relatively easy for <a href=\"https:\/\/liora.io\/en\/all-about-certified-ethical-hackers\">a hacker<\/a> to intercept this information, including <b>passwords<\/b> and data submitted via a <b>form<\/b>.\n\nTo make the Web more secure, the company <b>Netscape<\/b>, which created the first popular <b>web browser<\/b>, developed an encryption protocol called SSL. <b>Websites<\/b> using this protection were identified by the HTTPS designation. By the late 2010s, <b>Google<\/b> deemed it essential and began penalizing HTTP sites in its search engine to encourage the shift to HTTPS.\n\nWhat&#8217;s the difference between HTTPS and TLS? There&#8217;s essentially no difference. SSL and hence the HTTPS protocol incorporate the <b>TLS algorithm<\/b>.\n\n<style><br \/>\n.elementor-widget-image{text-align:center}.elementor-widget-image a{display:inline-block}.elementor-widget-image a img[src$=\".svg\"]{width:48px}.elementor-widget-image img{vertical-align:middle;display:inline-block}<\/style>\t\t\t\t\t\t\t\t\t\t\t\t<img decoding=\"async\" width=\"1536\" height=\"1024\" src=\"https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-2.webp\" alt=\"\" loading=\"lazy\" srcset=\"https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-2.webp 1536w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-2-300x200.webp 300w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-2-1024x683.webp 1024w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-2-768x512.webp 768w\" sizes=\"(max-width: 1536px) 100vw, 1536px\">\n\nIn fact, HTTPS refers to implementing TLS encryption as an enhancement of the <b>HTTP protocol<\/b>. Hence, a website using HTTPS indeed relies on <b>TLS encryption<\/b>.\n\nIf you&#8217;ve read our earlier points, you might feel that HTTPS might not be sufficient in all situations. Why is that? Because some <b>HTTPS implementations<\/b> still depend on the original 1999 standard, namely <b>TLS 1.0<\/b>.\n\nTherefore, it\u2019s critical to ensure that an HTTPS TLS certificate specifies <b>TLS 1.3<\/b>. Why is this important?\n<h2>What is a TLS certificate?<\/h2>\nA website protected by HTTPS contains a TLS certificate. This certificate includes information about the domain owner and the server\u2019s public key (derived from a confidential private key), which are crucial for authenticating the server. This kind of certificate is issued by a certification authority such as Let\u2019s Encrypt, DigiCert, or GoDaddy, to a domain owner.\n\nYou can easily check any site\u2019s certificate while browsing. Click the small icon in the address bar before a website\u2019s address. This allows you to view the server&#8217;s TLS certificate\u2014it\u2019s sometimes called an \u201cSSL certificate\u201d due to confusion regarding the names of these protocols.\n\n<img decoding=\"async\" width=\"1536\" height=\"1024\" src=\"https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-4.webp\" alt=\"\" loading=\"lazy\" srcset=\"https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-4.webp 1536w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-4-300x200.webp 300w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-4-1024x683.webp 1024w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-4-768x512.webp 768w\" sizes=\"(max-width: 1536px) 100vw, 1536px\">\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex is-content-justification-center\"><div class=\"wp-block-button \"><a class=\"wp-block-button__link wp-element-button \" href=\"\/en\/courses\/data-ai\/\">Become a systems and network administrator<\/a><\/div><\/div>\n\n<h2>TLS handshake<\/h2>\nTo better understand how the certificate functions, let\u2019s explore what happens when a connection via TLS is established between a computer and a web server.\n\nWhen you enter or select a web address in your browser, a \u201c<b>TLS handshake<\/b>\u201d initiates between your computer or smartphone and the server hosting that website.\n\nDuring this handshake, your computer and the server:\n<ul>\n \t<li style=\"font-weight: 400;\" aria-level=\"1\">Specify the <b>version of TLS<\/b> (TLS 1.0, 1.2, 1.3) being used.<\/li>\n \t<li style=\"font-weight: 400;\" aria-level=\"1\">Agree on the <b>encryption<\/b> that will take place in the communication session <b>between the user&#8217;s computer and the server<\/b>. This encryption prevents data interception by third-parties.<\/li>\n \t<li style=\"font-weight: 400;\" aria-level=\"1\">Authenticate the <b>identity of the server<\/b> via its TLS certificate, meaning the server must verify its identity to the requesting computer.<\/li>\n \t<li style=\"font-weight: 400;\" aria-level=\"1\">Generate <a href=\"https:\/\/liora.io\/en\/all-about-cryptography\">cryptographic keys<\/a> that will manage the <b>encryption of the data exchanged<\/b> between both parties.<\/li>\n<\/ul>\n<img decoding=\"async\" width=\"1536\" height=\"1024\" src=\"https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-1.webp\" alt=\"\" loading=\"lazy\" srcset=\"https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-1.webp 1536w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-1-300x200.webp 300w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-1-1024x683.webp 1024w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-1-768x512.webp 768w\" sizes=\"(max-width: 1536px) 100vw, 1536px\">\n<h2>What has changed with TLS 1.3?<\/h2>\nAs we\u2019ve mentioned, the initial handshake step involves establishing the version of TLS in use. However, versions <b>TLS 1.0 and 1.1<\/b> are now considered outdated and insufficiently secure.\n\nA series of attacks around 2010 highlighted vulnerabilities in the basic TLS protection. Notable attacks include:\n<ul>\n \t<li style=\"font-weight: 400;\" aria-level=\"1\"><b>BEAST<\/b> (2011).<\/li>\n \t<li style=\"font-weight: 400;\" aria-level=\"1\"><b>CRIME<\/b> (2012) and <b>BREACH<\/b> (2013).<\/li>\n \t<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Heartbleed<\/b> (2014)<\/li>\n<\/ul>\nMajor <a href=\"https:\/\/liora.io\/en\/cloud-native-definition-features-benefits\">cloud platforms<\/a> have long stopped supporting TLS 1.0. The suggested version is TLS 1.3. Why?\n\nTLS 1.3 introduces the concept of <b>Perfect Forward Secrecy (PFS)<\/b>. Each session has a temporary protection key. Even if a server&#8217;s private key is compromised, a hacker couldn&#8217;t reconstruct data from previous sessions\u2014the decryption wouldn\u2019t succeed.\n\nThe key takeaway: ensure <b>TLS libraries<\/b> are current, especially on e-commerce sites. Tools like <b>Qualys SSL Labs<\/b> can verify this for you.\n\n<img decoding=\"async\" width=\"1536\" height=\"1024\" src=\"https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-3.webp\" alt=\"\" loading=\"lazy\" srcset=\"https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-3.webp 1536w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-3-300x200.webp 300w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-3-1024x683.webp 1024w, https:\/\/liora.io\/app\/uploads\/sites\/9\/2025\/07\/Transport-Layer-Security-Liora-3-768x512.webp 768w\" sizes=\"(max-width: 1536px) 100vw, 1536px\">\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex is-content-justification-center\"><div class=\"wp-block-button \"><a class=\"wp-block-button__link wp-element-button \" href=\"\/en\/courses\/data-ai\/\">Discover our training courses<\/a><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Since 2018, Google has mandated the use of the HTTPS protocol as the security standard for websites. Most likely, your own site has adopted this safeguard. But should you feel completely secure? Not entirely. In truth, HTTPS connections can be vulnerable if they&#8217;re not properly configured. Ideally, the TLS protection they integrate should be robust. [&hellip;]<\/p>\n","protected":false},"author":78,"featured_media":197884,"comment_status":"open","ping_status":"open","sticky":false,"template":"elementor_theme","format":"standard","meta":{"_acf_changed":false,"editor_notices":[],"footnotes":""},"categories":[2426],"class_list":["post-197882","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cybersecurity"],"acf":[],"_links":{"self":[{"href":"https:\/\/liora.io\/en\/wp-json\/wp\/v2\/posts\/197882","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/liora.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/liora.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/liora.io\/en\/wp-json\/wp\/v2\/users\/78"}],"replies":[{"embeddable":true,"href":"https:\/\/liora.io\/en\/wp-json\/wp\/v2\/comments?post=197882"}],"version-history":[{"count":5,"href":"https:\/\/liora.io\/en\/wp-json\/wp\/v2\/posts\/197882\/revisions"}],"predecessor-version":[{"id":205518,"href":"https:\/\/liora.io\/en\/wp-json\/wp\/v2\/posts\/197882\/revisions\/205518"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/liora.io\/en\/wp-json\/wp\/v2\/media\/197884"}],"wp:attachment":[{"href":"https:\/\/liora.io\/en\/wp-json\/wp\/v2\/media?parent=197882"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/liora.io\/en\/wp-json\/wp\/v2\/categories?post=197882"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}