What audit committees change about penetration testing reporting
Penetration testing reports written for engineers rarely satisfy audit committees, and this session shows how to make findings credible to both audiences.
Session Details
Penetration testing reports are often technically sound but poorly received by senior decision-makers. Nowhere is this more apparent than when penetration test reports are presented to Audit and Risk Committees, where unclear risk models, inconsistent ratings, and audience-agnostic reporting can quickly erode confidence.
This has become a more pressing issue with the introduction of the Cybersecurity Topical Requirement under the Global Internal Audit Standards, which became effective in early 2026. Cyber security is now a mandatory assurance topic for Internal Audit when it is in scope, meaning penetration testing results are increasingly relied upon as audit evidence and presented to governance forums. As a result, more security practitioners and testers are finding themselves required to produce reports that are understandable and actionable for audit, risk, and board-level stakeholders, in order to inform decision-making.
This talk draws on real-world experience delivering penetration testing as part of Internal Audit programs and compares this with penetration testing performed for delivery-focused contexts, such as pre-release penetration testing assessments. While the underlying testing methodologies are the same, the reporting requirements are not. Audit Committees require consistency, clearly defined and consistently applied risk ratings, explicit linkage to governance and control objectives, and a clear articulation of residual risk. By contrast, software engineers and delivery teams require detailed technical evidence of weaknesses, clear reproduction steps, tooling context, and practical guidance on remediation.
The session explores common reporting failures in audit-facing penetration testing reports, including poorly defined risk models, inconsistently applied severity ratings, and reports written without a clear understanding of the decision the audience is expected to make. Attendees will leave with practical lessons for writing penetration testing reports that are credible to Audit Committees, useful to delivery teams, and aligned with the increasing expectations placed on cyber security assurance.
There's More Where This Came From
Browse hundreds of sessions and build an agenda around the topics that matter to you.








