ISACA CISA: Reporting Audit Findings Clearly
A useful IT audit finding tells management what condition was observed, which criterion it failed, why that matters and what action can reasonably reduce the risk. Reporting is not the same as reproducing fieldwork notes. An audit report should help decision-makers understand a control weakness well enough to assign ownership and verify remediation.
For CISA preparation, connect reporting to the evidence gathered during planning and testing. ISACA emphasizes professional judgment and reliable audit evidence; conclusions should be proportionate to what the audit actually demonstrated.
Use a finding structure that supports review
Begin with the observed condition and the expected criterion, such as an approved access-review procedure or a documented configuration baseline. Add the consequence of the gap in specific operational terms. A vague statement such as “access management needs improvement” does not explain which identities, control step or systems were tested.
Separate the immediate observation from an inferred root cause. If access requests lacked approval evidence, that is an observation. The reason might be an incomplete workflow, a failure to retain records or an unsupported exception; the audit team should not present one possible explanation as fact without testing it.
Make the evidence trail reproducible
A finding must identify the period, population, selection method, sample or test result, and exceptions relevant to its conclusion. If a sample contains three exceptions, say which controls were tested and how broadly the finding applies. Do not imply the entire enterprise failed when the evidence only covers one application and one review period.
The evidence-quality review gives context to reliability, provenance, completeness and independence. Audit workpapers should permit another qualified reviewer to trace a conclusion back to the underlying source without exposing sensitive records unnecessarily.
Assign severity based on plausible impact
Severity is a judgment about risk, not a synonym for how surprising an exception appears. Consider the asset and data sensitivity, likelihood of misuse, strength of compensating controls, time exposed and existing business impact. A missing approval for a privileged production account can require a different response from the same paperwork gap in a test environment.
Explain the reasoning briefly enough that management can challenge assumptions. Where uncertainty is material, document it. A disciplined report may describe a confirmed control design gap while acknowledging that no harmful transaction was observed in the tested period.
Recommendations should be owned and testable
Recommend the control outcome rather than prescribing an unproven product purchase. For example: require documented authorization before privileged access is granted, record the approver and reason, and review active privileges on a defined cadence. Management can then choose a suitable implementation while remaining accountable for the result.
Each agreed action needs an owner, a due date and a way to demonstrate completion. A revised policy document alone may not prove that control operation improved; a later sample of actual transactions or access changes may be necessary.
Close the loop without rewriting history
After management responds, report any unresolved disagreement accurately. Do not reduce a finding’s severity solely because remediation was promised. Once the action is complete, independently test whether the new process operated effectively during a relevant period.
Strong audit reporting preserves the original observation, the management response and the validation record. It connects directly to risk-based audit scoping: the final message should stay within the systems and risks the audit actually assessed.