CPA Information Systems & Controls (ISC) • Information Systems

Evaluate IT Governance Structures And Responsibilities

Understanding how organizations align IT decision-making with strategic objectives to safeguard stakeholder value.

A certification badge with calculator and balance symbols for CPA preparation
Inside this lesson 9 sections 5 questions 6 figures

SECTION 1

Historical Context & Motivation

The concept of IT governance did not emerge in a vacuum; it evolved in direct response to a series of corporate failures, regulatory mandates, and the rapid digitization of business processes. In the 1990s, organizations began to recognize that information technology was no longer a back-office support function but rather a strategic asset capable of creating or destroying shareholder value. As enterprises invested billions of dollars in enterprise resource planning systems, data warehouses, and internet-based platforms, boards of directors and C-suite executives found themselves ill-equipped to oversee the risks and returns associated with these investments. The absence of formal governance mechanisms led to spectacular failures—cost overruns, security breaches, and compliance violations—that eroded investor confidence and triggered regulatory scrutiny.

1996 • COBIT 1.0 Released

The Information Systems Audit and Control Association (ISACA) published the first edition of COBIT, establishing a framework for IT audit and control that laid the groundwork for formal IT governance.

2002 • Sarbanes-Oxley Act (SOX)

In the wake of Enron and WorldCom, SOX mandated that public companies establish internal controls over financial reporting—including IT controls—elevating IT governance from best practice to legal requirement.

2005 • ISO/IEC 38500 Development Begins

The International Organization for Standardization began developing the first international standard dedicated to corporate governance of information technology, codifying board-level responsibilities.

2012 • COBIT 5 Integrates Governance & Management

ISACA released COBIT 5, which explicitly separated governance processes (Evaluate, Direct, Monitor) from management processes, providing a comprehensive enterprise IT governance model.

2019 • COBIT 2019 and Modern Risk Frameworks

COBIT 2019 introduced design factors and focus areas to tailor governance structures to enterprise-specific needs, reflecting the growing complexity of cloud computing, AI, and cybersecurity.

The central question that IT governance seeks to answer remains deceptively simple: Who makes IT decisions, how are those decisions made, and how are decision-makers held accountable? For CPA candidates preparing for the ISC exam, understanding these governance structures is essential because auditors must evaluate whether an organization's IT environment supports reliable financial reporting, regulatory compliance, and effective risk management.

SECTION 2

Core Principles & Definitions

At its foundation, IT governance rests on several interrelated principles that distinguish it from day-to-day IT management. While IT management deals with planning, building, running, and monitoring IT activities, IT governance operates at the board and executive level, establishing the policies, structures, and accountability mechanisms that ensure IT supports strategic objectives. The ISO/IEC 38500 standard distills governance into three core activities: Evaluate, Direct, and Monitor (EDM). These three activities form a continuous cycle that the governing body uses to oversee IT's contribution to enterprise value.

1

Strategic Alignment

IT investments and activities must be aligned with the organization's strategic goals. The governance structure ensures that IT priorities are derived from—and traceable to—business objectives.
2

Value Delivery

IT governance ensures that IT investments deliver measurable value by optimizing costs, managing benefits realization, and confirming that projects yield their intended outcomes within acceptable risk parameters.
3

Risk Management

A governance framework integrates IT risk into the enterprise risk management process, ensuring that cybersecurity threats, system failures, and compliance gaps are identified, assessed, and mitigated systematically.
4

Resource Optimization

Governance structures define how IT resources—people, technology, data, and budget—are acquired, allocated, and utilized to achieve maximum efficiency and effectiveness across the enterprise.
5

Performance Measurement

Through balanced scorecards, key performance indicators, and maturity models, governance mechanisms track IT performance and provide transparency to stakeholders including auditors and regulators.

SECTION 3

Visual Explanation — IT Governance Structure

