III - Techniques: Methodology For Information Systems Risk Analysis and Management
III - Techniques: Methodology For Information Systems Risk Analysis and Management
ADMINISTRACIONES
PÚBLICAS
MAGERIT – version 2
Methodology for Information Systems Risk
Analysis and Management
III – Techniques
Director:
Francisco López Crespo
Ministerio de Administraciones Públicas
Javier Candau
Centro Criptológico Nacional
External consultant:
José Antonio Mañas
Professor
Universidad Politécnica de Madrid
Magerit version 2 Introduction
Index
1. Introduction....................................................................................................................4
2. Specific techniques .......................................................................................................5
2.1. Analysis using tables..............................................................................................................6
2.1.1. References .....................................................................................................................7
2.2. Algorithmic analysis................................................................................................................8
2.2.1. A qualitative model .........................................................................................................8
2.2.2. A quantitative model .....................................................................................................12
2.2.3. A model using steps .....................................................................................................17
2.2.4. On the efficiency of safeguards ....................................................................................20
2.3. Attack trees ..........................................................................................................................22
References .............................................................................................................................22
3. Generic techniques......................................................................................................23
3.1. Cost-benefit analysis ............................................................................................................24
References .............................................................................................................................24
3.2. Data flow diagrams (DFD)....................................................................................................25
References .............................................................................................................................25
3.3. Process diagrams.................................................................................................................26
References .............................................................................................................................26
3.4. Graph techniques .................................................................................................................27
3.5. Project planning....................................................................................................................28
References .............................................................................................................................28
3.6. Working sessions .................................................................................................................29
3.6.1. Interviews......................................................................................................................29
3.6.2. Meetings .......................................................................................................................29
3.6.3. Presentations................................................................................................................29
References .............................................................................................................................29
3.7. The Delphi method ...............................................................................................................30
References .............................................................................................................................30
1. Introduction
This book of techniques completes the guide to the Magerit methodology. It assumes that the con-
cepts of risk analysis and management, as explained in the methodology guide, are already known
and understood.
The aim is to describe techniques to be used in risk analysis and management projects 1. Tech-
niques are considered to be a set of heuristics and procedures supported by standards. It is im-
plied that they use one, or several, specific notations for syntax and semantics and apply criteria of
excellence when applied. Practices are procedures to achieve specific objectives rapidly, securely
and precisely, with minimal room for the unexpected.
For each of the techniques and practices referred to below:
• there is a brief explanation of the aimed objective,
• the basic associated elements are described,
• the basic principles, on which the technique is based, are described,
• a text and/or graphic notation is presented, and
• bibliography sources deemed of interest to readers who wish to study each subject further
are provided, although the list is can never be complete.
All the techniques in this book can be used without automated aids; however, for repeated or com-
plex use, it is recommended to use tools as widely and frequently as possible.
It is important to point out that the notation proposed for applying the technique is in no case com-
pulsory. Each organization may adapt to the available tools or sector specific notations.
1 Several of the techniques referred to have been incorporated from Métrica version 3.
2. Specific techniques
This chapter focuses on very specific techniques for risk analysis and management projects.
These are techniques that are not used in other work contexts.
The following are thought to be of special interest:
1. the use of tables to derive simple results
2. algorithmic techniques to derive complex results
3. attack trees to complement the reasoning behind which threats could attack an information
system
and are dealt with in the sections below.
Impact estimation
Impact can be calculated from simple, double-entry tables:
degradation
impact
1% 10% 100%
VH M H VH
H L M H
value M VL L M
L VL VL L
VL VL VL VL
Any assets that are graded as very high impact (VH) should receive immediate attention.
Risk estimation
The frequency is also modelled from a simple scale:
VF: very frequent (daily)
F: frequent (monthly)
NF: normal frequency (yearly)
I: infrequent (every few years)
The impact and the frequency can be combined into a table to calculate the risk:
frequency
risk
PF FN F MF
VH H VH VH VH
H M H VH VH
impact M B M H VH
L VL L M H
VL VL VL L M
Any assets that are graded as very high risk (VH) should receive immediate attention. Those
graded as high risk should be subject to immediate safeguard planning.
2.1.1. References
• ISO/IEC 13335-1:2004 – Information technology – Guidelines for the management of IT se-
curity – Part 1: Concepts and models for Information and communications technology secu-
rity management.
Values
A risk analysis needs to be able to assess, relatively at least, the elements involved. Specifically,
the assets, the impact of the threats and the risk run.
A scale of symbolic levels is used throughout:
V = { ..., v0, v1, ..., vi, ... }
this series of levels satisfies the following properties:
2 This negligible level establishes a subjective boundary between what can be appreciated and should give
cause for concern, and what is insignificant and can be disregarded. Values below v0 are disregarded.
3 If the reader wishes, the points on this assessment system can be interpreted as orders of magnitude, for
example vx can be read as 10x.
C
The transitive closure of direct dependencies between assets is of interest.
A ⇒ C ⇔ ∃ B, ( A ⇒ B ) ∧ ( B → C )
A depends (indirectly) on C if and only if
there is an asset B, so that A depends directly or indirectly on B and
B depends directly on C.
The following does not differentiate between direct and indirect dependencies.
The risk
Risk is measured by the scale of values, being a function of the impact and the frequency:
• it grows with the value: ∀ fi, ℜ(vi, fj) < ℜ(vi+1 , fj)
• it grows with the frequency: ∀ vi, ℜ(vi, fj) < ℜ(vi , fj+1)
• ℜ(v0, fn) = v0
A simple function that satisfies these properties is
Safeguard packages
When a threat is in force, a series of safeguards is implemented, a safeguard package, whose effi-
ciency, “e”, is calculated as shown below. For now, it is sufficient to say that efficiency is a real
value between 0.0 (no protection) and 1.0 (fully efficient safeguard), a value that can be broken
down into efficiency against impact, “ei”, and efficiency against frequency “ef”.
for A for B
accumulated value: v5 accumulated value: v5 + v8 = v8
deflected impact: v4 accumulated impact: v7
deflected risk: v3 accumulated risk: v6
residual degradation: 45% residual degradation: 45%
residual impact: v2 residual impact: v3
residual frequency: f1 residual frequency: f1
residual risk: v0 residual risk: v1
Summary
This is the qualitative model, where the assets have been placed on a scale of relative value by
defining an arbitrary value “v0” as drawing the line between values of concern and those that are
negligible.
On this scale of value, measurements are taken both of the basic or accumulated value of the as-
set and the impact of a threat when it occurs and the risk to which it is exposed.
While the impact measures the value of the potential problem, the risk weights this impact with the
estimated frequency at which the threat may occur. The impact is the measure of the cost if the
problem should occur, while the risk measures the exposure during a specific period of time.
Estimations of the impact and residual risk include the efficiency of the safeguards to deal with the
threat, either by limiting the impact, “ei”, or by reducing the frequency, “ef”.
Therefore, the model combines the following analysis parameters:
• rating the value of the asset through a discrete scale
• rating the degradation posed by a threat as a percentage
• rating the frequency at which a threat occurs through a discrete scale
• the integration of a package of safeguards
• rating the efficiency of the safeguards through a percentage
All these parameters allow for upward or downward movement on the scale of values.
A ⇒ C ⇔ ∃ B, ( A ⇒ B ) ∧ ( B → C )
A depends (indirectly) on C if, and only if, there exists an asset B so that A depends di-
rectly or indirectly on B, and B depends directly on C.
By calculating the degree of dependency as:
50%
5 This addition satisfies the commutative, associative properties and the existence of a neutral element, in
addition to containing the result within the range [0..1] if the addends are within this range.
The choice of this peculiar formula, taken from the Bayes calculation of probability, arises from the need
to reflect the fact that, if an asset depends on another through various routes (diamond structures), the to-
tal dependency cannot exceed 100%.
When the impact is reduced to “v0”, or less, the impact is said to be negligible.
When the impact is reduced to “v0”, or less, the impact is said to be negligible.
The risk
The risk is calculated as
risk = impact × frequency
This is a real value, higher than zero.
A threshold “r0“ is set below which the risk is “negligible”, that is:
r0 = v0
Safeguard packages
When faced with a threat, a series of safeguards, the safeguard package, is deployed, whose effi-
ciency, “e”, is calculated as shown below. For now, it is sufficient to say that the efficiency is a real
value between 0.0 (no protection) and 1.9 (safeguard fully effective), a value that can be broken
down into efficiency against impact, “ei”, and efficiency against frequency “ef”, so that
(1 – ei ) × (1 – ef ) = 1 – e 6
Example
Supposing there is an asset valued at 1,000,000, which has fallen prey to a threat that has de-
graded it by 90%. The impact is of the amount
1,000,000 x 90% = 900,000
If the safeguards are 90% efficient on the impact, the residual impact is
900,000 x (1 – 0.9) = 90,000
The accumulated impact is calculated from the data of the accumulated impact on an asset and
the proper safeguards against threats on the asset.
The deflected impact is calculated from the data of the deflected impact on the higher value asset
6 The chosen formula has the following properties. If ei= 0% and ef= 0%, e= 0%. If ei= 0%, e= ef. If ef= 0%,
e= ei. If ei or ef= 100%, e= 100%. Therefore, the results increase with the components ei and ef, while at
the same time remaining within the range [0%..100%].
Summary
This is the quantitative model and functions with real values that are always higher than zero.
The degree of dependency between assets is modelled as a continuum between 0.0 (independent
assets) and 1.0 (fully dependent assets; any incident on the lower one has a severe effect on the
higher one).
The value of the asset, basic or accumulated, is measured, as well as the impact of the threat
whenever it occurs and the risk involved.
While the impact measures the value of the potential problem, the risk weights the impact with the
estimated frequency at which the threats will occur. The impact measures the cost, should the
threat occur, while the risk is the measure of exposure over a period of time.
If the asset is valued in economic terms (the monetary cost entailed by its complete loss), the cal-
culated impact is the cost deriving from the threat, and the calculated risk is the amount which has
to be planned for as annual losses. Therefore, the quantitative model allows a comparison be-
tween the cost of safeguards and the reduction of losses.
The estimations of impact and residual risk incorporate the efficiency of the safeguards when deal-
ing with a threat.
If the valuation of the asset is economic, the quantitative model allows a comparison between the
cost of the safeguards and the reduction in losses.
Therefore, the model combines the following analysis parameters:
© Ministerio de Administraciones Públicas page 16 (of 30)
Magerit version 2 Algorithmic analysis
• rating of the value of the asset through a numerical quantity
• rating of the dependency between assets through a percentage
• rating of the degradation posed by a threat through a percentage
• rating of the frequency at which a threat occurs through a frequency
• the integration of a package of safeguards
• rating of the efficiency of the safeguards through a percentage
All these parameters can be moved up and down the scale of values.
10
6
cost
4
0
15m
30m
1h
2h
6h
1d
2d
1s
S1
2s
1m
2m
6m
1a
total
interuption period
where cost of interruption grows up to a maximum limit corresponding to the thorough destruction
of the asset (no remaining value).
The following sections show how to analyse these steps, either qualitatively (discrete scale of val-
ues) or quantitatively (continuous values).
The steps
An ordered series of value steps is determined:
E = { e1, e2, ..., en }
Each step represents an interruption period (see the above diagram).
Accumulated value
This is calculated independently (in parallel) for each step.
This means that an actual value and an accumulated value are calculated for each step.
Example
An administration unit provides a claims service that has traditionally been carried out via mail:
the claimant sends in the claim by letter and is answered within the maximum period of 1 week.
Currently, an alternative, online service has been set up with a reply given in less than 1 hour
(during attendance hours), which is considered excellent. After one hour, the image offered to
the public starts to suffer. If the service takes more than one day, it is considered useless, even
though the seriousness is relative, as there is always the option of claiming by post.
Both services depend on computer equipment holding the data of both services:
7 The reasoning is as follows. If a stop of longer than x1 hours involves damage of v1, and a stop of longer
than x2 hours, damage of v2; then a stop of x hours, being x1 …≤ x < x2, means damage of v1, given
that it has not reached the level of x2.
The efficiency step may be e0, if the safeguard is so effective that it does not allow even the first
step e1.
This efficiency step is the same as the degradation when the safeguard is unable to reduce the
impact 8.
This efficiency step can never be higher than the degradation step, as a safeguard cannot worsen
the situation of an asset under threat.
In addition to the efficiency step, the safeguards applied to the case constitute a package charac-
terised by their efficiency in reducing the impact, ei, and their efficiency in reducing the frequency,
ef. How to calculate these coefficients is described below.
What must be shown, however, is how to calculate the effectiveness step for a package of safe-
guards:
Where the special value “na” 9 behaves as a neutral element in the operations.
Therefore, a set of alternative safeguards must contain at least one that will be effective. In a set of
concurrent safeguards, efficiency is rated by the worst of these.
Residual degradation
If the unprotected asset is positioned on degradation step “ed“, the safeguards will place it on the
step proposed as efficiency step, “es“; but modulated by efficiency “ei” against the impact, resulting
in a residual step “er“:
r = ⎣d − ((d − s) × ei)⎦ 10
Residual impact
This is the value corresponding to the residual step:
residual_impact = value[er]
Example
In the case above, if an antivirus system is deployed that enables service to be resumed in 6
hours, the residual impact on the server and Internet service is [3].
If an antivirus system is deployed that guarantees service to be resumed in 30 minutes, the re-
sidual impact will be [0].
Residual frequency
The qualitative or quantitative model is used, as necessary.
8 A back-up centre that starts up after 48 hours is useless against threats that stop the service for 6 hours.
9 na: not applicable.
10 Notation ⎣ν⎦ stands for the integer floor of the value.
Package of safeguards
When a threat appears, a package of safeguards is deployed which is simply a set of separate
safeguards accumulated over an asset. The various safeguards can be accumulated concurrently
(all are needed to produce the desired effect), or exclusively (only one of the set produces an ef-
fect) or additively (the more, the better).
ps::= safeguard
| all(ps0, ps1, ...)
| some (ps0, ps1, ...)
| one (ps0, ps1, ...)
Where the special value “na” behaves as a neutral element in the operations for calculating the
maximum, product or sum.
As a result, the efficiency of a package of concurrent safeguards is the average of these; the effi-
ciency of a package of additive safeguards is accumulated to a limit of 100%; and in a package of
alternative safeguards, the efficiency is set by the best one.
11 The average value is calculated as usual: efficiencies other than NA are added and divided by the
number of addends.
e(ps) = Σk e(psk) × pk / Σk p k
If all the safeguards should have the same importance, then “p = 1”.
References
• J. Viega et al., “Risk Analysis: Attack Trees and Other Tricks”, Software Development Maga-
zine, August 2002.
• A.P. Moore et al., “Attack Modeling for Information Security and Survivability”, Software En-
gineering Institute, Carnegie Mellon University, Technical Note CMU/SEI-2001-TN-001,
2001.
• B. Schneier, “Secrets and Lies: Digital Security in a Networked World”, John Wiley & Sons,
2000.
• B. Schneier, “Attack Trees: Modeling Security Threats”, Dr. Dobb's Journal, December 1999.
3. Generic techniques
This chapter deals with general techniques that are widely used, but that also apply to some
stages of a risk analysis and management project. It is shown where do they apply, and how. This
section builds on the methodology explanations.
The following techniques are referenced:
1. cost-benefit analysis
2. data flow diagrams (DFD)
3. process diagrams (SADT)
4. graph techniques
5. project planning (PERT)
6. working sessions
7. the Delphi method
References
• R.A. Brealey and S.C. Myers, “Principles of Corporate Finance”, Mcgraw-Hill College; 6th
edition, December 2000.
• A.E. Boardman, “Cost-Benefit Analysis: Concepts and Practice”, Prentice Hall, 2nd Edition,
October 2000.
• H.M. Levin and P.J. McEwan, “Cost-Effectiveness Analysis Methods and Applications”, Sage
Publications, Inc., 2nd edition, September 2000.
• Office of The Deputy Chief Information Officer, “Cost-Benefit Analysis Guide for NIH IT Pro-
jects”, Revised May, 1999.
• Office of Management and Budget, Circular No. A-94 Revised, “Guidelines and Discount
Rates for Benefit-Cost Analysis of Federal Programs”, October 29, 1992.
References
• S.W. Ambler, “The Object Primer. Agile Model Driven Development with UML 2”, Cambridge
University Press, 3rd ed. 2004.
• C.P. Gane and T. Sarson, “Structured Systems Analysis: Tools and Techniques”, Prentice
Hall, 1st ed. 1979.
References
• Clarence G. Feldmann, “The Practical Guide to Business Process Reengineering Using
IDEF0”, Dorset House Publishing Company, 1998.
• Hill, S. and L. Robinson, “A Concise Guide to the IDEF0 Technique”, Enterprise Technology
Concepts, 1995.
• FIPS 183: “Integration Definition for Function Modeling (IDEF0)”. Federal Information Proc-
essing Standards. December, 1993.
• David A. Marca and Clement L. McGowan, “SADT: Structured Analysis and Design Tech-
niques”. McGraw-Hill, New York, NY, 1988.
References
• R. Burke, “Project Management: Planning and Control Techniques”, John Wiley & Sons; 3rd
edition. May 16, 2001.
• J.J. Moder, C.R. Phillips, E.W. Davis, “Project Management With Cpm, Pert & Precedence
Diagramming”, Blitz Publishing Company; 3rd edition. February, 1995.
• K. Lockyer, J. Gordon, “Project Management and Project Network Techniques”, Trans-
Atlantic Publications; 6th edition. December 1, 1995.
• R.D. Archibald, R.L. Yilloria, “Network-based Management Systems”, (Information Science
S.) John Wiley & Sons Inc. March, 1967.
3.6.1. Interviews
This section is only available in Spanish.
3.6.2. Meetings
This section is only available in Spanish.
3.6.3. Presentations
This section is only available in Spanish.
References
• “Managing Information Security Risks: The OCTAVE Approach”, C.J. Alberts and A.J. Doro-
fee, Addison-Wesley Pub Co; 1st edition (July 9, 2002)
http://www.cert.org/octave/
• Magerit, “Metodología de Análisis y Gestión de Riesgos de los Sistemas de Información”,
MAP, versión 1.0, 1997
http://www.csi.map.es/csi/pg5m20.htm
References
• J. Fowles, “Handbook of Futures Research. Westport, Greenwood Press, 1978.
• H.A. Linstone and M. Turoff (eds), “The Delphi Method: Techniques and Applications”, Read-
ing, MA: Addison-Wesley Publishing Company, 1975.
• N.C. Dalkey, “The Delphi Method: An Experimental Study of Group Opinion”, RAND Corpo-
ration, RM-5888-PR, 1969.
• O. Helmer, “Analysis of the Future: The Delphi Method”. RAND Corporation Technical Re-
port, P-3558, March 1967.
• N. Dalkey and O. Helmer, “An Experimental Application of the Delphi Method to the Use of
Experts”. Management Science, vol. 9, no. 3, April 1963.
• M. Girshick, A. Kaplan and A. Skogstad, “The Prediction of Social and Technological
Events”. Public Opinion Quarterly, Spring 1950.