Following the first part of the return on the 3rd CTO Cybersecurity Forum (which is reachable here) in the afternoon of Thursday, April 25, there were two tracks of choice and ours was to participate in the workshop on the Critical Information Infrastructure Protection (CIIP) led by David POLLINGTON from Microsoft Security in partnership with FIRST (Forum for Incident Response and Security Teams).
From the outset, the master session insisted that while it is Microsoft, during the workshop there will be no sale of any product of the firm’s employment, but rather to share State of the art and best practices for CIIP and what is being done at Microsoft to get there.
The workshop was divided into two parts:
- Critical Infrastructure Protection: Concept and Continuum: on the definition and contours of the Critical Infrastructure (CI) concept.
- A Framework for Critical Information Infrastructure Risk Management, which offered us a set of process dedicated to the identification and management of risks in our CIIs (Critical Information Infrastructures).
For this purpose, two books were given to us, each focusing on a part of the workshop.
Speaking about CIIP, we should already be able to differentiate what is Critique and what isn’t. The criticality notion is variable from one state to another, there are no fixed patterns on it. However, some areas are included in several Critical Infrastructures models / catalogs in the example of Energy, Finance, Water, Transport, Food, Public Safety, … The following figure shows an overview of the areas considered critical in some countries.
Nowadays, with almost all automated and interconnected systems, our critical or not infrastructures depends more and more on IT. However, when it comes to CIIP, it is not only a protection against threat which IT is the vector, including cyber attacks, but all types of factors that undermine our infrastructures which that either the original example of Terrorist Attacks, Natural Disasters, Wars, and many other kind of chaotic situations.
Critical Infrastructures Protection is intimately linked to four key points to be implemented :
- Trustworthy Policies and Plans
This trustworthy need to meet the following three criteria : Build and reinforce strong cooperative partnerships among stakeholders, be Adaptable and Scalable, responding to ongoing changes in threat profiles and Contains Milestones and metrics that track the progress of a Critical Infrastructures Protection Program.
Resilience in this case is the ability to be able to anticipate or protect against the risk/significant attacks and to minimize the duration and impact of the incident suffered. Critical Infrastructure Resilience allows not only to protect for the potential risks, but also and especially to be able to optimally manage to return to normal as soon as possible. This can not be done without regulars exercises to test incident response capabilities and it involves governments, vendors and enterprises working together to appropriately assess, mitigate and recover from attacks.
CIP must be constantly aware of latest sophisticated threats. Due to that, People, processes and technology must be considered when defining CIP practices, programs, education/training and Reaseach and Development.
- Trusted Collaboration and Information Sharing
The first three criteria mentioned above, put together thanks to a good collaboration and information sharing among different stakeholders enable partners said.
The figure below shows the structure exploded of four key steps listed above and their subsets
Following these strategic axes for the Critical Infrastructure Protection (CIP) Microsoft has established a framework for comprehensive management of risk associated with these assets. This framework is divided into five consecutive steps defined as follows :
1. Determine Risk Management scope
This phase will determine the appropriate well as the objectives and activities for the risk management scope. It will be done into three consecutive steps :
– Reaching stakeholder consensus on statement of mission and vision, it in determining what should be protected and why.
– State the specific security and resiliency goals, objectives and assurances
– Identify essential services
2. Identify Critical Information Infrastructures functions
Determining the Critical Information Infrastructure functions is the second stage of the CII Risk Management plan. This refers to the stakeholders to have an open debate on the criticality of assets and together define which Information Infrastructure elements, critical functions and key resources are necessary to deliver vital government services, economy, and to ensure public safety.
3. Analyze Critical Function Value Chain and Interdependencies
Services, processes and core functions are not partitioned entities, but rather composed of several closely related sub-components that jointly enable an end objective, understanding the complexity and interdependence between value chain is not just used to analyze threats, vulnerabilities and consequences, but more importantly, identifies stakeholders and strategic suppliers of value chains involved. As an example, the figure below shows an overview of what this step can bring:
4. Assess Critical Function Risk
This step focuses specifically on threats and vulnerabilities of critical functions. In terms of CII, the risk is function of threat, vulnerability and their consequences. This results in the equation:
Risk = ƒ(Threat, Vulnerability, Consequence)
In this equation:
– Threat refers to any natural or Human factor
– Vulnerability here means a weakness or failure which can be exploited by a threat
– Consequence also called « Impact » refers to costs, losses or results from the successful exploitation of a vulnerability by a threat.
5. Prioritize and Treat Critical Function risk
Prioritize and deal with a continual and ongoing risks to critical functions of our infrastructures leads to four possibilities:
– Risk Mitigation, Mitigating the impact/effect of risk
– Risk Prevention
– Risk Transfer (in the case of insurance, for example)
– Risk Acceptance/Retention, whose means to accept the probability and impact of a particular risk.
At the end the trainer noted in caption that CII Risk Management is not a static state, but a Continuous Process lead by the culture of ongoing risk management activity throughout each phase of the CIP Continuum. It is on this score that ended this very informative workshop on Critical Information Infrastructures Protection.
After this, we will like to know: How many African Countries have already setup this types of Critical Information Infrastructures Risk Management Process? much more how many of them have only finish with the first step of this framework? What about Cameroon, are we aware about this? too much work need to be done, but it’s not too late!
1- Microsoft Trustworthy Computing : Critical Infrastructure Protection : Concepts and Continuum – Global Security Strategy and Diplomacy
2- Microsoft Trustworthy Computing : A Framework for Critical Information Infrastructure Risk Management – Global Security Strategy and Diplomacy