IT Governance Structure — Organizational HierarchyBoard of DirectorsEvaluate · Direct · MonitorIT Strategy CommitteeC-suite, Business LeadersIT Steering CommitteePrioritizes Projects · Allocates ResourcesCIO / CTOIT Operations & StrategyCISOSecurity & Risk ManagementInternal AuditAssurance & ComplianceIT Development · InfrastructureService Delivery TeamsSOC · Incident ResponseSecurity OperationsIT Audit · SOX TestingAudit TeamsAccountability flows upward · Policy and direction flows downward
The diagram illustrates the hierarchical IT governance structure from the Board of Directors at the top, through the IT Strategy Committee and IT Steering Committee, down to operational roles. Policy flows downward while accountability flows upward.

The diagram above represents a typical IT governance hierarchy found in publicly traded companies. At the apex, the Board of Directors exercises its Evaluate, Direct, and Monitor responsibilities through a dedicated IT Strategy Committee—a board-level committee that includes senior executives and, ideally, at least one director with significant technology expertise. Below that sits the IT Steering Committee, which translates strategic directives into project priorities and resource allocations. The operational layer—comprising the Chief Information Officer, Chief Information Security Officer, and Internal Audit function—executes and monitors IT activities on a day-to-day basis, with clear reporting lines back up to the governing bodies. For CPA candidates, the critical observation is that Internal Audit maintains an independent reporting line to the audit committee of the board, preserving objectivity in its assessment of IT controls.

SECTION 4

How IT Governance Works — The EDM Cycle & RACI Framework

IT governance operates through a structured decision-making cycle and clearly defined responsibilities. Two foundational mechanisms are the Evaluate-Direct-Monitor (EDM) cycle codified in ISO/IEC 38500 and the RACI matrix (Responsible, Accountable, Consulted, Informed) used extensively in COBIT to assign process-level roles. Understanding these mechanisms is essential because auditors evaluate whether the governance structure includes clear accountability and whether the right stakeholders are involved in IT decisions that affect financial reporting integrity.

The EDM Cycle

The Evaluate phase requires the governing body to assess the current and future use of IT, considering stakeholder needs, competitive pressures, and regulatory requirements. In the Direct phase, the board issues policies and guidelines that steer IT strategy, investment decisions, and risk tolerance thresholds. Finally, the Monitor phase involves reviewing performance metrics, audit reports, and compliance dashboards to verify that directives are being followed and objectives are being met. This cycle is continuous; the outputs of monitoring feed back into the next evaluation, creating a feedback loop similar to the Plan-Do-Check-Act cycle familiar from quality management.

The RACI Matrix

RACI RoleDefinitionExample in IT Governance
Responsible (R)The person or group that performs the work to complete the activity.IT Security team implements firewall configuration changes.
Accountable (A)The single individual who is ultimately answerable for the activity; has authority to approve or reject outcomes.CISO is accountable for overall security posture and signs off on policy exceptions.
Consulted (C)Subject-matter experts whose input is sought before a decision is made; two-way communication.Legal counsel is consulted on data privacy implications before deploying a new CRM system.
Informed (I)Stakeholders who are kept updated on progress or decisions; one-way communication.The audit committee is informed of material IT incidents and remediation status.

RACI Matrix — Defining Governance Roles and Responsibilities

ℹ
CPA Exam Tip

SECTION 5

Key IT Governance Frameworks — COBIT, ITIL, and ISO 38500

Several frameworks provide structured approaches to implementing IT governance, and CPA candidates should understand how they complement each other. The three most relevant frameworks for auditors are COBIT (Control Objectives for Information and Related Technologies), ITIL (Information Technology Infrastructure Library), and ISO/IEC 38500. While COBIT provides the most comprehensive governance and management framework, ITIL focuses on IT service management, and ISO 38500 addresses the board-level governance principles. In practice, organizations often layer multiple frameworks, using COBIT for governance processes, ITIL for service delivery, and ISO 38500 for board-level oversight standards.

