The Three Lines of Defense Model: Separating Roles in IT and Information Security

How the three lines of defense model is set up in practice between IT operations, information security and internal audit: merged lines in SMEs, a conflict table and ways to compensate.
Technical summary
Technology
IIA Three Lines Model, ISO/IEC 27001:2022 clauses 5.3 and 9.2, Annex A 5.3 and 5.35
Topic
Organizational separation of risk management and assurance functions
Level
Intermediate
Prerequisites
  • ISMS roles and responsibilities defined
  • Access to the company organization chart
In this article7 sections

If the IT team that writes the firewall rules also assesses the risk of those rules and audits its own work at year end, the resulting assurance stays on paper. Nobody questions anybody. The three lines of defense model exists to resolve this deadlock: it separates the functions that take on risk, oversee risk and provide independent assurance. Below we explain how we fit the model to IT and information security, situations where lines merge in mid-sized companies, and the compensating arrangements that keep independence standing.

The basic logic of the model

The model was popularized by the Institute of Internal Auditors (IIA); in 2020 the IIA updated it under the name “Three Lines Model”. The current version emphasizes clear role definitions and collaboration rather than separating the lines with rigid walls. The basic distinction hasn’t changed:

  • Governing body (board or top management): Sets risk appetite and takes on accountability.
  • Management — first line roles: Own the risk and operate controls while delivering products and services.
  • Management — second line roles: Provide expertise, frameworks, monitoring and challenge on risk management.
  • Internal audit — third line: Independently of management, gives the governing body assurance on the effectiveness of the first two lines.

External auditors, certification bodies and regulators are additional assurance providers standing outside this structure. On the ISO/IEC 27001 side, the model’s counterpart is spread across several clauses: clause 5.3 requires roles to be assigned, Annex A 5.3 conflicting duties to be segregated, Annex A 5.35 independent review of information security, and clause 9.2 internal audit to be conducted impartially.

First line: IT operations and process owners

Risk is born in the first line. System administrators, the network team, application owners and business units operate controls while doing their daily work: they approve access requests, apply patches, take backups, open change records.

The first line’s responsibilities:

  • Recognizing the risks in its own area and providing input to the risk register.
  • Operating controls as designed and producing their evidence.
  • Reporting control failures and incidents in time.
  • Carrying out self-assessment: for example completing the quarterly access review itself.

A mistake you may come across is “handing over” security entirely to the second line. The network team says “security is their job”, and the information security team approves rules without ever seeing them. The information security team can assess the risk of a firewall rule; but the network team that writes and maintains the rule owns that risk. Ownership isn’t handed over.

Second line: the information security and risk function

The second line stands next to the first line; it doesn’t do the work for it. The information security manager or CISO, the risk manager, and the compliance and KVKK officers are typical roles in this line. Their tasks:

  • Writing policies, standards and the risk methodology.
  • Facilitating risk assessment and managing the risk register.
  • Monitoring control effectiveness with indicators and escalating threshold breaches.
  • Questioning the first line’s risk decisions; objecting where necessary.

The second line’s strength comes from standing sufficiently apart from the first line. If the information security manager reports to the IT manager, taking a risk finding that would strain the IT budget to management becomes difficult in practice; the finding either softens or slips to the next quarter. The reporting line is decisive here. The rest of the design depends on it.

Third line: internal audit

The third line gives independent assurance that the first two lines actually work. In the ISMS context, this is the internal audit under clause 9.2. The planning and frequency side is explained in the ISO 27001 internal audit program guide, and how findings are reported in the writing audit findings guide.

Third-line independence has two dimensions:

  1. Organizational independence: Internal audit reports to the governing body or audit committee, not to the function it audits.
  2. Individual objectivity: An auditor doesn’t audit a process they designed or operate. The person who wrote the ISMS documents a year ago auditing the same documents this year weakens objectivity.

Lines merging in small and mid-sized organizations

