<?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[Stories by Jad Boutros on Medium]]></title>
        <description><![CDATA[Stories by Jad Boutros on Medium]]></description>
        <link>https://medium.com/@jadboutros?source=rss-8d2d859f2f3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*tqE5HTRBkzhblwiPjRX2AA.jpeg</url>
            <title>Stories by Jad Boutros on Medium</title>
            <link>https://medium.com/@jadboutros?source=rss-8d2d859f2f3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:42:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jadboutros/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Thoughts on starting a security and privacy program for your SMB]]></title>
            <link>https://medium.com/swlh/thoughts-on-starting-a-security-and-privacy-program-for-your-smb-915cd70ed9ee?source=rss-8d2d859f2f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/915cd70ed9ee</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Jad Boutros]]></dc:creator>
            <pubDate>Tue, 05 May 2020 00:02:22 GMT</pubDate>
            <atom:updated>2020-05-06T01:37:52.985Z</atom:updated>
            <content:encoded><![CDATA[<p>Following nine years at Google focused on application security and many more years as a developer, I joined Snapchat in 2014 to build a security and privacy team from the ground up. Amidst such a fast-growing company, I was determined to build a strong enough team that it could not only protect the business but in fact enable it to do more. I saw first hand the complexities involved and in the time since, I’ve met countless companies struggling with how to start a security and privacy program. I hope these few thoughts can help you.</p><p><strong>Invest early.</strong></p><p>Investing early in your security and privacy program has a compounding effect. It allows strong relationships to cultivate over-time between security, privacy, product, engineering and other teams based on trust and shared experiences. These relationships then facilitate more effective decision making, such as when your product innovates in new directions requiring fundamentally new security and privacy approaches, or when facing reported serious vulnerabilities. It also takes time for your company culture to embrace security and privacy and to truly recognize that everyone has a role in keeping your company data as well as your customer data safe.</p><p>Yet again some companies delay investing in security and privacy until a severe event occurs and then commit in panic and haste (and waste). Why the push-back? Budget considerations aside, some executives fear that security and privacy enact barriers that slow down innovation and execution, putting the company’s growth at risk.</p><p>This thinking however is not right. Security and privacy can be integrated into your organization without bogging you down, and in fact over-time enable you to innovate even better. For example, Snap couldn’t have developed a successful SnapKit framework to integrate with other applications had they not built a secure first-class authentication service in the first place. Moreover, responding to serious security and privacy incidents can significantly affect your momentum. One recent example is Zoom which declared a ninety day moratorium on all product development to <a href="https://blog.zoom.us/wordpress/2020/04/08/update-on-zoom-90-day-plan-to-bolster-key-privacy-and-security-initiatives/">focus on security and privacy</a>.</p><p>Spare yourself unnecessary risk of data theft and data compromise and consider building a security program early-on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oq2XLVT1H-U2hN7024CjWA.jpeg" /><figcaption>Invest early in your security and privacy program.</figcaption></figure><p><strong>Invest initially in security and privacy by design.</strong></p><p>The security and privacy fields are now so large covering so many specializations that it is daunting to know where to start. For many companies, a good place to start is with <a href="https://en.wikipedia.org/wiki/Secure_by_design">security-by-design</a> and <a href="https://en.wikipedia.org/wiki/Privacy_by_design">privacy-by-design</a>, which can be summarized as follows: whenever you are introducing a change to your product or to your organization that could introduce security or privacy risks, consider those risks before proceeding with the change.</p><p>There are two main reasons to start there. The first is that in the early stages of your company, your biggest exposure on the Internet is often your product so paying careful attention to protecting its security and privacy will go a long way. The other is that security-by-design and privacy-by-design are fundamentally cross-functional, requiring active involvement from many teams, including product and engineering.The earlier you start, the easier these processes will be shared through institutional knowledge and improved.</p><p><strong>Build gradually.</strong></p><p>As you integrate security and privacy in your software development life cycle, keep in mind there isn’t a one size fits all. If you ask too much of this process early on, everyone loses. Your security and privacy team will be overwhelmed; developers and product teams will have to wait endlessly for their reviews to be done, and eventually begin to circumvent the process. For over a year, I reviewed almost all production code as it was being written by hundreds of talented developers. Even with the use of safe frameworks, this approach was simply not sustainable.</p><p>Instead, focus initially on a simple process that prioritizes the most significant risks and then over-time expand it to cover more surface and more depth. Typical areas that call for scrutiny upfront are authentication and authorization, use of cryptography, as well as new APIs using customer data.</p><p>Conducting those reviews before you ship new features is critical to building an effective security and privacy program. Reviews bring attention to risks that may not have been considered during product design and development, and facilitate solutions to mitigate these risks. As such, start the reviews as early as possible in the feature life-cycle to give yourself time to address findings without having to delay feature launches.</p><p>During the course of reviews, you likely will find patterns of risk — classes of vulnerabilities — that emerge repeatedly. Consider eliminating these risks by building appropriate defenses against them. Doing so, often requires sustained development, this is why a good security and privacy team usually includes software developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Or7OKX8QDw8GxT0joPyzWA.jpeg" /><figcaption><strong>Invest initially in security and privacy by design.</strong></figcaption></figure><p><strong>Where to go from here?</strong></p><p>As your company grows, you’ll also want to invest in a number of other key components of a security and privacy program including: protecting your infrastructure and corporate assets; building strong incident response; managing third party risk; mitigating risks of social engineering, administrative account compromise, and insider threats. At Snap, our head of engineering reasoned that 10% of all of engineering headcount should be dedicated to security, privacy, and spam-and-abuse. While this number varies based on numerous factors, you may find your own number that helps you benchmark the growth of your security and privacy team.</p><p>I firmly believe that investing early and steadily in your security and privacy program does not need to slow you down; it makes you much safer, and empowers your innovation in the long run.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=915cd70ed9ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/thoughts-on-starting-a-security-and-privacy-program-for-your-smb-915cd70ed9ee">Thoughts on starting a security and privacy program for your SMB</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>