290 likes | 306 Views
This presentation discusses a risk-based sampling method using CobiT for IT auditing. It provides an overview of the methodology and shares practical experiences from Norway. The objective is to help auditors select the right areas and processes for IT auditing and contribute to improvement and quality in IT risk assessment.
E N D
Risk-based sampling using CobiT By Rune Johannessen and Børre Lagesen June 2005 Lithuania
IS THIS YOUR DAY? AI1 ? DS5 PO1 PO8 PO1 AI6 DS11 PO11
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 What is the objective for this workshop? Background Method for Risk-based sampling Case study Experiences from practical use in Norway. Sum up and questions
1. The objective for this workshop. Help the auditor to select the right areas and processes for IT auditing. Contribute to improvement and quality in the performance of the IT risk assessment Contribute to an open discussion and knowledge sharing.
2. Background Why CobiT? 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 sampling The method presented is not intended as a final template. The presentation is based on qualitative assessments of risks. The method uses the following sources: Audit Guidelines Controll Ojectives but could also use the maturity model in “Management Guidelines”
Method for Risk-based sampling Selection based on criterias/processes/resources Phase 1 Phase 2 Risk assessment of selected processes Phase 3 IT audit
P1 P2 P3
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 Don’t exist
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’t exist 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
Scale 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 Method for Risk-based sampling
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).
IT process and audit questions Results of evaluation and testing Recommendation Ref. P1 P2 P3 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 … Method for Risk-based sampling
WORK!!!! • 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) • Use the questions on the case study. Evaluate risk and conclude on further audit. (from 14.30 to 15.30 – 60 minutes including break. ) • Discussions (from 15.30 to 16.15 – 45 minutes)
Method for Risk-based sampling Selection based on targets/processes/resources Phase 1 Phase 2 Risk assessment of selected processes Phase 3 IT audit
P1 P2 P3 Selection of processes
P1 P2 P3 The risk assessment of processes
P1 P2 P3 Result of risk assessment in four different government agencies
P1 P2 P3 Short about developing our IT audit program Control objektive Audit program Audit guidelines
P1 P2 P3 Result of audit
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.