SDG data protection blog

Laws & regulationIT security

Information Security Officer: When Is One Mandatory?

26 October 2026 by Sebastian Baier · Reading time approx. 10 minutes

If you fall under NIS2 or KRITIS, are certified to ISO 27001 or commit to responsibilities for information security towards a cyber insurer, you need an information security officer. The law usually does not name the role, but it does require responsible management of information security that cannot be achieved without an information security officer. In these cases, we therefore consider an information security officer mandatory. The role should be taken on neither by the Head of IT nor by the data protection officer, because both would otherwise be checking their own work.

This article shows what the law, the standard and insurers actually require, and who can take on the role. What an information security officer does in practice and why we recommend an external appointment is described on the page external information security officer.

When an information security officer is mandatory

Your situation What is required Our assessment
Particularly important or important entity under NIS2 risk management, reporting obligations, registration and monitoring by management (Sections 30, 32, 33, 38 BSIG) mandatory, because these tasks cannot be fulfilled without someone steering them
Operator of critical facilities (KRITIS) in addition, a higher level of protection, attack detection, evidence every three years and availability (Sections 31, 33, 39 BSIG) mandatory
ISO 27001 certification planned or in place assigned responsibilities and authorities for the ISMS and for reporting to management (clause 5.3) mandatory as a role; the title is up to you
Cyber insurance information on responsibilities and measures in the risk questionnaire mandatory as soon as you commit to responsibilities there
Operators of public telecommunications networks and providers of publicly available telecommunications services security officer (Section 166 (1) No. 1 TKG) statutory obligation
none of these cases no requirement recommended as soon as customers or your own risk situation suggest it

What the law literally requires

For context: an express obligation to appoint a person with the title "information security officer" exists for companies only in individual sectors, for example the security officer under Section 166 TKG. The BSIG (the BSI Act) contains an express obligation to appoint one only for federal administration bodies (Section 45 BSIG). Unlike the data protection officer, there is no general rule such as Art. 37 GDPR.

However, NIS2, KRITIS and ISO 27001 require responsible, ongoing management of information security. Anyone who wants to meet these requirements needs a person to take on this steering role. That is why we treat the information security officer as mandatory in these cases, even though the law does not name the role.

NIS2 and KRITIS: why it does not work without an information security officer

The BSIG requires affected entities to perform a number of ongoing tasks. Our page on NIS2 consulting gives an overview of all obligations.

Obligation under the BSIG What it requires organisationally
Implement and document risk management measures in ten areas (Section 30) someone has to assess risks, plan measures and track progress
Report significant security incidents within 24 hours (Section 32) someone has to assess incidents and steer the reporting process
Registration and availability (Section 33) a point of contact must be named and reachable
Management implements and monitors (Section 38 (1)) management needs regular, expert reports
KRITIS: evidence every three years (Section 39) someone has to coordinate the audit basis, the audit and the remedying of deficiencies
Important

Responsibility remains with management. Under Section 38 BSIG, management must implement the risk management measures, monitor their implementation and take part in training regularly. An information security officer relieves management operationally, but cannot take over its responsibility or liability. More on this in the article NIS2 and management.

In its guidance on management training, the BSI (Federal Office for Information Security) expressly names regular exchanges between the information security officer and the whole of management as a suitable format. You can clarify whether your company falls under NIS2 with the NIS2 applicability assessment. The article KRITIS and NIS2 explains the differences between NIS2 and KRITIS.

ISO 27001 and cyber insurance

ISO 27001: Clause 5.3 requires top management to assign responsibilities and authorities for information security, in particular for ensuring that the ISMS conforms to the standard and for reporting on its performance to management. The standard does not prescribe the title "information security officer", but the role must be filled. The article Introducing an ISMS shows how the introduction works.

Cyber insurance: In the risk questionnaire, insurers ask about responsibilities and measures for information security. Whatever you state there, you must be able to prove in the event of a claim. A named information security officer, a documented ISMS and regular reports to management provide that evidence. The specific requirements of your insurer follow from the questionnaire and the policy conditions.

Also pay attention to the exclusions: many cyber insurance policies exclude damage caused by war and state cyber attacks, as do the non-binding model conditions of the GDV (German Insurance Association) (AVB Cyber, version of February 2024, item A1-17.2). Insurance is therefore no substitute for managed information security, which the information security officer ensures.

Customers: Regulated customers have to manage their supply chain and are therefore increasingly asking for a named person responsible for information security. See NIS2 and the supply chain.

Who may be the information security officer, and who may not?

The information security officer checks whether information security in the company works. They must therefore not audit their own work.