IT Governance Frameworks — Scope & OverlapCOBIT 2019Governance + Management37 Governance & Mgmt ObjectivesITIL 4Service Management34 PracticesISO/IEC 38500Board-Level Governance Principles (EDM)OverlapIT ControlsRisk · Compliance• EDM Processes• APO, BAI, DSS, MEA• Maturity Levels• Design Factors• Service Value Chain• Incident Mgmt• Change Enablement• Continual ImprovementCOBIT covers the broadest scope (governance + management) · ITIL focuses on service delivery · ISO 38500 addresses board-level principlesOrganizations typically combine frameworks for comprehensive coverage
This Venn-style diagram illustrates how COBIT provides the broadest governance and management coverage, ITIL specializes in service management, and ISO 38500 sets board-level governance principles. The overlap zone represents shared concerns: IT controls, risk management, and compliance.
FrameworkIssuing BodyPrimary FocusCPA Exam Relevance
COBIT 2019ISACAEnd-to-end governance and management of enterprise IT; 40 objectives across 5 domainsHigh — Most frequently tested IT governance framework
ITIL 4Axelos / PeopleCertIT service management best practices; service value system and 34 management practicesModerate — Relevant to IT operations and change management controls
ISO/IEC 38500ISO / IECHigh-level governance principles for boards of directors; Evaluate-Direct-Monitor modelModerate — Tested as a conceptual governance model
COSO ERMCOSOEnterprise risk management framework that IT governance integrates with for risk alignmentHigh — COSO Internal Control framework is foundational to SOX compliance

Comparison of Major IT Governance and Related Frameworks

SECTION 6

Worked Example — Evaluating an IT Governance Structure

Consider the following scenario: you are a CPA performing an IT governance review for Apex Financial Corp., a mid-size publicly traded company. You have been provided with the company's IT organizational chart, committee charters, and recent board meeting minutes. Your task is to evaluate whether the governance structure is adequate to support reliable financial reporting and regulatory compliance.

Worked example

  1. 1

    Step 1 — Identify the Governance Structure

    Review the organizational chart to identify the key governance bodies. Apex has a Board Audit Committee, an IT Strategy Committee chaired by the CFO, and an IT Steering Committee chaired by the CIO. The CISO reports to the CIO. There is no separate IT Risk Committee.
    Three governance bodies identified; CISO reporting line noted as potential concern.
  2. 2

    Step 2 — Assess Roles and Responsibilities Using RACI

    Map key IT governance activities to RACI roles. For IT investment decisions: the IT Steering Committee is Responsible, the CFO (as IT Strategy Committee chair) is Accountable, business unit leaders are Consulted, and the Board Audit Committee is Informed. For cybersecurity risk: the CISO is Responsible, but the CIO—not an independent risk function—is Accountable. This creates a potential segregation of duties issue because the CIO also manages IT operations that generate the risks the CISO is supposed to mitigate.
    Deficiency: CISO reporting to CIO may compromise independent risk oversight.
  3. 3

    Step 3 — Evaluate Against Framework Criteria (COBIT EDM Domain)

    Check whether each EDM process is addressed. EDM01 (Ensure Governance Framework Setting and Maintenance): Apex has committee charters but they have not been updated in three years. EDM02 (Ensure Benefits Delivery): Post-implementation reviews are not consistently performed. EDM03 (Ensure Risk Optimization): IT risk is not formally integrated into enterprise risk management. EDM04 (Ensure Resource Optimization): IT budgets are reviewed annually by the IT Strategy Committee. EDM05 (Ensure Stakeholder Engagement): Board receives quarterly IT updates.
    Gaps found in EDM01 (stale charters), EDM02 (no post-implementation reviews), and EDM03 (IT risk not integrated into ERM).
  4. 4

    Step 4 — Formulate Findings and Recommendations

    Document findings with their potential impact on financial reporting. The CISO reporting line increases the risk that security vulnerabilities affecting financial systems may not be escalated independently. Stale charters mean that governance roles may not reflect current regulatory requirements (e.g., new SEC cybersecurity disclosure rules). The absence of ERM integration means that IT risks may not be appropriately weighted in the entity's overall risk assessment.
    Recommendations: (1) CISO should report directly to the Board Audit Committee or CEO; (2) Update committee charters annually; (3) Integrate IT risk into the COSO ERM framework.

