COBIT Control Objectives for IT Related Technology

Arrianto Mukti Wibowo, M.Sc., CISA IT Governance Lab Faculty of Computer Science University of Indonesia

History
Ditrigger oleh Committee of Sponsoring Organization (COSO) of Treadway Committee mengenai Internal Controls An Integrated Framework, tahun 1980an yang belum memiliki panduan mengenai TI. Padahal laporan keuangan banyak dibuat oleh TI. Bermula dari EDP Auditor Association (sekarang bernama ISACA), cabang Eropa, yang membuat panduan control objectives. Dipelopori oleh Erik Guldentops, executive professor dari University of Antwerpen Management School, yang memulai inisiatif COBIT tahun 1994. Sekarang dikelola oleh COBIT Steering Committee dari IT Governance Institute (underbow ISACA)

Introduction
Its mission is to research, develop, publicize and promote an authoritative, up-to-date, international set of generally accepted information technology control objectives for day-to-day use by business managers and auditors. Managers, auditors, and users benefit from the development of COBIT because it helps them understand their IT systems and decide the level of security and control that is necessary to protect their companies assets through the development of an IT governance model.
Business managers: IT dashboard IT management: to communicate performance or to direct subordinates IT staff: to build capability to perform daily duty to meet business expecations.
3

Framework IT Governance

COBIT focuses primarily on what is required rather than how to undertake the activities themselves.
4

Sifat COBIT
Lebih condong pada business requirements for IT Tidak memfokuskan diri pada praktek-praktek teknis Oleh karena itu, sangat menarik bagi orang-orang bisnis yang non-teknis. Tapi kurang menarik bagi orang teknis yang perlunya detailed day by day how-to.

COBIT content diagram

Interrelaitonship of COBIT Components

Pendekatan Dari COBIT

By being: Business Focused Process Oriented Control Based Measurement Driven

COBIT as a business focused tool

Basic COBIT principles

10

Defining IT Goals and Enterprise Architecture for IT

(baca penjelasan pada slide berikut)

11

Defining IT Goals and Enterprise Architecture for IT

If IT is to successfully deliver services to support the enterprises strategy, there should be:
a clear ownership and direction of the requirements by the business (the customer) and a clear understanding of what needs to be delivered, and how to do it, by IT (the provider).

Previous slide illustrates how the enterprise strategy should be translated by the business into objectives related to ITenabled initiatives (the business goals for IT). These objectives should lead to:
a clear definition of ITs own objectives (the IT goals), which in turn define the IT resources and capabilities (the enterprise architecture for IT) required to successfully execute ITs part of the enterprises strategy.
12

Linking Business Goal to IT Goal Pada Appendix I, COBIT 4.1

13

14

Managing IT Resource to deliver IT Goals

15

COBIT as a Process Oriented Tool

16

Pengantar
COBIT defines IT activities in a generic process model within four domains. These domains are
1. 2. 3. 4. Plan and Organise, Acquire and Implement, Deliver and Support, and Monitor and Evaluate.

The domains map to ITs traditional responsibility areas of plan, build, run and monitor. The COBIT framework provides a reference process model and common language for everyone in an enterprise to view and manage IT activities. Incorporating an operational model and a common language for all parts of the business involved in IT is one of the most important and initial steps toward good governance.
17

PLAN AND ORGANISE (PO)

This domain covers strategy and tactics, and concerns the identification of the way IT can best contribute to the achievement of the business objectives. The realisation of the strategic vision needs to be planned, communicated and managed for different perspectives. A proper organisation as well as technological infrastructure should be put in place. This domain typically addresses the following management questions:
Are IT and the business strategy aligned? Is the enterprise achieving optimum use of its resources? Does everyone in the organisation understand the IT objectives? Are IT risks understood and being managed? Is the quality of IT systems appropriate for business needs?

18

ACQUIRE AND IMPLEMENT (AI)

To realise the IT strategy, IT solutions need to be identified, developed or acquired, as well as implemented and integrated into the business process. In addition, changes in and maintenance of existing systems are covered by this domain to make sure the solutions continue to meet business objectives. This domain typically addresses the following management questions:
Are new projects likely to deliver solutions that meet business needs? Are new projects likely to be delivered on time and within budget? Will the new systems work properly when implemented? Will changes be made without upsetting current business operations?
19

DELIVER AND SUPPORT (DS)

This domain is concerned with the actual delivery of required services, which includes service delivery, management of security and continuity, service support for users, and management of data and operational facilities. It typically addresses the followingmanagement questions:
Are IT services being delivered in line with business priorities? Are IT costs optimised? Is the workforce able to use the IT systems productively and safely? Are adequate confidentiality, integrity and availability in place for information security?
20

MONITOR AND EVALUATE (ME)

All IT processes need to be regularly assessed over time for their quality and compliance with control requirements. This domain addresses performance management, monitoring of internal control, regulatory compliance and governance. It typically addresses the following management questions:
Is ITs performance measured to detect problems before it is too late? Does management ensure that internal controls are effective and efficient? Can IT performance be linked back to business goals? Are adequate confidentiality, integrity and availability controls in place for information security?
21

