COBIT 2019: what it is, its 40 objectives and when to adopt it
If someone at your company proposes to "implement COBIT", the first question is not how but why. This guide explains what COBIT 2019 is, how it is organized, how it relates to ISO/IEC 38500 and when it makes sense to adopt it.

The committee asks for "IT governance" and someone answers with an acronym: COBIT. It is a well-known name, but the acronym alone does not say what problem it solves or how much work it involves.
This guide explains what COBIT 2019 is, how it is organized, how it relates to the ISO/IEC 38500 standard, when it makes sense to adopt it and what leadership should decide before starting.
What is COBIT 2019?
ISACA, the association that publishes it, describes COBIT as a framework for the governance and management of enterprise information technology. Its official page says COBIT 2019 is designed to integrate with other standards, regulations and good practices, and includes an updated framework and more implementation resources.
Its core is the model of governance and management objectives: according to ISACA, there are 40. They range from aligning and planning to delivering services and monitoring results. In our view, each objective is a starting point for assigning an owner and an indicator.
How is it organized: domains and objectives?
An ISACA article on COBIT 2019 explains that the governance and management objectives are grouped into five domains: one for governance and four for management. The acronyms come from the English names.
| Acronym | Name | Type |
|---|---|---|
| EDM | Evaluate, Direct and Monitor | Governance |
| APO | Align, Plan and Organize | Management |
| BAI | Build, Acquire and Implement | Management |
| DSS | Deliver, Service and Support | Management |
| MEA | Monitor, Evaluate and Assess | Management |
The same article mentions 13 enterprise goals and 13 alignment goals. Beyond this core, ISACA's page lists focus areas, such as DevOps, information and technology risk, and information security, which apply COBIT to specific topics.
ISACA also publishes a design guide, whose purpose is to put COBIT to practical use, and an implementation guide that introduces the design factors. You do not need to know every objective to decide whether COBIT is useful: you need to know which decisions the company wants to govern.
Which IT decisions does your company need to govern?
Before choosing a framework, we define what technology the business needs, in what order and who decides on that portfolio.
- IT portfolio prioritized by business impact
- IT governance with a committee, indicators and a review cycle

How does COBIT relate to ISO/IEC 38500?
ISO/IEC 38500:2024, published in February 2024 in its third edition, provides guiding principles for members of governing bodies, and those who support them, on the effective, efficient and acceptable use of IT. According to its official abstract, it applies to organizations of all sizes, public, private and not-for-profit.
In our view, the practical difference is the level: the ISO standard tells the board which principles to apply when governing IT, and COBIT offers a model with concrete objectives that management can assign and measure. They can be used together, or neither, depending on the size and maturity of the company.
To see how both fit inside a complete IT strategy, see the guide on the five parts of an IT strategy.
When does it make sense to adopt COBIT, and when not?
An ISACA article on corporate governance is clear on one point: governance programs must be initiated and sponsored by executive management, be properly scoped and always define attainable objectives. In our view, it is a warning against the governance project that is born in the IT department and never reaches the decision-making table.
In our view, COBIT makes sense when the company already knows what it wants to govern (for example technology risk, service delivery or security) and needs a common language to assign owners and indicators. It does not yet make sense when there is no IT strategy and no owner of technology decisions: a 40-objective framework applied over that vacuum produces documents, not governance.
A governance framework with nobody deciding through it is a library; with executive management behind it, it is a decision system.
How do you start without implementing all 40 objectives?
ISACA does not say all 40 objectives must be implemented at once: its page offers a design guide, focused on putting COBIT to practical use, and an implementation guide. In our view, a reasonable start has five steps:
First, define the problem or decision to be governed and who makes it today. Second, place that problem in the domains and pick the few objectives that apply to it, instead of all 40. Third, assign an owner per objective. Fourth, define how progress is measured, with indicators leadership can read. Fifth, set how often it is reviewed and who chairs the review.
This order is Cyrrus's judgment, not an ISACA procedure. What ISACA does say is that the scope should be limited and the objectives attainable.
IT governance without a full-time role
CIO or CTO as a Service: IT governance, architecture and alignment of technology with the business, on demand.
- Same judgment, adjusted commitment
- Vendor-agnostic

Do you need to be COBIT-certified?
ISACA's official page lists a COBIT foundation certificate, a design and implementation certification program and accredited training partners. These are training credentials. The page does not mention a certification of the company as such.
If a third party (a client, an auditor or a vendor) requires a "COBIT certification", it helps to ask in writing what they mean before taking on the cost, because it may be a requirement on people, on processes or on a different standard.
What should leadership decide before launching a COBIT project?
There are four management decisions, not IT department ones: what is to be governed and why now; who sponsors the program in executive management; which part of the framework applies first and which is left out; and how it will be known, a year from now, that governance works.
If the sponsorship is unclear or the scope covers all 40 objectives from day one, the project runs the risk ISACA points to: a program without sponsorship or a limited scope.
How we can help
At Cyrrus we provide IT strategy consulting as part of the Construct phase of the CIRA method: assessment, target architecture, a prioritized portfolio and the IT governance that decides on it. If the company decides to lean on COBIT or ISO/IEC 38500, we do it on top of that portfolio and with no vendor bias.
If the company needs technology leadership without a full-time role, we offer CIO and CTO as a Service, and if the underlying topic is security, we work on cybersecurity governance with the same logic.
To go deeper: what data governance is and what leadership decides, and why software selection should start from criteria and not from demos.
Sources
- ISACA. COBIT — Control Objectives for Information Technologies (official COBIT page; 40 governance and management objectives, focus areas, guides and certificates). Accessed November 18, 2026
- Anoruo, C. Employing COBIT 2019 for Enterprise Governance Strategy. ISACA Industry News, October 28, 2019 (five domains; 13 enterprise goals and 13 alignment goals; executive sponsorship). Accessed November 18, 2026
- ISO. ISO/IEC 38500:2024 Information technology — Governance of IT for the organization (official abstract; 3rd edition, February 2024). Accessed November 18, 2026

30 years in strategy and IT: Oracle consultant, IT leader at PepsiCo Latin America, Covidien and Coremar, and founder of Cyrrus in 2017. MBA, Universidad del Norte.
About the authorReady to connect the decision to the execution?
Tell us your organization's challenge. We'll set up a conversation with the right team and tell you straight whether we can help.
Not sure where to start? Request a free diagnostic session