Blog

CISA Domain 1.9: Reporting and Communication Techniques

CISA Domain 1.9: communicating results, condition-criteria-cause-effect findings, report contents, documentation, follow-up and report types.

Your evidence supports a serious control failure, and management asks you to drop the finding. Do you? This lesson covers CISA Domain 1, Section 1.9: how an IS auditor communicates supported results to the people who need to act, and follows through until the risk is addressed.

1.9.1 Communicating audit results

Audit reporting communicates the supported results of the work. Discussion with management can validate facts and clarify actions, but audit is responsible for its conclusion. Communicate what is known accurately, distinguish uncertainty, and keep working to support the conclusion.

Situation Appropriate approach
Suspicious access, unknown cause or extent Corroborate, assess exposure, investigate before claiming a proven breach
Confirmed serious control weakness Communicate promptly; establish extent, cause and impact for the final conclusion
Ongoing harmful activity Use defined escalation or incident procedures without waiting for the final report
Management disputes verified facts Review its evidence, correct inaccuracies, document unresolved disagreement fairly
Management accepts excessive residual risk Confirm authority and rationale, document, escalate through audit leadership

Prompt communication does not eliminate the need for evidence.

1.9.2 Audit report objectives

An audit report answers the audit objective, explains significant exposure, presents conclusions and recommendations, and records agreed actions. It also provides a reference for oversight and follow-up. Its usefulness depends on accurate evidence, a clear scope, and a conclusion the reader can understand.

1.9.3 Audit report structure and contents

A finding explains the gap between what is happening and what is required, why it matters, and what should change.

Element Leaver access example
Condition Three sampled payroll accounts remained active beyond the removal deadline
Criteria Policy requires removal within the defined period after termination
Cause HR notifications did not reach the access team through a monitored workflow
Effect or risk Former staff could retain access to payroll information or functions
Recommendation Monitored HR to IT notification, reconcile leavers, verify closure
Management action Owner, agreed action, completion date, any interim measure

Keep a suspected cause separate from a cause supported by evidence. If the reason is unknown, say so and recommend analysis rather than inventing a convenient explanation.

  • Closing discussion: checks facts and obtains responses, owners and realistic dates. Management's agreement does not determine whether a supported material finding is reported.
  • Severity: a control deficiency is a weakness in design or operation. Significant deficiency and material weakness can have specific definitions in particular frameworks. Neither the number of exceptions nor a dramatic label sets severity by itself.
  • Report contents: objective, scope and period, criteria, methods, limitations, significant findings, overall conclusion, management actions, owners and dates. A balanced report recognizes effective controls too.
  • Detail for the reader: an interim communication flags a serious issue early, a restricted technical appendix covers sensitive vulnerabilities, and minor local matters may be communicated separately.
  • Exit meeting: budget or coordination needs may affect timing; they do not remove a significant finding.

1.9.4 Audit documentation

Maintain the scope and plan, procedures, evidence, findings, conclusions, report and supervisory review, with dates, authorship, cross-references and version control. Restrict access, follow approved retention rules, and suspend destruction when preservation is required. Do not assume an external requester is entitled to working papers; obtain authorization and legal advice first.

1.9.5 Follow-up activities

Remediation is management's action to correct the weakness. Follow-up is audit's assessment of that response. The extent depends on significance: a high-risk failure may need configuration inspection and retesting, not just an owner's statement. If management accepts risk, document the decision and authority, and escalate excessive exposure through audit leadership. Do not suppress a supported finding or take over management's decision.

Memory aid: what is happening, what should happen, why the gap exists, why it matters, and what action addresses it.

1.9.6 Types of IS audit reports

Engagement Reporting distinction
Examination Reasonable-assurance conclusion or opinion
Review Limited-assurance conclusion, not equivalent to an examination
Agreed-upon procedures Procedures and factual findings, no assurance opinion
Internal IS audit Agreed scope, significant findings, conclusion and management actions

For service reports, SOC 1, 2 or 3 describes the subject; Type 1 or Type 2 describes the time dimension (see Section 1.2).

Practice questions

1. At the exit meeting, management disagrees with a finding the IS auditor has supported with sufficient evidence. What is the BEST course of action? A. Remove the finding to preserve the working relationship B. Postpone the final report until management agrees C. Report the finding and record management's view fairly D. Rewrite the finding using management's description

Answer: C. Management disagreement does not require removing a supported finding. Record the response fairly and keep audit's conclusion.

2. Management reports that a high-risk access control failure has been remediated. Which evidence BEST supports closing the finding? A. A signed statement from the action owner B. Inspection of the configuration and a retest of the control C. An updated procedure approved by the IT director D. Minutes of the meeting where the fix was discussed

Answer: B. Closing a high-risk finding needs evidence that the action works in operation, proportionate to the risk.

Keep going

Free study material. Not affiliated with or endorsed by ISACA. CISA is a registered trademark of ISACA.

Muhammad Aamir
Muhammad Aamir
Technology risk and digital transformation leader, co-founder of CertPrepX, author and educator. More explainers on YouTube.

Certifications of Muhammad Aamir

Mirak X | mirakx.com
Free books
CISA Study GuideFree PDF · 352 pages CISA Video Course ↗Free full lessons on YouTube CAF-3 DSR Study GuideFree PDF · 457 pages CAF-3 DSR Exam PrepMCQs, mocks, AI marking CertPrepX ↗CISA practice & mock exams