Customizibility
While most enterprises have defined plan, build, run and monitor responsibilities for IT, and most have the same key processes, few will have the same process structure or apply all 34 COBIT processes. COBIT provides a complete list of processes that can be used to verify the completeness of activities and responsibilities; however, they need not all apply, and, even more, they can be combined as required by each enterprise.

22

COBIT as a Control Based Approach

23

Control Based Approach

COBIT defines control objectives for all 34 processes, as well as overarching process and application controls. Process need controls! Effective controls reduce risk, increase the likelihood of value delivery and improve efficiency because there will be fewer errors and a more consistent management approach.

24

Controls
Kebijakan, prosedur, praktek dan struktur organisasi yang dirancang untuk menjamin agar business objective dapat tercapai, sehingga kejadian-kejadian yang tak diingikan dapat dicegah dan diperbaiki.

25

Control Objectives
Control objectives : statement of the desired result, or purpose to be archived by implementing control procedurs in a particular activity IT control objectives provide a complete set of highlevel requirements to be considered by management for effective control of each IT process. They:
Are statements of managerial actions to increase value or reduce risk Consist of policies, procedures, practices and organisational structures Are designed to provide reasonable assurance that business objectives will be achieved and undesired events will be prevented or detected and corrected
26

Internal Controls (Kendali Internal)

Internal control is a process put in place by the board of directors, senior management and all levels of personnel to provide reasonable assurance that an organization's business objectives will be achieved.

27

Controls & Control Objectives (5)

Contoh dari information systems control objectives : 1. Information on automated systems is secured from improper access 2. Each transaction is authorized and entered only once 3. All rejected transactions are reported. 4. Duplicate transactions are reported 5. Files are adequately backed up to allow for proper recovery

The control objectives are identified by a twocharacter domain reference (PO, AI, DS and ME) plus a process number and a control objective number.

28

Control Model
When the room temperature (standard) for the heating system (process) is set, the system will constantly check (compare) ambient room temperature (control information) and will signal (act) the heating system to provide more or less heat.

29

30

Internal Control Yang Berdampak Pada IT

1. 2. 3. Executive management level (yang kita pelajari selama ini) Business process level IT services

31

IT General & Application Control

General controls are controls embedded in IT processes and services. Examples include:
Systems development Change management Security Computer operations

Controls embedded in business process applications are commonly referred to as application controls. Examples include:
Completeness Accuracy Validity Authorisation Segregation of duties
32

Boundaries of Business, General and Application Controls

33

Generic Control Requirements

In addition to the control objectives, each COBIT process has generic control requirements that are identified by PCn, for process control number. They should be considered together with the process control objectives to have a complete view of control requirements.
PC1 Process Goals & Objective PC2 Process Ownership PC3 Process Repeatability PC4 Roles & Responsabilities PC5 Policy, Plan & Procedures PC6 Process Performance Improvement

34

COBIT as a Measurement-Driven Approach

35

COBIT Provides:
1. Maturity models to enable benchmarking and identification of necessary capability improvements 2. Performance goals and metrics for the IT processes, demonstrating how processes meet business and IT goals and are used for measuring internal process performance based on balanced scorecard principles 3. Activity goals for enabling effective process performance

36

Maturity Models
Maturity modelling for management and control over IT processes is based on a method of evaluating the organisation, so it can be rated from a maturity level of nonexistent (0) to optimised (5). A generic definition is provided for the COBIT maturity scale, which is similar to CMM but interpreted for the nature of COBITs IT management processes. The purpose of maturity model is to identify where issues are and how to set priorities for improvements. The purpose is not to assess the level of adherence to the control objectives. Process management capability is not the same as process performance. Capability may not always be the same across IT environment.
37

Graphical Representaiton of Maturity Models

38

Generic Maturity Models

0 Non-existentComplete lack of any recognisable processes. The enterprise has not even recognised that there is an issue to be addressed. 1 Initial/ Ad HocThere is evidence that the enterprise has recognised that the issues exist and need to be addressed. There are, however, no standardised processes; instead, there are ad hoc approaches that tend to be applied on an individual or case-by-case basis. The overall approach to management is disorganised. 2 Repeatable but IntuitiveProcesses have developed to the stage where similar procedures are followed by different people undertaking thesame task. There is no formal training or communication of standard procedures, and responsibility is left to the individual. There is a high degree of reliance on the knowledge of individuals and, therefore, errors are likely. 3 Defined ProcessProcedures have been standardised and documented, and communicated through training. It is mandated that these processes should be followed; however, it is unlikely that deviations will be detected. The procedures themselves are not sophisticated but are the formalisation of existing practices. 4 Managed and MeasurableManagement monitors and measures compliance with procedures and takes action where processes appear not to be working effectively. Processes are under constant improvement and provide good practice. Automation and tools are used in a limited or fragmented way. 5 OptimisedProcesses have been refined to a level of good practice, based on the results of continuous improvement and maturity modelling with other enterprises. IT is used in an integrated way to automate the workflow, providing tools to improve quality and effectiveness, making the enterprise quick to adapt.

