The third line of defence is the independent audit function that tests whether AML governance and controls are designed and operating effectively. It should not run the controls it reviews; its role is to provide independent assurance, challenge weak evidence and report findings to senior management and the board.
What the Third Line of Defence Actually Does
The third line of defence is the independent assurance function in a financial crime or control environment. It does not own day-to-day operations; instead, it checks whether the first and second lines have designed, documented, and operated controls that are fit for purpose.
Its value comes from independence. The function must be able to challenge evidence, test conclusions, and report issues without being responsible for the controls under review. That separation is what makes the assurance credible to senior management and the board.
Where It Sits in the Three-Lines Model
The model is a governance structure, not a job title. The first line runs the business and executes controls, the second line sets oversight and monitoring expectations, and the third line provides independent review. In practice, the third line often maps to internal audit, while the first and second lines remain responsible for control ownership and remediation.
That placement matters because the third line should not be used as an extra control owner or a workaround for weak operational discipline. If audit starts operating controls, it loses the ability to independently evaluate whether those controls actually work.
What Independent Assurance Covers
Third-line review usually focuses on control design, operating effectiveness, issue validation, evidence quality, and management escalation. In an AML context, that includes whether transaction monitoring, customer due diligence, sanctions screening, alerts, and case management are governed consistently and whether exceptions are being handled properly.
Good assurance looks beyond paperwork. It asks whether the control framework is complete, whether evidence is reliable, whether findings are repeatable, and whether the organisation can show that weak controls are identified and tracked through to closure.
How the Role Supports Governance and Accountability
The third line helps senior leaders understand whether the organisation can trust its own control environment. It provides a channel for independent challenge when management is overconfident, controls are inconsistently applied, or remediation has stalled.
That challenge function is especially important when decisions depend on the quality of the control environment, not just on whether policies exist. A strong third line improves accountability by making weaknesses visible to the board and by preventing self-assessment from becoming self-certification.
Risk and Threat Considerations
The main risk is role confusion: if the third line starts owning controls, independence weakens and assurance becomes less credible. Over time that can leave serious control gaps undiscovered, especially in environments where management relies on audit to “fix” rather than test. For AML and other regulated controls, that creates exposure to regulatory findings, repeat issues, and false confidence in the control environment.
Failure mechanism: The assurance function becomes operationally involved in the very controls it is meant to evaluate, so it can no longer give an unbiased view of design or performance. Poor evidence standards, unmanaged remediation, and weak issue escalation then persist because no truly independent review is left to challenge them.
Impact: Problems can remain hidden until they surface in regulatory review, internal loss events, or repeated audit findings. The organisation may also miss patterns of control failure that only become visible when testing is independent, consistent, and properly escalated.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, NIST CSF 2.0 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 and SOC 2 (AICPA) define the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AU-6 — Audit Record Review, Analysis, and Reporting | Third-line assurance depends on independent review and reporting of control evidence. |
| Recommendation — Review audit evidence independently and report control exceptions to management. | ||
| NIST CSF 2.0 | GV.OV-01 — Oversight of Cyber Risk Management | The third line provides governance oversight and independent evaluation of control effectiveness. |
| Recommendation — Assign independent oversight to evaluate whether controls are operating as intended. | ||
| ISO/IEC 27001:2022 | A.5.36 — Independent review of information security | Independent review is the core operating principle behind third-line assurance. |
| Recommendation — Perform independent reviews of controls and escalate weaknesses for remediation. | ||
| SOC 2 (AICPA) | CC4.1 — Monitoring Activities | Third-line testing strengthens monitoring of whether controls continue to operate effectively. |
| Recommendation — Validate that monitoring and review activities detect control breakdowns promptly. | ||
| CIS Controls v8 | CIS-18 — Penetration Testing | Independent testing logic aligns with the third line's verification role, even though the subject is broader than penetration testing. |
| Recommendation — Use independent testing to verify control assumptions and expose weaknesses. | ||
Practitioner Guidance
Why practitioners should care: The third line only works when its boundaries are clear. Internal audit, compliance testing, and operational control ownership should be separated enough that findings are trusted and remediation can be challenged objectively.
Common misunderstanding: “Independent” does not mean distant from the business, it means separate from control operation. The function still needs enough subject-matter understanding to test evidence rigorously and to explain why a finding matters.
Practitioner takeaway: If the third line cannot credibly challenge the evidence behind a control, it is not providing real assurance, only confirmation.
Related resources from NHI Mgmt Group
- What breaks when native platform controls are the only line of defence for DLP?
- Should organisations trust LLM judges as the last line of defence for autonomous agents?
- How should security teams design cloud controls so native platform security does not become the only line of defence?
- What happens when organisations rely on penetration tests as their only line of defence?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 11, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org