SECTION 7

Strengths and Limitations of Common Governance Structures

No single IT governance structure is universally optimal. Organizations must weigh the strengths and limitations of different structural approaches based on their size, industry, regulatory environment, and risk profile. Understanding these trade-offs is vital for CPA candidates, who must not only identify governance structures but also assess their effectiveness in a given context.

Governance StructureStrengthsLimitations
Centralized IT GovernanceConsistent policies and standards; strong control environment; economies of scale in procurement; clearer accountability lines.Slower response to local business unit needs; potential bottlenecks in decision-making; reduced innovation at the operational level.
Decentralized IT GovernanceHigh responsiveness to individual business unit requirements; encourages innovation; empowers local management.Inconsistent policies and controls; duplication of resources; higher risk of control gaps; challenging for enterprise-wide compliance.
Federated (Hybrid) IT GovernanceBalances standardization with flexibility; central policies with local execution; commonly adopted by large enterprises.Complex to implement and manage; requires mature communication channels; risk of ambiguous accountability if roles are not clearly defined.
Board-Level IT CommitteeEnsures board-level oversight; aligns IT with fiduciary responsibilities; demonstrates 'tone at the top' for technology risk.Requires directors with sufficient IT expertise; may create additional governance overhead; effectiveness depends on committee composition.

Comparison of IT Governance Structural Approaches

SECTION 8

Connection to Advanced Theory — IT Governance in Cloud and Digital Transformation

As organizations increasingly adopt cloud computing, artificial intelligence, and third-party managed services, IT governance must evolve to address new complexities. Traditional governance structures assumed that the organization owned and operated most of its IT infrastructure, but cloud computing introduces a shared responsibility model where the cloud service provider manages infrastructure-level controls while the customer retains responsibility for data classification, access management, and application-layer controls. This shared model demands that governance structures explicitly assign accountability for each layer of the technology stack and that audit procedures verify whether the division of responsibilities is clearly documented and monitored.

Governance DimensionTraditional On-PremiseCloud / Digital Transformation
Control over InfrastructureFull internal control; physical and logical access managed by the organization.Shared responsibility; reliance on SOC 2 reports from cloud providers for infrastructure controls.
Vendor GovernanceLimited third-party dependency; vendor management focused on hardware and software licensing.Extensive third-party risk management; governance must include vendor due diligence, SLA monitoring, and exit strategies.
Data GovernanceData resides within the organization's perimeter; location and sovereignty are straightforward.Data may reside in multiple jurisdictions; governance must address data residency, privacy regulations (GDPR, CCPA), and encryption requirements.
Change ManagementFormal change advisory boards with scheduled release windows.Continuous deployment pipelines; governance must adapt to DevOps and CI/CD practices while maintaining control.

Traditional vs. Cloud-Era IT Governance Considerations

For CPA candidates, the takeaway is that evaluating IT governance in the modern environment requires an understanding of how complementary user entity controls (CUECs) operate in conjunction with a service organization's controls, and how SOC 1 and SOC 2 reports provide assurance about third-party governance. As you progress in your career, expect IT governance evaluation to increasingly intersect with topics like AI ethics governance, data privacy impact assessments, and resilience planning for systemic technology risks.

SECTION 9

Practice Problems

Question 1: CONCEPTUAL

