Study guide
8.2 Culture, Ethics, and Behavior
ISACA COBIT 2019 Foundation Certificate Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Certificate Rules, Retakes, and How to Study
2 Chapter 2: Framework Introduction
2.1 Purpose of COBIT and EGIT 2.2 I&T Versus the IT Function 2.3 COBIT 2019 Product Family 2.4 Stakeholders, Audience, and Benefits
3 Chapter 3: Framework Positioning
3.1 Umbrella Framework and Related Standards 3.2 Evolution from COBIT 5 to COBIT 2019
4 Chapter 4: Governance System Principles I
4.1 Provide Stakeholder Value 4.2 Holistic Approach 4.3 Dynamic Governance System
5 Chapter 5: Governance System Principles II and Framework Principles
5.1 Governance Distinct from Management 5.2 Tailored to Enterprise Needs 5.3 End-to-End Coverage 5.4 Three Governance Framework Principles
6 Chapter 6: Governance System Components Overview
6.1 Seven Governance System Components 6.2 Generic Versus Variant Components 6.3 Focus Areas
7 Chapter 7: Process and Structure Components
7.1 Processes Component 7.2 Practices, Activities, and Metrics 7.3 Organizational Structures 7.4 Principles, Policies, and Frameworks
8 Chapter 8: Information and People Components
8.1 Information Component 8.2 Culture, Ethics, and Behavior 8.3 People, Skills, and Competencies 8.4 Services, Infrastructure, and Applications
9 Chapter 9: Integrating Governance System Components
9.1 How Components Work Together 9.2 RACI Charts and Key Roles 9.3 Components Supporting Objectives
10 Chapter 10: The Goals Cascade
10.1 The Goals Cascade 10.2 Enterprise Goals and Alignment Goals
11 Chapter 11: Core Model and EDM Governance Objectives
11.1 The 40-Objective Core Model 11.2 EDM Governance Objectives 11.3 Governance Versus Management Objectives
12 Chapter 12: APO Align, Plan, and Organize
12.1 APO Strategy, Architecture, and Innovation 12.2 APO Portfolio, Resources, and Relationships 12.3 APO Risk, Security, Data, and Quality
13 Chapter 13: BAI, DSS, and MEA Management Objectives
13.1 BAI Build, Acquire, and Implement 13.2 DSS Deliver, Service, and Support 13.3 MEA Monitor, Evaluate, and Assess
14 Chapter 14: Performance Management
14.1 Performance Management Principles 14.2 Capability Levels 0–5 and Maturity
15 Chapter 15: Designing a Tailored Governance System
15.1 Why Tailor: Design Factors 15.2 The Eleven Design Factors 15.3 Design Workflow and Toolkit
16 Chapter 16: Business Case
16.1 Business Case for EGIT 16.2 Benefits, Costs, Risk, and Tracking
17 Chapter 17: Implementation Lifecycle
17.1 Implementation Lifecycle Overview 17.2 Seven Implementation Phases 17.3 Roles, Pain Points, and Challenges 17.4 Design Guide and Implementation Guide Together
8.2 Culture, Ethics, and Behavior
Key Takeaways Explain This Topic AI
Culture, ethics and behavior is a first-class COBIT 2019 component of every objective, not optional color commentary after the process is written.
Desired behaviors must be created, encouraged, and maintained — they do not appear because a RACI chart exists.
Individual ethics and organizational ethics both relate to goals; leadership tone, incentives, sanctions, speak-up channels, and risk culture are the usual levers.
A perfect process still fails if the culture rewards heroics and hidden workarounds, as when engineers bypass change control to “just ship.”
The exam trap is calling culture “soft” and untestable; COBIT designs and assesses it as a component.
Last updated: August 2026
Quick Answer: Culture, ethics and behavior is a first-class COBIT 2019 component of every objective — not a soft afterthought. Desired behaviors must be created, encouraged, and maintained . Individual ethics and organizational ethics both relate to goals. Leadership tone, incentives, sanctions, speak-up channels, and risk culture are the usual levers. A perfect process fails if the culture rewards heroics and hidden workarounds. The exam trap is calling culture “untestable.” COBIT tests it as a designed component.
Chapter 6 already warned that this slot is “often underestimated.” That sentence is not decoration. In the 30% Governance System and Components domain, items that look like process questions are frequently culture questions in disguise. The process document is complete. The committee exists. The policy is signed. Production still runs on a back-door script because that is what last year’s bonus rewarded.
Desired behaviors do not appear by themselves
COBIT does not treat culture as office artwork. For each objective, the enterprise must decide which behaviors the objective requires , then do three jobs:
Create the desired behaviors — define them, model them, and put them in goals and codes of conduct.
Encourage them — incentives, recognition, tooling that makes the right path the easy path.
Maintain them — sanctions, monitoring, speak-up follow-through, and leadership that does not quietly bless the workaround when the quarter is tight.
If any of the three is missing, the component is incomplete. A code of ethics in the employee handbook creates a statement. It does not encourage anything if the only people who were promoted last year were the ones who shipped around the CAB. It does not maintain anything if a reported bypass is “taken offline” and never heard from again.
Write the three verbs on the inside cover of your notes. Stems that say “we published a value statement” have only done the first verb, and maybe not even that if nobody can name a behavior the statement forbids.
Individual ethics and organizational ethics
Two layers sit in this component, and both relate to goals.
Individual ethics is what a person will or will not do when the process is inconvenient — log the incident, refuse the unauthorized change, escalate the unreconciled number. Organizational ethics is what the enterprise systematically rewards, ignores, or punishes — the real rules, not the poster. COBIT cares about both because an objective fails either way: a well-designed bank with one trader who hides losses, or a shop where honest people learn that hiding work is how you keep your job.
Goals connect the layers. If the enterprise goal is “reliable change,” but the personal goal on the scorecard is “features shipped this sprint,” the culture component is fighting the process component. That is a design error, not a motivational-poster gap. Alignment of personal objectives, team objectives, and enterprise goals is how this component supports provide stakeholder value instead of providing last quarter’s hero story.
Levers you should be able to name
Foundation items will not ask you to run an employee-engagement survey. They will ask which levers belong in this component.
Lever What it does Failure mode
Leadership tone Shows what actually matters when the policy and the deadline collide Executives praise the weekend warrior who bypassed the CAB
Incentives Pay, promotion, and recognition pull behavior Bonuses for “just ship”; no credit for clean change records
Sanctions Make the forbidden path costly Repeat bypasses with no consequence
Speak-up Give people a safe way to surface bad news and workarounds Retaliation, or a hotline that never closes the loop
Risk culture Shared habit of surfacing uncertainty before it becomes an incident “Don’t bring me problems” becomes the operating system
These levers are how culture is designed . They are also how it is evidenced . A candidate who says culture cannot be tested has not looked at incentive plans, sanction logs, speak-up metrics, or the last three all-hands. COBIT does not need a feeling. It needs behaviors that can be described, encouraged, and checked.
Related components do not replace this one. A policy can forbid unauthorized production access. Organizational structures can name a CAB. Information can show how many emergency changes landed. None of that operates if the culture treats the CAB as theater. Holistic approach: the culture slot is empty, so the objective is empty, even if the other six slots look populated.
Scenario: Riverbend Payments “just ships”
Riverbend Payments has a complete BAI06 Managed IT Changes process, a weekly CAB, and a policy that production changes require a ticket, a peer review, and a back-out plan. On-call engineers still push Friday-night hotfixes from laptops because last year’s promotions went to the people who “saved the release.” The incident channel treats a logged near-miss as disloyalty. A new join who files a bypass report is told privately to be a team player.
Nothing is wrong with the process text. The culture, ethics and behavior component is failing in all three verbs. Desired behavior (use the change path) was stated, so “create” is half-done. It is not encouraged — incentives point the other way. It is not maintained — speak-up is punished and sanctions never land on the hero. Traders at a sister desk do the same thing with unapproved pricing spreadsheets: the control exists; the behavior is to go around it.
The repair is not a thicker process document. The repair is tone (“I will not praise a silent bypass”), incentives (credit for clean changes and for stopped bad releases), sanctions that apply to stars, and a speak-up path that closes. Until those move, Riverbend is rehearsing a Foundation item: a perfect process that still fails.
Exam traps for this component
Soft and untestable: This is the big one. COBIT lists culture, ethics and behavior as a component of every objective. If it were untestable, it would not be in the model.
HR-only / out of EGIT: People operations may own some programs. The component still belongs on APO12, BAI06, DSS02, and EDM01. Governance does not outsource behavior and then claim the objective is complete.
Process will fix it: More swimlanes do not create courage. If the stem shows a workaround culture, the missing slot is this one.
One poster equals the component: A values poster is not create + encourage + maintain.
Replaced processes in 2019: No. All seven components remain. Culture did not eat processes.
- How items are written
- Workaround / heroics / “just ship” despite a complete process → this component, not “write another procedure.”
“Culture is soft; skip it on the exam” → reject.
Tone, incentives, sanctions, speak-up, risk culture → the lever set for this slot.
Individual ethics versus organizational ethics → both in scope; both relate to goals.
“Only EDM needs culture” → reject; every objective includes the slot.
Carry the three verbs and the Riverbend picture into the next section. Skills cannot save an objective if the culture punishes the people who use those skills the right way.