Managing the risk of tightly coupled networks
Monday, June 16th, 2008In Financial Services we are all familiar with the idea that the financial system is so interdependent that the failure of a relatively small firm has the potential to cause larger failures and, possibly, complete meltdown of the system. There is a general principle at work here, that of tightly coupled networks. Basically, this says that if a network is highly efficient, redundancy has been removed and therefore an apparently insignificant failure in one location can lead to a total failure. One of the classic cases of this was the electricity blackouts experienced in North America in 2003, as a result of the failure of apparently unimportant nodes in the grid.
This same concept can be applied to business processes within a global financial enterprise. As financial services organisations become more highly organised and (hopefully) more efficient, redundancy is removed. The question is, where should redundancy be retained, and how do we identify when lack of it might become a threat? Risk managers identify individual risks in business processes across the organisation and put controls in place to mitigate them. The difficulty is that risks are usually managed in silos across the organisation, so the correlation between, say, credit risk and liquidity risk may not be known and won’t therefore be controlled. Even within a silo, there is rarely much attention given to the inter-relatedness of risks. And correlation also applies to controls; if a control fails or is not run this may have an impact not just on the related risk(s) but on other controls as well. There can be several consequences of this, all of them undesirable: in the best case scenario, the impact and likelihood of risks may be underestimated and the ability of controls to mitigate those risks may be overestimated, in the worst case risks are not recognised at all and are therefore completely uncontrolled.
I have blogged before about the EU’s MUSING project and one of the key benefits that MUSING aims to deliver is in this area of correlation. How does this work? Firstly, MUSING uses ontologies to describe the risk management domain. The use of ontologies has the advantage over simple Object Oriented domain modelling in that it has a logical inference capability that allows us to model not just the relationships between elements (e.g. risks and controls) but the rationale behind those relationships. Once we have that information, we can start to assign quantitative information to those relationships and, here, bayesian networks can help us not just to understand and measure the impact of correlation but to model it on an ongoing basis. By combining this technology with an enterprise-wide view of risk and its mitigation, financial services organisations can start to understand the impact of tightly coupled networks in their business processes and ensure that it is managed.
Mike MacDonagh