39

Kapasitas Organisasi Mencapai Maturitas

The maturity model is a way of measuring how well developed management processes are, i.e., how capable they actually are. How well developed or capable they should be primarily depends on the IT goals and the underlying business needs they support. How much of that capability is actually deployed largely depends on the return an enterprise wants from the investment.
For example, there will be critical processes and systems that need more and tighter security management than others that are less critical. Bank butuh investasi TI dan kapabilitas TI lebih tinggi daripada KUD Bibit, Pupuk dan Panen

On the other hand, the degree and sophistication of controls that need to be applied in a process are more driven by the enterprises risk appetite and applicable compliance requirements.
40

Tree Dimensions of Maturity

41

Capability Maturity Model

The maturity model scales will help professionals explain to managers where IT process management shortcomings exist and set targets for where they need to be. The right maturity level will be influenced by the enterprises business objectives, the operating environment and industry practices. Specifically, the level of management maturity will depend on the enterprises dependence on IT, its technology sophistication and, most important, the value of its information.
42

43

Question
Does higher COBIT maturity level always imply more sophisticated IT controls (i.e. split second backup means higher maturity level than weekly backup?

44

COBIT as a Performance Measurement Tool

45

Goal Relationships
IT goal is achieved by one process or the interaction of a number of processes. Therefore, IT goals help define the different process goals. In turn, each process goal requires a number of activities, thereby establishing the activity goals. Contoh:

46

Metrics in COBIT
1. Outcome measures, previously key goal indicators (KGIs), indicate whether the goals have been met. These can be measured only after the fact and, therefore, are called lag indicators. Performance indicators, previously key performance indicators (KPIs), indicate whether goals are likely to be met. They can be measured before the outcome is clear and, therefore, are called lead indicators. KPI will _drive_ higher level goals!

2.

47

Performance Drivers

48

Contoh Hubungan Business Goal & IT Activity pada DS5- Ensure Systems Security

49

Catatan tentang implementasi COBIT

Best practice is not the ultimate goal. Allow organizations to best determine which IT activities are important Kita bisa menganalisis IT process apa yang penting berdasarkan suatu inisatif strategic tertentu, misalnya rencana implementasi ERP, atau kebijakan strategic outsourcing. Bisa diselaraskan dengan IT Balanced Scorecard! Karena fokusnya pada requirement bukan pada how-to, maka COBIT sangat cocok untuk assessment. COBIT tidak memaksakan cara pengendalian teknis 50 tertentu!

The COBIT Framework

51

34 IT Process within COBIT 4.0

52

COBIT Cube

IT resources are managed by IT processes to achieve IT goals that respond to the business requirements. 53

COBIT Users
Executive managementTo obtain value from IT investments and balance risk and control investment in an often unpredictable IT environment Business managementTo obtain assurance on the management and control of IT services provided by internal or third parties IT managementTo provide the IT services that the business requires to support the business strategy in a controlled andmanaged way AuditorsTo substantiate their opinions and/or provide advice to management on internal controls
54

How COBIT Framework Enables IT Governance Focus Areas

Bagaimana dan contohnya apa?

55

COBIT Navigation
How to read COBIT 4.1!

56

Components of COBIT
Section 1 (lihat halaman berikut) contains a process description summarising the process objectives, with the process description represented in a waterfall. This page also shows the mapping of the process to the information criteria, IT resources and IT governance focus area.
what the process owner needs to do

Section 2 contains the control objectives for this process. Section 3 contains the process inputs and outputs, RACI chart, goals and metrics.
what the process owner needs from others how should it be measured what must be delegated and to whom?

Section 4 contains the maturity model for the process.

what must be done to improve?
57

58

RACI Chart
The roles in the RACI chart are categorised for all processes as: Chief executive officer (CEO) Chief financial officer (CFO) Business executives Chief information officer (CIO) Business process owner Head operations Chief architect Head development Head IT administration (for large enterprises, the head of functions such as human resources, budgeting and internal control) The project management officer (PMO) or function Compliance, audit, risk and security (groups with control responsibilities but not operational IT responsibilities)
59

60

61

62

63

64

65

Conclusions

66

Why is COBIT good for IT Governance?

Simple, checklist based Common language for all level Template based, can be customized later Provides a maturity level, very good measure for benchmarking

67

Why must COBIT be cautiously used for IT Governance?

Difficult to comprehend by business executives Not suited for strategic management of IT Generally it is a control based framework, doesnt tell you precisely how to do it! Even there are hows in COBIT, the hows in COBIT are scattered around, does not create a holistic and complete picture and enough for reasoning. If not carefully understood, people tend to use it as a one-size-fits-all solution. Doesnt tell you how to customize your IT Governance! Is not a tool to find root-cause of your IT problem.
68

Question
Bagi yang pernah baca COBIT, apakah penjelasan di atas make sense? Apakah penjelasan COBIT yang anda barusan jelaskan mengubah persepsi anda tentang COBIT?

69

TULISLAH: Apa persepsi anda dahulu terhadap COBIT (sebelum perkuliahan ini)

70