Role Suitable as information security officer? Reasoning
Head of IT no The Head of IT is responsible for operating the systems whose security the information security officer is supposed to assess. BSI Standard 200-2 (chapter 4.4) also recommends placing the information security officer in a staff position reporting directly to top management, and advises against locating the role in the IT department because of role conflicts.
Data protection officer no The DPO checks technical and organisational measures that the information security officer defines. We therefore always keep the roles separate (see below).
Management no Management bears responsibility and monitors. The information security officer advises and reports to it; combining both in one person prevents oversight.
internal specialist outside IT and management yes with a direct reporting line to management, sufficient time and further training
external service provider yes independent, with up-to-date expertise and cover; ideally with a fixed internal contact person

None of these combinations is expressly prohibited by law. However, they contradict the principle that oversight and implementation must be separate, and we therefore rule them out.

Information security officer and data protection officer

Information security officer Data protection officer
What is protected all information and company assets personal data and the rights of data subjects
Obligation to appoint by law only in individual areas, in practice in the cases listed above under the conditions of Art. 37 GDPR and Section 38 BDSG (German Federal Data Protection Act)
Legal status not regulated in general Art. 38 and 39 GDPR, including freedom from instructions and protection against dismissal

Why we keep the information security officer and the DPO separate: Legally, under Art. 38 (6) GDPR the data protection officer may perform other tasks as long as they do not result in a conflict of interests. According to the case law of the CJEU, whether there is a conflict must be assessed on a case-by-case basis (judgment of 9 February 2023, C-453/21). The question is assessed differently in legal commentaries and by the supervisory authorities. The Lower Saxony data protection authority, for example, expressly recommends avoiding appointing the same person as DPO and information security officer. The conflict is obvious: as information security officer, the person would define measures that they would then have to assess themselves as DPO. We therefore always keep the roles separate.

Nevertheless, the two topics overlap considerably, for example in technical and organisational measures, risk analyses, management of service providers and incidents. On request, SDG takes on both roles, as external data protection officer and as external information security officer, through different people in our team who work closely together.

How SDG supports you

  • Assessment: Do you need an information security officer, and who can take on the role in your company? Together with lawyers from our team where needed.
  • External information security officer: We take on the role, ideally with a fixed internal contact person: external information security officer
  • Support for internal information security officers: review of appointment, position and tasks, expert support
  • Information security officer and DPO from a single source, through different people and closely coordinated
  • Management training under Section 38 (3) BSIG: training

Frequently asked questions about the obligation to have an information security officer

Is an information security officer mandatory?

Yes, for companies under NIS2 or KRITIS, with ISO 27001 certification or with commitments towards a cyber insurer. The law usually does not name the information security officer in these cases, but it does require responsible management of information security that cannot be achieved without one. It is expressly required by law, for example, as a security officer for telecommunications providers (Section 166 TKG).

Do I need an information security officer under NIS2?

Yes. The BSIG does not name the information security officer, but risk management, reporting obligations and monitoring by management cannot be fulfilled without someone steering them. Under Section 38 BSIG, responsibility nevertheless remains with management.

Does ISO 27001 require an information security officer?

The standard requires the role, not the title. Clause 5.3 requires top management to assign responsibilities and authorities for the ISMS and for reporting. In practice, an information security officer takes this on.

Do I need an information security officer for cyber insurance?

If you state responsibilities for information security in the risk questionnaire, you must be able to prove them in the event of a claim. A named information security officer, a documented ISMS and regular reports provide that evidence. The specific requirements follow from the questionnaire and the policy conditions.

Can the Head of IT be the information security officer?

No. The Head of IT is responsible for operating the systems whose security the information security officer is supposed to check, and would therefore be auditing their own work. BSI Standard 200-2 (chapter 4.4) also recommends placing the information security officer in a staff position reporting directly to top management, and advises against locating the role in the IT department because of role conflicts.

May the information security officer and the data protection officer be the same person?

We always keep the roles separate. Legally, under Art. 38 (6) GDPR and the case law of the CJEU, this is a question for the individual case, but supervisory authorities such as the Lower Saxony data protection authority recommend avoiding combining the roles in one person. At SDG, the two roles are therefore held by different people.

Can management transfer its NIS2 responsibility to the information security officer?

No. Under Section 38 BSIG, management must implement the risk management measures and monitor their implementation. The information security officer provides operational support; responsibility and liability remain with management.

Can the information security officer be external?

Yes. An external appointment is possible and often advantageous because of independence, expertise and continuity. A fixed internal contact person is important.

Sources: Section 38 BSIG, Section 45 BSIG, Section 166 TKG, GDPR, Section 38 BDSG, CJEU, judgment of 9 February 2023, C-453/21, LfD Niedersachsen: FAQ on data protection officers in companies

Note: This article provides general information and does not replace legal advice in individual cases. The classification as mandatory in the cases listed and the exclusion of the Head of IT, management and the data protection officer reflect SDG's professional position.