I’ve written before about the importance of assuming things will go wrong – that it’s not a matter of if, but strictly a matter of when. In my role, a large part of my focus is working with teams across Microsoft to identify the types of things that can go wrong in the complex ecosystem that makes up the cloud (everything from infrastructure to networks, to software – even administrator error), and build resilience into our services to ensure the impact – when things do go wrong – is minimized.
But if an organization truly wants to be resilient, there are many other facets of risk they should consider.
This month Asia Futures magazine has published an article on organizational resilience, in which Pierre Noel, chief security officer and advisor, Microsoft Asia, shares his thoughts on the topic. In the article, he looks at what it takes for an organization to be resilient, how to effectively plan for and mitigate disaster, and some of the specific challenges and opportunities on the theme of resilience.
As Noel says, “Being resilient refers to an organization’s capability to efficiently respond to an incident and minimize any adverse impact to the organization, as opposed to putting up and building a fence around the organization hoping that threats won’t get through.”
I found the article interesting and encourage you to read it and share your thoughts on resilience and risk via comments below. This article is one of several in a series dedicated to resiliency, so you can check back each week with Asia Futures magazine to read the latest.