In many listed companies the audit committee, not the full board, is where cyber risk actually gets examined, yet most cyber reporting is written for a general board audience and gives audit committee members little they can test. This briefing is for audit committee chairs and members, company secretaries who set the committee agenda, and the CISOs, chief audit executives and finance leaders who report to it. It explains why cyber oversight has landed on the audit committee, how that role differs from the full board's, the questions to ask, the evidence to expect and a 90-day plan for strengthening oversight. For reporting to the whole board, see the Board Cyber Risk Reporting Guide.
The risk in one paragraph
Cyber incidents now reach the audit committee's core territory directly: they disrupt financial systems and reporting, create disclosure obligations with short deadlines, trigger questions about the effectiveness of internal controls and can lead to material losses that must be estimated and reported. The committee is often given colourful dashboards rather than evidence, and it rarely sees the controls that attackers most often exploit, such as service accounts, API keys and other non-human identities with standing access to financial systems. The risk is not only a breach. It is that the committee signs off disclosures and control statements that it cannot support if a regulator, auditor or shareholder later asks how oversight worked.
Why this is an audit committee issue now
Three developments have pulled cyber into the audit committee's remit.
Disclosure rules name board oversight
The US Securities and Exchange Commission's 2023 cybersecurity disclosure rules require registrants to describe the board's oversight of cybersecurity risks and management's role and expertise in assessing and managing them, under Regulation S-K Item 106, for fiscal years ending on or after 15 December 2023. Material incidents must be disclosed on Form 8-K Item 1.05, generally within four business days of the company determining that an incident is material, and that determination must be made without unreasonable delay after discovery. Foreign private issuers have comparable obligations through Forms 20-F and 6-K. When a company describes a committee as responsible for cyber oversight, that description is a public statement the committee must be able to stand behind.
Control effectiveness declarations
In the UK, Provision 29 of the FRC's UK Corporate Governance Code 2024 applies to financial years beginning on or after 1 January 2026. It asks boards to declare the effectiveness of their material internal controls, covering financial, operational, reporting and compliance controls. The Code does not mention cyber specifically and each board decides what is material, but the FRC notes that for many companies principal risks will include cyber or IT security, and its supporting Guidance considers cyber risk. In practice, audit committees are doing the preparatory work for the board's declaration, which means asking whether access controls over key systems, including machine access, are material controls.
Management accountability in wider regulation
Frameworks such as NIS2 in the EU place responsibility for approving and overseeing cyber risk measures on management bodies, and the NIST Cybersecurity Framework 2.0 added a Govern function whose Oversight category (GV.OV) expects cybersecurity risk management strategy outcomes to be reviewed and adjusted. Whichever regime applies, the expectation is the same: oversight must be active, informed and recorded.
What the audit committee owns and what it does not
Confusion about the committee's role is the most common source of weak oversight. A clear split helps.
| Area | Audit committee | Full board or risk committee | Management |
|---|---|---|---|
| Cyber strategy and risk appetite | Considers impact on controls and reporting | Sets appetite and approves strategy | Proposes and executes |
| Internal controls over key systems | Oversees effectiveness and assurance | Makes any formal declaration | Designs and operates controls |
| Incident disclosure | Oversees the materiality process and disclosure controls | Approves material disclosures where required | Assesses and drafts |
| Internal audit coverage of cyber | Approves the plan and reviews results | Receives summary | Responds to findings |
| External auditor's IT findings | Reviews and tracks remediation | Receives summary | Remediates |
Write the split into the committee's terms of reference and into the board's own description of oversight. If a separate risk or technology committee exists, record how the two committees share information so nothing falls between them.
Five questions for the board to ask
These questions are framed for the audit committee, which usually asks them on the board's behalf.
- Which cyber controls do we treat as material, and why? Expect a short list linked to principal risks and key financial and operational systems, not a copy of a framework. Access control over financial systems, privileged access, backup and recovery, and the identities used by automation should all be considered.
- How do we decide whether an incident is material, and how quickly? Expect a documented process with named decision makers, criteria that include quantitative and qualitative factors, and evidence that it has been rehearsed against the four business day window where SEC rules apply.
- What independent assurance do we have over those controls? Expect internal audit coverage in the risk-based plan, external auditor IT general control findings, and any third party testing, with dates and outcomes.
- Do we know every identity, human and non-human, that can change financial data or systems? Expect an inventory that includes service accounts, API keys, integration tokens and AI agents, with owners and last review dates.
- Which findings are overdue, and what is the residual risk while they stay open? Expect an ageing report of cyber findings from all assurance sources, with accepted risks signed by an accountable executive.
Red flags in management answers
- Reporting consists of activity counts (phishing emails blocked, patches applied) with no link to material controls or risk appetite.
- The materiality process has never been exercised, or the first time it will be tested is a real incident.
- Assurance over cyber comes only from the team that runs the controls.
- Access reviews cover employees but exclude service accounts, API keys and third party integrations.
- The same findings appear in successive external auditor management letters.
- Management cannot say who would brief the committee in the first hours of a major incident.
What good looks like
- A defined oversight model. Terms of reference state what the committee oversees on cyber, how often and with what inputs, and the board's public description of oversight matches it.
- Combined assurance. A single view shows which assurance provider (management, internal audit, external audit, specialist testers) covers each material cyber control, so gaps and overlaps are visible.
- Evidence-based reporting. Each committee pack includes a small set of stable metrics, the status of material controls, overdue findings and incidents assessed for materiality, with commentary on trends.
- Rehearsed disclosure. The incident materiality process has been tested in a tabletop that included finance, legal, investor relations and at least one committee member.
- Machine identity in scope. Non-human identities with access to financial systems are inventoried, owned, reviewed and covered by assurance work. See Board Briefing: NHI Risk.
- Committee capability. Members receive regular cyber education and can access independent expert advice when they need it.
Where to invest first
- Define material cyber controls. Without this list, neither control declarations nor assurance planning can be targeted.
- Build the combined assurance map. It is cheap, uses existing information and immediately shows where the committee is relying on management alone.
- Rehearse the materiality decision. One well-run tabletop exercise reduces the largest disclosure risk.
- Bring non-human identities into access governance. Service accounts and API keys often outnumber people and are rarely reviewed, yet they routinely hold access to finance and ERP systems.
- Agree a reporting pack. Fix the metrics for at least four quarters so trends mean something.
Metrics to track
| Metric | Why it matters to the committee |
|---|---|
| Material cyber controls with current independent assurance (%) | Supports any control effectiveness declaration |
| Overdue high-rated cyber findings, by age | Shows whether known weaknesses are being fixed |
| Privileged and non-human identities on financial systems reviewed in the last quarter (%) | Tests a control auditors and attackers both care about |
| Incidents assessed for materiality and time taken to decide | Shows the disclosure process works under time pressure |
| Recovery tests of critical financial systems completed and passed | Evidence that operations and reporting can resume |
| Third parties with access to financial data assessed in the last year (%) | Covers supply chain exposure in the control environment |
For a structured approach to putting financial values on cyber scenarios, see the Cyber Risk Quantification Guide.
A 90-day plan
Days 1 to 30: clarify
- Review terms of reference and the board's published description of cyber oversight, and align them.
- Ask management for a draft list of material cyber controls and the principal risks they address.
- Ask the chief audit executive for current and planned cyber coverage in the internal audit plan.
Days 31 to 60: map
- Receive the combined assurance map and identify material controls with no independent assurance.
- Agree the standing metrics for the committee pack.
- Request an inventory of identities with access to financial systems, explicitly including service accounts, API keys and integrations.
Days 61 to 90: test
- Run a materiality tabletop exercise with finance, legal, investor relations and a committee member.
- Adjust the internal audit plan to cover the largest assurance gaps.
- Record the committee's conclusions and follow-up actions in the minutes, so the oversight trail exists if it is ever examined.
Working with internal and external audit
The audit committee's distinctive advantage over the full board is its direct relationship with both assurance providers. Use it deliberately.
Internal audit
The committee approves the internal audit plan, so it can shape cyber coverage directly. Ask the chief audit executive how cyber is assessed in the risk-based plan, how often the most significant cyber risks are audited, and whether the function has the skills to do so or relies on co-sourced specialists. Where the internal audit function follows the Institute of Internal Auditors' Global Internal Audit Standards, the IIA's Cybersecurity Topical Requirement sets a baseline for how in-scope cyber engagements should be performed; ask how the function is meeting it. Private sessions with the chief audit executive, without management present, are the right place to hear concerns about access to information or pressure on findings.
External audit
External auditors test IT general controls that support financial reporting: access, change management and operations over in-scope systems. Their findings are often the most concrete evidence the committee receives about cyber control effectiveness. Ask the external auditor which IT general control deficiencies were found, whether any involved privileged or system accounts, and how management's remediation compares with prior years. Repeated findings on access to financial systems are a signal that the control environment, not just a single control, needs attention.
Specialist testing
Penetration tests, red team exercises and recovery tests are commissioned by management, but the committee should know when they happen, what was in scope and what was found. Ask that significant results reach the committee in summary, with remediation tracked alongside audit findings in a single register.
Where identity fits
Most of the cyber controls an audit committee cares about are identity controls in disguise: who can post journal entries, who can change payment details, who can alter system configuration, and who can disable logging. Increasingly the answer is not a person. Batch jobs, integration platforms, robotic process automation, CI/CD pipelines and AI agents all use non-human identities with standing access to finance systems, and they are often excluded from user access reviews and segregation of duties analysis. Ask management to show that these identities are inventoried, owned, least-privileged and reviewed, and ask internal audit whether its work covers them. The Internal Audit for Cybersecurity Guide describes how audit teams bring this into scope.
Common failure patterns
- Oversight by presentation. The CISO presents once a year, questions are general and nothing is recorded that shows challenge.
- Two committees, no handover. A risk committee discusses cyber strategy and the audit committee discusses controls, but neither sees the other's material.
- Public statements ahead of practice. Annual report language describes oversight that the minutes cannot evidence.
- Materiality left to the security team. Disclosure decisions are treated as technical rather than involving finance and legal from the start.
- Machine access ignored. Controls testing covers human users and misses the service accounts and keys that touch the same systems.
Practitioner checklist
- Terms of reference define the committee's cyber oversight role and its interface with any risk committee.
- The board's public description of cyber oversight matches what the committee actually does.
- A list of material cyber controls exists and is linked to principal risks.
- A combined assurance map shows independent coverage of each material control.
- The incident materiality process is documented, owned and rehearsed.
- Committee packs carry stable metrics, overdue findings and incidents assessed for materiality.
- Non-human identities with access to financial systems are inventoried, owned and reviewed.
- Committee members receive regular cyber education and can call on independent advice.
Standards and references
- SEC: Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure fact sheet
- FRC: UK Corporate Governance Code
- NIST: The NIST Cybersecurity Framework (CSF) 2.0
- EUR-Lex: Directive (EU) 2022/2555 (NIS2)
How NHI Mgmt Group can help
We provide independent assessments of identity and non-human identity controls, board and audit committee briefings, and support for bringing machine identities into control frameworks and assurance plans. Our NHI Foundation Level Training Course helps security, GRC and audit teams understand machine credentials. Contact us to arrange a briefing.
Related NHI Mgmt Group resources: Board Cyber Risk Reporting Guide · Cyber Compliance and Assurance · Internal Audit for Cybersecurity Guide · Board Briefing: NHI Risk