{
  "slug": "operating-model",
  "topic": "Operating model",
  "status": "published",
  "order": 59,
  "capability": "leadership/operating-model",
  "title": "Operating model: who decides, who does it, who checks?",
  "short": "Name one accountable person for each of six core security processes and fit the whole operating model on two pages.",
  "answer": "This quarter, write down on two pages who decides, who does the work and who checks it for six core processes, from patching to exceptions, and have management approve it. Buy the work wherever that is cheaper, but keep decisions, risk acceptance and supplier oversight with your own named people.",
  "audience": "Heads of security and CISOs, IT leads who own security, and the managing directors they report to",
  "version": "1.0",
  "lastReviewed": "2026-11-05",
  "reviewEveryDays": 30,
  "blocks": [
    {
      "type": "ranked",
      "id": "first",
      "title": "If you only do five things",
      "navTitle": "Five things",
      "items": [
        {
          "title": "Give each core process one accountable name.",
          "text": "Name one A and the people who do the work for each of the six processes below. NIST suggests documenting who is responsible, accountable, consulted and informed[^csfie]."
        },
        {
          "title": "Write down who decides what.",
          "text": "The BSI's training curriculum asks management which cyber decisions need its approval[^bsicurr]. Then list who accepts which risk and approves which exception."
        },
        {
          "title": "Separate doing from checking.",
          "text": "Assurance isn't credible if the reviewer designs or operates the process, the IIA says[^iia3l]. Don't let those who run systems audit them."
        },
        {
          "title": "Buy the work, keep the decisions.",
          "text": "NIS2 leaves approving and overseeing the measures with management[^nis2], and the BSI says outsourcing all IT doesn't move the responsibility[^bsifaq]."
        },
        {
          "title": "Get it approved and review it yearly.",
          "text": "For digital providers, Regulation 2024/2690 has management review roles at planned intervals and after significant incidents or changes[^ir2690]. Do the same yearly and after every reorganization."
        }
      ]
    },
    {
      "type": "steps",
      "id": "write",
      "title": "Write it down in two pages",
      "navTitle": "Two pages",
      "items": [
        {
          "title": "Page 1, top: scope and structure.",
          "text": "Entities, sites and main suppliers in scope, who leads security, and whether it runs central, federated or hybrid."
        },
        {
          "title": "Page 1, below: RACI and three lines.",
          "text": "One row per core process with one A each, then who operates, who monitors and who checks independently."
        },
        {
          "title": "Page 2, top: the service catalog.",
          "text": "Each service, such as project reviews, exceptions, scanning, supplier checks, incident response and audit evidence, with how to ask, how fast (project reviews within 5 working days, say) and who delivers it. Add what security doesn't do: patch, grant access, sign contracts."
        },
        {
          "title": "Page 2, middle: the decision table.",
          "text": "Who accepts which risk, approves which exception and may stop which system, each with a deputy."
        },
        {
          "title": "Page 2, bottom: approval.",
          "text": "The phone chain, the next review date and management's sign-off. ENISA advises dating the organization chart and naming who updated it[^enisatig]."
        }
      ]
    },
    {
      "type": "list",
      "id": "raci",
      "title": "A RACI for six core processes",
      "navTitle": "RACI",
      "span": "full",
      "intro": "A answers for the outcome, R does the work, C is asked before and I is told after. Keep one A per row. ENISA maps the roles requirement of 2024/2690 to ISO/IEC 27001 clause 5.3[^enisatig], so one RACI can serve both.",
      "items": [
        "**Patching.** A: head of IT. R: IT operations or the MSP. C: security, which sets deadlines from the patching sheet, and system owners for maintenance windows. I: management, about exploited flaws past deadline.",
        "**Vulnerability management.** A: head of security. R: security scans, rates and tracks; system owners fix. C: IT operations. I: management, monthly. Digital providers must document why a finding needs no fix[^ir2690].",
        "**Access reviews.** A: each application's business owner. R: the owner's team leads, with lists from IT. C: security, for admin rights. I: internal audit. Digital providers must document results and changes[^ir2690].",
        "**Incident response.** A: head of security. R: the SOC or MDR and IT operations. C: legal, data protection, communications. I: management and insurer; a named owner files reports to authorities (EU security laws sheet). Stopping business processes is for the crisis team.",
        "**Supplier onboarding.** A: the business owner who wants the supplier. R: procurement, with a contract manager per contract[^iiatp]. C: security, for tier and clauses. I: IT, to grant and later remove access.",
        "**Exceptions.** A: the risk owner, at the level set in the risk register sheet. R: the requester, with the case, a compensating measure and an end date. C: security. I: management, via the open exceptions list."
      ]
    },
    {
      "type": "list",
      "id": "lines",
      "title": "Three lines, applied to security",
      "navTitle": "Three lines",
      "items": [
        "**First line: whoever runs it.** The IIA's first line owns the risk and runs the controls[^iia3l]: IT operations, the MSP, application owners.",
        "**Second line: security.** It advises, monitors and challenges the first line[^iia3l]. If it also runs the firewall or EDR, have someone else check that.",
        "**Third line: someone independent.** Internal audit, in-house or bought in. The IIA treats at least 12 months between running and assuring a process as typically enough for objectivity[^iia3l].",
        "**Small companies may merge the first two.** The rules for digital providers allow duties on top of existing roles and, where size rules out reviewers outside the reviewed line, other ways to keep reviews impartial[^ir2690]."
      ]
    },
    {
      "type": "list",
      "id": "structure",
      "title": "Central, federated or hybrid",
      "navTitle": "Structure",
      "items": [
        "**Central.** One team sets the rules and runs security for everyone. Choose it when one IT team runs everything.",
        "**Hybrid.** Central security owns the standards, risk register, MDR and scanning; units patch, review access and name champions. Choose it for most growing companies.",
        "**Federated.** Each unit has its own security officer, as the BSI describes for large organizations[^std2002]. Choose it for subsidiaries with their own IT and, where in scope, their own duties under the BSIG[^bsig], and keep one shared risk register."
      ]
    },
    {
      "type": "list",
      "id": "sourcing",
      "title": "What to buy and what to keep",
      "navTitle": "Buy or keep",
      "items": [
        "**Buy what is rare or round the clock.** The NCSC says a SOC can outsource seldom-used functions, though in-house staff know the business better[^ncscsoc]. Typical buys: MDR (see the SOC and MDR sheet), pentests, a response retainer, a virtual CISO.",
        "**Put a responsibility matrix in the MSP contract.** State what the MSP does and what stays with you, as the NCSC advises[^ncscmsp].",
        "**Know which line a provider is in.** The IIA places providers in the line of whoever engages and directs them[^iia3l]: a pentest ordered by IT isn't independent.",
        "**Keep risk acceptance and supplier oversight.** DORA makes financial entities above micro size name a role to monitor ICT suppliers[^dora]. Give every supplier an internal owner anyway."
      ]
    },
    {
      "type": "list",
      "id": "decisions",
      "title": "Decision rights and escalation",
      "navTitle": "Decisions",
      "items": [
        "**Let delegates accept smaller risks.** 2024/2690 lets digital providers delegate to accountable people with the authority, if management gets adequate reports[^ir2690]. Set levels with the risk register sheet.",
        "**Pre-authorize containment.** Let on-call staff or the MDR isolate a device or disable an account without asking. Leave business shutdowns to the crisis team.",
        "**Escalate on triggers.** IIA auditors must check for a process that escalates unacceptable cyber risks quickly[^iiacyber]. Set triggers such as an exploited flaw past its deadline.",
        "**Set when security must be asked.** Grundschutz++ requires defining when the security officer joins projects[^std3001]."
      ]
    },
    {
      "type": "list",
      "id": "champions",
      "title": "Security champions in business and IT teams",
      "navTitle": "Champions",
      "items": [
        "**Name one per team that holds risk.** IT operations, development, finance for payment changes, HR for leavers and plant operations for OT.",
        "**Put their time in writing.** OWASP advises formally allocating champions' time and getting management support, because formal priorities win when priorities conflict[^owaspsc].",
        "**Give them tasks, not authority.** They triage findings, review risky changes and are first contact in incidents, but don't approve exceptions."
      ]
    },
    {
      "type": "list",
      "id": "changed",
      "title": "What changed in 2026",
      "navTitle": "What changed",
      "items": [
        "**The IIA updated its Three Lines Model.** Its July 2026 Statement of Position adds guidance for organizations not required to keep separate assurance functions[^iia3l]. Recheck where you've merged lines.",
        "**Internal audit now checks roles.** Since 5 February 2026, cyber audits must assess roles and escalation[^iiacyber]; since 15 September 2026, supplier audits must assess who selects, manages and monitors suppliers[^iiatp].",
        "**The BSI spelled out delegation limits.** Its non-binding October 2026 curriculum on BSIG § 38 says management may delegate operational work, not responsibility or oversight, and suggests a responsibility matrix[^bsicurr]."
      ]
    },
    {
      "type": "list",
      "id": "skip",
      "title": "What you can skip",
      "items": [
        "**A RACI for every task.** Six processes and a decision table settle most disputes. Add a row only when a dispute comes back.",
        "**An internal audit department in a small company.** Buy a yearly review from an auditor who neither runs nor advises on your IT.",
        "**A target operating model deck.** Two pages people use beat 40 slides nobody opens."
      ]
    },
    {
      "type": "list",
      "id": "mistakes",
      "title": "Mistakes that cost the most",
      "navTitle": "Mistakes",
      "items": [
        "**Two accountable people for one process.** Then nobody is. Split the process or pick one.",
        "**Security as A for everything.** IT and the business then stop treating patching and access as their job.",
        "**No deputies.** ENISA advises a deputy for each security role where possible[^enisatig]. Name one for every A and test the phone chain twice a year."
      ]
    },
    {
      "type": "columns",
      "id": "by-size",
      "title": "What this looks like at your size",
      "navTitle": "By team size",
      "span": "full",
      "columns": [
        {
          "title": "Small team, no security staff",
          "items": [
            "The managing director accepts risks; the IT lead or MSP runs the controls.",
            "Write the two pages with your MSP and approve them in a management meeting.",
            "Merge the first two lines if you must, but buy the independent check."
          ]
        },
        {
          "title": "Growing, with IT or security staff",
          "items": [
            "Run hybrid, with champions in IT and business teams.",
            "Don't make the IT lead the security officer: Grundschutz++ calls that a conflict to avoid[^std3001].",
            "Publish the service catalog and the decision table."
          ]
        },
        {
          "title": "Enterprise or regulated",
          "items": [
            "Name security officers per unit or entity, under one group standard and register.",
            "Keep an assurance map of who checks which risk, to find gaps and duplicates[^iia3l].",
            "Under DORA, keep ICT risk control separate from internal audit[^dora]."
          ]
        }
      ]
    }
  ],
  "changes": [
    {
      "date": "2026-11-05",
      "version": "1.0",
      "text": "Published after a copy edit and a source-by-source fact check, which labeled every Regulation 2024/2690 rule as applying to digital providers, quoted the IIA's July 2026 position on the three lines exactly and narrowed the NCSC sourcing advice to SOCs."
    },
    {
      "date": "2026-11-05",
      "version": "0.1",
      "text": "First draft, based on the IIA's 2026 Three Lines Model, NIS2, BSIG § 38, Regulation 2024/2690, DORA, and BSI and ENISA guidance."
    }
  ],
  "sources": [
    {
      "id": "csfie",
      "title": "CSF 2.0 Implementation Examples, GV.RR-02",
      "publisher": "NIST",
      "date": "26 Feb 2024",
      "url": "https://www.nist.gov/system/files/documents/2024/02/21/CSF%202.0%20Implementation%20Examples.pdf"
    },
    {
      "id": "bsicurr",
      "title": "Curriculum für eine Geschäftsleitungsschulung nach NIS-2",
      "publisher": "BSI",
      "date": "28 Oct 2026",
      "url": "https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/NIS-2/nis-2-curriculum-geschaeftsleitungsschulung.pdf?__blob=publicationFile&v=6"
    },
    {
      "id": "iia3l",
      "title": "Statement of Position: Three Lines Model",
      "publisher": "IIA",
      "date": "8 Jul 2026",
      "url": "https://www.theiia.org/globalassets/site/resources/statements-of-position/tlm_assurance_advice_support_effective_gov_en.pdf"
    },
    {
      "id": "bsifaq",
      "title": "Fragen und Antworten zu NIS-2",
      "publisher": "BSI",
      "date": "checked 5 Nov 2026",
      "url": "https://www.bsi.bund.de/DE/Themen/Regulierte-Wirtschaft/NIS-2-regulierte-Unternehmen/NIS-2-FAQ/NIS-2-FAQ-allgemein/FAQ-zu-NIS-2.html"
    },
    {
      "id": "ir2690",
      "title": "Implementing Regulation (EU) 2024/2690, Annex",
      "publisher": "EUR-Lex",
      "date": "17 Oct 2024",
      "url": "https://eur-lex.europa.eu/eli/reg_impl/2024/2690/oj"
    },
    {
      "id": "enisatig",
      "title": "NIS2 technical implementation guidance and mapping table v1.2",
      "publisher": "ENISA",
      "date": "26 Jun 2025",
      "url": "https://www.enisa.europa.eu/publications/nis2-technical-implementation-guidance"
    },
    {
      "id": "iiatp",
      "title": "Third-Party Topical Requirement",
      "publisher": "IIA",
      "date": "effective 15 Sep 2026",
      "url": "https://www.theiia.org/globalassets/site/standards/topical-requirements/third-party/third_party_topical_requirement_english.pdf"
    },
    {
      "id": "iiacyber",
      "title": "Cybersecurity Topical Requirement",
      "publisher": "IIA",
      "date": "effective 5 Feb 2026",
      "url": "https://www.theiia.org/globalassets/site/standards/topical-requirements/cybersecurity/cybersecurity_topical_requirement.pdf"
    },
    {
      "id": "std2002",
      "title": "BSI-Standard 200-2, chapter 4",
      "publisher": "BSI",
      "date": "Oct 2017",
      "url": "https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Grundschutz/BSI_Standards/standard_200_2.pdf?__blob=publicationFile&v=2"
    },
    {
      "id": "bsig",
      "title": "BSI-Gesetz (BSIG), § 38",
      "publisher": "BMJV (Germany)",
      "date": "checked 5 Nov 2026",
      "url": "https://www.gesetze-im-internet.de/bsig_2025/__38.html"
    },
    {
      "id": "ncscsoc",
      "title": "Building a SOC: Designing an operating model",
      "publisher": "NCSC (UK)",
      "date": "23 May 2022",
      "url": "https://www.ncsc.gov.uk/collection/building-a-security-operations-centre/operating-model/designing-an-operating-model"
    },
    {
      "id": "ncscmsp",
      "title": "Choosing a managed service provider",
      "publisher": "NCSC (UK)",
      "date": "24 Nov 2025",
      "url": "https://www.ncsc.gov.uk/guidance/choosing-a-managed-service-provider-msp"
    },
    {
      "id": "dora",
      "title": "Regulation (EU) 2022/2554 (DORA), Art. 5 and 6",
      "publisher": "EUR-Lex",
      "date": "2022",
      "url": "https://eur-lex.europa.eu/eli/reg/2022/2554/oj"
    },
    {
      "id": "std3001",
      "title": "BSI-Standard 300-1, version 1.0",
      "publisher": "BSI",
      "date": "20 Oct 2026",
      "url": "https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Grundschutz/BSI_Standards/standard_300-1.pdf?__blob=publicationFile&v=3"
    },
    {
      "id": "owaspsc",
      "title": "Security Champions Guide",
      "publisher": "OWASP",
      "date": "checked 5 Nov 2026",
      "url": "https://securitychampions.owasp.org/"
    },
    {
      "id": "nis2",
      "title": "Directive (EU) 2022/2555 (NIS2), Art. 20",
      "publisher": "EUR-Lex",
      "date": "2022",
      "url": "https://eur-lex.europa.eu/eli/dir/2022/2555/oj"
    }
  ]
}