![](\"http:\/\/www.cloudcomputing-news.net\/media\/img\/news\/silos-towers-picture-id516261852.jpg\")
<\/p>\n<\/p>\n
It started with DevOps. Then there was NetOps. Now SecOps. Or is it DevSecOps? Or maybe SecDevOps?<\/span><\/span><\/p>\n Whatever you decide to call it, too often the end result is little more than the same old siloes with shiny new names. We've become so focused on "what do we call these folks" that we sometimes forget "what is it we're trying to accomplish".<\/span><\/span><\/p>\n Shakespeare said that a rose would smell as sweet by any other name. Let's apply that today to the number of factions rising in the operations game. Changing your name does nothing if you don't change your core behaviours and practices.<\/span><\/span><\/p>\n Back when cloud first rose – pun intended – there were plenty of pundits who dismissed enterprise efforts to build private (on-premises) cloud. Because it didn't fit the precise definition they wanted to associate with cloud. They ignored that the outcome <\/em>was the measure of success, not measuring up to someone else's pedantic definition. They sought agility and efficiency and speed by changing the way infrastructure was provisioned, configured, and managed. They changed behaviours <\/em>and practices <\/em>through the use of technology.<\/span><\/span><\/p>\n Today the terminology wars are focused on X-Ops and what we should call the latest arrival, security.<\/span><\/span><\/p>\n I know I've used the terms, and sometimes I use them all at the same time. But perhaps what we need is fewer<\/em> distinctions. Perhaps I should just say you're either adopting "modern ops" in terms of behaviours and practices or you're remaining "traditional ops" and that's all there is to it.<\/span><\/span><\/p>\n Modern ops employ technology like cloud and automation to build pipelines that codify processes to speed delivery and deployment of applications.<\/span><\/span><\/p>\n And they do it by changing behaviours and practices. They are collaborative and communicative. They use technology to modernise and optimise decades old processes that are impeding delivery and deployment. They work together, not in siloed X-Ops teams, to achieve their goal of faster, more frequent releases that deliver value to the business and delight consumers.<\/span><\/span><\/p>\n Focusing on what to call "security" as they get onboard with modern ops can be detrimental to the basic premise that delivery and deployment can only succeed at speed with a collaborative approach. Slapping new labels on a new focused team just builds differenter siloes; it doesn't smash them and open up the lines of communication that are required to operate at speed and scale.<\/span><\/span><\/p>\n It also unintentionally gives permission to other, non-security ops to abdicate security responsibilities to the <SecDevOps | DevSecOps> team. Because it's in their name, right?<\/span><\/span><\/p>\n That's an increasingly bad idea given that application security is a stack and thus requires a full stack to implement the right protections. You need network security and transport security and you definitely need application security. The attack surface for an app includes all seven layers and, increasingly, the stack comprising its operational environment. There is no room for silos when it comes to security.<\/span><\/span><\/p>\n The focus of IT as its moving through its digital transformation should be to modernise ops – from the technology to the teams that use it to innovate and deliver value to the business. Modern ops are not consumed by concern for titles, they are passionate about producing results. Modern ops work together, communicate freely, and collaborate across concerns to build out an efficient, adaptive delivery and deployment pipeline.<\/span><\/span><\/p>\n That will take network, security, infrastructure, storage, and development expertise working together.<\/span><\/span><\/p>\n In the network, we use labels to tag traffic and apply policies that control what devices can talk to which infrastructure and applications. In container clusters we use labels to isolate and restrict, to constrain and to disallow.<\/span><\/span><\/p>\n Labels in organisations can have the same affect.<\/span><\/span><\/p>\n So maybe it would be better if we just said you are either modern ops or traditional ops. And that some are in a transitional state between the two. Let's stop spending so many cycles on what to call each other that we miss the opportunity to create a collaborative environment in which to deliver and deploy apps faster, more frequently, and most of all, securely.<\/span><\/span><\/p>\n It started with DevOps. Then there was NetOps. Now SecOps. Or is it DevSecOps? Or maybe SecDevOps?<\/span><\/span><\/p>\n Whatever you decide to call it, too often the end result is little more than the same old siloes with shiny new names. We’ve become so focused on “what do we call these folks” that we sometimes forget “what is it we’re trying to accomplish”.<\/span><\/span><\/p>\n Shakespeare said that a rose would smell as sweet by any other name. Let’s apply that today to the number of factions rising in the operations game. Changing your name does nothing if you don’t change your core behaviours and practices.<\/span><\/span><\/p>\n Back when cloud first rose – pun intended – there were plenty of pundits who dismissed enterprise efforts to build private (on-premises) cloud. Because it didn’t fit the precise definition they wanted to associate with cloud. They ignored that the outcome <\/em>was the measure of success, not measuring up to someone else’s pedantic definition. They sought agility and efficiency and speed by changing the way infrastructure was provisioned, configured, and managed. They changed behaviours <\/em>and practices <\/em>through the use of technology.<\/span><\/span><\/p>\n Today the terminology wars are focused on X-Ops and what we should call the latest arrival, security.<\/span><\/span><\/p>\n I know I’ve used the terms, and sometimes I use them all at the same time. But perhaps what we need is fewer<\/em> distinctions. Perhaps I should just say you’re either adopting “modern ops” in terms of behaviours and practices or you’re remaining “traditional ops” and that’s all there is to it.<\/span><\/span><\/p>\n Modern ops employ technology like cloud and automation to build pipelines that codify processes to speed delivery and deployment of applications.<\/span><\/span><\/p>\n And they do it by changing behaviours and practices. They are collaborative and communicative. They use technology to modernise and optimise decades old processes that are impeding delivery and deployment. They work together, not in siloed X-Ops teams, to achieve their goal of faster, more frequent releases that deliver value to the business and delight consumers.<\/span><\/span><\/p>\n Focusing on what to call “security” as they get onboard with modern ops can be detrimental to the basic premise that delivery and deployment can only succeed at speed with a collaborative approach. Slapping new labels on a new focused team just builds differenter siloes; it doesn’t smash them and open up the lines of communication that are required to operate at speed and scale.<\/span><\/span><\/p>\n It also unintentionally gives permission to other, non-security ops to abdicate security responsibilities to the <SecDevOps | DevSecOps> team. Because it’s in their name, right?<\/span><\/span><\/p>\n That’s an increasingly bad idea given that application security is a stack and thus requires a full stack to implement the right protections. You need network security and transport security and you definitely need application security. The attack surface for an app includes all seven layers and, increasingly, the stack comprising its operational environment. There is no room for silos when it comes to security.<\/span><\/span><\/p>\n The focus of IT as its moving through its digital transformation should be to modernise ops – from the technology to the teams that use it to innovate and deliver value to the business. Modern ops are not consumed by concern for titles, they are passionate about producing results. Modern ops work together, communicate freely, and collaborate across concerns to build out an efficient, adaptive delivery and deployment pipeline.<\/span><\/span><\/p>\n That will take network, security, infrastructure, storage, and development expertise working together.<\/span><\/span><\/p>\n In the network, we use labels to tag traffic and apply policies that control what devices can talk to which infrastructure and applications. In container clusters we use labels to isolate and restrict, to constrain and to disallow.<\/span><\/span><\/p>\n Labels in organisations can have the same affect.<\/span><\/span><\/p>\n So maybe it would be better if we just said you are either modern ops or traditional ops. And that some are in a transitional state between the two. Let’s stop spending so many cycles on what to call each other that we miss the opportunity to create a collaborative environment in which to deliver and deploy apps faster, more frequently, and most of all, securely.<\/span><\/span><\/p>\n![\"https:\/\/www.cybersecuritycloudexpo.com\/wp-content\/uploads\/2018\/09\/cyber-security-world-series-1.png\"](\"https:\/\/www.cybersecuritycloudexpo.com\/wp-content\/uploads\/2018\/09\/cyber-security-world-series-1.png\")
<\/span><\/a>Interested in hearing industry leaders discuss subjects like this and sharing their experiences and use-cases<\/strong>? Attend the Cyber Security & Cloud Expo World Series<\/a> with upcoming events in Silicon Valley, London and Amsterdam to learn more.<\/p>\n","protected":false},"excerpt":{"rendered":"<\/p>\n<\/span><\/a>Interested in hearing industry leaders discuss subjects like this and sharing their experiences and use-cases<\/strong>? Attend the Cyber Security & Cloud Expo World Series<\/a> with upcoming events in Silicon Valley, London and Amsterdam to learn more.<\/p>\n","protected":false},"author":550,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-39783","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/39783","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/users\/550"}],"replies":[{"embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/comments?post=39783"}],"version-history":[{"count":2,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/39783\/revisions"}],"predecessor-version":[{"id":40035,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/39783\/revisions\/40035"}],"wp:attachment":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/media?parent=39783"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/categories?post=39783"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/tags?post=39783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}