Who do you nominate as security officer, and why that choice is harder than it looks

Date: 11/16/2026

ABDO ABRO

Who do you nominate as security officer, and why that choice is harder than it looks

Requirement 1.1.6 of ABRO 2026 sets four conditions on your security officer, and three of them are about position rather than expertise: on the payroll, a direct line to the board, and authority to act without going through superiors.

Who do you nominate as security officer, and why that choice is harder than it looks

TL;DR

ABRO 2026 requires you to nominate one security officer, and requirement 1.1.6 sets four conditions on that person. Three of them are not about security but about position: on the payroll, a direct reporting line to the highest governing body, and enough authority to act without going through superiors. That is where it pinches, because whoever is senior enough has no time and whoever has time has no authority. It is a personnel decision with liability attached, not a form, and the NBIV has to approve them before they are appointed.

One name, and not one you fill in casually

The previous two pieces were about what you do not determine: which regime your contract names and which chapters of the requirements apply to you. This is about the first decision that is yours, and it is immediately one you cannot reverse without applying again.

One note before the quotations: ABRO 2026 is published in Dutch only, so every passage quoted here is my own translation and the Dutch original governs.

The document requires the contractor to nominate an employee for the role of security officer to the NBIV, using the form 'Appointment of Security Officer' (requirement 1.1.4). After approval the NBIV appoints them. There is one, although you may place sub-officers alongside as stand-ins or for multiple sites, and a cyber security officer for the digital side.

The nomination is not made by HR or by the project manager, either. The document places that with the contractor's highest governing body. That is not a formality, and the reason is in the next requirement.

The four conditions, and why three are about position

Requirement 1.1.6 of ABRO 2026 states that the security officer acts as primary point of contact for the NBIV, and then sets out four things. They:

  • are on the payroll of the company concerned;
  • have a direct reporting line to the highest governing body of the contractor;
  • have sufficient authority, seniority, executive capability and control over the relevant operational staff to carry out the responsibilities without the intervention of superiors;
  • hold a certificate of conduct or a security clearance at the highest classification level of the special contract(s).

Only the last is about screening. The first three are about where this person sits in your organisation, and between them they rule out a good many candidates who look suitable on paper.

The first rules out the external. You cannot hire the role in, not from a consultancy and not as an interim. That is awkward to write down when you are a consultant yourself, and it is what the document says.

The second rules out the arrangement where security sits three layers below the board and reports through a manager. A direct reporting line is literally what it says.

And the third is the hardest, because it rules out the most popular solution: someone who does it "on the side". Being able to act without the intervention of superiors means being able to decide on a Saturday evening that something gets shut down, without first having to convince anyone. Someone who cannot does not meet the requirement, even if they would do the job well on the merits.

Why that pinches in practice

At a large company this is solvable and mostly paperwork. At a supplier of fifty or two hundred people it runs aground on an arithmetic nobody says out loud.

Whoever is senior enough and already has the direct line to the board, the operations director, the IT manager, sometimes one of the owners, has no room for an annual risk analysis, a self-inspection and a register that stays current. Whoever does have that room sits two layers down and has to go back to their manager for every decision. That is precisely the case requirement 1.1.6 excludes.

The way out is not a different candidate but the mandate. You can promote someone into that line, or you can change the reporting line for this role. The second is what most companies end up doing, and it is why this decision belongs at board level and not with the project manager: you are changing a line in your organisation, for one contract, and that change has to hold when things get tense.

The test, in three questions

The piece is called "who do you nominate", so here is the test itself. Take your candidate and answer these three yes or no. They come straight from requirement 1.1.6 and not one of them is about expertise.

  1. Are they on your payroll? Not a freelancer, not a secondment, not an adviser on a services contract. No is a hard no here; this is the one of the three with no room to negotiate.
  2. Do they report directly to the highest governing body? Not "has access to" and not "sometimes joins the management meeting", but a fixed line that appears in your org chart. No does not disqualify them, but it means you have to put that line in place before you nominate.
  3. Can they decide on a Friday evening that something gets shut down, and have it done? Without first convincing anyone, and with enough grip on the people who have to carry it out. This is the question most candidates fail, and the only one you cannot solve with a form.

