Study guide
6.2 Core Workflows and Decision Points
CISA Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CISA Orientation and Exam Strategy
1.1 Current CISA Exam Facts 1.2 Eligibility, Application, and Scheduling 1.3 Blueprint Domains and Weighting 1.4 Question Style and Score Report Thinking 1.5 Study Calendar and Practice Plan
2 Chapter 2: Information System Auditing Process
2.1 Information System Auditing Process Overview 2.2 Core Workflows and Decision Points 2.3 Scenario Practice for Information System Auditing Process 2.4 Common Traps in Information System Auditing Process 2.5 Practice Drills and Readiness Markers
3 Chapter 3: Governance and Management of IT
3.1 Governance and Management of IT Overview 3.2 Core Workflows and Decision Points 3.3 Scenario Practice for Governance and Management of IT 3.4 Common Traps in Governance and Management of IT 3.5 Practice Drills and Readiness Markers
4 Chapter 4: Information Systems Acquisition, Development, and Implementation
4.1 Information Systems Acquisition, Development, and Implementation Overview 4.2 Core Workflows and Decision Points 4.3 Scenario Practice for Information Systems Acquisition, Development, and Implementation 4.4 Common Traps in Information Systems Acquisition, Development, and Implementation 4.5 Practice Drills and Readiness Markers
5 Chapter 5: Information Systems Operations and Business Resilience
5.1 Information Systems Operations and Business Resilience Overview 5.2 Core Workflows and Decision Points 5.3 Scenario Practice for Information Systems Operations and Business Resilience 5.4 Common Traps in Information Systems Operations and Business Resilience 5.5 Practice Drills and Readiness Markers
6 Chapter 6: Protection of Information Assets
6.1 Protection of Information Assets Overview 6.2 Core Workflows and Decision Points 6.3 Scenario Practice for Protection of Information Assets 6.4 Common Traps in Protection of Information Assets 6.5 Practice Drills and Readiness Markers
7 Chapter 7: Final Review and Test Day
7.1 Timed Practice Strategy 7.2 Last-Week Review Map 7.3 Exam-Day Checklist 7.4 After the Exam and Next Steps
6.2 Core Workflows and Decision Points
Key Takeaways Explain This Topic AI
IAAA sequences every access decision: Identification, Authentication, Authorization, Accountability.
MFA combines two or more of: something you know, something you have, something you are.
MAC, DAC, RBAC, and ABAC differ in WHO decides access and on what basis.
The IAM lifecycle (provision, modify, recertify, deprovision) is where most audit findings live.
Least privilege and need-to-know limit access to the minimum required for the role and task.
Last updated: June 2026
The IAAA Access-Control Sequence
Every access decision the exam tests follows IAAA , in order:
Identification — the subject asserts a unique identity (username, user ID, badge number). Identity claims must be unique so actions trace to one person.
Authentication — the subject proves the claim using one or more factors : something you know (password, PIN), something you have (token, smart card, phone), or something you are (biometric fingerprint, iris, face).
Authorization — the system grants the authenticated subject only the rights their role and policy permit.
Accountability — actions are logged and attributable to the unique identity, supporting non-repudiation and investigation.
Multi-factor authentication (MFA) requires two or more factors from different categories. Two passwords are not MFA; a password plus a one-time code from a hardware token is. Single sign-on (SSO) lets a user authenticate once to reach many systems — convenient and it reduces password fatigue, but it concentrates risk, so the SSO credential becomes a high-value target requiring strong MFA.
Authentication strength order
- Factor type Examples Audit note
- Something you know Password, PIN, passphrase Weakest alone; subject to guessing, phishing, reuse
- Something you have Smart card, OTP token, phone app Lost/stolen risk; pair with a PIN
Something you are Fingerprint, iris, facial, voice Strong; watch false acceptance rate (FAR) vs. false rejection rate (FRR)
For biometrics, the crossover error rate (CER/EER) — the point where FAR equals FRR — is the standard measure of accuracy; a lower CER means a more accurate system.
Access-Control Models and the IAM Lifecycle
CISA tests four authorization models by who decides access:
Mandatory Access Control (MAC) — the system enforces access from security labels/classifications (e.g., Secret, Confidential); owners cannot override. Strongest, used in military and high-regulation settings; supports strict need-to-know .
Discretionary Access Control (DAC) — the resource owner grants access at their discretion. Flexible but error-prone; access can sprawl.
Role-Based Access Control (RBAC) — permissions attach to roles/job functions , and users inherit them through role membership. Scales well and eases segregation of duties.
Attribute-Based Access Control (ABAC) — decisions use attributes (department, location, time, device) for fine-grained, dynamic policy.
Two principles govern every model: least privilege (grant the minimum access needed to do the job) and need-to-know (limit access to the specific data the task requires). Together they shrink the attack surface and limit insider damage.
The identity and access management (IAM) lifecycle
Most access findings arise from a broken lifecycle. The auditor traces each stage:
- Stage Control objective Common finding
- Provisioning Access matches an approved request and role Access granted without authorization
- Modification Role changes trigger access review Privilege creep as users move roles but keep old rights
- Recertification Owners periodically attest access is still needed Reviews skipped or rubber-stamped
- Deprovisioning Access removed promptly on termination/transfer Orphan/terminated accounts remain active
The highest-risk failure is delayed deprovisioning : a terminated employee retaining access for days creates a window to steal or damage assets. Access should be revoked immediately on termination, ideally automatically via HR-driven feeds. Privileged accounts (administrators, root) demand extra control — separate logging, privileged access management (PAM) , and just-in-time elevation — because their actions can disable other controls.
Segregation of Duties and Federated Identity
Access design is incomplete without segregation of duties (SoD) — splitting a sensitive process so no single person can both perpetrate and conceal an error or fraud. The classic example is preventing the same user from creating a vendor and approving its payment. Where headcount makes full SoD impractical, the auditor expects compensating controls such as independent review, mandatory vacations, job rotation, and detailed activity logging. RBAC supports SoD because conflicting roles can be flagged and blocked at assignment.
Federation, directories, and password controls
Large environments centralize identity in a directory service (such as LDAP/Active Directory) and extend trust across organizations through federated identity using standards like SAML , OAuth 2.0 , and OpenID Connect — a user authenticates with their home identity provider and accesses a partner's application without a separate password. The auditor confirms the federation trust is properly scoped and that token issuance and expiry are controlled.
Password and credential controls remain heavily tested:
- Control What the auditor verifies
- Length and complexity Minimum length enforced by the standard
- Storage Passwords stored hashed and salted, never in cleartext
- Lockout Accounts lock after a defined number of failed attempts
- Rotation/reuse History prevents reuse; rotation aligns with policy
- Default credentials Vendor defaults changed before production use
- Common access findings
The most common Domain 5 access findings cluster around the lifecycle: shared or generic accounts that defeat accountability, dormant accounts never disabled, excessive privileges beyond least privilege, terminated users still active, and access reviews that are skipped or signed off without genuine scrutiny. For each, the auditor's best recommendation is the control that restores unique attribution , enforces least privilege , and produces a reviewable trail .