Introduction to Risk management

 This is a part of chapter "Security" of my forthcoming book "Infrastructure Architecture". Please feel free to comment using my email address stated in the right column of this website. 

Managing security is all about risk management and analysis. If there are no risks to handle, we don't need any security measures. The amount of effort we put in securing our infrastructure should therefore be directly related to the risk we face. Risk management is the process of determining an acceptable level of risk, assessing the current level of risk, taking steps to reduce risk to the acceptable level, and maintaining that level.

Before getting into details, it is good to explain some terminology most used in risk management.  

    • An asset is an infrastructure component that must be protected.
    • A vulnerability is any weakness, process or physical exposure that makes an infrastructure component susceptible to exploit by a threat.
    • A threat is a potential event that causes an unwanted impact to an infrastructure component by exploiting a vulnerability.
  • Risk is the combination of the probability of a threat and its consequence.
  • An exploit is actually using a vulnerability to attack an asset.
  • A safeguard is the control or countermeasure employed to reduce risk.

Or in a more popular way:  

  • Asset: that is your daughter
  • Vulnerability: She is 13 years old and goes to school with her friends who have a big influence on her
  • Threat: She gets addicted to smoking
  • Risk: There is a high chance of her taking a cigarette and start smoking
  • Exploit: Her friends offering her a cigarette
  • Safeguard: Explain her about the risk of smoking cigarettes

To quantify risks first a risk list is compiled. This can best be done in a workshop with all relevant stakeholders of one or more assets. A risk list contains the following parts.  

  • Asset name
  • Threat and/or vulnerability
  • Exploit
  • Probability: an estimation of the likelihood of the occurrence of an exploit of the vulnerability (how often we estimate this will happen)
    • 5: Frequent
    • 4: Likely
    • 3: Occasional
    • 2: Seldom
    • 1: Unlikely
  • Impact: the severity of the damage when the vulnerability is exploited:
    • 4: Catastrophic: Complete mission failure, death
    • 3: Critical: Major mission degradation, major system damage, exposure of sensitive data, or affecting all staff
    • 2: Moderate: Minor mission degradation, minor system damage, exposure of data, or affecting staff of one department
    • 1: Negligible: Some mission degradation, affecting less than 10 people
  • The quantified risk (= Likelihood x Severity)

A typical risk list would look like this:

Asset

Threat/vulnerability

Exploit

Proba-bility

Impact

Quan- tified Risk

Laptop

Laptop gets stolen

Sensitive data on hard disk is readable

5

3

15

Printer

Printer hard disk contains sensitive data

Repair man could swap hard disk and the hard disk could get on the market with our sensitive data

1

3

3

Work- stations

Virus attack unknown to virus scanner

Unavailability or disclosure of data

2

3

6

SAN

Data protection via LUN masking contains error

Data could get exposed to wrong server

1

3

3


This entry was posted on Friday 21 January 2011

Earlier articles

Infrastructure as code

My Book

DevOps for infrastructure

Infrastructure as a Service (IaaS)

(Hyper) Converged Infrastructure

Object storage

Software Defined Networking (SDN) and Network Function Virtualization (NFV)

Software Defined Storage (SDS)

What's the point of using Docker containers?

Identity and Access Management

Using user profiles to determine infrastructure load

Public wireless networks

Supercomputer architecture

Desktop virtualization

Stakeholder management

x86 platform architecture

Midrange systems architecture

Mainframe Architecture

Software Defined Data Center - SDDC

The Virtualization Model

What are concurrent users?

Performance and availability monitoring in levels

UX/UI has no business rules

Technical debt: a time related issue

Solution shaping workshops

Architecture life cycle

Project managers and architects

Using ArchiMate for describing infrastructures

Kruchten’s 4+1 views for solution architecture

The SEI stack of solution architecture frameworks

TOGAF and infrastructure architecture

The Zachman framework

An introduction to architecture frameworks

How to handle a Distributed Denial of Service (DDoS) attack

Architecture Principles

Views and viewpoints explained

Stakeholders and their concerns

Skills of a solution architect architect

Solution architects versus enterprise architects

Definition of IT Architecture

What is Big Data?

How to make your IT "Greener"

What is Cloud computing and IaaS?

Purchasing of IT infrastructure technologies and services

IDS/IPS systems

IP Protocol (IPv4) classes and subnets

Infrastructure Architecture - Course materials

Introduction to Bring Your Own Device (BYOD)

IT Infrastructure Architecture model

Fire prevention in the datacenter

Where to build your datacenter

Availability - Fall-back, hot site, warm site

Reliabilty of infrastructure components

Human factors in availability of systems

Business Continuity Management (BCM) and Disaster Recovery Plan (DRP)

Performance - Design for use

Performance concepts - Load balancing

Performance concepts - Scaling

Performance concept - Caching

Perceived performance

Ethical hacking

The first computers

Open group ITAC /Open CA Certification

Sjaak Laan


Recommended links

Ruth Malan
Gaudi site
Esther Barthel's site on virtualization
Eltjo Poort's site on architecture


Feeds

 
XML: RSS Feed 
XML: Atom Feed 


Disclaimer

The postings on this site are my opinions and do not necessarily represent CGI’s strategies, views or opinions.

 

Copyright Sjaak Laan