{"id":13080,"date":"2020-09-02T10:59:20","date_gmt":"2020-09-02T14:59:20","guid":{"rendered":"https:\/\/www.thesslstore.com\/blog\/?p=13080"},"modified":"2023-04-10T12:55:11","modified_gmt":"2023-04-10T16:55:11","slug":"tls-is-only-as-strong-as-its-weakest-link","status":"publish","type":"post","link":"https:\/\/www.thesslstore.com\/blog\/tls-is-only-as-strong-as-its-weakest-link\/","title":{"rendered":"TLS Is Only as Strong as Its Weakest Link"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\" id=\"h-weak-encryption-is-a-real-risk-to-data-privacy-and-security-this-article-based-on-packet-detectives-episode-the-case-of-the-unknown-tls-versions-shows-how-you-can-use-packet-capture-via-endace-and-wireshark-to-discover-the-outdated-vulnerable-devices-that-exist-on-your-network\">Weak encryption is a real risk to data privacy and security. This article, based on Packet Detectives\u2019 episode \u201c<a href=\"https:\/\/www.youtube.com\/watch?v=hxCDqLn0NLc\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>The case of the unknown TLS versions,<\/strong><\/a>\u201d shows how you can use packet capture (via Endace) and Wireshark to discover the outdated &amp; vulnerable devices that exist on your network<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Updates to TLS have significantly strengthened data privacy over the Internet with the introduction of perfect forward secrecy and stronger crypto ciphers in TLS 1.2 and <a href=\"https:\/\/www.thesslstore.com\/blog\/tls-1-3-everything-possibly-needed-know\/\">TLS 1.3<\/a>. Stronger cyphers, which are almost impossible to crack using modern computers, protects the privacy of sensitive data as it traverses the Internet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Weak cyphers can leave sensitive transactions exposed to brute force attacks and <a href=\"https:\/\/www.thesslstore.com\/blog\/man-in-the-middle-attack\/\">man-in-the-middle (MitM) attacks<\/a>. For example, your login credentials, password, or sensitive data that displays in your web browser may be exposed if a cybercriminal decrypts a TLS session can be decrypted. It\u2019s for this reason that the industry is rapidly moving to deprecate TLS 1.0 and 1.1.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Back in 2018, <a href=\"https:\/\/www.thesslstore.com\/blog\/apple-microsoft-google-disable-tls-1-0-tls-1-1\/\">Google, Microsoft, Apple and Mozilla announced<\/a> that their browsers will remove support for these outdated versions of TLS. Many cloud services, such as Office 365, have pledged to do the same.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To reduce the threat of these attacks and the consequences that accompany them, it\u2019s essential that all of your devices, servers and applications are using the most recent versions of TLS (TLS 1.2 or later). But how can you tell what version of TLS encryption is being used? And how can you ensure that all of your connected devices and endpoints aren\u2019t using outdated versions of the TLS protocol? We\u2019ll walk you through the process of collecting network packet data using Endace and Wireshark.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s hash it out.<span id=\"newline\"><\/span><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-why-using-tls-1-2-or-better-matters-to-secure-data-encryption-channels\">Why Using TLS 1.2 or Better Matters to Secure Data Encryption Channels<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">It\u2019s important to ensure recent versions of TLS are being used by all devices, servers and applications in the enterprise to reduce these threats. <a href=\"https:\/\/www.ssllabs.com\/ssl-pulse\/\" target=\"_blank\" rel=\"noreferrer noopener\">August 2020 data from SSL Labs<\/a> shows that 65.5% of sites support TLS 1.2, whereas 32.8% support TLS 1.3. This data is based on the 150,000 most popular sites in the world (according to Alexa\u2019s list).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">But what decides which version of TLS the client and server use to communication? The version of TLS that\u2019s used to encrypt data is defined through a negotiation between the server and client where a handshake agrees on the strongest encryption that both can handle.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hashed Out has broken down the <a href=\"https:\/\/www.thesslstore.com\/blog\/explaining-ssl-handshake\/\">TLS handshake process<\/a> before. However, here\u2019s a visual overview of how that process works \u2014 and the communications that take place between the client and the server \u2014 as a quick reminder.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"897\" height=\"1024\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2017\/01\/SSL_Handshake_10-Steps-1-897x1024.png\" alt=\"A visual breakdown of the TLS 1.2 handshake\" class=\"wp-image-3366 addshadow\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2017\/01\/SSL_Handshake_10-Steps-1-897x1024.png 897w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2017\/01\/SSL_Handshake_10-Steps-1-263x300.png 263w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2017\/01\/SSL_Handshake_10-Steps-1-768x876.png 768w\" sizes=\"auto, (max-width: 897px) 100vw, 897px\" \/><figcaption>An illustration of how the TLS 1.2 handshake process works<\/figcaption><\/figure><\/div>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1000\" height=\"374\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/03\/TLS_1_3_Handshake.jpg\" alt=\"A visual breakdown of the TLS 1.3 handshake\" class=\"wp-image-6088 addshadow\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/03\/TLS_1_3_Handshake.jpg 1000w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/03\/TLS_1_3_Handshake-300x112.jpg 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2018\/03\/TLS_1_3_Handshake-768x287.jpg 768w\" sizes=\"auto, (max-width: 1000px) 100vw, 1000px\" \/><figcaption>An illustration of the shorter TLS 1.3 handshake process, which involves one roundtrip instead of two.<\/figcaption><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">Every device that uses SSL\/TLS \u2014 including applications, networking elements, servers, IoT devices and endpoints \u2014 must be updated with the latest software and\/or OS that supports TLS 1.2 or greater. Furthermore, each device must be configured to deny connection requests at TLS 1.1 and lower.<\/p>\n\n\n<span style=\"display:none\" class=\"tl-placeholder-f-type-shortcode_12653\"><\/span>\n\n\n<p class=\"wp-block-paragraph\">That\u2019s because outdated and legacy devices become the weakest link for security and data privacy. Needless to say, tracking down all the devices in your enterprise and updating them can be a daunting task \u2014 especially when just about every device connects to Wi-Fi and has a web interface!<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-you-can-use-packet-capture-to-detect-old-tls-version-traffic\">You Can Use Packet Capture to Detect Old TLS Version Traffic<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Some firewalls can detect and block traffic by TLS version, so one solution is to block older TLS traffic in your network. However, blocking older versions of TLS without certain knowledge of who or what is using them can lead to nasty (and unintended) surprises.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Updating web browsers may not be enough to remove older TLS traffic. Many endpoints on the network use TLS \u2014 including servers, software agents and IoT devices \u2014 and all of these can also be outdated. Another approach is to observe what is happening on the network and identify where older TLS traffic is originating. Outdated TLS agents can then be identified and, if needed, updated or replaced before blocking traffic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Server logs, event logs and monitoring systems don\u2019t necessarily track the TLS version, so an EndaceProbe is used to capture the TLS version negotiations. Packet capture gives a true and accurate picture of all network activity \u2014 so nothing is missed or altered, and it\u2019s hard to argue with (should that become necessary). The downside is without good methodology, a huge amount of data (that&#8217;s difficult to use) can be collected \u2014 and that\u2019s a lot of noise to sort through. But with the right steps, this process is easily managed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-how-to-capture-assess-tls-version-negotiations-traffic\">How to Capture &amp; Assess TLS Version Negotiations &amp; Traffic<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">First, create a filter on the EndaceProbe (for example, <strong>Port443<\/strong>) in a Wireshark-compatible syntax to capture Port 443 traffic. Set the filter to ignore any other traffic that you don\u2019t need.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"504\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-filter-1024x504.png\" alt=\"Screenshot of packet filtering using EndaceProbe\" class=\"wp-image-13081 addshadow\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-filter-1024x504.png 1024w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-filter-300x148.png 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-filter-768x378.png 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-filter.png 1284w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">Using smart truncation in addition to filtering will reduce the data volume even further by truncating data packets and leaving TLS handshake negotiations intact. This reduces the size of the capture file, which is easier to store and manage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Apply the Port443 filter to a data pipe on the EndaceProbe and let that capture for a full day to get a typical traffic sample. Port 443 is strictly for <a href=\"https:\/\/www.thesslstore.com\/blog\/what-does-https-protect\/\">HTTPS traffic<\/a>.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"493\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-data-pipe-1024x493.png\" alt=\"Screenshot of the data pipe on EndaceProbe\" class=\"wp-image-13082 addshadow\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-data-pipe-1024x493.png 1024w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-data-pipe-300x144.png 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-data-pipe-768x370.png 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-data-pipe.png 1278w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"729\" height=\"193\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-files.png\" alt=\"Screenshot of files using EndaceProbe\" class=\"wp-image-13083 addshadow\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-files.png 729w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-files-300x79.png 300w\" sizes=\"auto, (max-width: 729px) 100vw, 729px\" \/><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">You are now ready to analyze. You can get a quick overview, using the built-in investigation tool, where traffic on Port 443 is going. Microsoft One Drive traffic tops the list, which is not unexpected \u2014 but take a look at that Tik Tok (musical.ly) traffic!<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"985\" height=\"325\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-traffic-breakdown.png\" alt=\"A screenshot of the port 443 traffic breakdown\" class=\"wp-image-13084 addshadow\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-traffic-breakdown.png 985w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-traffic-breakdown-300x99.png 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/endaceprobe-traffic-breakdown-768x253.png 768w\" sizes=\"auto, (max-width: 985px) 100vw, 985px\" \/><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">To get into more detail and look into the fields of the TLS Hello packets, you\u2019ll need to use a tool like Wireshark. Limit the time window to work hours and extract the capture from the EndaceProbe. This results in a 48GB capture file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can further reduce the amount of data by applying a Wireshark read filter when opening the capture file. This limits what is read into <em>tls.handshake.type<\/em> packets with a type of 1 or 2 \u2014 the handshake types for client and server Hellos \u2014 and ignores items like certificate and key exchanges. This reduces the number of packets loaded into Wireshark from more than 5 million to about 42,000.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"729\" height=\"480\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-open-capture-file.png\" alt=\"A screenshot of the WireShark open capture file window\" class=\"wp-image-13086 addshadow\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-open-capture-file.png 729w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-open-capture-file-300x198.png 300w\" sizes=\"auto, (max-width: 729px) 100vw, 729px\" \/><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">You can save time in Wireshark by using a profile. These examples use a Wireshark profile that has been created to filter by TLS version on the client or server. You can download this Wireshark profile from the <a href=\"https:\/\/www2.endace.com\/packet-detectives-EP2-wireshark-profiles.zip\">Endace website<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-assess-the-packet-details-to-determine-the-highest-version-of-tls\">Assess the Packet Details to Determine the Highest Version of TLS<\/h3>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"107\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-profile-1024x107.png\" alt=\"A screenshot of the TLS audit window\" class=\"wp-image-13085 addshadow\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-profile-1024x107.png 1024w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-profile-300x31.png 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-profile-768x80.png 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-profile.png 1471w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">During the handshake, the server will only go to the highest TLS version that the client supports. This means that a good starting point is to examine the Client Hellos first. If you look at the packet detail of a Client Hello packet, you can see the TLS version and maximum version capabilities of that client.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The capture shows the actual TLS version in use and the clients using it. Many things can influence the TLS version used. For example, a web browser requesting an older TLS version may be due to a cookie from the last conversation, or maybe a non-browser software agent or device is in use.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If outdated clients are found, there may be much work yet to be done, but at least you now know with some certainty where the problem areas are.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"870\" height=\"394\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-client-hello-record-layer.png\" alt=\"A screenshot of the traffic capture window that shows the version of TLS\" class=\"wp-image-13087 addshadow\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-client-hello-record-layer.png 870w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-client-hello-record-layer-300x136.png 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-client-hello-record-layer-768x348.png 768w\" sizes=\"auto, (max-width: 870px) 100vw, 870px\" \/><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">The server makes the final determination of which TLS version is used by selecting the highest version that both client and server support. You can list servers using Wireshark\u2019s statistics and endpoints, and then apply <strong>Limit to display<\/strong> using the filter, so only those servers using TLS 1.1 or older are listed. This will allow you to further narrow down on the specific traffic you\u2019re targeting.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"504\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-filter-traffic-display-1024x504.png\" alt=\"A screenshot of how to apply the limit to display filter\" class=\"wp-image-13088 addshadow\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-filter-traffic-display-1024x504.png 1024w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-filter-traffic-display-300x148.png 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-filter-traffic-display-768x378.png 768w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/wireshark-filter-traffic-display.png 1293w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">At this stage, you can export a list of servers from Wireshark (in CSV or YAML format) that might need updates. By switching your filters and endpoints, you can identify other areas that may need attention. The best case is to get everything up to TLS version 1.3. However, there is some urgency to eliminate the use of TLS versions below 1.2 (and the vulnerabilities that accompany them).<\/p>\n\n\n<span style=\"display:none\" class=\"tl-placeholder-f-type-shortcode_12753\"><\/span>\n\n\n<h2 class=\"wp-block-heading\" id=\"h-final-thoughts\">Final Thoughts<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Applying Wireshark with a sound methodology and filtering gives an effective and efficient way to analyze TLS use in your network. When combined with untamperable packet capture, you can build a detailed, complete and certain picture of what is going on in your network that enables change without guess work. As a result, you can start addressing TLS issues where they originate, before blocking activity at the network level.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By identifying the weakest links in your network, you get on with eliminating them, without any unpleasant surprises \u2014 and without managing irate users\u2019 complaints.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>This article was co-written with Betty DuBois, Chief Detective for Packet Detectives, an application and network performance consulting and training firm based in Atlanta, GA. DuBois has been solving mysteries since 1997. Experienced with a range of hardware and software packet capture solutions, she captures the right data, in the right place, and at the right time to find the real culprit. Check out bettydubois.com to learn more or to contact her<\/strong><\/em>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Weak encryption is a real risk to data privacy and security. This article, based on Packet Detectives\u2019 episode \u201cThe case of the unknown TLS versions,\u201d shows how you can use&#8230;<\/p>\n","protected":false},"author":36,"featured_media":13095,"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":[16,10200],"tags":[12856,12857],"class_list":["post-13080","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hashing-out-cyber-security","category-monthly-digest","tag-packet-capture","tag-packets","post-with-tags"],"views":11911,"jetpack_featured_media_url":"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2020\/09\/web-traffic-packet-capture-feature.jpg","_links":{"self":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/13080","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\/36"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/comments?post=13080"}],"version-history":[{"count":0,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/13080\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media\/13095"}],"wp:attachment":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media?parent=13080"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/categories?post=13080"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/tags?post=13080"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}