GOVERNANCE & RISK / TECHNICAL EXPLAINER

ISACA CISA Exam: Five Domains, Audit Scenarios, and a Practical Study Plan

Updated October 23, 2026. The ISACA CISA exam assesses candidates for the Certified Information Systems Auditor designation. It is not an examination administered by the […]

In this article

Updated October 23, 2026. The ISACA CISA exam assesses candidates for the Certified Information Systems Auditor designation. It is not an examination administered by the U.S. Cybersecurity and Infrastructure Security Agency, which shares the acronym. Candidates should use ISACA’s job-practice outline rather than treating a government vulnerability-management directive as the exam blueprint.

What the ISACA CISA exam assesses

CISA measures how an information systems auditor plans work, evaluates governance and controls, assesses technology changes, reviews operational resilience, and judges whether information assets are protected. A good auditor does not simply check whether a policy exists. The auditor connects a business risk to a control objective, obtains sufficient and appropriate evidence, tests how the control works, and communicates a finding in a way an accountable owner can act on.

According to ISACA’s current CISA content outline, the exam covers 150 questions across five domains. The current outline took effect in August 2024. ISACA’s exam candidate guide describes a four-hour assessment and reports outcomes on a scaled score from 200 to 800; a scaled score of at least 450 is required to pass. Candidates should confirm these details, the applicable examination guide and testing policies with ISACA before booking.

Know the five CISA domains and their different emphases

  • Domain 1 — Information Systems Auditing Process (18%). Risk-based audit planning, audit standards, sampling, evidence collection, testing, data analytics, reporting and audit-quality improvement.
  • Domain 2 — Governance and Management of IT (18%). Strategy alignment, organizational accountability, IT policies and standards, enterprise risk management, privacy, architecture, vendor management and performance monitoring.
  • Domain 3 — Information Systems Acquisition, Development and Implementation (12%). Business cases, project governance, development methods, control design, readiness testing, change and release management, data conversion and post-implementation review.
  • Domain 4 — Information Systems Operations and Business Resilience (26%). Production operations, service management, asset and configuration controls, incident and problem management, business impact analysis, continuity, backup and recovery.
  • Domain 5 — Protection of Information Assets (26%). Identity and access management, physical and environmental safeguards, encryption, endpoint and network security, cloud controls, security monitoring, incident response and evidence handling.

The percentages are relative coverage indicators rather than promises of an exact number of questions from each topic. Domain 4 and Domain 5 receive the greatest combined weight, but candidates still need to understand how planning and governance affect the audit conclusion. Practicing only technical security questions would leave substantial gaps in audit methodology and business judgment.

Domain 1: build an audit trail from risk to finding

Consider an organization that allows a development team to approve its own production deployments. A weak approach is to memorize that segregation of duties matters and stop there. The CISA perspective asks which conflicting functions exist, what risk they create, whether compensating controls operate, and which evidence can establish effectiveness during the audit period.

Begin with the audit objective and criteria. Identify the relevant process owners, understand the workflow, and select an appropriate testing method. Documentation may include approved access matrices, change tickets, code review records, deployment logs and independent approval evidence. A sample needs a rationale: the auditor should know what population it represents and whether it can support the proposed conclusion.

When evidence disagrees, record the inconsistency and seek clarification instead of treating one document as definitive. Findings should distinguish the condition observed, the rule or criterion involved, the potential impact and a practical recommendation. Strong audit work is evidence-driven rather than a contest to identify the largest number of minor exceptions.

Domain 2: connect technology controls to governance decisions

Governance questions often turn on who is responsible for a decision. Senior leaders approve risk appetite and strategy; business and technology managers implement practices within their responsibilities; auditors provide assurance without assuming management’s role. The existence of a policy does not prove that it is understood, enforced or monitored.

Imagine a new supplier hosting customer data. An auditor should examine due diligence, contractual and regulatory obligations, data classification, access rules, service-level metrics, incident notification and exit planning. If the contract is strong but no one monitors performance, the organization still has a governance and assurance gap. Conversely, extensive monitoring does not fix an unclear allocation of risk ownership.

Work with examples that combine governance, privacy, business goals and security controls. Ask what should be escalated, what can be accepted by an authorized risk owner and which matters need independent validation. Those distinctions are more durable than memorizing a framework label.

Domain 3: evaluate systems across the entire change lifecycle

Project audits are not limited to whether a new application launched on time. An auditor may need to evaluate requirements traceability, data migration integrity, configuration management, access controls, testing, release approval and operational readiness. A system can meet its feature targets while introducing unacceptable reporting or security risks.

