Assurance programmes and independent verification: the arrangement behind the checks
How separate checks become one assurance programme, and why independence carries it.

An assurance programme is the arrangement that turns many separate checks into one coverage claim: internal audit engagements, second-line monitoring, management attestations, management-system audits and external assessments, each producing something different, scheduled and read together. The individual checks are the L1–L4 material; the programme that coordinates them is what this sheet owns.
Independence is the load-bearing element: a check’s only value is its ability to disagree with the people who built what it examines. Remove it and the programme still produces documents, but stops producing assurance.
The coordination model: three lines, one arrangement
The IIA’s Three Lines Model is the reference arrangement. The governing body’s roles are “integrity, leadership, and transparency” (line 178). Inside management, “First line roles are most directly aligned with the delivery of products and/or services to clients” (line 129) — the roles that own the risk by owning the delivery. Second line roles are a complementary check: “Some second line roles may be assigned to specialists to provide complementary expertise, support, monitoring, and challenge to those with first line roles” (lines 132–134). The third line differs in kind, not degree: “Internal audit provides independent and objective assurance and advice on the adequacy and effectiveness of governance and risk management” (lines 142–143), and “A defining characteristic of third line roles is independence from management” (line 372).
Independence is not separation. Internal audit’s “independence from the responsibilities of management is critical to its objectivity, authority, and credibility” (lines 150–151), yet “independence does not imply isolation” (line 315); the lines must coordinate “to ensure there is no unnecessary duplication, overlap, or gaps” (lines 320–321) — the programme in miniature.
How a programme is composed, and what its parts produce
A programme is a set of engagements with one production line, and the IIA Standards fix the parts: “Performing internal audit services requires internal auditors to effectively plan engagements, conduct the engagement work to develop findings and conclusions, collaborate with management to identify recommendations and/or action plans that address the findings, and communicate with management and the employees responsible for the activity under review throughout the engagement and after it closes” (line 118). Each engagement is planned and bounded: “Internal auditors must establish and document the objectives and scope for each engagement” (Standard 13.3, line 2043), against criteria identified for that scope (Standard 13.4, lines 2077–2078). Standard 14.4 assumes disagreement: “If internal auditors and management disagree about the engagement recommendations and/or action plans, internal auditors must follow an established methodology to allow both parties to express their positions and rationale and to determine a resolution” (lines 2235–2237). A route for disagreement is what keeps a programme challengeable. Standard 15.1 fixes what the communication carries, including “A conclusion regarding the effectiveness of the governance, risk management, and control processes of the activity reviewed” (lines 2290–2291). Standard 15.2 closes the loop separately: the confirmation involves “Inquiring about progress on the implementation”, “Performing follow-up assessments using a risk-based approach”, and “Updating the status of management’s actions in a tracking system” (lines 2327–2329).
governing body sets appetite, owns oversight accountability
first line runs delivery, owns the risk management attestation
second line expertise, monitoring, challenge analysis on risk
third line independent objective assurance engagement conclusion
external/assessor contracted independence assessment findings
one programme: every part planned, communicated, and tracked to closure
Internal audit as a function, and the finding it produces, belong to the L4 sheet of this area; this sheet owns where they sit in the programme.
Auditing a management system, and who may assess
The management-system side has its own programme discipline. ISO 19011:2026 states that “ISO 19011 is an international standard that provides guidelines for auditing management systems” (line 18); it is Edition 4, “Publication date: 2026-05” (lines 38, 40), replacing the withdrawn 2018 edition (line 46). Its page is explicit about what an audit programme does not produce: “No, ISO 19011 provides guidance but does not itself lead to certification” (line 28).
The assessor side names who may sit in the programme. SP 800-53A Rev. 5 states the purpose of assessment output — “The findings identified by assessors are used to determine the overall effectiveness of security and privacy controls associated with systems and their environments of operation and to provide credible and meaningful inputs to the organization’s risk management process” (lines 351–353) — and lists the roles, among them “Inspectors General, system evaluators, assessors, independent verifiers/validators, auditors, analysts, system owners, common control providers” (lines 648–649). SP 800-53 Rev. 5 makes independence a control in its own right: CA-2(1) requires organisations to “Employ independent assessors or assessment teams to conduct control assessments” (line 6427), and defines impartiality as being “free from any perceived or actual conflicts of interest” (lines 6430–6431). CA-7(1) carries the same requirement into ongoing monitoring (lines 6823–6824).
Where independence is required by name
One legal text makes the arrangement mandatory rather than advisable. DORA, Article 24(4), requires that “Financial entities, other than microenterprises, shall ensure that tests are undertaken by independent parties, whether internal or external” (line 835). Both routes are permitted, but the tester must not be the builder: conflicts of interest must be “avoided throughout the design and execution phases of the test” (line 835). The testing programme itself is the neighbouring sheet’s subject; this sheet takes only the independence condition attached to it.
Where a programme stops being assurance
Four failures turn the arrangement into paper. An assurance map whose lines overlap is coverage on paper and re-work in practice. An internal verifier who sits inside the team that built the control is independence on paper: the SP 800-53 definition turns on conflicts of interest, not on job titles. A programme that reports only summary results cannot be challenged, because nobody outside it can reconstruct what produced the figure. And the number of findings is not a measure of assurance: many findings and no conclusion on effectiveness is activity, not assurance.
The neighbours own their parts — the internal-audit function and evidence mechanics the L4 sheets, the acceptance decision the risk-acceptance sheet, the testing programme the crisis-scenarios sheet, the conversion of findings into change the improvement sheet — and this sheet owns only how those parts are arranged and kept independent.
Level and prerequisites
L5 — specialist: the sheet integrates checks that L1–L4 already define and asks who may perform them, under what independence, and how they are arranged together. Prerequisites: the L1 vocabulary of control, evidence and audit trail; the L2 records (control objectives, criteria, the risk and exception register); the L3 processes (traceability, remediation and residual risk, change); and the L4 sheets on internal audit, on evidence, and on documentary conformity versus operational effectiveness.
Where to go next
- Knowledge — the Knowledge register this sheet belongs to.
- Cybersecurity Governance — the macro-area.
- Assurance — the node this sheet sits in.
References
- IIA — The IIA’s Three Lines Model (2020) — the governing-body, first-, second- and third-line role definitions and the independence-not-isolation clause.
- IIA — Global Internal Audit Standards (2024) — the Domain V description and Standards 13.3, 13.4, 14.4, 15.1 and 15.2.
- ISO — ISO 19011:2026 store page — the edition, publication date, life-cycle succession and the certification statement.
- NIST — SP 800-53A Rev. 5 — who identifies assessment findings, what they are used for, and the roles listed for assessment and monitoring.
- NIST — SP 800-53 Rev. 5 — CA-2(1) independent assessors and CA-7(1) independent assessment.
- EU — Regulation (EU) 2022/2554 (DORA), Article 24(4) — the independent-party requirement for testing.