by Gregor Petri | May 30, 2016 | Comments Off on Tune into the Cloud: Total Madness
It took some time but the need for Total Security Management is slowly starting to sink in. With regard to quality it took the western manufacturing industry several decades before it realized that a separate quality department – standing at the end of the production line to check which products did not meet the mandated specs – was a costly and disastrous path to take. And slowly but surely we are seeing similar thinking with regard to cyber and cloud security emerge.
Not that we are taking cloud executives on today’s equivalent of a Japanese factory tour. A quality tour let managers firsthand experience it was everyone’s responsibility to ensure quality and that everyone had the right (and the moral obligation) to personally halt the line when something went wrong. But that may be more because we are not sure yet where the contemporary equivalent of such a tour would need to take our executives. Would it be visiting the hyperscale datacenters of a Google or an Amazon (assuming our executives could get in). Or maybe a visit to the offices of various security start-ups in Silicon Valley and Israel? Or are the cyber control rooms of major telco’s and big accounting firms a better wake up environment? The more courageous may even contemplate a trip to China, Russia or other emerging cyber hotspots, to encounter some of these modern threats in the wild?
I’m not a security expert but to me the similarities between total quality and total security management are very striking. The mantra “Zero Defects” can be easily exchanged for the just as catchy sounding “Zero Breaches” and “Design for Security” is today’s equivalent of “Design for Manufacturing”. With regard to quality it were guru’s like Demming that led the path from expensive and ad hoc quality control at the end of the production line to continuous and iterative quality processes incorporated and embedded into the design and the process.
In the area of security the Jericho Forum already in 2004 pointed out the dangers of merely focusing on perimeter security. In 2013 this forum even deemed itself no longer necessary, in their own words “on the basis of proven success”. Nevertheless it is often still scary what malicious things one can do once inside the firewall of many a company or organization. After complete de-perimeterisation you basically would not need a VPN to reach your applications and be protected from outsiders. Each application would protect itself and decide for each user what he is allowed to do or not do. But with the exception of maybe (web-)email and some SaaS applications, most companies have not come close to setting up the majority of their business applications in a way that they can protect themselves and are no longer dependent on a company perimeter defense.
The advent of micro-services is a good time to re-examine your current security policies. Not only because the security challenges around micro services will typically increase rather than decrease, but also because with the advent of the Internet of Things, security at the source is increasingly mandated and required. Ideally each micro-service will determine itself who does or does not get access to its services and should be able to adequately fence of access attempts by malicious external forces. Also because adding this type of security as an afterthought, on the outside of the service itself, is likely to be cost prohibitive, as many of these external security solutions are at least as pricy as maintaining after the fact quality control , like we did in the days that quality was still a cost instead of a benefit.
With regard to cost, total quality thinking does to reason in terms of an “optimal” rates of defects. A fictional point after which any further reduction of defects will cost more than is economically justifiable. In the end it is namely always cheaper to get things right the first time around, rather than having to return 5%, 0.5% or even 0:05% for repair. Or worse, having to compensate x% of customers for consequential damages (which can easily outweigh the cost of any production improvement). As a result the manufacturing industry no longer measures its defects in percentages but in the initially hard to imagine measure of PPM a.k.a. parts per million. And that iucreasingly in single digits, with a maximum of 1-9 parts per million produced products showing any defect
Now granted, security can be a little bit like health. No matter how healthy you live, you can be unlucky – statistically unexpected but nonetheless very devastating – and get seriously ill. Hence, security is increasingly extending on the one hand from preventive measures to keep out the bad guys, to ongoing monitoring of the current state for anomalies (similar to the active search for signs of a disease in a so-called health pre-scan) and on the other hand by taking measures to reduce the impact of any breaches by counter by beeing able to act appropriately and quickly when something does go wrong. And also for the latter it is necessary that the entire organization is involved with security, it can no longer be delegated to the department at the end of the hall.
Total Madness is the compilation album of the very British Ska revival band Madness. The song “Our House” is about a family that initially is kind of living apart together but that eventually come close together. The song achieved a global cult status in the Netherlands as theme song to the TV hit series “Divorce”.
Read Complimentary Relevant Research
Cloud Computing Primer for 2018
Cloud is evolving from a market disruptor to an expected approach for traditional and next-generation IT. Our research offers actionable...
View Relevant Webinars
Key Market Dynamics in Application Infrastructure and Middleware
We discuss the most-significant supply- and demand-side trends affecting current and upcoming dynamics in the application infrastructure...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.