For example, a finance-platform migration might successfully move transaction records but mishandle historical identifiers. The appropriate audit evidence could include reconciliation reports, exception handling, sample tracing, cutover approvals and results from post-implementation monitoring. Questions may ask which control should operate before release and which retrospective review is appropriate after the system becomes operational.

Distinguish management’s responsibility to design and operate controls from the auditor’s responsibility to evaluate them. A recommendation should be grounded in the business objective and observed risk, not in a preference for a particular implementation tool.

Domain 4: test operational resilience, not merely paperwork

Operational reviews connect daily controls to the organization’s capacity to deliver services. Change management, asset records, job scheduling, monitoring and incident response all affect resilience. A complete inventory is useful only if it is accurate enough to support security, maintenance and recovery decisions.

A business impact analysis identifies critical processes and the consequences of interruption. Recovery time and recovery point objectives express different constraints: one addresses acceptable restoration time, while the other addresses tolerable data loss. An auditor should assess whether proposed recovery arrangements, test results, dependencies and management approvals support those objectives. A policy that says “backups are performed” does not establish that restoration is feasible.

An audit of business resilience connects approved recovery objectives to restoration evidence, system dependencies, test exceptions and accountable remediation. The auditor should establish whether actual recovery meets the business requirement, record any limitations, and identify who will verify corrective action.

Domain 5: judge the effectiveness of protection controls

Access reviews, monitoring and encryption are common subjects, but CISA frames them as assurance problems. A control is not effective just because a security team can name it. An auditor must understand the objective, scope, ownership, operation, exceptions and supporting evidence.

For identity and access management, consider how privileges are requested, approved, provisioned, reviewed and removed. A quarterly access review may satisfy a written schedule while still failing if reviewers lack context or high-risk changes occur without timely controls. For encryption, verify not only the algorithm named in a standard but also key management, access restrictions, rotation policy and operational implementation where applicable.

Incident response evidence may include detection records, escalation timestamps, investigation notes and post-incident actions. An audit should evaluate whether the process is repeatable and appropriate to the organization’s risk. Avoid confusing vulnerability-management guidance issued by a regulator or government agency with ISACA’s certification domain requirements: the former may supply an example of applicable criteria, but it is not the CISA exam blueprint.

A practical CISA study workflow

Start with the five official domains and a diagnostic review. Map each missed question to both the tested concept and the reason the proposed answer was weak. Typical weaknesses include confusing a risk owner’s decision with an auditor’s recommendation, selecting insufficient evidence, treating a detective control as preventive, and prioritizing technical details when the question asks about governance.

Use one-page case studies for active recall. For each scenario, write the business objective, principal risk, relevant control, suitable evidence and most defensible next audit step. Rotate through audit planning, governance, implementation, operations and asset protection rather than studying one technical area in isolation. Review the official outline periodically so that topics receiving less personal attention are not overlooked.

Practice interpreting question language carefully. Identify the actor, the timing of the decision, what evidence already exists, and whether the question asks for the best, first or most important action. In a risk-based audit, the correct sequence often involves understanding business impact and gathering sufficient evidence before recommending a control or escalating a finding. Study why an answer is correct; do not learn answer keys without context.

When assessing readiness, use legitimate, current ISACA materials and realistic timing practice. Keep a record of missed domains and the reasoning errors you repeat. No study plan can guarantee a passing result, and the right preparation duration depends on prior audit and technology experience.

Passing the exam is not the same as earning the credential

ISACA permits candidates to sit the CISA exam before meeting the professional experience requirement. However, the certification application requires qualifying professional work experience, verification, ethics commitments and other issuer conditions. ISACA states a standard minimum of five years of relevant information systems audit, control or security experience, with specified application rules and possible substitutions subject to its current policies. Candidates who pass the exam have five years from the passing date to apply for certification.

After certification, maintaining the designation requires continuing professional education and compliance with professional standards. ISACA lists at least 20 CPE hours annually and 120 over a three-year reporting period. Check the most recent requirements rather than relying on a third-party summary when submitting an application or renewing.

CISA is most relevant when a career involves audit, controls assurance, governance or technology risk. The way CISA audit skills translate into professional responsibilities depends on whether someone can plan risk-based tests, evaluate evidence independently and communicate findings that a responsible owner can act on. An exam pass does not replace that judgment or qualifying work experience.

Final preparation priorities

Use the current ISACA content outline as the curriculum, practice scenario-based audit decisions, learn to distinguish management responsibilities from independent assurance, and be precise about what evidence supports a conclusion. Confirm exam format, scoring, booking eligibility and certification requirements with ISACA near your appointment date. A strong CISA candidate does not simply know security vocabulary; they can explain how an organization knows whether its information systems controls are working and what should happen when the evidence says they are not.