Risk-based sampling using CobiT

By Rune Johannessen and Børre Lagesen

June 2005 Lithuania

IS THIS YOUR DAY?

?PO8PO1

DS11AI6

PO11

AI1

PO1DS5

The purpose of this session!

Presentation

• Rune Johansen– CISA, CIA, Dipl. Int revisor– 9 years experience in IT audits and quality insurance from various ministries with their subordinate agencies, private companies and system development projects.

• Børre Lagesen– CISA– 6 years experience in IT audit from various ministries with their subordinate agencies.

Agenda

1. What is the objective for this workshop?

2. Background

3. Method for Risk-based sampling

4. Case study

5. Experiences from practical use in Norway.

6. Sum up and questions

1. The objective for this workshop.

1. Help the auditor to select the right areas and processes for IT auditing.

2. Contribute to improvement and quality in the performance of the IT risk assessment

3. Contribute to an open discussion and knowledge sharing.

2. Background1. Why CobiT?

2. Why this risk assessment approach?– CobiT is highly comprehensive and its use quite

time consuming. – This in stark contrast to our everyday situation,

where time is a critical factor. – CobiT does not provide clear guidelines on how to

carry out an overall (or “high level”) audit risk assessment.

Method for Risk-based sampling1. The method presented is not intended as a final

template.

2. The presentation is based on qualitative assessments of risks.

3. The method uses the following sources:• Audit Guidelines

• Controll Ojectives

but could also use the maturity model in “Management Guidelines”

Selection based on criterias/processes/resources

Risk assessment of selected processes

IT audit

Phase 1

Phase 2

Phase 3

Method for Risk-based sampling

P1 P2 P3

P1 P2 P3

Results of Phase 1:

The auditor have a list of relevant processes.

In our last example, AI2 and AI6 were identified as the most relevant within the domain “Acquisitions and implementation”.

P1 P2 P3

P1 P2 P3

P1 P2 P3

Don

’t e

xist

Scale Control routines

Doc The audited entity has a documented routine or process that deals with the matter.

Undoc The audited entity does not have a documented routine or documented processes that deal with the matter.

Don’texist

The process does not exist in this organisation. Futher actions and consequences for other types of audits needs to be considered.

P1 P2 P3

Scale Probability

H It is regarded as highly probable that this process will be negatively affected by internal or external events.

M It is regarded as possible that this process will be negatively affected by internal or external events.

L It is not regarded as very probable that this process will be negatively affected by internal or external events

P1 P2 P3

Method for Risk-based samplingScale Consequence

H Negative internal or external incidents are expected to have major consequences.

M Negative internal or external incidents are expected to have medium consequences.

L Negative internal or external incidents are expected to have minor consequences.

P1 P2 P3

Each process is then subject to a risk assessment where probability and consequences are considered together.

On the basis of how the process is rated in terms of risk (H high, M medium, L low – in our example), they are selected for further IT audit (phase 3).

P1 P2 P3

Method for Risk-based samplingIT process and audit

questionsResults of evaluation

and testingRecommendation Ref.

AI6 Change management      

  Has a method been established for prioritisation of change recommendations from users, and if so, is it being used? Have procedures been compiled for sudden changes, and if so, are they being used? Is there a formal procedure for monitoring changes, and if so, is it being used?Etc. 

Observation: Method for changes… There is no procedure for sudden changes … Etc. Assessments: The methodology is incomplete in terms of sudden changes…  Conclusion: The methodology is inadequate …

We recommend …

 

P1 P2 P3

WORK!!!!

1. Identify relevant questions for chosen processes (PO9, DS4, DS5) based on your points in “and takes into consideration”. (from 14.05 to 14.30 – 25 minutes)

2. Use the questions on the case study. Evaluate risk and conclude on further audit. (from 14.30 to 15.30 – 60 minutes including break. )

3. Discussions (from 15.30 to 16.15 – 45 minutes)

5. Practical use and experiences from Norway

Selection based on targets/processes/resources

Risk assessment of selected processes

IT audit

Phase 1

Phase 2

Phase 3

Method for Risk-based sampling

Selection of processes P1 P2 P3

The risk assessment of processesP3P1 P2

Result of risk assessment in four

different government agencies

P1 P2 P3

Short about developing our IT audit program

 

P1 P3P2

Audit programAudit guidelines

Control objektive

Result of auditP1 P3P2

Agency 1 Agency 2 Agency 3 Agency 4

PO9

Findings reported to

ministry

Findings reported to parlament

Findings reported to parlament

Findings reported to

ministry

DS4

Findings reported to parlament

Findings reported to parlament

Findings reported to parlament

Findings reported to

ministry

DS11

Findings reported to parlament

Findings reported to

agency

Findings reported to

agency

Nothing reported

Government agencies

Experience

Pros

• able to develop a good risk profile

• able to select the right process to audit

• reuse of questionnaire and risk profile

Cons

• it took time to develop the questions

• takes time to perform such a comprehensive risk assessment.

You can’t hide – we see it all