Three times yes: nominate. Yes on 1 and 3 but no on 2: changing the reporting line is a half-hour decision and then it is right. No on question 3: find another candidate or give this one the mandate, but do not nominate them hoping it will be fine in practice, because the NBIV is the one who calls them when it is not.

And no on question 1 with nobody else available: then this stops being a security question and becomes a personnel decision, and it belongs at board level. That is uncomfortable, and it is better to know now than after your tender has been awarded.

What you are putting that person through

Annex 2 of ABRO 2026 lists the responsibilities. The full list is in the document; these are the six that cost the most time and are most often underestimated:

  • Drawing up the security plan and updating it at least annually or on changes.
  • Carrying out a risk analysis for the special contract and updating it at least annually.
  • Carrying out a self-inspection at least annually, using the self-inspection list.
  • Informing and advising the highest governing body directly, independently and factually on security matters around the contract.
  • Keeping a current register of protected interests, including copies, and of who has had access to them, so that investigation after the fact is possible.
  • Keeping a current overview of the entire chain of suppliers and subcontractors involved in the contract.

Note that fourth point. "Directly, independently and factually" is the phrasing you also meet in supervisory frameworks, and it means the same here: this person must not be in a position where reporting bad news is awkward. That is another reason the reporting line is not a formality.

Delegating tasks is allowed, issuing authorisations, for instance, or bringing in a sub-officer. The responsibility stays with them.

Three things you can get right immediately

  1. Appoint a stand-in, not just a principal. The document permits sub-officers, among other things as stand-ins during absence. One name with no backup is a single point of failure in a role that is the point of contact for the NBIV. The annex also requires that the stand-in is regularly briefed on procedures and incidents, so this is not a name on paper.
  2. Put the reporting line in writing before you nominate. Not because the form asks for it, but because the requirement is about authority, and authority that is written down nowhere evaporates at the first reorganisation.
  3. Start the screening alongside the nomination. The officer needs a certificate of conduct or a security clearance at the contract's highest classification level. That is a lead time you can run in parallel with the appointment rather than after it.

And one thing not to do: combine the role with something it conflicts with. Crypto custodian is fine, the document expressly allows the same person to do both, with two forms. But an officer who is also accountable for the project's delivery date will at some point have to contradict themselves.

Where I think this ends up

This is my expectation, not a figure. As ABRO is rolled out more widely, through 2026 and 2027 at the ministries and their agencies, and possibly after that at provinces and municipalities, this role lands at companies that have never had a security organisation. Not defence suppliers with thirty years of experience, but IT service providers, builders and consultancies.

There it becomes the hardest requirement in the whole document. Not because the tasks are heavy, but because the requirement about authority asks an organisation to change something about how it is arranged. A security plan you can have written. A reporting line you cannot.

Frequently asked questions

Can an external adviser be our security officer?

No. Requirement 1.1.6 of ABRO 2026 states that the security officer is on the payroll of the company concerned. An external can coach and train that person and help draw up the security plan, and that is where we help, but the role itself is internal. That is a different thing from an interim or fractional CISO, which is not an ABRO role.

How much time does the role take?

That depends on the TBB category, the number of sites and the size of the chain, and I am not going to attach a number I cannot support. What is fixed is the frequency: the security plan, the risk analysis and the self-inspection all three have to be updated at least annually, and the registers continuously.

Can we change the role later?

Yes. On a change of function or for another reason you can submit a request for discharge using the form 'Discharge of Security Officer'. A successor goes through the same route: nomination by the highest governing body, and appointment by the NBIV after approval.

Do we also need a cyber security officer?

You may, depending on the nature and size of the contract (requirement 1.1.5). They support the security officer on the digital side: the register of digital classified information, the cyber measures, and handling cyber incidents. Ultimate responsibility stays with the security officer.

Our IT manager is willing to do it. Is that enough?

Test them against the three position conditions, not against their expertise. Do they report directly to the board, and can they take and carry out decisions without their manager's intervention? If not, the question is not whether they are suitable but whether you are prepared to change the line.

What if we have nobody who meets this?

Then that is a board decision and not a security problem: promote someone, change a reporting line, or hire. Better to establish that now than after the security plan has been written, because without an appointed officer there is nobody who may draw that plan up.

Further reading

Related articles