An IS auditor is evaluating internal controls over financial reporting (ICFR) at a publicly traded company. During planning, the auditor identifies several observations. For each observation below, select whether it represents an IT Governance issue, an IT Management issue, or Both.
Show answer
Step-by-step analysis of each observation: Observation 1 — 'The board of directors has not established a formal IT risk appetite statement, and no IT risk reporting is provided to the audit committee.' This concerns the board and audit committee — the highest level of organizational oversight. Establishing risk appetite and ensuring risk reporting flows to governance bodies are responsibilities of IT governance structures, not day-to-day IT management. Under COSO, this is a control environment deficiency (tone at the top / oversight). Under AS 2201, entity-level control deficiencies of this nature can have a pervasive effect on ICFR. → ANSWER: IT Governance Issue Observation 2 — 'The IT operations team failed to apply a critical security patch to the ERP system within the organization's required 30-day patching window.' This is an operational execution failure. A patching policy exists (governance set the rule); management failed to execute it. Patch management is a day-to-day IT operational control — a management responsibility. This is a localized control deficiency rather than a pervasive governance failure. → ANSWER: IT Management Issue Observation 3 — 'There is no defined accountability structure for who is responsible for IT-related financial reporting risks at the executive level, AND the IT department lacks documented change management procedures.' The absence of executive-level accountability structures is an IT governance deficiency (COSO control environment — assignment of authority and responsibility). The absence of change management procedures is an IT management deficiency (operational process control). Because both layers are implicated in a single observation, the answer is Both. → ANSWER: Both Observation 4 — 'The company's IT investments are not formally evaluated against strategic business objectives before approval.' Aligning IT investments with business strategy is a core IT governance responsibility under frameworks such as COBIT and ISO/IEC 38500. This is a directional/oversight question ('Are we doing the right things?'), not an operational execution question. It reflects a failure at the governance layer to establish and enforce an IT investment management framework. → ANSWER: IT Governance Issue Observation 5 — 'During a recent system migration, the IT team did not perform parallel processing or reconcile converted data balances to the prior system.' This is an operational execution failure during a specific project — the IT team did not follow sound data migration and conversion controls. Data conversion reconciliation is an IT management/operational control. There is no indication that governance structures are absent; rather, the team failed to execute a specific technical control procedure. → ANSWER: IT Management Issue SUMMARY TABLE: 1 → IT Governance Issue 2 → IT Management Issue 3 → Both 4 → IT Governance Issue 5 → IT Management Issue Auditor's Note: Governance deficiencies (Observations 1, 4) are entity-level control weaknesses under COSO and AS 2201 with potentially pervasive ICFR implications. Management deficiencies (Observations 2, 5) tend to be more localized. Observation 3 illustrates that an organization can have strong day-to-day operations in some areas yet still carry a material weakness risk if the governance accountability structure is absent — the governance layer provides the direction and oversight that sustains management controls over time.

Question 2: BASIC CALCULATION

A company's IT Steering Committee approved five projects with the following budgets: ERP Upgrade ($2.4M), Cybersecurity Enhancement ($800K), Cloud Migration ($1.6M), Data Analytics Platform ($1.2M), and Regulatory Compliance System ($600K). If the governance policy requires that at least 20% of the total IT investment portfolio be allocated to risk mitigation projects (cybersecurity and compliance combined), does the current portfolio comply?
Show answer
First, calculate the total IT investment: $2.4M + $0.8M + $1.6M + $1.2M + $0.6M = $6.6M. Next, identify risk mitigation projects: Cybersecurity Enhancement ($0.8M) and Regulatory Compliance System ($0.6M), totaling $1.4M. The percentage allocated to risk mitigation is $1.4M ÷ $6.6M = 21.2%. Since 21.2% exceeds the 20% threshold, the portfolio complies with the governance policy. However, an auditor might note that the margin is narrow and recommend that the steering committee establish a buffer to account for potential budget reallocations during the fiscal year.

Question 3: INTERMEDIATE

