{"id":14839,"date":"2019-03-14T10:45:03","date_gmt":"2019-03-14T18:45:03","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2019\/03\/14\/news-8588\/"},"modified":"2019-03-14T10:45:03","modified_gmt":"2019-03-14T18:45:03","slug":"news-8588","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2019\/03\/14\/news-8588\/","title":{"rendered":"When Facebook Goes Down, Don&#8217;t Blame Hackers"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/media.wired.com\/photos\/5c897f7346e19a01ab72c081\/master\/pass\/facebookhack-security-1052438512-final.jpg\"\/><\/p>\n<p><strong>Credit to Author: Brian Barrett| Date: Wed, 13 Mar 2019 23:18:13 +0000<\/strong><\/p>\n<p>It happened again. <a href=\"https:\/\/www.wired.com\/tag\/facebook\">Facebook<\/a> went down in <a href=\"https:\/\/downdetector.com\/status\/facebook\/map\/\" target=\"_blank\">pockets<\/a> around the world for several hours Wednesday, as did Facebook-owned Instagram and WhatsApp. The outage inspired the usual existential jokes\u2014and <a href=\"https:\/\/www.wired.com\/story\/what-we-do-when-facebook-youtube-crash\">rush to news sites<\/a> to fill the void\u2014but it also gave rise to conspiracy <a href=\"https:\/\/twitter.com\/kurteichenwald\/status\/1105893972117999616\" target=\"_blank\">theories<\/a> that hackers were the cause. As is almost always the case, those theories are wrong.<\/p>\n<p>Facebook confirmed as much in a <a href=\"https:\/\/twitter.com\/facebook\/status\/1105907126424109056\" target=\"_blank\">tweet<\/a>, saying that while it was still investigating the root cause of its woes, it had ruled out a distributed denial of service attack. On the surface, DDoS makes for a reasonable enough suspect; as a class of attack, its whole purpose is to bring sites down. But assumptions that hackers would hobble not just Facebook but also Instagram and WhatsApp with a DDoS attack rely on a shaky grasp of what that would entail and how prepared companies are to stop them.<\/p>\n<p class=\"paywall\">For its part, Facebook has provided vague guidance as to what actually did happen. \u201cWe are currently experiencing issues that may cause some API requests to take longer or fail unexpectedly,\u201d the company <a href=\"https:\/\/developers.facebook.com\/status\/issues\/559896447845433\/\" target=\"_blank\">wrote<\/a> on a developer status page. &quot;We are investigating the issue and working on a resolution.\u201d That could indicate a wide range of culprits, from routine maintenance gone awry to a <a href=\"https:\/\/www.wired.com\/story\/iran-dns-hijacking\/\">Domain Name System<\/a> issue. [<em><strong>Update:<\/strong> Facebook confirmed Thursday that the problem stemmed from a &quot;server configuration change that triggered a cascading series of issues.&quot; It has since resolved the issue.<\/em>]<\/p>\n<p class=\"paywall\">Even before that disclosure, it was apparent that the down time was unrelated to any sort of cyberattack. &quot;I can confirm that it has nothing to do with outside hacking efforts,&quot; wrote Facebook spokesperson Tom Parnell in an email to WIRED Wednesday. But you don\u2019t even have to take Facebook\u2019s word for it.<\/p>\n<p class=\"paywall\">\u201cThere\u2019s no collaborating evidence of any kind to indicate a malicious attack,\u201d says Troy Mursch, a security researcher who runs <a href=\"https:\/\/badpackets.net\/\" target=\"_blank\">Bad Packets Report<\/a>, which keeps close tabs on the activity of botnets and network attacks that cause actual harm. \u201cIn regards to an actual attack or any widespread attack, we can confirm that is not the case there.\u201d<\/p>\n<p class=\"paywall\">Which is not to say that hackers don\u2019t try to compromise Facebook every day. They do! They\u2019ve even succeeded at least once, compromising account data of a <a href=\"https:\/\/www.wired.com\/story\/how-facebook-hackers-compromised-30-million-accounts\/\">whopping 30 million users<\/a>. But <a href=\"https:\/\/www.wired.com\/story\/facebook-hack-data-spammers\/\">Facebook\u2019s value for criminals<\/a> rests in its data. Taking it offline doesn\u2019t serve any obvious ends. And even if it did, it\u2019s unclear who might be able to pull it off.<\/p>\n<p class=\"paywall\">At its most basic level, a DDoS works by throwing more traffic at a site or service than it can handle. By overwhelming servers, a successful DDoS will make it impossible for anyone to pull up a page or refresh their app. They\u2019ve also gotten huge; in 2018, network security firm NetScout <a href=\"https:\/\/www.netscout.com\/blog\/asert\/netscout-arbor-confirms-17-tbps-ddos-attack-terabit-attack-era\" target=\"_blank\">spotted<\/a> a DDoS that funneled 1.7 terabits per second of data at a single target. Around that same time, <a href=\"https:\/\/www.wired.com\/story\/github-ddos-memcached\/\">GitHub got slammed with a 1.35 Tbps attack<\/a>. What those assaults have in common, aside from their girth? Neither of them succeeded.<\/p>\n<p class=\"paywall\">DDoS itself <a href=\"https:\/\/www.wired.com\/story\/creative-ddos-attacks-still-slip-past-defenses\/\">isn\u2019t a solved problem<\/a>, especially as perpetrators have found clever ways to incorporate so-called memcached servers and ransomware into the mix\u2014<a href=\"https:\/\/www.wired.com\/story\/netflix-ddos-attack\/\">Netflix even DDoS\u2019d itself once<\/a>, to demonstrate a novel technique. \u201cIt\u2019s always an arms race between the attackers and the defenders,\u201d says Roland Dobbins, a principal engineer at NetScout. \u201cThat\u2019s the nature of the beast. It\u2019s what we\u2019ve seen over the last 25 years or so of DDoS attacks on the public internet.\u201d<\/p>\n<p class=\"paywall\">But while roughly 20,000 DDoS attacks take place every single day on the public internet, Facebook makes for an exceedingly unlikely target. \u201cIf you\u2019re a DDoS attacker and you\u2019re trying for a big target, and you want to have a big impact, you would probably look for an organization or a brand that doesn\u2019t have as much connectivity to begin with,\u201d says Alex Henthorn-Iwane, vice president at network security firm ThousandEyes. \u201cA Facebook, a Google\u2014those kinds of companies\u2014are so massive, and their bandwidth and interconnectivity is so huge, that they can effectively absorb large-scale attacks on their own. And they undoubtedly have architected their internet connectivity to do just that.\u201d<\/p>\n<p class=\"paywall\">Think of DDoS targets as wells and data as water. The smaller the well, the less water you need to overflow it. To flood Facebook, you\u2019d need to drain Lake Erie.<\/p>\n<p class=\"paywall\">That\u2019s why truly disruptive DDoS attacks have focused on boring infrastructural corners of the internet. A 2016 blast that <a href=\"https:\/\/www.wired.com\/2016\/10\/internet-outage-ddos-dns-dyn\/\">shut down the internet<\/a> for much of the East Coast didn\u2019t hit individual sites but, rather, a company called Dyn, which handles the relatively data-light chore of DNS services. (It was also <a href=\"https:\/\/www.wired.com\/story\/mirai-botnet-minecraft-scam-brought-down-the-internet\/\">part of a Minecraft-related scheme. No, really<\/a>.)<\/p>\n<p class=\"paywall\">None of the network security experts WIRED spoke with had seen any evidence of DDoS activity related to Wednesday\u2019s outage, or to similar issues Google services faced yesterday. Dobbins suggests that the real problem could be any number of things, including a &quot;nontrivial&quot; disruption of internet routing that occurred Wednesday afternoon, of which Facebook may have been collateral damage. ThousandEyes suggests it was likely an internal issue. Either way, as with every other time Facebook has gone down, it wasn\u2019t hackers.<\/p>\n<p class=\"paywall\">The knee-jerk assumption that it is, though, has potentially corrosive effects. \u201cWhen stuff like this happens, affecting large infrastructure organizations like Facebook, it\u2019s going to be prone to conspiracy theories,\u201d Mursch says. \u201cThat kind of stuff is frustrating when we\u2019re trying to establish or present something that\u2019s factual, when you see social media spread that disinformation.\u201d<\/p>\n<p class=\"paywall\">The idea of nation-state hackers taking down the world\u2019s biggest social network has plenty of appeal, both for its easy explanation of a prolonged inconvenience and for the touch of schadenfreude. But jumping to that conclusion only muddles an already confusing issue. Hackers will continue to target Facebook. DDoS attacks will continue to take down sites. But those two truths are much further from intersecting than the more paranoid corners of the internet would have you believe.<\/p>\n<p class=\"related-cne-video-component__dek\">DDoS! It stands for distributed denial of service, a kind of attack that turns insecure, internet-connected devices into a sort of zombie army. So here&#39;s how you can avoid being part of that zombie army.<\/p>\n<p><a href=\"https:\/\/www.wired.com\/story\/facebook-down-dont-blame-hackers\" target=\"bwo\" >https:\/\/www.wired.com\/category\/security\/feed\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/media.wired.com\/photos\/5c897f7346e19a01ab72c081\/master\/pass\/facebookhack-security-1052438512-final.jpg\"\/><\/p>\n<p><strong>Credit to Author: Brian Barrett| Date: Wed, 13 Mar 2019 23:18:13 +0000<\/strong><\/p>\n<p>Facebook, Instagram, and WhatsApp spent several hours offline in many parts of the world today. Just don&#8217;t call it a DDoS attack.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[10378,10607],"tags":[714],"class_list":["post-14839","post","type-post","status-publish","format-standard","hentry","category-security","category-wired","tag-security"],"_links":{"self":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/14839","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=14839"}],"version-history":[{"count":0,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/14839\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=14839"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=14839"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=14839"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}