{"id":29813,"date":"2020-04-14T06:00:35","date_gmt":"2020-04-14T12:00:35","guid":{"rendered":"https://www.webroot.com/blog/?p=29813"},"modified":"2020-04-13T12:39:46","modified_gmt":"2020-04-13T18:39:46","slug":"the-problem-with-https","status":"publish","type":"post","link":"https://www.webroot.com/blog/2020\/04\/14\/the-problem-with-https\/","title":{"rendered":"The Problem with HTTPS"},"content":{"rendered":"\n<p>Despite the intent of ensuring safe transit of information\nto and from a trusted website, encrypted protocols (usually HTTPS) do little to\nvalidate that the content of certified websites is safe.<\/p>\n\n\n\n<p>With the widespread usage of HTTPS protocols on major\nwebsites, network and security devices relying on interception of user traffic\nto apply filtering policies have lost visibility into page-level traffic.\nCybercriminals can take advantage of this encryption to hide malicious content on\nsecure connections, leaving users vulnerable to visiting malicious URLs within supposedly\nbenign domains.<\/p>\n\n\n\n<p>This limited visibility affects network devices that are\nunable to implement SSL\/TLS decrypt functionality due to limited resources,\ncost, and capabilities. These devices are typically meant for home or small\nbusiness use, but are also found in the enterprise arena, meaning the impact of\nthis limited visibility can be widespread.<\/p>\n\n\n\n<p>With 25% of malicious URLs identified by Webroot hosted within\nbenign domains in 2019, a deeper view into underlying URLs is necessary to\nprovide additional context to make better, more informed decisions when the\nexact URL path isn\u2019t available.<\/p>\n\n\n\n<h2>Digging Deeper with Advanced Threat Intel<\/h2>\n\n\n\n<p>The BrightCloud\u00ae Web Classification and Web Reputation\nServices offers technology providers the most effective way to supplement\ndomain-level visibility. Using cloud-based analytics and machine learning with\nmore than 10 years of real-world refinement, BrightCloud\u00ae Threat Intelligence services\nhave classified more than 842 million domains and 37 billion URLs to-date and can\ngenerate a predictive risk score for every domain on the internet. <\/p>\n\n\n\n<p>The Domain Safety Score, available as a premium feature with\nBrightCloud\u00ae Web Classification and Reputation services, can be a valuable\nmetric for filtering decisions when there is lack of path-level visibility on\nwebsites using HTTPs protocols. Even technology partners who <em>do<\/em> have\npath-level visibility can benefit from using the Domain Safety Score to avoid\nthe complexity and compliance hurdles of deciding when to decrypt user traffic.<\/p>\n\n\n\n<p>The Domain Safety Score is available for every domain and\nrepresents the estimated safety of the content found within that domain,\nranging from 1 to 100, with 1 being the least safe. A domain with a low score\nhas a higher predictive risk of having content within its pages that could\ncompromise the security of users and systems, such as phishing forms or\nmalicious downloads.<\/p>\n\n\n\n<p>Using these services, organizations can implement and\nenforce effective web policies that protect users against web threats, whether\nencrypted through HTTPs or not.<\/p>\n\n\n\n<h2>Devising Domain Safety Scores<\/h2>\n\n\n\n<p>As mentioned, a Domain Safety Score represents the estimated\nsafety of the content found within that domain. This enables better security\nfiltering decisions for devices with minimal page-level visibility due to\nincreasing adoption of HTTPS encryption.<\/p>\n\n\n\n<p>How do we do it?<\/p>\n\n\n\n<p>BrightCloud uses high-level input features to help determine\nDomain Safety Scores, including: <\/p>\n\n\n\n<ul><li><strong>Domain attribute data<\/strong>, including publicly\navailable information associated with the domain, such as registry information,\ncertificate information, IP address information, and the domain name itself.<\/li><li><strong>Behavioral features<\/strong> obtained from\nhistorical records of known communication events with the domain, gathered from\nreal-world endpoints. <\/li><li><strong>A novel deep-learning architecture<\/strong> employing\nmultiple deep, recurrent neural networks to extract sequence information,\nfeeding them into a classification network that is fully differentiable. This\nallows us to use the most cutting-edge technology to leverage as much\ninformation possible from a domain to determine a safety score. <\/li><li><strong>Model training<\/strong> using a standard\nbackpropagation through time algorithm, fully unrolling all sequences to\ncalculate gradients. In order to train such a network on a huge dataset, we\nhave developed a custom framework that optimizes the memory footprint to run\nefficiently on GPU resources in a supercomputing cluster. This approach allows\nus to train models faster and iterate quickly so we can remain responsive and\nadapt to large changes in the threat landscape over time.<\/li><\/ul>\n\n\n\n<p>A secure connection doesn\u2019t have to compromise your privacy.\nThat\u2019s why Webroot\u2019s Domain Safety Scores peek below the domain level to the\nplaces where up to a quarter of online threats lurk. <\/p>\n\n\n\n<p>Learn more about Domain Safety Scores, <a href=\"https:\/\/www-cdn.webroot.com\/2715\/8396\/4433\/HTTPS_Domain_Safety_Score.pdf\">here<\/a>.\n<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Despite the intent of ensuring safe transit of information to and from a trusted website, encrypted protocols (usually HTTPS) do little to validate that the content of certified websites is safe. With the widespread usage of HTTPS protocols on major websites, network and security devices relying on interception of user traffic to apply filtering policies [&hellip;]<\/p>\n","protected":false},"author":163,"featured_media":29817,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3005],"tags":[25407,24453],"yst_prominent_words":[],"acf":[],"_links":{"self":[{"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/posts\/29813"}],"collection":[{"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/users\/163"}],"replies":[{"embeddable":true,"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/comments?post=29813"}],"version-history":[{"count":1,"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/posts\/29813\/revisions"}],"predecessor-version":[{"id":29815,"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/posts\/29813\/revisions\/29815"}],"wp:featuredmedia":[{"embeddable":true,"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/media\/29817"}],"wp:attachment":[{"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/media?parent=29813"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/categories?post=29813"},{"taxonomy":"post_tag","embeddable":true,"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/tags?post=29813"},{"taxonomy":"yst_prominent_words","embeddable":true,"href":"https://www.webroot.com/blog/wp-json\/wp\/v2\/yst_prominent_words?post=29813"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}