<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Two-Factor Everything - Medium]]></title>
        <description><![CDATA[Keeping the web safe is every developer’s job. - Medium]]></description>
        <link>https://medium.com/two-factor-everything?source=rss----3446c73693c0---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Two-Factor Everything - Medium</title>
            <link>https://medium.com/two-factor-everything?source=rss----3446c73693c0---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:31:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/two-factor-everything" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Never spend more than 37% — the golden rule of security spending]]></title>
            <link>https://medium.com/two-factor-everything/an-economic-model-for-security-spending-3d982d05d0c1?source=rss----3446c73693c0---4</link>
            <guid isPermaLink="false">https://medium.com/p/3d982d05d0c1</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Darrell Jones III]]></dc:creator>
            <pubDate>Thu, 17 Nov 2016 18:12:49 GMT</pubDate>
            <atom:updated>2016-11-18T00:58:53.240Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*gFqAgSyXh7B823PotCH6kw.png" /></figure><p>Knowing how much to spend on security products is hard. Sales reps trump up the fear of a breach, solutions return supposed savings instead of revenue, and the probabilities of an actual loss seem miniscule. Faced with opaque costs and benefits, most people end up avoiding this decision entirely.</p><p>Thankfully, some economists came up with an economic framework to help us estimate how much we should shell out. It’s called the Gordon-Loeb model, and it’s awesome.</p><p>The fundamental principle starts out simple enough: <strong>the benefits of any investment should be greater than the costs</strong>. The framework takes three variables into consideration:</p><ol><li>Potential loss of value from a cybersecurity breach</li><li>Probability of a breach</li><li>How cybersecurity investments reduce probability of breach</li></ol><p>With those variables in place, the framework offers 4 steps to help us arrive at an optimal level of security spending.</p><ul><li>Segment information sets and estimate the value or potential Loss (L) for each information set.</li><li>Estimate the probability that an information set will be breached and assign each set a vulnerability score.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*WpJeY584VCVbV7Gug1M2Mw.png" /></figure><ul><li>Taking the steps above, develop a grid ranging from low value/low vulnerability to high value/high vulnerability information sets. Each grid cell tracks to the expected loss (L) absent any additional investment in cybersecurity. The expected loss represents the potential benefits of cost savings from security spending.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*tFFzEUshw5tmD2rEgjBuCw.png" /></figure><ul><li>Put your cybersecurity dollars where they’ll be most productive in terms of reducing expected losses. Keep in mind that benefits from investments increase at a decreasing rate.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*6lQ-Q52D3I_sBtlC0H7-vg.png" /></figure><p>Working through this framework helps impose some semblance of order in an otherwise obscure situation. There are 2 big findings to bear in mind regardless of what amount you arrive at.</p><ol><li>Spending should <strong>not exceed 1/3 or roughly 37% </strong>of the total expected losses</li><li>The optimal amount to spend to protect information does not always increases with an information set’s vulnerability</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Wm9ALal-EZnMzRIR-SH5aw.gif" /><figcaption>Be frugal! More spending doesn’t equate to more value!</figcaption></figure><p>Hope this is helpful! You can explore the full paper <a href="http://ns2.virusflags.dc.hu/~mfelegyhazi/courses/EconSec/readings/04_GordonL02economics_security_investment.pdf">here</a> and example applications <a href="http://file.scirp.org/pdf/JIS_2016032315382494.pdf">here</a>. If you have any other methodologies you use for determining how much you spend on security, I’d love to see it!</p><p><em>Darrell leads business development at Clef. If two-factor authentication has been in your backlog for months, but still hasn’t gotten prioritized, check out Clef’s new product </em><a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=economicmodel"><em>Instant2FA.com</em></a><em> — it’s two-factor authentication that takes minutes to integrate instead of weeks.</em></p><figure><a href="https://blog.instant2fa.com/"><img alt="" src="https://cdn-images-1.medium.com/max/400/1*QyM0HCXUXwxUAb-QI4KGSg.png" /></a></figure><figure><a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=economicmodel"><img alt="" src="https://cdn-images-1.medium.com/max/400/1*qBpRmihydixWt1eRXo7tfQ.png" /></a></figure><figure><a href="https://twitter.com/instant2fa"><img alt="" src="https://cdn-images-1.medium.com/max/400/1*X-2_rMbS-lWWsoxA-l2hxw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d982d05d0c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/two-factor-everything/an-economic-model-for-security-spending-3d982d05d0c1">Never spend more than 37% — the golden rule of security spending</a> was originally published in <a href="https://medium.com/two-factor-everything">Two-Factor Everything</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customizing the look of Instant 2FA]]></title>
            <link>https://medium.com/two-factor-everything/customizing-the-look-of-instant-2fa-55b6dee90c8e?source=rss----3446c73693c0---4</link>
            <guid isPermaLink="false">https://medium.com/p/55b6dee90c8e</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[new-features]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[instant-2fa]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Jesse Pollak]]></dc:creator>
            <pubDate>Wed, 16 Nov 2016 23:15:48 GMT</pubDate>
            <atom:updated>2016-11-16T23:33:14.359Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CDVIW165W0D4OPKO2ICkHA.gif" /></figure><h4>Now you can customize the primary color used in buttons and links.</h4><p>Today, we’re rolling out our first customization feature: the ability to choose a primary color that will be used in buttons, links, and icons across the Instant 2FA experience.</p><p>When we set out to build <a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=primary-color-feature">Instant 2FA</a>, we knew there were a few things businesses would need from a hosted two-factor authentication solution:</p><ol><li><strong>Security.</strong> Two-factor is a critical part of a company’s security architecture and they need to trust their provider to keep them safe.</li><li><strong>Ease of integration. </strong>Many businesses never roll out 2FA because it takes too long to integrate, so we knew Instant 2FA needed to be…<em>instant</em>.</li><li><strong>Customization.</strong> A business’s brand is one of their most valuable assets and account security is an important place to strengthen and extend that brand — we knew Instant 2FA needed to be customizable so it felt native.</li></ol><p>This is just the first of many customization options, but we’re excited to get started!</p><p><em>If 2FA has been in your backlog for months, check out </em><a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=primary-color-feature"><em>Instant 2FA</em></a><em>, the easiest way to add two-factor authentication to any site in minutes.</em></p><figure><a href="https://twitter.com/instant2fa"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kzUKc_qwKSNPu_2BRILXSA.png" /></a></figure><figure><a href="https://medium.com/two-factor-everything"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cP0LmY26f6sEW0tJBrzfEQ.png" /></a></figure><figure><a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=primary-color-feature"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JVor0bDapeq0QFgziLosNw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55b6dee90c8e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/two-factor-everything/customizing-the-look-of-instant-2fa-55b6dee90c8e">Customizing the look of Instant 2FA</a> was originally published in <a href="https://medium.com/two-factor-everything">Two-Factor Everything</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Death Star the Rebels Won’t Destroy]]></title>
            <link>https://medium.com/two-factor-everything/a-death-star-the-rebels-wont-destroy-3d02d78d7f3e?source=rss----3446c73693c0---4</link>
            <guid isPermaLink="false">https://medium.com/p/3d02d78d7f3e</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[star-wars]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[fantastic-threat-models]]></category>
            <dc:creator><![CDATA[B]]></dc:creator>
            <pubDate>Wed, 16 Nov 2016 19:59:41 GMT</pubDate>
            <atom:updated>2016-11-16T23:33:04.015Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zidTVuYz9OYZGaZ5m7JLKg.jpeg" /></figure><h4>Fourth time’s the charm</h4><p>If you’ve seen more than one Star Wars movie, you’ve probably noticed a pattern. The villains spend a lot of time and money building a massive super-weapon (Death Star I, Death Star II, and then most recently Starkiller Base) only to have it destroyed in a few minutes by those meddling Jedis. <br> <br>If you’re rooting for the Jedi and the forces of good in the universe, then this is awesome — if you’re a Sith, it probably sucks. Some amazing nerds did the math on how much the steel would cost for Death Star I (by far the smallest of the three), and it comes to about <a href="http://www.centives.net/S/2012/how-much-would-it-cost-to-build-the-death-star/">$852,000,000,000,000,000</a>. Yeah, 852,000 trillion dollars. So it’s probably worth putting some resources towards keeping that thing from getting blown up, yeah? <br> <br>Well let’s imagine we’re the Sith Death Star designers (the Geonosians led by Archduke Poggle the Lesser to be specific) and we want to build a fourth super-weapon. This time, let’s start with a threat model. Creating the threat model takes three steps:</p><ol><li>Break the super-weapon down into each of its parts</li><li>Figure out how the Rebels could attack each part</li><li>Make a strategy to defend against each attack</li></ol><h3>1. What makes a Death Star?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*LRQNKGjPZjL83C51EZlgzA.png" /></figure><p>First, we need to think about all of the different pieces that it’ll take to build a Death Star in the first place, and it’s <em>always</em> worth drawing a diagram. We need to think about how people come and go, where our weak points are, and what we depend on to keep the weapon functional. <br> <br> Our Death Star is composed of these five sections:</p><ul><li>Physical shell and body</li><li>Reactor Core</li><li>Protective Shields</li><li>Station Schematics</li><li>Storm Troopers</li></ul><p>All of these are related, so is any of them is compromised, our Death Star is probably going down.</p><blockquote>“An analysis of the plans provided by Princess Leia has demonstrated a weakness in the battle station.” ~General Dodonna</blockquote><h3>2. Check everything for weaknesses</h3><p>We’ve already messed this up three times and had tons of money and hard work obliterated, so this time let’s use a framework to make sure we’re not forgetting anything. Thankfully, some company called Microsoft from a galaxy far far away created a framework for threat modeling called STRIDE. STRIDE stands for:</p><ul><li>S — Spoofing (pretending not to be someone you’re not)</li><li>T — Tampering (modifying something you shouldn’t be able to)</li><li>R — Repudiation (denying responsibility for some action, whether you did it or not)</li><li>I — Information Disclosure (accessing information you shouldn’t have)</li><li>D — Denial of Service (preventing something from operating correctly)</li><li>E — Elevation of Privilege (gaining abilities you shouldn’t have)</li></ul><p>If we think through all of those different kinds of attacks for every component, we’re way less likely to miss something.</p><h4>Physical Shell and body</h4><p>The outside of the Death Star is pretty tough, but its large size and crew give it some vulnerabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*-rFG9GogrEEnmzaVS82gCw.png" /></figure><p><strong>Spoofing</strong>: The Death Star only allows certain ships to approach, so if you’re able to take over one of their ships, you might be able to get access to the Death Star. <br><em>Tampering</em>:<strong> </strong><br><em>Repudiation</em>:<br><strong>Information Disclosure</strong>: Where is the Death Star? How big is it? These are important questions for anyone who wants to destroy it. <br><strong>Denial of Service</strong>: It would take a massive attack to destroy it, but what if the Rebels build their own Death Star ��<br><em>Elevation of Privilege</em>:</p><h3>Reactor core</h3><p>This has been the achilles heel of the Death Stars. We have <em>got</em> to do a better job protecting this darn thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*9in9wFJ36wunuHx8YUMMiw.png" /></figure><p><em>Spoofing:</em><strong><em> </em></strong><br><em>Tampering</em>:<strong> </strong><br><em>Repudiation</em>:<br><strong>Information Disclosure</strong>: It’s really important that the rebels not know where the reactor’s thermal exhaust shafts are, or how to get to them. We already know they will use that information if they can. <br><strong>Denial of Service</strong>: This is a highly volatile reactor, destroying it will blow up the whole Death Star<strong> </strong><br><em>Elevation of Privilege</em>:</p><h3>Protective Shields</h3><p>We use shields every time, but they keep getting through! It turns out there are a lot of ways to attack the shields.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*XSponAQoPYCMf7imHsw6RA.png" /></figure><p><strong>Spoofing</strong>: These shields let some people through, so the rebels could pretend to be those people<strong>.</strong><br><em>Tampering</em>:<strong> </strong><br><strong>Repudiation</strong>: The shields are invisible, so it could seem like they’re online when they’re actually down. <br><strong>Information Disclosure</strong>: Learning where the base that generates the shield is located is the first step to disabling the shield.<br><strong>Denial of Service</strong>: Destroy the base, take down the shield. <br><strong>Elevation of Privilege</strong>: If you take control of the base, you can turn the shield on or off</p><h3>Station Schematics</h3><p>The rebels always seem to know our weak spots. Maybe it’s because they keep getting our blueprints?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*wisyG3gSdizniAPIRQfSfw.png" /></figure><p><em>Spoofing</em>:<strong> </strong><br><em>Tampering</em>:<strong> </strong><br><em>Repudiation</em>:<br><strong>Information Disclosure</strong>: It takes millions of people to run this ship, so the crew to build it must have been huge too. That means a lot of copies of construction schematics, which keep getting into the wrong hands. <br><em>Denial of Service</em>:<strong> </strong><br><em>Elevation of Privilege</em>:</p><h3>Storm troopers</h3><p>The crew of our ship, and the ones who are supposed to protect it. Equipped with lasers, which unfortunately always miss.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*ZLny2iRFY7OMZEHlPJ-VLw.png" /></figure><p><strong>Spoofing</strong>: These uniforms make it impossible to know who’s inside them, so it’s really easy to steal a suit and spoof your way into almost any protected area. Seriously, who designed these things?<br><em>Tampering</em>:<strong> </strong><br><em>Repudiation</em>:<br><strong>Information Disclosure</strong>: The storm troopers don’t usually know that much, but what they do know, they give up easily. <br><strong>Denial of Service</strong>: There are a lot of storm troopers, so this would take a massive army to pull off, but they are killable. <br><strong>Elevation of Privilege</strong>: Put on the suit, get the privileges.</p><h3>3. Learn from our mistakes</h3><p>The biggest security problem is fundamental for a project like this. We are building a <em>massive</em> object which will be very hard to change quickly, and millions of people are going to know about it. That means that information about the ship is bound to get out, and it’ll probably still be relevant by the time the Rebels get it. That means we need to build our newest Death Star with the mindset that all information is public, <strong>we cannot rely on security through obscurity</strong>. <br> <br>With that in mind, our primary vulnerabilities are still our reactor core and the base where we generate the protective shield. We already have tons of soldiers, but they do a terrible job of protecting our important targets. So first, we should invest in target practice for literally everyone. Seriously, we pay for millions of blasters and they’ve basically never hit one of the important targets. Second, we need uniforms that aren’t so easy to steal. How about an alarm that goes off when the suit is taken off without a commander present? Then the alarm can be turned off by any commander who has verified the identity of the person inside the suit. <br> <br>Finally, is there a way for us to use smaller thermal exhaust ports for our reactor? We can have more of them, as long as the rebels can’t fly an X-Wing into them.</p><h3>That’s a threat model</h3><p>Now we’re much better equipped to build a Death Star that’s actually worth the quadrillions of dollars that we’re going to pour into it. It only takes a minute to break anything down into its pieces, run through STRIDE for each piece, and see where the vulnerabilities are, but it makes such a huge difference. That’s why, just like version control, threat models are a tool that should be in every engineer’s toolbox. <br> <br>It doesn’t matter if you’re building a Death Star, the <a href="https://blog.instant2fa.com/how-to-build-a-wall-that-stops-white-walkers-fantastic-threat-models-ef2dfa7864a4#.p6xvva0b5">Westeros Wall</a>, or an app to share photos with friends, someone’s going to try to break what you build. It’s up to you to defend it.</p><p><em>B is the CEO and co-founder at Clef. If two-factor authentication has been in your backlog for months, but still hasn’t gotten prioritized, check out Clef’s new product </em><a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=death-star-ftm"><em>Instant2FA.com</em></a><em> — it’s two-factor authentication that takes minutes to integrate instead of weeks.</em></p><figure><a href="https://blog.instant2fa.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cP0LmY26f6sEW0tJBrzfEQ.png" /></a></figure><figure><a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=death-star-ftm"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JVor0bDapeq0QFgziLosNw.png" /></a></figure><figure><a href="http://twitter.com/instant2fa"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kzUKc_qwKSNPu_2BRILXSA.png" /></a></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*prif7-04oPf8Dqo1gvSDsQ.gif" /><figcaption>If you liked this post, you should ❤ it so other people can like it too.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d02d78d7f3e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/two-factor-everything/a-death-star-the-rebels-wont-destroy-3d02d78d7f3e">A Death Star the Rebels Won’t Destroy</a> was originally published in <a href="https://medium.com/two-factor-everything">Two-Factor Everything</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Choosing Ember over React in 2016]]></title>
            <link>https://medium.com/two-factor-everything/choosing-ember-over-react-in-2016-41a2e7fd341?source=rss----3446c73693c0---4</link>
            <guid isPermaLink="false">https://medium.com/p/41a2e7fd341</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[ember]]></category>
            <dc:creator><![CDATA[Jesse Pollak]]></dc:creator>
            <pubDate>Mon, 14 Nov 2016 19:22:52 GMT</pubDate>
            <atom:updated>2016-11-16T23:32:37.388Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*--wRIhx_atl50C4NlkMY5Q.jpeg" /></figure><p>One month ago, we started working on a new product: <a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=ember-over-react">Instant 2FA</a>, the easiest way to add two-factor authentication to any site in less than an hour.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*ENIiHo1IKB8mwOxp9BAyOQ.gif" /></figure><p>Currently, whether you roll your own two-factor with Google Authenticator or use an API service like Authy, a standard integration often takes weeks.</p><p>With <a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=ember-over-react">Instant 2FA</a>, we’re building a solution that reduces the entire integration to 3 API calls and provides everything out of the box: Google Authenticator, SMS, and Yubikey support; remember this computer; rate-limiting and alerting; and with our first few customers, we’ve done the integration in a development environment in less than an hour.</p><p>This blog post outlines our thinking behind choosing Ember (a technology none of us had ever used before) over React (which we’ve been running for 2.5 years in production at Clef) and our reflections on the decision after one month of work.</p><h3>Our experience</h3><p>Every new project requires a million technology decisions. Luckily, 4 years of company experience building Clef, a two-factor product used by nearly a million websites, made most of our decisions obvious. We knew our backend services would be built with Python, SQL, and Flask, leveraging all the tooling and libraries we’d spent years working on. <br> <br>The frontend, however, was a different story: we’ve been using React and flux (powered by reflux) in production for two and a half years, but as we began considering how to build Instant 2FA, we wondered whether using a more fully featured framework like Ember or Angular would be a better decision.</p><h3>Evaluating ember</h3><p>When we started considering Ember over React, there were two main hypotheses that drove our curiosity:</p><ol><li><strong>Convention over configuration. </strong>Since Ember handles many things out of the box that React requires composition of other libraries to do, we would be able to accomplish more, faster, and without suffering from decision fatigue.</li><li><strong>Progressive enhancement &amp; surviving the framework hype cycle. </strong>Since Ember has a very strong community that’s very committed to making Ember the best way to build modern web applications, we would be able to use the latest and greatest technologies, even if our use came a little later on the adoption curve (perhaps <a href="https://speakerdeck.com/tehviking/surviving-the-framework-hype-cycle">on the plateau of productivity</a>).</li></ol><p>As we dug into each of these hypotheses, we found compelling evidence that ultimately led us to choosing Ember for both our applications.</p><h3>Convention over configuration</h3><p>One of the best things about React is that, since it’s only a view layer, it can easily be added to a pre-existing JavaScript application. Three years ago, when the frontend for Clef was built on our own object oriented JavaScript framework and we started exploring whether React could help us, this was one of the best parts. Rather than swap in a new “framework,” we gradually replaced different components with React components — adding additional logic layers on top of React (like redux to handle data flow) only as necessary. <br> <br> Over time, this gradual composition of libraries cemented into our own little incarnation of the React ecosystem. Different libraries duplicated each other, but things worked. We used:</p><ul><li><em>coffeescript</em></li><li><em>React</em> for the view</li><li><em>reflux</em> for data flow</li><li><em>react-router 2</em> for routing</li><li><em>jQuery.ajax</em> for network requests</li><li><em>underscore</em> for utilities</li><li><em>browserify</em> for module building</li><li><em>gulp</em> for tasks</li><li><em>SASS</em> for styles</li><li>no tests 😬</li></ul><p>A few months ago, we did a little side project where we had to create a client application from scratch. We went with React for the view layer, but given the dramatic evolution of the surrounding ecosystem over the last few years, we ended up with a very different composition:</p><ul><li><em>ES6</em></li><li><em>React</em> for the view</li><li><em>redux</em> and <em>redux-saga</em> for data flow</li><li><em>react-router 3</em> for routing</li><li><em>fetch</em> for network requests</li><li><em>lodash</em> for utilities</li><li><em>webpack</em> for module building</li><li><em>post-css</em> &amp; <em>css-modules</em> for styles</li><li><em>karma</em>, <em>mocha</em>, <em>sinon</em> and <em>chai</em> for tests</li></ul><p>It was fun to get to pick and choose, but every step of the way we doubted our choices: were we making the wrong decision with a given library choice? We were “configuring” our own framework from the tools available in the React ecosystem, but had major concerns about whether our configuration would help or hurt us.</p><p>Entrusting high-level architectural technology decisions to engineers who have limited experience in a domain often leads to bikeshedding and bad decisions — and this showed in the side project we did. We are a team of 4 engineers building Clef, but since we regularly maintain code across 5 platforms (iOS, Android, backend Python, client JavaScript, and our WordPress plugin), only two of our engineers have really worked on our React application. By the end of working on the side project as a team, we’d saddled ourselves with a set of tools which often proved unstable and got in the way of getting our work done.</p><p>With Instant 2FA, every engineer would be working in JavaScript for half their time, so this meant more than half of the people writing code would be relatively inexperienced JavaScript engineers. This makeup — senior overall, but relatively inexperienced with front end engineering — made the issue of convention over configuration feel particularly relevant.<br> <br>As we started working on Instant 2FA, the thought of Ember making all these decisions for us — enforcing a convention over configuration — was very alluring. Some of the decisions we were most excited about <em>not</em> making were:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*XjqQi7qvXP6SYTMh1UnNRQ.gif" /></figure><h4>Tests</h4><p>Ember ships with testing built in and tests are auto-generated when new units (models, routes, services, serializers, etc) are created. For the last React application we built, we’d spent days setting up test harnesses, acceptance tests, and all of the other tools necessary to have a fast, easy-to-use test suite, and we still were constantly frustrated with our setup. Ember built acceptance and unit testing into the framework, which we hoped would make it easier for our code to be tested at every level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*xnvCDtpesLfwC2TB37DMVA.gif" /></figure><h4>Builds &amp; deployment</h4><p>Ember is powered by ember-cli, which handles every step of your build: transpiling JavaScript, building modules, productionizing code, and even deploying (with ember-cli-deploy). This toolchain comes with sane defaults out of the box (ES6 and modules, for instance), but the community built around this standard is the most powerful part.</p><p>In our previous setups, every time we needed to change our build to implement a specific goal, we needed to write custom code. One great example of this is uploading sourcemaps to Sentry when our code is deployed. In our React apps, we did this in a shell script after our webpack build was done.</p><p>With ember-cli, almost any new step we need to add is available as an Ember addon (like <a href="https://github.com/dschmidt/ember-cli-deploy-sentry">ember-cli-deploy-sentry</a>). And, because of the way Ember enforces conventions, these addons almost always work out of the box. As a result our build and deploy logic has transformed from a mess of custom JavaScript and shell script logic to a clean composition of different community maintained modules.</p><h4>Data flow &amp; modeling</h4><p>The default implementation of data flow and persistence in Ember relies on ember-data, which is maintained by the core team (along with ember-cli and Ember core). With our most recent React experience, when we used redux with redux-saga, while we felt at the cutting edge, we always seemed moments away from flushing days down the drain trying to figure out how to do something. When evaluating Ember, We were excited that with ember-data there were established patterns for how to do things — even if some of those patterns felt a little outdated.</p><h4>Server side rendering.</h4><p>Ember F<a href="https://ember-fastboot.com/">astBoot</a> enables server side rendering in any Ember app with one command. Having explored server side rendering in our previous React apps, we knew that for every configuration of libraries around React there was an equally complicated server side rendering setup. Server side rendering wasn’t something we needed out of the box, and we still haven’t enabled it, but knowing that it’s a cli command away, rather than a major project away, is a weight off our shoulders.</p><p>After outlining and exploring all the decisions we would need to make if we went with the React ecosystem, taking those decisions out of our hands, and putting them in the hands of a core team and community that has been building client-side applications for years, became an obvious choice.</p><h3>Progressive enhancement</h3><p>When the topic of progressive enhancement is discussed, it most often refers to the progressive enhancement of webpages from plain HTML &amp; CSS to advanced, interactive JavaScript powered applications. The argument goes like this: for people browsing a web application, their experience should be progressively enhanced given the technologies their browser supports (or has enabled). A user with no JS support in their browser will get a plain HTML &amp; CSS experience — which though it may be slower or clunkier, will still work — while a user with a modern browser will be served the JavaScript necessary to make their experience fully modern. In other words, with progressive enhancement, we meet users where they are — and, perhaps most importantly,<strong> </strong><em>they get the best experience available to them without having to do any work.</em></p><p><strong>The best ideas of progressive enhancement should be evident in JavaScript frameworks and libraries as well — we refer to this a <em>Progressive Developer Experience (Progressive DX) </em>and it’s one of the defining goals of the Ember framework and community.</strong><br> <br>In the React ecosystem, progress most often happens through the creation of new libraries. The flux paradigm, and the concept of uni-directional data flow, is a particularly good example of this. When Facebook first published the flux architecture, a litany of small libraries that implemented the pattern sprang up (one of which was reflux, which we started using). Over time, many of these libraries died off, while communities formed around others (like redux), but the evolution of the concept most often happened through the introduction of new libraries. For instance, for handling asynchronous actions in redux, this has evolved from just handling the logic in redux to a slightly more involved layer like redux-thunk to using promises with redux-promise to the concept of sagas with redux-saga. For each new iteration of progress at the conceptual level, a new library or tool needs to be added to your toolset: or tying this back to the language of progressive enhancement, <em>the developer has to do work or change their tools to get the best experience.</em><br> <br>In contrast, one of the goals of Ember is to <em>give the developer the best experience currently available without having them do any work (or as little as possible)</em>. Take the same example of uni-directional data flow. While Ember 1.0 existed before this pattern became well known, as the concept grew in popularity and conceptual clarity in the React &amp; flux ecosystem the Ember core team started figuring out how they could roll it back into Ember. With Ember 2.0, and the gradual shift from controllers to components, uni-directional data flow has found a home in Ember without Ember developers needing to add new libraries or adopt major conceptual paradigms. It may have taken a little longer to get to this enhancement — but when it came it was well thought out, built into the framework they already used, and there was a straightforward migration path. <strong>This is a perfect example of how Ember employs Progressive DX to give its developers access to the latest patterns and tools!</strong><br> <br>Reading the core team&#39;s work during our evaluation period, this theme of Progressive DX felt consistent: features like Ember Fastboot (server side rendering), glimmer (faster rendering enginer), routable components (uni-directional data flow), and services (isolated cross cutting concerns) are all examples of how the Ember experience has been progressively enhanced, often borrowing directly from patterns other frameworks have introduced, to give Ember users the best of the web.<br> <br>At the beginning of a project that will last for years, it&#39;s comforting to know that we have a team working to integrate the latest and greatest into the tools we already use, so we don&#39;t have to search for it ourselves.</p><h3>Reflections one month in</h3><p>One month in, we’re very happy with our decision to use Ember. It’s still early, but overall, our two hypotheses have held — we’re enjoying following conventions defined by more senior engineers and are already benefiting from different ways Ember has progressively enhanced our experience.</p><blockquote><em>The solid documentation makes getting started with the framework pretty easy and having a bunch of conventions already determined is freeing. <br></em>- Grace Wong, Engineer</blockquote><blockquote><em>Ember is sweet. Really easy to pick up enough to design well, and I really love using css-modules.<br></em>- Aayush Iyer, Designer</blockquote><p>We’ve also found a ton of other, smaller reasons to love Ember.</p><h3>Some more good parts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*mcsY0zzkIcqlrUb6JFTsfA.gif" /></figure><h4>ember generate</h4><p>Having never used a framework that provided command line tools for generating new units of logic, we were skeptical of the value ember-cli would provide with the ember generate command. After working with the framework for a little more than a month, it&#39;s one of our favorite things: having a canonical way to generate any unit of logic (model, route, service, etc), means there&#39;s no cognitive overhead to writing many, small, easily testable units. It also means that whenever a unit is created, a test is auto-generated for it, so developers have an even easier time testing their code.</p><h4>ember-cli-mirage</h4><p>Mirage is a ember-cli plugin that makes it dead simple to mock AJAX requests and responses in development. This has proven invaluable for building new features on a team. Instead of waiting for a teammate to get server routes up, or context switching to do it ourselves, we can create routes and seed the data we need with just a few lines. Combined with ember-data, it&#39;s even easy to generate complex relationship setups, which has historically been a challenge in our development workflows.</p><h4>Loading and error substates</h4><p>Adding loading and error states to views is a pattern that every frontend engineer has had to implement multiple times. With Ember, for route loading, loading and error states are automatically handled: given a route hierarchy (for instance /organization/&lt;id&gt;/applications), Ember will look for a loading.hbs and error.hbs template in every template folder. When data is loading, or loading fails, Ember will automatically render the respective loading or error template closest to the route the user is currently on. This lets you easily add a top-level loading state, then add specific loading states throughout your app where necessary. It&#39;s beautiful!</p><h3>Some not so good parts</h3><p>Of course everything hasn’t been perfect — learning any new framework is a challenge and migrating from one framework to another always brings some amount of frustration with the different paradigms.</p><h4>No hot-reloading or time travel debugging</h4><p>Hot-reloading and time travel debugging are two of the most useful tools that have come out of the React ecosystem. <br> <br> With hot-reloading, when you change code, the logic is reloaded in place, without requiring a page load. As a developer, this means you don’t need to navigate back to the point in the page — with the appropriate state — where you were working every time you make a change. Instead, the logic just refreshes and you can keep on working. <br> <br> With time travel debugging, it’s trivial to see how state in your application changes over time, and jump through those different states. This makes it easy to diagnose and fix bugs that come from complicated state manipulation!<br> <br> While there is a <a href="https://github.com/toranb/ember-cli-hot-loader">project to do hot reloading in Ember</a>, it’s very young and has limited support for different parts of an Ember application. Similarly, time travel debugging isn’t a concept that’s gotten traction in the Ember community — partially because data flow in Ember isn’t as well suited to it as a system like redux. <br> <br> Not having access to these tools is sad, but not the end of the world.</p><h4>Styling components is still the wild west</h4><p>In our React applications, styling components was always a point of frustration. This boiled down to two primary issues:</p><ol><li>There wasn’t a defined best-practice for how to style components. css-modules? CSS in JS? plain SASS?</li><li>Mostly because of (1), there wasn’t a defined best-practice for how to style components in a way where they could be published to NPM and then easily consumed in other projects</li></ol><p>In the Ember eco-system, (1) seems similarly unsolved: we’ve gone with css-modules for styling components, but have had to do contortions to make it work with a base styling system (like foundation). We haven’t had to do (2) yet, but it seems much simpler in Ember with Ember addons.</p><h3>Conclusion</h3><p>This post isn’t about whether Ember is better than React. This post is about why, when Clef was deciding whether to use React or Ember to build <a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=ember-over-react">Instant 2FA</a>, we went with Ember.</p><p>There are an infinite number of ways to build a web application and there are an infinite number of reasons the right decisions for our needs could be the wrong ones for you. This diversity of options is what makes the web evolve so fast — and what makes it so powerful. <br> <br><em> We hope you learned something from our thought process — and we’d love to learn something from yours. If you’ve made the same choice, we’d love to hear why! If you’ve made a different one, we’d love to hear why too!</em></p><p><em>Post a response or tweet at me at </em><a href="https://twitter.com/jessepollak"><em>@jessepollak</em></a><em> to continue the conversation.</em></p><p><em>Many thanks to </em><a href="https://medium.com/u/9bc1af085216"><em>Chris</em></a><em> and </em><a href="https://medium.com/u/5f8e94166bff"><em>Trek Glowacki</em></a><em> for reading the first draft of this and </em><a href="https://medium.com/u/5864d154f7f6"><em>mixonic</em></a><em> for inventing the Progressive DX terminology.</em></p><p><em>If 2FA has been in your backlog for months, check out </em><a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=ember-over-react"><em>Instant 2FA</em></a><em>, the easiest way to add two-factor authentication to any site in minutes.</em></p><figure><a href="https://twitter.com/instant2fa"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kzUKc_qwKSNPu_2BRILXSA.png" /></a></figure><figure><a href="https://medium.com/two-factor-everything"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cP0LmY26f6sEW0tJBrzfEQ.png" /></a></figure><figure><a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=ember-over-react"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JVor0bDapeq0QFgziLosNw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41a2e7fd341" width="1" height="1" alt=""><hr><p><a href="https://medium.com/two-factor-everything/choosing-ember-over-react-in-2016-41a2e7fd341">Choosing Ember over React in 2016</a> was originally published in <a href="https://medium.com/two-factor-everything">Two-Factor Everything</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Teams Don’t Integrate Two Factor Authentication]]></title>
            <link>https://medium.com/two-factor-everything/why-teams-dont-integrate-two-factor-authentication-e38a40cd7724?source=rss----3446c73693c0---4</link>
            <guid isPermaLink="false">https://medium.com/p/e38a40cd7724</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Darrell Jones III]]></dc:creator>
            <pubDate>Thu, 03 Nov 2016 16:25:54 GMT</pubDate>
            <atom:updated>2016-11-08T20:09:04.160Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*An5qMf0pLxrTlP8TSbQ7Kg.gif" /></figure><h4>The Cognitive Biases Behind Bad Security</h4><p>We all know that two-factor auth is a virtual necessity nowadays, yet a bunch of companies still haven’t hopped on.</p><p>What gives?</p><p>From experience, I can tell you that the folks making these decisions are smart, rational folks. There are a bunch of different reasons I hear for lagging behind, but I’ve rounded up the most popular.</p><h4>Two Factor will reduce signup rates (Deprival super-reaction tendency)</h4><ul><li>Misconception: Adding an additional hurdle to their signup flow will limit overall throughput.</li><li>Reality: Most folks keep their registration flow exactly the same while adding two factor as an opt-in feature. This means that there’s no extra hurdle for registration, but security conscious customers can still enable two factor at their convenience.</li></ul><h4>Two Factor will increase churn (Confirmation bias)</h4><ul><li>Misconception: Clunky codes, additional devices, and the occasional account lockout will annoy my users away from my site.</li><li>Reality: There are a bunch of different two factor solutions that streamline the login flow and/or offer BYOD implementations. Back up codes are pretty ubiquitous so users should always have a way in. Furthermore, with opt-in two factor deployments, only those users with an appetite for more security will endure the added protections.</li></ul><h4>Two factor auth still isn’t bulletproof (Misinformation effect)</h4><ul><li>Misconception: Two factor authentication is easily comprised and offers little actual protection for my customers.</li><li>Reality: While two factor authentication is no panacea, it certainly protects against the most common ways attackers compromise accounts. And two factor is not created equal. The spectrum between SMS, TOTP, PKI, and Hardware token allows you to choose what degree of protection makes sense for your use case.</li></ul><h4>Not a priority (Hyperbolic discounting)</h4><ul><li>Misconception: We don’t really need this security feature since no one is asking for it and we don’t expect to get hacked anytime soon.</li><li>Reality: Customer feedback works great for feature additions but falls short for critical infrastructure enhancements. Your operational risk, not your customers, should be your barometer for determining <a href="https://blog.instant2fa.com/the-best-time-to-integrate-two-factor-authentication-924c865ea93c#.m6qc2o2va">when is the right time to add two factor</a>.</li></ul><h4>Integration too time consuming and difficult (Ambiguity bias)</h4><ul><li>Misconception: A two factor integration would take me weeks to ship and require me to build out support for a lot of edge cases.</li><li>Reality: While most integrations do require a little time, there are providers that build two factor that you can ship in 15 minutes.</li></ul><p>These are the most common concerns I come across. As you can see, most of them are rooted in unfounded fear and general misunderstanding of the product, market, and functional necessity of two factor.</p><p>See something I missed? Reach out and let me know!</p><p><em>Darrell leads BD at Clef. Their new product — </em><a href="http://instant2fa.com/"><em>Instant2FA.com </em></a><em>— helps you integrate two-factor authentication in minutes instead of weeks.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e38a40cd7724" width="1" height="1" alt=""><hr><p><a href="https://medium.com/two-factor-everything/why-teams-dont-integrate-two-factor-authentication-e38a40cd7724">Why Teams Don’t Integrate Two Factor Authentication</a> was originally published in <a href="https://medium.com/two-factor-everything">Two-Factor Everything</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Would Two-Factor Authentication (2FA) Have Saved John Podesta’s Emails?]]></title>
            <link>https://medium.com/two-factor-everything/would-two-factor-authentication-2fa-have-saved-john-podestas-emails-1bf71880327d?source=rss----3446c73693c0---4</link>
            <guid isPermaLink="false">https://medium.com/p/1bf71880327d</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[2016-election]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[democrats]]></category>
            <dc:creator><![CDATA[B]]></dc:creator>
            <pubDate>Wed, 02 Nov 2016 19:50:33 GMT</pubDate>
            <atom:updated>2016-11-02T19:50:32.624Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past several weeks, I’ve heard different versions of this question a hundred times, and every security person I follow has taken the opportunity to remind everyone to turn on two-factor auth.</p><p><strong>But, the short answer is, probably not.</strong></p><p>Two-factor authentication makes logins much safer. I work on building 2FA because it is an incredibly important security tool, and nothing here changes my full endorsement of 2FA. You should go turn on 2FA today, <em>especially for your emails</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*KDx_Bufm61n0mGbNEikohA.png" /></figure><p>But, while 2FA protects against a lot of different kinds of attack, John Podesta’s emails were compromised by a phishing attack, and it probably would have worked even if he had 2FA turned on.</p><p>We know that he was phished because<em> the email that phished his Gmail account was included in the leak</em> (talk about swagger).</p><p>In a phishing attack, the user gets an email that looks like it’s from Google, but is really from the attacker. In this case, Podesta got an email from no-reply@accounts.googlemail.com with the subject line “Someone has your password” and a link to change his password. The link goes to a web page that looks like a Google password reset form, but is actually the attacker’s website. When they type their password to log in, the form submits it to the attacker, not Google.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*q8hNiZHUXKl4edvni5O9hA.png" /><figcaption>If you’re ever suspicious of an email, always check the URLs of the email address and the links!</figcaption></figure><p>In basic phishing attacks, the attacker is sending emails with phishing links to tons of people all at once and then storing all of the passwords that they collect to sell or use later. Since 2FA codes expire, users with 2FA are protected against these attacks.</p><p>However, in a more sophisticated attack (like the one that would target a high profile person like John Podesta), an attacker can also get the target’s 2FA code and then use it to log in immediately. If they’re clever, they can also redirect their target back to the real Gmail site when they’re done and make it look like the target simply mis-typed their password.</p><p>It’s possible that John Podesta just happened to get caught by a broad, basic attack which turned into a big deal because of his status, but it’s more likely that the person who sent this email knew who they were sending it to and were capable of the more sophisticated attack. If that’s true, he still should have had 2FA turned on, but it wouldn’t have kept his email safe.</p><p>So the moral of this story is still that you should turn on 2FA for your email, but <em>also</em> that phishing is a really dangerous and effective attack.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bf71880327d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/two-factor-everything/would-two-factor-authentication-2fa-have-saved-john-podestas-emails-1bf71880327d">Would Two-Factor Authentication (2FA) Have Saved John Podesta’s Emails?</a> was originally published in <a href="https://medium.com/two-factor-everything">Two-Factor Everything</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best Time to Integrate Two Factor Authentication]]></title>
            <link>https://medium.com/two-factor-everything/the-best-time-to-integrate-two-factor-authentication-924c865ea93c?source=rss----3446c73693c0---4</link>
            <guid isPermaLink="false">https://medium.com/p/924c865ea93c</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Darrell Jones III]]></dc:creator>
            <pubDate>Tue, 01 Nov 2016 23:13:34 GMT</pubDate>
            <atom:updated>2016-11-01T20:53:46.566Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XIoDTJDLJK54iGi45TPrxQ.jpeg" /></figure><h4>Before the Hack, After the Hack, or Nah?</h4><p>“When should we add two factor?”</p><p>Every engineering team I speak with has that question. A few folks have an answer, but what’s even more troubling, is that no one even has a process for this decision. Dev teams have no clue where to start.</p><p>Two factor is too important to be an afterthought, so I thought I’d compile some best practices from my experience helping teams figure out when it makes sense and when it doesn’t. There are really <strong>3 times</strong> when it makes sense to add two factor: <strong>after you get breached</strong>, <strong>before you get breached</strong>, and, well, <strong>never</strong>.</p><h3>After you get breached</h3><p>This one is a no-brainer. Breaches suck. When they happen you usually lose assets, users, and face. Two factor auth helps remedy each loss. Public facing security deployments help reassure user confidence while also improving site wide security. At this point, you’ve got a bunch of different fires to put out, so you might as well use one api to tackle all three.</p><h3>Before you get breached (This is the pro move)</h3><p>For all the pros out there who prefer to prevent messes instead of clean them up, this is the criteria I walk through with my clients to determine the urgency of an integration. It’s a simple acronym named CRAFT that helps you gauge your operational risk.</p><p>Customer. If your customers are developers or other technical crowds who have high security standards, you’re going to want to integrate two factor. If you service nontechnical folks, your customers won’t demand two factor as much.</p><p>Regulation and Compliance. If your business is subject to HIPAA, PCI DSS, FFIEC or any other mandate for security standards, you should absolutely offer two factor. Otherwise, regulation isn’t a problem for you.</p><p>Assets. If you store personally identifiable information, currency, or any sensitive information, you should add two factor to your next sprint. However, no need to rush on adding two factor if you don’t store valuable information.</p><p>Fraud. If your platform is prime for fake accounts, fraudulent transactions, spam or other abusive behavior, you’ll want to integrate two factor. If your platform is immune to those attacks, then fraud isn’t a problem for you.</p><p>Transactions. If your service permits users to transfer value or abuse coupons/promos, you should look into adding two factor. If y’all don’t transfer value, then transactions don’t increase your operational risk.</p><p>After working through the criteria, most clients develop a pretty clear sense of urgency around this critical piece of infrastructure. Some folks, however, find that their business doesn’t experience any of the above operational risk factors. Those companies are the ones who I advise to never integrate two factor.</p><h3>Never</h3><p>I’ve met a bunch of companies who would actually be better off <em>not</em> integrating 2FA. These folks don’t meet any CRAFT criteria. A few other things often differentiate their business:</p><h4>Trust</h4><ul><li>Their service requires little to no user trust in brand reputation</li></ul><h4>No user accounts</h4><ul><li>They don’t offer user accounts</li></ul><h4>Engagement</h4><ul><li>Customers don’t login to their site more than a few times in a complete lifecycle</li></ul><p>Companies in this boat have an operational risk profile so low that it doesn’t justify the dev time or cost. Weird as it may seem for someone who sells two factor, I advise folks like this to never buy two factor until their business model changes.</p><h3>Conclusion</h3><p>If your business meets a couple criteria of CRAFT, you might want to consider putting it on the product backlog. You might have a bit of trouble getting buy in from the brass, but <a href="https://blog.instant2fa.com/how-to-2fa-everything-pt-1-7abecee316bd#.wxb1gl1dr">working on your persuasion skills as a developer can be rewarding</a>. If you have a 5 alarm, full-on CRAFT-carrying business, you should definitely look into tossing in two factor stat. The methodology I outlined is meant to help you, but at the end of the day, the question of two factor is really about whether you prefer the ounce of cure or the pound of medicine.</p><p><em>Darrell leads BD at Clef. If two-factor authentication has been in your backlog for months, but still hasn’t gotten prioritized, check out Clef’s new product </em><a href="http://instant2fa.com/"><em>Instant2FA.com </em></a><em>— it’s two-factor authentication that takes minutes to integrate instead of weeks.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=924c865ea93c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/two-factor-everything/the-best-time-to-integrate-two-factor-authentication-924c865ea93c">The Best Time to Integrate Two Factor Authentication</a> was originally published in <a href="https://medium.com/two-factor-everything">Two-Factor Everything</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build a Wall That Stops White Walkers—Fantastic Threat Models]]></title>
            <link>https://medium.com/two-factor-everything/how-to-build-a-wall-that-stops-white-walkers-fantastic-threat-models-ef2dfa7864a4?source=rss----3446c73693c0---4</link>
            <guid isPermaLink="false">https://medium.com/p/ef2dfa7864a4</guid>
            <category><![CDATA[television]]></category>
            <category><![CDATA[fantastic-threat-models]]></category>
            <category><![CDATA[game-of-thrones]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[B]]></dc:creator>
            <pubDate>Mon, 31 Oct 2016 19:55:59 GMT</pubDate>
            <atom:updated>2016-10-31T19:55:58.357Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kg7fMqoDAu2PdJb8maKZqQ.png" /></figure><h4>Protecting the Seven Kingdoms from a giant horde of magic ice zombies</h4><p><em>WARNING: LOTS OF GAME OF THRONES SPOILERS</em><br> <br>Eight thousand years before that incredible moment when Tyrion smacked Joffrey’s smug little face in Winterfell, Brandon the Builder created the Wall a few hundred miles north. The Wall was built to protect Westeros from the super creepy White Walkers and its construction finally ended the Long Night. All of the plotting and killing and… romancing that happens in Game of Thrones is possible because of that wall — <em>thankfully</em> someone thought about how to make it secure. <br> <br>A wall that doesn’t keep out White Walkers is pointless, so the first step Brandon must have taken in building the wall was to develop a threat model. A threat model is a structured analysis of the security of anything you build.<br> <br>Imagine you’re Brandon the Builder and that you’re building the Wall. Creating the threat model takes three steps:</p><ol><li>Break the Wall down into each of its parts</li><li>Figure out how the White Walkers could attack each part</li><li>Make a strategy to defend against each attack</li></ol><h3>1. What Does it Take to Build a Wall That Strong?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*Bt69OKKHegjvl7jgDm1Xww.png" /></figure><p>First we need to break the Wall into its parts, and it’s <em>always</em> worth drawing a diagram. Think about all of the entry and exit points — where are people coming in and where do they go out? What other things do they depend on to keep working? Are they storing anything valuable? Where? <br> <br>Let’s work with these five sections:</p><ul><li><strong>300 miles of rock and ice 700 feet tall</strong></li><li><strong>Tunnels</strong> through the Wall with massive gates</li><li><strong>Weapons</strong> on the top of the Wall (trebuchets, catapults, cranes, a scythe)</li><li><strong>19 Castles</strong> south of the Wall (only three are occupied</li><li><strong>The Sworn Brothers of the Night’s Watch</strong> (aka Crows)</li></ul><p>All of these components are related, but they each serve a critical part in keeping the White Walkers out. If the White Walkers break any of them, it won’t matter who’s sitting on the Iron throne, everybody’s going to die.</p><h3>2. Testing the Defenses with STRIDE</h3><p>Now that we’ve broken the Wall down into its pieces, we want to see how the White Walkers could mess with each one. Again, they’re going to eat everyone if we miss one, so it pays to be thorough. Thankfully, someone (Microsoft) created a mnemonic for thinking about security threats: STRIDE. STRIDE stands for:</p><ul><li><strong>S — Spoofing</strong> (pretending not to be someone you’re not)</li><li><strong>T — Tampering</strong> (modifying something you shouldn’t be able to)</li><li><strong>R — Repudiation</strong> (denying responsibility for some action, whether you did it or not)</li><li><strong>I — Information Disclosure</strong> (accessing information you shouldn’t have)</li><li><strong>D — Denial of Service</strong> (preventing something from operating correctly)</li><li><strong>E — Elevation of Privilege</strong> (gaining abilities you shouldn’t have)</li></ul><p>This should help us think through the different angles the White Walkers might take. With a methodology in mind, we can apply it to each part of the Wall. Let’s start with the physical wall itself.</p><h4>300 miles of rock and ice 700 feet tall</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*hHfhsEqDDW5ICPS5q7bkrA.png" /></figure><p><em>Spoofing</em>:<strong> </strong>The Wall in no way cares who you pretend to be.<br><em>Tampering</em>:<strong> </strong>Modifying this Wall is only likely to crush you with falling ice and rock.<br><em>Repudiation</em><strong>:</strong> If you break the Wall, we’re going to know it was you.<br><em>Information Disclosure</em>: The Wall is big, what else do you want to know? <br><strong>Denial of Service — Vulnerability: </strong>Legends say that there is a horn called the Horn of Winter (or the Horn of Joramun), and that if someone blows into the horn, the entire Wall will collapse. That’s pretty much the only way to stop the Wall from working, but it’s one hell of a vulnerability. <br><em>Elevation of Privilege</em>: No one has any privileges with the Wall.</p><h4>Tunnels</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*yKlncVhQRRHAPpeSFWATyw.png" /></figure><p><strong>Spoofing — Vulnerability:</strong> The Crows control access to the tunnels, so you’d need to convince them that you’re a Crow (say, by wearing a black cloak? it’s a long shot) to get access to the tunnels. The Wights spoof their way through the tunnel by seeming/being dead, so if you can come back from the dead, that’s a trick that we know has worked before. <br><strong>Tampering—Vulnerability: </strong>The gates that protect the tunnels are 4 inch thick rolled steel, but apparently they can be broken. This is supposed to be super hard, but Mag the Mighty did it on his own. Granted, he’s a giant but still, damn.<br><em>Repudiation</em>: Nope. <br><em>Information Disclosure</em>:<em> </em>The tunnels don’t know anything. <br><em>Denial of Service:</em> This wouldn’t be a very good way to get through the Wall (in fact, filling the tunnel with rocks and ice is a built in <em>defense). </em><br><strong>Elevation of Privilege — Vulnerability: </strong>If you makes it through a tunnel, it’s pretty much game over because they can take over the access controls of the tunnel and let in the rest of their army.</p><h4>Weapons</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*6QSjtjjtzda3VG7Ub_usRw.png" /></figure><p><strong>Spoofing—Vulnerability</strong><em>: </em>You can get the Crows to waste their ammo on a dummy, they’re pretty well stocked, but eventually this could take the weapons offline.<br><strong>Tampering—Vulnerability: </strong>The weapons are on the top of the Wall, but if you can reach them (warging, giants firing bows, climbers) then you can take them offline.<br><em>Repudiation</em>:<em> </em>The weapons don’t care what you did or didn’t do. <br><strong>Information Disclosure — Vulnerability: </strong>You could figure out where the weapons are located by warging into a bird to help prepare for an attack. <br><strong>Denial of Service — Vulnerability: </strong>In one episode, when the Wall is under attack, the Crows release a giant scythe connected to the Wall with a chain. It swings in an arc and kills a group of climbers in its path. However, the scythe is slow to reset, so an attacker could intentionally trigger the scythe (by sacrificing climbers or by faking it out somehow), and then climb past it before it can be reloaded. <br><strong>Elevation of Privilege — Vulnerability: </strong>If you take control of the weapons and point them south, the battle will turn very quickly.</p><h4>Nineteen Castles</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*TE_IT90wiLwXRYb_6yDo7w.png" /></figure><p><em>Spoofing</em>: It’s possible that you can spoof your way into the castle from the south, but a White Walker would have to take the tunnels and we already covered spoofing those. <br><em>Tampering</em>:<em> </em>Only 3 of the 19 castles are occupied, so you could mess with or destroy the other 16 if you could get to them. Again, you’d basically have to come from the south. <br><em>Repudiation</em>: Hm, don’t think so. <br><strong>Information Disclosure — Vulnerability: </strong>The castles receive messages via ravens that could be intercepted, especially by a warg. <br><em>Denial of Service</em>: Cutting off supplies to a castle from the south would keep it from functioning for defenses. <br><em>Elevation of Privilege</em>: If you take a castle, including one of the empty ones, your position becomes much harder to attack. Again, this isn’t that useful to White Walkers.</p><h4>The Sworn Brothers of the Night’s Watch</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*cHG_oSDzYQ6rLidOzfXcdg.png" /></figure><p><em>Spoofing</em>: These dudes are all criminals or hiding from something, so if you’re human it would be pretty easy to infiltrate their ranks (this was Cersei’s plan to kill Jon Snow with Osney Kettleblack in the books). If you’re a White Walker, it’s way less easy because you’re creepy and white and have horns and glowing eyes and look like an ice lizard. <br><strong>Tampering — Vulnerability: </strong>Hm, this covers wounding a crow, which the White Walkers can definitely do if they get close enough. <br><strong>Repudiation — Vulnerability: </strong>The Crows lack trust, so repudiation could be a deadly strategy against them. If you are able to successfully carry out an attack and then avoid blame for it, you can turn the Crows against each other. <br><strong>Information Disclosure — Vulnerability: </strong>The Crows are pretty tough, but they’re human and the White Walkers are pretty twisted, so they probably have ways to make a Crow talk. <br><strong>Denial of Service — Vulnerability: </strong>Sowing discord can totally ruin the Crows. A little politicking and the infighting makes them completely vulnerable to an attack. <br><strong>Elevation of Privilege — Vulnerability: </strong>If you can infiltrate the Crows, you can get access to the weapons and the gate controls.</p><h3>3. Patching the holes</h3><p>This breakdown shows three major flaws in the Wall’s defenses.</p><ol><li>The Horn of Winter totally owns it</li><li>The Tunnels can be breached by giants</li><li>The Sworn Brothers of the Night’s Watch are flawed humans who can be exploited in a bunch of different ways.</li></ol><p>Then, there are a second tier of vulnerabilities like wargs being able to intercept messages from ravens or determine the placement of weapons. Those are a lot less critical fixes for now.</p><p>First things first, we should prioritize finding and destroying that horn, because it’s most likely to result in catastrophic failure (a horn that was probably fake was found and destroyed in the books, but only because the wildlings were threatening to use it — the Crows should have been proactive about finding it themselves). The Tunnels already have the self-destruct defense where they get filled in, but can we get some stronger doors on the tunnels? Someone should look into that and figure out how much it would cost. Then, in order to address the Crows being humans, we need more structure for their order. They keep getting distracted with human things instead of focusing on ice-demon things, so lets increase the ratio of maesters to warriors to make sure they’re staying focused on the right enemy. Also, new recruits (and we should be getting way more new recruits) should go through their training in less important castles so they’re less likely to mess the whole thing up. Also, how about some terrifying White Walker murals in the castles? Yeah, that would probably help.</p><p>If we could get all of that done, the Crows could feel a lot better about the Wall’s chances against the growing army of icy undead.</p><h3>Go forth and threat model</h3><p>And that’s how Brandon the Builder would threat model the Wall he built. Break it into pieces, think about how each piece can be attacked, then prioritize the flaws and get to fixing them. The term “threat model” sounds like it requires a bunch of special training, but in reality it’s a simple process that everyone should be doing it all the time. Just like version control, it should be in the toolbox of every developer. With practice, it gets easier and more natural, though some structure like STRIDE helps keep us honest and makes sure we don’t get sloppy.<br> <br>So far, the Wall has been good enough to protect the Seven Kingdoms. With a quick analysis, however, we can see that it’s far from perfect, and there’s more to do if the Crows want to avoid becoming White Walker lunch.</p><p>Of course, if the White Walkers get a dragon, all bets are off…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*JeuSKO4cNWkwq-4tydJtsw.png" /><figcaption>This poster isn’t real, but George RR Martin would totally pull something like this.</figcaption></figure><p><em>B is the CEO and co-founder at Clef. If two-factor authentication has been in your backlog for months, but still hasn’t gotten prioritized, check out Clef’s new product </em><a href="http://instant2fa.com/"><em>Instant2FA.com </em></a><em>— it’s two-factor authentication that takes minutes to integrate instead of weeks.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef2dfa7864a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/two-factor-everything/how-to-build-a-wall-that-stops-white-walkers-fantastic-threat-models-ef2dfa7864a4">How to Build a Wall That Stops White Walkers—Fantastic Threat Models</a> was originally published in <a href="https://medium.com/two-factor-everything">Two-Factor Everything</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to 2FA Everything — Pt 2.]]></title>
            <link>https://medium.com/two-factor-everything/persuasion-for-engineers-on-large-teams-b8c4676c48c?source=rss----3446c73693c0---4</link>
            <guid isPermaLink="false">https://medium.com/p/b8c4676c48c</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Darrell Jones III]]></dc:creator>
            <pubDate>Wed, 26 Oct 2016 17:10:31 GMT</pubDate>
            <atom:updated>2016-10-28T16:46:33.236Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dSilsjXSXHqLnzt0YHrjyw.jpeg" /></figure><h4>Indirectly build what you want</h4><p>Last blog I shared a bit of <a href="https://blog.instant2fa.com/how-to-2fa-everything-pt-1-7abecee316bd#.d4us1kzdt">how I help engineers develop a voice </a>so they can advocate for what they want to build within their teams. Those tips work great for small technical teams (&lt;5 engineers).</p><p>Large technical teams often have more bureaucracy which makes decision-making a convoluted process. A simple pitch won’t change what’s on the product roadmap. Instead, engineers on large teams have to present a compelling business case for the features they want to ship.</p><p>That’s where I typically step in, because most engineers make a critical mistake here: they try and convince people directly. That rarely works. Instead, I teach engineers how to persuade indirectly.</p><h4>Persuading Indirectly</h4><p>The objective of indirect persuasion is to help your targets convince themselves of your intended idea. We accomplish this by asking a series of questions that spur guided self-inquiry. Most sales literature builds upon this underlying mechanic with a bunch of different methods. In my experience, engineers tend to have pretty good results with the SPIN model, so we’ll use that as our starting point into indirect persuasion.</p><h4>The SPIN model</h4><p>SPIN (Situational, Problem, Implication, Need-Payoff) is a simple framework oriented around 4 key kinds of question.</p><p>You pretty much need to casually ask your targets questions from each category, in order. You should know the answer to the question before you ask it, so you might need to do research beforehand. The question should lead your target down the logical direction you’d like them to pursue — that there is a problem with scary implications, but with the right solution, you can reap a bunch of benefits for the business.</p><p>When asking your questions, I recommend not diving in through each section in one sitting. Remember, this is not a direct confrontation, this is an indirect workaround. Pepper some questions through Slack, followup with some over meals, ask a couple in between meetings, and take note of the answers. <br> <br>Once you’ve compiled answers to each theme, simply string together the responses into a coherent presentation. Formally, sales folk call this a scope of work, but you can just call it your full script.</p><p>Run through this script with a few teammates to get broad based support. Use their feedback to improve your delivery and questions. After you’ve gathered enough buy in and evidence, run your engineering lead or CPO through the script during a 1-on-1 or lunch.</p><p>If you’ve accurately identified a business need, evoked the right responses with thoughtful questions, and proposed (hopefully developed) a strong solution, your team should gladly move in your direction. After all, if you’ve persuaded them indirectly, they’ll think it’s their own!</p><h3>Example Questions</h3><h4>Situation (these are questions seeking facts)</h4><ul><li>Have we experienced any hacked accounts?</li><li>Do we have any user facing security measures in place?</li><li>Are any users asking for 2FA</li></ul><h4>Problem (ask about the difficulties and dissatisfactions the target is experiencing and focus the target on this pain while clarifying the problem)</h4><ul><li>Do we look less trustworthy and reputable without 2FA?</li><li>Why don’t we currently offer 2FA?</li><li>What kind of risk are we exposing ourselves to without 2FA?</li></ul><h4>Implication (discuss the effects of the problem, and develop the seriousness of the problem to increase the buyer’s motivation to change)</h4><ul><li>How many users do we lose by appearing untrustworthy and illegitimate?</li><li>How much would it cost us to recover from a hack?</li></ul><h4>Need-payoff (these probe for explicit needs and get the buyer to state the benefits)</h4><ul><li>If we appeared more reputable, how would that help our business?</li><li>What features would we be able to offer if users trusted us with more of their information?</li></ul><p><em>Darrell leads business development at </em><a href="http://getclef.com/"><em>Clef</em></a><em>. If two-factor authentication has been in your backlog for months, but still hasn’t gotten prioritized, check out Clef’s new product </em><a href="https://instant2fa.com/?utm_source=medium&amp;utm_medium=referral"><em>Instant2FA.com</em></a><em> — it’s two-factor authentication that takes minutes to integrate instead of weeks.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8c4676c48c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/two-factor-everything/persuasion-for-engineers-on-large-teams-b8c4676c48c">How to 2FA Everything — Pt 2.</a> was originally published in <a href="https://medium.com/two-factor-everything">Two-Factor Everything</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a DDoS and why was Twitter down all day?]]></title>
            <link>https://medium.com/two-factor-everything/what-is-a-ddos-and-why-was-twitter-down-all-day-863741950577?source=rss----3446c73693c0---4</link>
            <guid isPermaLink="false">https://medium.com/p/863741950577</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[breaking-news]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[news]]></category>
            <dc:creator><![CDATA[B]]></dc:creator>
            <pubDate>Fri, 21 Oct 2016 23:28:27 GMT</pubDate>
            <atom:updated>2016-10-22T00:16:43.628Z</atom:updated>
            <content:encoded><![CDATA[<p>A big chunk of the internet was down today, which you probably noticed (unless someone printed this Medium post out for you). I just saw this hilarious image of Fox News anchors trying to explain what happened and figured that there might be a lot of confused people today — if you’re one of those people, I’m here to help!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qKuk3qKC8lBSWljCnGOEvw.png" /></figure><p>Here’s the top line, jargon-filled explanation of what happened: <strong>someone used a DDoS attack to take down a popular DNS host </strong>called<strong> </strong>Dyn to shut down a lot of websites all at once. Now, let’s break that down.</p><h4>What’s a DNS host?</h4><p>DNS stands for Domain Name System, and it’s like the address book in your phone. When you want to call someone, you only need to remember their name, not their phone number. Well websites (and every computer on the internet) have a phone number called an IP Address, and a DNS host is where your computer looks up that phone number when you type the website’s name into your browser. Have you ever dropped your phone in the toilet and lost all of your phone numbers? That’s exactly what it’s like when a DNS goes down.</p><p>In this case, the DNS host was a company called Dyn, and it was used by a bunch of big Internet companies, including Twitter.</p><h4>Well how does a DDoS take a DNS host down?</h4><p>DDoS stands for Distributed Denial of Service, and it basically means that someone has lots of computers (like, hundreds of thousands of them) all trying to access the same website at the same time to overwhelm it and shut it down.</p><p>You should think of a DDoS attack like sinking a ship by putting holes in it. The crew is ready to bail out a certain amount of water, so in order to sink the ship (take the website down) the attacker needs to be able to fill faster than they can bail.</p><p>To take down a big, well prepared website like a major DNS host, you need to put <em>a lot </em>of holes in the ship — which is why the Internet doesn’t go down every day.</p><h4>Well who did this and how did they do it?</h4><p>We’re still not sure who did this and we might not ever know. Figuring out who carried out an attack (called Threat Attribution in the infosec world) is really hard. There are a lot of theories flying around, and at least one hacker group has already claimed responsibility, but it’s worth letting the dust settle before you take any of that at face value.</p><p>But while we don’t know who did it, we do know how they did it. Attacks of this scale are almost always carried out by botnets. A botnet is like a zombie army of computers — a virus spreads and silently infects all of the computers. Then, when the attacker wants to do something, they activate the virus and order all of the infected computers to attack the same target.</p><h4>I can’t live without Twitter! Is this going to keep happening?</h4><p>Lately there have been <a href="https://krebsonsecurity.com/2016/09/krebsonsecurity-hit-with-record-ddos/">several huge DDoS attacks</a> which indicate that more attacks like this could keep happening. However, an attack of this size is really hard to pull off, and once it happens, we can build up defenses to keep the same person from doing the same thing again. Today was a wake-up call for internet companies that we’ve centralized a lot of the internet’s infrastructure and made it easier to knock down a lot of big companies at once.</p><p>If you have other questions about what happened today, tweet me at <a href="http://twitter.com/iamb">@iamb</a>.</p><p><em>B is the CEO and co-founder at Clef. If two-factor authentication has been in your backlog for months, but still hasn’t gotten prioritized, check out Clef’s new product </em><a href="http://instant2fa.com/"><em>Instant2FA.com</em></a><em> — it’s two-factor authentication that takes minutes to integrate instead of weeks.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*prif7-04oPf8Dqo1gvSDsQ.gif" /><figcaption>Did you enjoy this post? Click the ❤ below to recommend it to other interested readers!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=863741950577" width="1" height="1" alt=""><hr><p><a href="https://medium.com/two-factor-everything/what-is-a-ddos-and-why-was-twitter-down-all-day-863741950577">What is a DDoS and why was Twitter down all day?</a> was originally published in <a href="https://medium.com/two-factor-everything">Two-Factor Everything</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>