{"id":6705,"date":"2024-04-01T03:16:04","date_gmt":"2024-04-01T03:16:04","guid":{"rendered":"https:\/\/www.pufsecurity.com\/?post_type=dlp_document&#038;p=6705"},"modified":"2024-04-01T03:16:07","modified_gmt":"2024-04-01T03:16:07","slug":"embracing-a-more-secure-era-with-tls-1-3","status":"publish","type":"dlp_document","link":"https:\/\/www.pufsecurity.com\/zh-hant\/document\/embracing-a-more-secure-era-with-tls-1-3\/","title":{"rendered":"Embracing a More Secure Era with TLS 1.3"},"content":{"rendered":"\n<p><strong>TLS Background and Latest Developments<\/strong><\/p>\n\n\n\n<p>Transport Layer Security (TLS) is the protocol that underpins secure client\/server communications over the Internet. TLS guarantees this by providing the cryptographic functions of authentication, confidentiality, and integrity checking. First, the identities of both the client and server are authenticated, to prevent impersonation by either party. For example, a bank\u2019s customer wants to be certain that they are sending their private information to their bank\u2019s authenticated server. Second, the messages sent between the endpoints need to remain confidential and unreadable, except for the client\/server. Finally, the integrity of exchanged messages must stay intact; that is, it should be impossible to modify messages without being detected. Together, the two phases of TLS perform these duties, with the \u201chandshake\u201d phase authenticating the client\/server and the \u201crecord\u201d phase preserving message confidentiality and integrity. TLS enhances security across various areas, including cloud services, data centers, network connections, and the expanding world of IoT.<\/p>\n\n\n\n<p>First developed in 1994 by Netscape, the Secure Socket Layer (SSL) was the predecessor of TLS. However, the initial version (v1.0) of SSL was never published because of too many security flaws. Thus, the official history of TLS begins with SSL v2.0, as seen in the timeline below:<\/p>\n\n\n\n<p><\/p>\n\n\n<style>.kb-image6705_575b3b-9a.kb-image-is-ratio-size, .kb-image6705_575b3b-9a .kb-image-is-ratio-size{max-width:575px;width:100%;}.wp-block-kadence-column > .kt-inside-inner-col > .kb-image6705_575b3b-9a.kb-image-is-ratio-size, .wp-block-kadence-column > .kt-inside-inner-col > .kb-image6705_575b3b-9a .kb-image-is-ratio-size{align-self:unset;}.kb-image6705_575b3b-9a figure{max-width:575px;}.kb-image6705_575b3b-9a .image-is-svg, .kb-image6705_575b3b-9a .image-is-svg img{width:100%;}.kb-image6705_575b3b-9a .kb-image-has-overlay:after{opacity:0.3;}.kb-image6705_575b3b-9a img.kb-img, .kb-image6705_575b3b-9a .kb-img img{box-shadow:0px 0px 14px 0px rgba(0, 0, 0, 0.2);}<\/style>\n<div class=\"wp-block-kadence-image kb-image6705_575b3b-9a\"><figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"716\" height=\"238\" src=\"https:\/\/www.pufsecurity.com\/wp-content\/uploads\/2024\/04\/Figure-1_TLS-Development.png\" alt=\"\" class=\"kb-img wp-image-6709\" srcset=\"https:\/\/www.pufsecurity.com\/wp-content\/uploads\/2024\/04\/Figure-1_TLS-Development.png 716w, https:\/\/www.pufsecurity.com\/wp-content\/uploads\/2024\/04\/Figure-1_TLS-Development-300x100.png 300w\" sizes=\"(max-width: 716px) 100vw, 716px\" \/><figcaption><em>Figure 1: TLS Development Timeline<\/em><\/figcaption><\/figure><\/div>\n\n\n\n<p>The final version of SSL published by Netscape was v3.0, after which subsequent protocols have been renamed to TLS, along with a change of ownership to the Internet Engineering Task Force (IETF). As <a href=\"https:\/\/techcommunity.microsoft.com\/t5\/windows-it-pro-blog\/tls-1-0-and-tls-1-1-soon-to-be-disabled-in-windows\/ba-p\/3887947\" title=\"\">Microsoft<\/a> plans to disable TLS 1.0 and 1.1 soon, users are getting ready to move to TLS 1.2 and 1.3.<\/p>\n\n\n\n<p>TLS 1.3 offers attractive speed and security improvement benefits that are hard to ignore. The handshake phase was sped up by removing one or more roundtrips (back and forth messaging between client and server) in TLS 1.3 \u2013 with \u201cor more\u201d meaning that for certain cases, roundtrips can be entirely eliminated (0-RTT). During the round phase, TLS 1.3 has added support for the generally faster Digital Signature Algorithm (DSA) over Edwards curves (EdDSA), as compared to DSA over elliptic curves (ECDSA). Security was improved by removing weaker elements while also mandating the use of stronger ones. This included removing obsolete ciphers (such as AES-CBC, RC4, Triple-DES) and less secure elliptic curves. In their place, only cipher suites using authenticated encryption with associated data (AEAD) are supported. Finally, all key agreements in TLS 1.3 are required to use ephemeral keys, granting perfect forward secrecy (PFS). So even if a previously used session key is discovered by hackers, future (forward) sessions will still be protected.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<p><strong>PUFsecurity Unveils Next-Generation Crypto Coprocessor \u2013 PUFcc7 to Support TLS 1.3<\/strong><\/p>\n\n\n\n<p>PUFsecurity has recently introduced the latest member of its <a href=\"https:\/\/www.pufsecurity.com\/products\/pufcc\/\" title=\"\">Crypto Coprocessor family<\/a>, PUFcc7. The new Crypto Coprocessor fully supports all the cryptographic primitive requirements of TLS 1.3 mentioned above.<\/p>\n\n\n\n<p>The AEAD cipher suite is handled by PUFcc7\u2019s AES cipher and secure hash engines, using keys from the built-in hash-based key derivation function (HKDF) module. Digital signatures and key agreements are implemented with PUFcc7\u2019s public key cryptography (PKC) engine. Finally, PUFcc7 also includes a<a href=\"https:\/\/csrc.nist.gov\/pubs\/sp\/800\/90\/a\/r1\/final\" title=\"\"> NIST SP800-90A<\/a> compliant deterministic random bit generator (DRBG), which is the same as the CSPRNG described in the TLS 1.3 documentation.<\/p>\n\n\n\n<p>A detailed mapping between these TLS 1.3 primitives and the standard crypto engine configuration of PUFcc7 is shown in Table 1:<\/p>\n\n\n<style>.kb-image6705_3cd5d9-2f.kb-image-is-ratio-size, .kb-image6705_3cd5d9-2f .kb-image-is-ratio-size{max-width:718px;width:100%;}.wp-block-kadence-column > .kt-inside-inner-col > .kb-image6705_3cd5d9-2f.kb-image-is-ratio-size, .wp-block-kadence-column > .kt-inside-inner-col > .kb-image6705_3cd5d9-2f .kb-image-is-ratio-size{align-self:unset;}.kb-image6705_3cd5d9-2f figure{max-width:718px;}.kb-image6705_3cd5d9-2f .image-is-svg, .kb-image6705_3cd5d9-2f .image-is-svg img{width:100%;}.kb-image6705_3cd5d9-2f .kb-image-has-overlay:after{opacity:0.3;}<\/style>\n<div class=\"wp-block-kadence-image kb-image6705_3cd5d9-2f\"><figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"799\" height=\"668\" src=\"https:\/\/www.pufsecurity.com\/wp-content\/uploads\/2024\/04\/Table-1.png\" alt=\"\" class=\"kb-img wp-image-6712\" srcset=\"https:\/\/www.pufsecurity.com\/wp-content\/uploads\/2024\/04\/Table-1.png 799w, https:\/\/www.pufsecurity.com\/wp-content\/uploads\/2024\/04\/Table-1-300x251.png 300w, https:\/\/www.pufsecurity.com\/wp-content\/uploads\/2024\/04\/Table-1-768x642.png 768w\" sizes=\"(max-width: 799px) 100vw, 799px\" \/><figcaption><em>Table1: TLS 1.3 Requirements Supported by PUFcc7<\/em><\/figcaption><\/figure><\/div>\n\n\n\n<p>PUFcc7 includes additional PKC, SHA, and MAC algorithms to increase security strength and time performance to meet TLS1.3 requirements.<\/p>\n\n\n\n<p>In the PKC part, PUFcc7 added EdDSA, X25519, and X448. The time performance of the overall Public Key Algorithm has been enhanced, and the three levels of performance settings make it more flexible to use in various applications. Regarding security strength, it also provides four selectable PKC configurations supporting 256, 384, 521, and RSA. PUFcc7 also adds SHA3 and KMAC to fully meet TLS1.3\u2019s requirements. In addition, the Key Wrapping method also provides further encryption processing options on top of the original PUF scramble. PUFcc7 also provides the flexibility to function as a TLS hardware accelerator, thereby offloading TLS functions from the main CPU and freeing up valuable cycles for other system processing tasks.<\/p>\n\n\n\n<p>Practically all secure communications over the Internet depend on the TLS protocol, with the latest version 1.3 offering a faster and more secure experience over version 1.2. Given the number of connected devices today, repeatedly executing the cryptographic primitives of TLS is a common occurrence for most modern systems. For system architects looking to add security as well as speed up the routine tasks of TLS, PUFsecurity\u2019s latest PUFcc7 Crypto Coprocessor makes this easy, with built-in <a href=\"https:\/\/www.pufsecurity.com\/technology\/hardware-root-of-trust\/\" title=\"\">hardware root of trust (HRoT)<\/a> and hardware-accelerated crypto engines for implementing TLS 1.3, all wrapped with a plug-and-play AMBA interface for drop-in integration. <\/p>\n\n\n\n<p>In modern IoT ecosystems, smart devices integrated with PUFcc7 and TLS1.3 support ensure secure data exchange with the cloud. These smart devices leverage PUF for generating unique cryptographic keys, avoiding potential attacks on key storage and transmission. With the latest TLS protocols in place, data communication between smart devices and the cloud occurs over encrypted channels, ensuring confidentiality and integrity during transmission. The TLS handshake process authenticates both ends of the communication, verifying the identity of the devices and establishing a secure connection. This robust combination of PUF and TLS enables seamless and secure data exchange between smart devices and the cloud, empowering a more secure IoT world.<\/p>\n\n\n\n<p><\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>TLS 1.3 offers attractive speed and security improvement benefits that are hard to ignore. The handshake phase was sped up by removing one or more roundtrips (back and forth messaging between client and server) in TLS 1.3 \u2013 with \u201cor more\u201d meaning that for certain cases, roundtrips can be entirely eliminated (0-RTT). During the round phase, TLS 1.3 has added support for the generally faster Digital Signature Algorithm (DSA) over Edwards curves (EdDSA), as compared to DSA over elliptic curves (ECDSA).<\/p>\n","protected":false},"author":12,"featured_media":6706,"template":"","doc_tags":[284,283,200,285,282],"class_list":["post-6705","dlp_document","type-dlp_document","status-publish","has-post-thumbnail","hentry","doc_categories-article","doc_tags-iot","doc_tags-pufcc7","doc_tags-root-of-trust","doc_tags-security","doc_tags-tls"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.pufsecurity.com\/zh-hant\/wp-json\/wp\/v2\/dlp_document\/6705"}],"collection":[{"href":"https:\/\/www.pufsecurity.com\/zh-hant\/wp-json\/wp\/v2\/dlp_document"}],"about":[{"href":"https:\/\/www.pufsecurity.com\/zh-hant\/wp-json\/wp\/v2\/types\/dlp_document"}],"author":[{"embeddable":true,"href":"https:\/\/www.pufsecurity.com\/zh-hant\/wp-json\/wp\/v2\/users\/12"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.pufsecurity.com\/zh-hant\/wp-json\/wp\/v2\/media\/6706"}],"wp:attachment":[{"href":"https:\/\/www.pufsecurity.com\/zh-hant\/wp-json\/wp\/v2\/media?parent=6705"}],"wp:term":[{"taxonomy":"doc_tags","embeddable":true,"href":"https:\/\/www.pufsecurity.com\/zh-hant\/wp-json\/wp\/v2\/doc_tags?post=6705"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}