{"id":3066,"date":"2019-10-03T10:04:53","date_gmt":"2019-10-03T14:04:53","guid":{"rendered":"http:\/\/www.soul-repairs.com\/blog\/?p=3066"},"modified":"2019-10-02T23:05:44","modified_gmt":"2019-10-03T03:05:44","slug":"building-alliances-or-why-security-is-awesome","status":"publish","type":"post","link":"https:\/\/soul-repairs.com\/blog\/2019\/10\/03\/building-alliances-or-why-security-is-awesome\/","title":{"rendered":"Building Alliances &#8211; or, Why Security is Awesome"},"content":{"rendered":"<h2>Time to Go Fast<\/h2>\r\n<p>We work with a lot of people who are implementing <a href=\"https:\/\/soul-repairs.com\/blog\/tag\/continuous-delivery\/\">Continuous Delivery<\/a>. We see that when various bumps and boulders get out of the way of delivering software stably and rapidly, there&#8217;s a strong push to go <em>very very fast<\/em>. When this happens, there are often barricades put up in the name of security &#8211; because traditionally speed and security have been considered <em>enemies<\/em>. Traditional enterprise IT security would say, <em>you can&#8217;t possibly go fast in a safe way,\u00a0<\/em><\/p>\r\n<p><!--more--><\/p>\r\n<p>However&#8230;that isn&#8217;t actually <strong>true<\/strong>. And despite the storied past of speed and stability being enemies, enterprise IT is starting to understand:<\/p>\r\n<blockquote>\r\n<p><em>&#8230;speed depends on stability, so good IT practices give you both.<\/em><br \/>&#8211; Martin Fowler,<a href=\"https:\/\/martinfowler.com\/articles\/accelerate-foreword.html\"> foreward to Accelerate<\/a><\/p>\r\n<\/blockquote>\r\n<h2>Speed and Security are <em>Allies<\/em><\/h2>\r\n<p>We recently gave a talk about Kubernetes security, and the section our audience found most interesting &#8211; and the section that\u00a0<em>we<\/em> found most interesting, after arguing about it a little bit &#8211; was a section addressing this very thing. We thought it would be good to distill that section into a blog post explaining our thinking about AppDev speed, agility, and security.<\/p>\r\n<h2>Possible Responses to Threats<\/h2>\r\n<p>Security threats to enterprises via their applications are real, and there are a few likely enterprise responses. Ideally, they respond to threats in ways that help everyone see that not only is security is <em>helpful<\/em> and not the enemy of innovation and delivery speed &#8211; but actually, security helps to\u00a0<em>enable<\/em> innovation and delivery speed.<\/p>\r\n<h3>Possible Response #1: Cover Your Eyes, Pretend it&#8217;s Not There<\/h3>\r\n<figure style=\"width: 187px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/lh3.googleusercontent.com\/HJ_dadNR4-d6ntsSglUx55Y5uSmOohnHzOVj705nwrqkIa7OVfvI-vSdPO4hRVDkqIFVuenYobUmbBF-ME1NwG5Vl2TCToNlWWxbkoat77ZsgK1FNhh8AK9xE3dSOt1BVxVaENvHvlY\" alt=\"\" width=\"187\" height=\"187\" data-wp-editing=\"1\" \/><figcaption class=\"wp-caption-text\">Just don&#8217;t look at it&#8230;<\/figcaption><\/figure>\r\n<blockquote>\r\n<p>\u201cWe\u2019ll just ignore that there <strong>are<\/strong> security threats.\u201d<\/p>\r\n<p>Speed in the moment: highest<br \/>Likelihood of catastrophes: very high\u00a0<br \/>Pain\/interruption of daily process: medium, varies with awareness of reality<br \/><strong>Overall speed: slow<\/strong><\/p>\r\n<\/blockquote>\r\n<p>This approach is all too common, especially in overloaded teams with no room to think or even breathe. They can&#8217;t get their heads up above the water level long enough to see what&#8217;s coming at them &#8211; so they have to prioritize and that means ignoring security threats.\u00a0<\/p>\r\n<p><em>Hopefully these teams can prioritize the actual worst threats &#8211; but it&#8217;s hard to prioritize if you don&#8217;t have time to think.<\/em><\/p>\r\n<h3>Possible Response #2: Everything is a Threat<\/h3>\r\n<figure style=\"width: 147px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" class=\"\" src=\"https:\/\/lh5.googleusercontent.com\/V1vSp0-RWJTipZXb3GspJ62PcwO6H9gUhIQDF3EhLHlFxbs0jy3QHV1iXnTy9Zw3WNUwoz0lCYPt1DWTfo2GS6pYA8DWenCJLSX0ASCf3f-GyD8R49vKx-Z-BLqB7wpavmbg9yX1ObY\" alt=\"\" width=\"147\" height=\"94\" \/><figcaption class=\"wp-caption-text\">PANIIIIIC EYES<\/figcaption><\/figure>\r\n<blockquote>\r\n<p>\u201cWe\u2019re afraid of everything &#8211; too afraid to make a plan. So&#8230;can you go through all of your code, line by line, and report back that there are no security issues (or other illogical, unhelpful things)?\u201d<\/p>\r\n<p>Speed in the moment: lowest<br \/>Likelihood of catastrophes: highest &#8211; not only ineffective, but gives a false sense of \u201csecurity\u201d<br \/>Pain\/interruption of daily process: highest<br \/><strong>Overall: slowest and most painful<\/strong><\/p>\r\n<\/blockquote>\r\n\r\n<p>This is the other side of ignoring threats &#8211; assuming that\u00a0<strong>everything<\/strong> is a threat, and therefore trying to pay attention to&#8230;<strong>everything<\/strong>.<em>\u00a0<\/em>Again, this tends to come from a complete lack of the ability to prioritize, which is how everything becomes the <em>most important problem<\/em>.<em>\u00a0<\/em>When everything is important, <strong>nothing<\/strong> is important &#8211; except you have much higher mental and emotional load from the panic.<\/p>\r\n<blockquote>\r\n<p>When everything is important, <strong>nothing<\/strong> is important &#8211; except you have much higher mental and emotional load from the panic.<\/p>\r\n<\/blockquote>\r\n<p>(And&#8230;as much as we wish it were an exaggeration, yes &#8211; some companies\u00a0<strong>do<\/strong> have multiple experts analyze every line of code for possible security issues. It&#8217;s massively expensive and no guarantee of safety &#8211; but they have to decide if it makes sense for them. Also that&#8217;s far from the goofiest security thing that&#8217;s been discussed on the internet &#8211; here are some <a href=\"https:\/\/www.networkcomputing.com\/careers-and-certifications\/10-worst-security-practices\">examples<\/a>, and some <a href=\"https:\/\/zeltser.com\/bad-information-security-advice\/\">more examples<\/a>.)<\/p>\r\n\r\n<h3>Possible Response #3: Open-Eyes, Reasonable Priorities, Brain Space to Address Things, and Trust that Recovery is Possible<\/h3>\r\n\r\n<figure class=\"wp-block-image\">\r\n<figure style=\"width: 230px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/lh5.googleusercontent.com\/_lW_bE2LnsMbrTbXerXrTbR6-SqaGR_d74IiTKpDCd0wNOylke8uKTfR2dN9Dp8MHVAUw38AQeK20coCqz3-elxZ8wOylsfZV55-q9-qa04iRwFpKtr5ESE4t5g-ks1Xi3R-y5MU6SA\" alt=\"\" width=\"230\" height=\"245\" \/><figcaption class=\"wp-caption-text\">This guy has his security risks prioritized and is working on addressing them&#8230;in priority order, of course.<\/figcaption><\/figure>\r\n<\/figure>\r\n<blockquote>\r\n<p>\u201cWe acknowledge that threats exist, and we\u2019ve made the best plan we can for proactively addressing them &#8211; and we trust that we can adapt that plan if we need to. We just\u2026 do security, built into our processes.\u201d<\/p>\r\n<p>Speed in the moment: medium to high, especially with automation<br \/>Likelihood of catastrophes: lowest<br \/>Pain\/interruption of daily process: low<br \/><strong>Overall: fastest!<\/strong><\/p>\r\n<\/blockquote>\r\n<p>And then there&#8217;s this option &#8211; security woven into all aspects of the application development and deployment life cycle, and done with reasonable asks and enough trust that if a catastrophe occurs,\u00a0<em>it&#8217;ll be okay<\/em>.\u00a0<\/p>\r\n<p>&#8230;we like this one the best. Probably you guessed that.<\/p>\r\n\r\n<h2>The Importance of Clarity: Application Development\/Infrastructure\/Security Communication<\/h2>\r\n<p>Like so many other things in transforming organizations, successfully building an agile, high-trust environment requires <strong>clear communication<\/strong> &#8211; of advantages and goals, and also of risks and challenges.<\/p>\r\n<p>App Dev and Architecture teams often have their own history, vocab, and understanding about the process of producing quality software. IT Security\/Data Security teams often <em>also<\/em> have their own history, vocab, and understanding about the process of creating and running secure software. Bridging these gaps and working <em>together<\/em> &#8211; usually with a lot of up-front clarity, and hopefully with shared goals from leadership &#8211; goes a long way toward building the successful, trusting, agile culture that fast application delivery requires.\u00a0<\/p>\r\n","protected":false},"excerpt":{"rendered":"<p>Time to Go Fast We work with a lot of people who are implementing Continuous Delivery. We see that when various bumps and boulders get out of the way of delivering software stably and rapidly, there&#8217;s a strong push to go very very fast. When this happens, there are often barricades put up in the &hellip; <\/p>\n<p class=\"read-more\"><a class=\"btn btn-default\" href=\"https:\/\/soul-repairs.com\/blog\/2019\/10\/03\/building-alliances-or-why-security-is-awesome\/\"> Read More<span class=\"screen-reader-text\">  Read More<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[29,28,4],"tags":[45,87,44,109,147],"wf_post_folders":[],"coauthors":[11,26],"class_list":["post-3066","post","type-post","status-publish","format-standard","hentry","category-leadership","category-organizations","category-technology","tag-continuous-delivery","tag-kubernetes","tag-openshift","tag-pain","tag-security"],"_links":{"self":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts\/3066","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/comments?post=3066"}],"version-history":[{"count":5,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts\/3066\/revisions"}],"predecessor-version":[{"id":3074,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/posts\/3066\/revisions\/3074"}],"wp:attachment":[{"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/media?parent=3066"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/categories?post=3066"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/tags?post=3066"},{"taxonomy":"wf_post_folders","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/wf_post_folders?post=3066"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/soul-repairs.com\/blog\/wp-json\/wp\/v2\/coauthors?post=3066"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}