In a company with fifty to a few hundred employees, setting up a separate team for each line is often unrealistic. Lines merge. The point is to merge them deliberately and manage the resulting conflict. The table below shows merges you may come across and a compensating arrangement for each.

Merged roles Resulting conflict Compensating arrangement
IT manager + information security officer (1st + 2nd line) Assesses the risk of their own operations Tie high-risk acceptances to top management approval; present the risk report directly to the general manager
Information security officer + internal auditor (2nd + 3rd line) Audits a framework they designed Outsource internal audit or give it to a trained auditor from another unit
System administrator + access approver (within the 1st line) Grants themselves permissions and approves them Monthly second-line review of the log of privileged account changes
External IT service provider + security assessment The supplier assesses its own service An independent audit right in the contract; have the assessment done by a different party
Quality manager + ISMS internal auditor Usually no conflict; IT competence may be lacking Add an auditor with IT knowledge to the audit team for technical areas

The merge in the second row is often questioned in certification audits. In a small company, a practical solution is to send an employee from another department (such as quality or finance) on ISO/IEC 27001 internal auditor training and pair them with a specialist on technical topics. The second route is to give internal audit to an external party; in that case the person doing the audit must not have consulted on setting up the ISMS. If the same person both builds and audits, they’re auditing their own work.

Documenting compensating arrangements

Merged roles and compensating methods should be written clearly in the roles and responsibilities document. How to define the roles themselves is in the ISMS RACI matrix guide; what’s added here is a short explanation showing the conflict is recognized and how it’s managed. When the auditor asks “Your IT manager is also the ISMS manager; who questions the risk decisions?”, the answer must rest on a document and the records supporting it: committee meeting minutes, risk acceptance forms approved by top management, and so on.

Reporting lines and independence

Reporting lines decide how the model works more than anything else. The structure we recommend:

  • The first line reports to the IT manager and business unit managers.
  • The second line reports administratively to a senior executive (general manager, CFO or COO), not to the IT manager. If that isn’t possible, at least the authority to present risk reports directly to top management or the ISMS committee is defined in writing.
  • The third line reports functionally to the audit committee or board; the audit plan and findings are approved by this body.

Verify the structure you’ve built with this checklist:

  • Is an owner (1st line) and a monitor (2nd line) defined for every control?
  • Is the information security officer’s direct access to top management written down, and is it actually used?
  • Has the internal auditor taken on an operational or consulting role in the area they audited in the last 12 months?
  • Are risk acceptance decisions made at an authority level appropriate to the risk level?
  • Are merged roles and compensating arrangements written down and reviewed once a year?

If the seniority or capacity needed to set up the second line in-house is missing, filling the role with the outsourced information security officer (vCISO) model is one way to create a risk voice independent of IT operations. If the role structure needs to be addressed together with the general governance framework, it can be assessed as part of our IT governance and process maturity work.

Frequently asked questions

Is the three lines model mandatory in ISO 27001?

No, ISO/IEC 27001 doesn’t require this model by name. However, it requires roles to be assigned (clause 5.3), duties to be segregated (Annex A 5.3), independent review of information security (Annex A 5.35) and impartiality of internal audit (clause 9.2). The three lines model is a practical way of placing these requirements on the organization chart.

Can the IT manager also be the information security officer?

In small companies, yes, but it’s a conflict of interest and the auditor will question it. Manage the conflict by tying risk decisions to top management or committee approval, presenting the second-line report directly to the general manager, and having periodic independent reviews done.

Does outsourcing internal audit ensure independence?

Usually, if the auditor has no relationship with the activity audited. But if the same consultant prepares the ISMS documents and then audits the same areas, they’ve audited their own work. Consulting and auditing should be done by different people, and this separation should be documented.

Why did the IIA drop the word “defense” from the model?

In its 2020 update, the IIA renamed the model the “Three Lines Model”. The aim was to emphasize that risk management isn’t only about defense but also supports achieving objectives, and to put collaboration between the lines ahead of rigid walls. In practice both names are still used.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles