Comparison of ITIL 4 and COBIT2019 Part3

Updated: Jan 9

Comparison of ITIL 4 and COBIT2019

Key Words: ITIL 4 COBIT2019 Certification information management

Hashtags: #ITIL4 #COBIT #COBIT2019 #Certification #management #itil

8. Synergy between ITIL service value chain activities and COBIT domain

ITIL 4 service value chain activities will use different ITIL practice combinations to create value. This is very similar to the governance and management objectives in the five areas of COBIT.

COBIT 2019 adjustment, planning, and organization, and ITIL service value chain planning activities: these two frameworks complement each other because the grouped processes/practices focus on all planning activities within the organization, such as projects, services, enterprise architecture, etc.

COBIT construction, acquisition, and implementation (BAI) and ITIL service value chain design/transformation construction/acquisition activities: COBIT domain BAI supplements ITIL SVC design/transformation activities in areas such as requirement definition, availability, and capacity.

The COBIT domain BAI also supplements ITIL SVC's construction/acquisition activities in the fields of hosting IT assets, configuration, and solution acceptance.

COBIT provides service support (DSS) and ITIL service value chain delivery and support activities: these two are probably the most complementary activities of COBIT and ITIL 4. Both are concentrated in areas such as service requests, problems, incidents, etc.

9. The synergy of ITIL practices and governance management goals

ITIL 4 and COBIT 2019 are frameworks that have similar goals but achieve goals through different perspectives. One-to-one mapping of the process is neither possible nor desirable. However, there are some similarities that can be used to complement each other.

COBIT 2019 adopts an open approach to clarify its scope of influence and is very enlightened to guide users to use other appropriate frameworks, standards, and processes. In the description of governance and management goals, each goal points to "relevant guidance" and "detailed reference." Therefore, it is easier for practitioners to combine COBIT's governance direction with ITIL activities to create a comprehensive solution. Nevertheless, since COBIT 2019 and ITIL 4 were released almost simultaneously, in the current version of COBIT 2019, each goal is only mapped to the ITIL v3 process.

10. ITIL 4 and COBIT 2019: Harmony but Different

COBIT 2019 focuses on the entire enterprise when creating and managing a governance system. On the other hand, ITIL 4 focuses on the smallest value creation opportunities between service providers and service consumers. Therefore, COBIT 2019 focuses on the system, while ITIL 4 involves every process within the system, regardless of its size.

ITIL 4 continues to evolve through a proactive and modular approach to IT service management.

Therefore, any organization can use ITIL 4 to manage and improve IT services at all levels and at any scale.

COBIT 2019 also has a comprehensive coverage in IT governance. However, unlike ITIL 4, it is difficult to shrink COBIT 2019 for use in smaller organizations. However, ITIL 4 and COBIT 2019 were created for different purposes, so it is unrealistic to expect them to apply to the same situation.

11. Conclusion: COBIT 2019 and/or ITIL 4

Organizations need to have a comprehensive understanding of IT services and manage them with the help of a strong governance framework. In addition, the framework needs strong support from the top of the organization to achieve its goals. COBIT 2019 can work in coordination with ITIL 4 in any complex IT environment. In particular, the existence of ITIL 4 practices in this IT environment will greatly support the implementation of the COBIT governance system.

In many ways, COBIT provides "what", while ITIL shows "how". Although COBIT 2019 focuses on the governance of enterprise IT, ITIL 4 focuses on the management and execution of IT in the enterprise to achieve value creation. Companies should use COBIT 2019 to determine the "what" part of the IT service value equation and should rely on ITIL 4 to find answers to the "how", "when" and "where" questions.

Both frameworks can be applied in a specific environment to work together, and the existence of one in a specific environment will facilitate the implementation of the other.

When organizations start with ITIL, they can effectively integrate IT into core business processes. IT provides organizations with a support role similar to human resources or procurement, but the main difference is that IT usually always exists throughout the company's operating cycle, while HR and procurement only play a specific role in specific situations or when needs arise. Therefore, it makes sense to include IT in the entire operating cycle because it can effectively support IT and add value to the business.

ITIL provides detailed recommendations on how to perform multiple COBIT processes.

COBIT principle 1 (meeting the needs of stakeholders) includes a target cascade mechanism to improve ITIL efficiency by supporting service management (when both exist): prioritize service management improvement opportunities, identify its key activities, and serve as improvement proposals The means of reasoning connects these with specific organizational goals.

Some processes in ITIL and COBIT match each other. For example, the BAI06 management change process in COBIT matches the ITIL change management process under the service transition chapter. On the other hand, risk mitigation in ITIL is addressed by the topic of risk management, but no specific process is available – and in COBIT, we find the process APO12 to manage risk.

When comparing COBIT and ITIL, you will notice a lot of overlap. Both of these frameworks attempt to place IT within a larger company as a service-oriented autonomous entity. This allows IT departments to guide their own strategies and practices, and to build their own roadmap with business instructions in mind, rather than forcing the department to yield to the whims of other departments of the company.

Although ITIL 4 and COBIT 2019 have some overlap, both provide guidance on best practices for companies adapting to their unique circumstances. Based on the above analysis and comparison, if you are considering what to use-COBIT 2019 and ITIL 4 or ITIL 4 and COBIT 2019-it is all very simple: the first phase of your ITSM implementation project should probably be ITIL. When you thoroughly understand your own way, you can start thinking about the overall situation, thinking about COBIT.

COBIT requires a top-down implementation, starting with stakeholders, and defining business goals from their perspective. Implementation requires coordination between stakeholders, C-level executives, and managers to ensure that the available processes or products meet the needs of stakeholders.

The IT team can implement ITIL within the department, almost without interference from C-level managers or the board of directors. Understanding IT as a service-based department may require changing the attitude of those who are not used to working for the company/client/client rather than the project itself.

let's move! Start implementation from the principles and practices in the two frameworks.


Launched in 2016 as 591Lab International. We are committed to offering our clients excellent experience on ISACA, PMI, Cisco and Huawei examination preparatory services. We focus strongly on popular exams, and exam preparations services. We provide our customers with the complete training needed to earn the best scores for their respective Management and IT career certifications. We have a huge list of satisfied customers with top grades to back up all the claims we make.

Quick Links


#1    Emma Xiu

Whatsapp: +86 135 2066 9321


#2    Zoey Pei

Whatsapp: +86 157 3679 8918


#3    Jenny Zhang

Whatsapp: +86 185 1429 4188


This material is not sponsored by, endorsed by, or affiliated with Cisco Systems, Inc & Huawei Technologies Co., Ltd. Cisco Certified Internetworking Engineer, the Cisco Systems logo and the CCIE™ logo are trademarks or registered trademarks of Cisco Systems, Inc. in the United States and certain other countries.Huawei Certified Internetwork Expert, the Huawei logo and the HCIE™ logo are trademarks or registered trademarks of Huawei Technologies Co., Ltd . in China and certain other countries All other trademarks are trademarks of their respective owners. 

© Copyright 591Lab 2020. All Rights Reserved.