IT Audit Fundamental Certificate — Lesson 4: Findings, Recommendations, Reporting, Follow-Up, and Quality Review

Learning Objectives

• Explain the roles, information, criteria, dependencies, and decision points governing audit findings and root causes.
• Implement or assess recommendations, audit reporting, and follow-up review using controlled evidence and acceptance criteria.
• Evaluate the condition where the activity is accepted before audit reporting and follow-up review demonstrate repeatable operation, accountable ownership, and effective handover and select a proportionate corrective response.

Detailed Topics

• audit findings applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• root causes applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• recommendations applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• audit reporting applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• follow-up review applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.

Instructor Demonstration

The instructor traces a junior auditor reviewing a technology process while maintaining objectivity, evidence quality, clear findings, and constructive follow-up. The walkthrough connects frameworks, processes, tools, decisions, and evidence captured in the IT audit plan, test sheets, evidence file, and final audit summary. It also tests the exception where the activity is accepted before audit reporting and follow-up review demonstrate repeatable operation, accountable ownership, and effective handover.

Hands-On Exercise

Complete a controlled ISACA-aligned exercise covering Findings, Recommendations, Reporting, Follow-Up, and Quality Review and preserve the verified result in the IT audit plan, test sheets, evidence file, and final audit summary.

1. Confirm scope, roles, criteria, prerequisites, information sources, dependencies, and acceptance conditions.
2. Execute the governance, risk, audit, security, data, cloud, or technology workflow while recording decisions and evidence.
3. Test normal behavior, one boundary condition, and the stated exception using a controlled scenario.
4. Document findings, corrections, ownership, retest criteria, communication, and operational handover.

Scenario Analysis

• Identify which role, process, objective, control, data source, or decision most strongly influences audit findings.
• Compare two defensible responses and explain governance, risk, audit, security, privacy, operational, and business trade-offs.
• Determine how the IT audit plan, test sheets, evidence file, and final audit summary should be approved, retained, reviewed, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check scope, criteria, ownership, data quality, process sequence, policy alignment, version compatibility, dependencies, status, and evidence separately. Treat “the activity is accepted before audit reporting and follow-up review demonstrate repeatable operation, accountable ownership, and effective handover” as a hypothesis until records, interviews, configurations, calculations, and retest outcomes confirm the cause.

Validation Checklist

• Required roles, processes, criteria, controls, information, approvals, and dependencies are present.
• The IT audit plan, test sheets, evidence file, and final audit summary connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, documentation, communication, and operational handover are complete.

Lesson Outcome

Learners can apply Findings, Recommendations, Reporting, Follow-Up, and Quality Review, explain the resulting governance, risk, audit, security, data, or operational behavior, and defend the outcome through the IT audit plan, test sheets, evidence file, and final audit summary.