You are reviewing the RACI chart for a company's change management process. The chart shows that the CIO is both Responsible and Accountable for approving emergency changes to production systems, while the IT Steering Committee is only Informed. Identify the governance weakness and explain how it could affect financial reporting.
Show answer
The governance weakness is twofold. First, having the CIO as both Responsible and Accountable for emergency changes violates the principle of segregation of duties—there is no independent party reviewing or approving the CIO's decisions. Second, the IT Steering Committee being merely Informed (rather than Consulted or Accountable) means that there is no cross-functional oversight before an emergency change is deployed to production. This could affect financial reporting because unauthorized or inadequately tested changes to financially significant systems—such as the general ledger, accounts payable, or revenue recognition modules—could introduce errors, processing failures, or vulnerabilities that compromise data integrity. The recommended remediation would be to designate an independent change advisory board or risk officer as the Accountable party for emergency changes, with the CIO remaining Responsible for execution and the IT Steering Committee being Consulted before deployment.

Question 4: APPLIED

GlobalTech Inc. recently migrated its financial reporting system to a major public cloud provider. During your IT governance evaluation, you discover that (a) the company relies on the cloud provider's SOC 2 Type II report for infrastructure controls but has not reviewed the report's complementary user entity controls (CUECs), (b) there is no vendor governance policy, and (c) the board has not been briefed on the shared responsibility model. Assess the governance risks and recommend corrective actions.
Show answer
This scenario presents three interconnected governance failures. First, failing to review CUECs means that GlobalTech may not have implemented the customer-side controls that the cloud provider assumes are in place—such as configuring access permissions, encrypting data at rest, and monitoring user activity. Without these controls, the assurance provided by the SOC 2 report is incomplete. Second, the absence of a vendor governance policy means there are no formal procedures for vendor due diligence, ongoing monitoring of SLA compliance, data residency requirements, or exit planning if the provider relationship deteriorates. Third, the board's lack of awareness about the shared responsibility model represents a failure in the 'Evaluate' component of the EDM cycle—the governing body cannot make informed decisions about IT risk if it does not understand the fundamental control architecture. Corrective actions should include: (1) immediately reviewing and implementing all CUECs identified in the SOC 2 report; (2) developing a comprehensive vendor governance policy that includes periodic provider risk assessments and SLA performance tracking; and (3) providing the board with a briefing on the shared responsibility model, including a clear mapping of which controls are managed by the provider versus the organization.

Question 5: CRITICAL THINKING

A mid-size financial services firm operates with a fully decentralized IT governance model: each of its four business units maintains its own IT infrastructure, security policies, and change management processes. The firm recently failed a regulatory examination due to inconsistent access controls across business units. The CEO proposes moving to a fully centralized governance model. As a CPA advisor, critically evaluate this proposal. What alternative governance design might better serve the organization, and what factors should the board consider?
Show answer
While the CEO's impulse to centralize is understandable given the regulatory failure, moving from fully decentralized to fully centralized governance carries significant risks. A sudden centralization could stifle the business units' ability to respond to their unique market and regulatory requirements, create resistance from local IT teams, and overwhelm a centralized governance function that lacks deep knowledge of each unit's operations. A more effective alternative would be a federated (hybrid) governance model in which the board establishes enterprise-wide governance principles—including minimum security standards, a unified access control framework, and standardized change management policies—while allowing each business unit to retain operational flexibility in how those standards are implemented. Critical factors the board should consider include: (1) the maturity of each business unit's existing IT controls and the feasibility of harmonization; (2) the cost of centralizing versus federating, including technology integration expenses and potential service disruptions; (3) the regulatory landscape—financial services regulators increasingly expect consistent, enterprise-wide controls; (4) the availability of qualified governance personnel to staff a centralized function; and (5) the organizational culture and change management challenges. The COBIT 2019 framework's concept of 'design factors'—enterprise strategy, IT-related risk profile, compliance requirements, and organizational structure—provides a systematic methodology for tailoring the governance model to the firm's specific circumstances.

Varsity Tutors • CPA (ISC) • Evaluate IT Governance Structures And Responsibilities