Date: 11/10/2026
ABDO ABRO
Implementing ABRO: where do you start, and why you don't
Your client sets the TBB category and the NBIV decides which chapters apply to you. Get ahead of that and you write your security plan twice. Four things you can already do, and the cloud boundary you cannot undo.

TL;DRYou don't begin. That is the honest answer, and it is in the requirements document itself: your client establishes, before procurement, whether there is an interest to be protected and what security level goes with it, and the NBIV establishes in advance which chapters of ABRO 2026 apply to you. Get ahead of that and have a security plan written, and you write it twice, make a cloud choice and you cannot undo it. There are four things you do in those weeks, and none of them change if the level turns out differently. |
The question you ask once it gets real
You have won a tender, or you have been named as a subcontractor on something touching national security. The word ABRO comes up. The first question is always the same: where do we start? And because nobody likes sitting still, what usually happens first is that someone goes off to write a security plan.
That is the most expensive way to begin. Not because the plan is unnecessary, it is a hard requirement, but because its content depends entirely on two things that are not settled at that moment, and neither of them is yours. This piece is about those two, and about what you do meanwhile. The previous piece covered the question before it: which regime your contract names at all.
What your client determines
One note before the quotations. ABRO 2026 is published in Dutch only; every passage quoted in this article is my own translation, and the Dutch original governs. Where a word matters I give the Dutch term as well.
ABRO 2026 is short and clear here: "Prior to a procurement process the Client establishes whether an interest to be protected is involved and what security level is required." Out of that comes a TBB category, running from 4 down to 1 with 1 the heaviest:
- TBB 4, Departmental CONFIDENTIAL. Disclosure to unauthorised parties could harm the interests of one or more ministries.
- TBB 3, State Secret CONFIDENTIAL. Damage to the interests of the State or its allies.
- TBB 2, State Secret SECRET. Serious damage.
- TBB 1, State Secret TOP SECRET. Very serious damage.
An interest to be protected does not have to be classified, incidentally. Classified information is always such an interest, but not the other way round: it can equally be systems, equipment, goods or physical sites. That is one reason companies with no defence history at all are now running into this.
To reach that judgement the government uses the national security quick scan, an instrument of the national counterterrorism coordinator for procurement and tendering. That is the contracting body's work, not yours, you will find the reverse stated online, and it is wrong. What you can do with it: know it exists, and ask what came out of it.
What the NBIV determines
Then the sentence that makes most implementation plans prematurely wrong. On which parts of the document apply to you: "Depending on the nature of the Special Contract, different chapters or parts of ABRO 2026 apply. This is established in advance by NBIV."
Not you, and not your adviser. The document has five chapters, governance and organisation, personnel, physical, cyber, cloud, and which of them are in play depends on how you come into contact with the protected interest. It distinguishes four applications:
- Access-to-site, the work takes place solely at the client's premises.
- Physical storage, physical storage and handling of the protected interest at your premises.
- Digital storage, digital storage and processing of classified information in your own environment.
- Cloud service, use of public cloud solutions.
The difference between those four is not a nuance. With access-to-site you do the work in someone else's building on someone else's systems; with digital storage the protected interest enters your network and turns that network into something that gets assessed. That is a different project, with different costs, and the difference lies not in how well you do it but in how the contract is set up.
And this is why you should not make a cloud choice in advance
The cloud chapter opens with a line that admits no exception: "Cloud solutions can only be deployed for Departmental CONFIDENTIAL (TBB 4). For information classified higher (State Secret CONFIDENTIAL up to and including State Secret TOP SECRET) cloud solutions cannot be used."
So if you do not yet know whether you land on TBB 4 or TBB 3, you do not know whether the solution you have in mind is permitted. That is not a detail you repair later; it is the difference between a SaaS service and an environment you have to build and isolate yourself.
One nuance that is rarely stated anywhere and that saves a lot: private cloud solutions do not fall under that chapter. They are treated as regular IT and assessed under chapter 4, Cyber. The line is about public cloud, not about virtualisation.
What the NBIV does not assess
A misconception I meet often, and the document clears it up itself. The NBIV investigation "focuses on the security of the operations of the Contractor concerned in the context of the Special Contract" and, explicitly: "The ABRO requirements and the NBIV Investigation do not address the quality or security of the product or service delivered during the Special Contract."
That matters for how you prepare. This is not a product assessment and not a penetration test. It is about your organisation: who may walk in, who may look on, who may decide, and whether you can evidence it. A team preparing by having its product tested is preparing for the wrong conversation.
Four things you do do meanwhile
These are the things that do not change if the level turns out higher or lower. They cost little, they drive the lead time, and all four are yours.
- Request the three facts everything hangs on. The TBB category, the classification level, and which of the four applications applies. You put that question to your client, and until you have the answer every plan is guesswork. In a subcontractor role this runs via the main contractor.
- Delimit which part of your business performs the contract. Which sites, which systems, which people. ABRO covers only that part of your operations and not the rest of the company or other contracts, so this delimitation is also the size of your investment. It is the one piece of design you can already do, and the one that saves the most.
- Find your candidate security officer. They must be an employee, have a direct reporting line to the highest governing body, and enough authority to act without going through superiors (requirement 1.1.6). They are nominated to the NBIV and only appointed after approval, so there is lead time here you can remove now. The next piece is about this, because the choice is harder than it looks.
- Map who needs screening. Anyone who can reach the protected interest usually needs a security clearance; where only TBB 4 or Departmental CONFIDENTIAL is involved a certificate of conduct can suffice. Do not forget the system administrator, and do not forget the contractor: someone hired in externally can just as well be an involved employee.
What you do not do in this phase: write policy, buy a tool, or fix an architecture. All three depend on a number you do not have yet.
And if your client does not know yet either
This is the normal situation right now, not the exception. Only a handful of organisations have switched, the police since 1 January 2026, Defence, General Affairs and Justice and Security since 1 July 2026, and the rest have no date yet, only a target quarter. The buyer handling your tender may well be doing this for the first time. "Ask your client" is then not an answer but a dead end.
One fact breaks that open, and it is in the ministry's Q&A: the NBIV investigation is requested by the client, the department, agency or police force putting out the contract, and not by you. You cannot set that investigation in motion yourself, however much you would like to. So without action from your client there is no ABRO clearance, and without a clearance you may not start on the contract.
That is not a complaint but your strongest argument, and it belongs in the conversation with procurement rather than in an email to your project manager. Concretely, in this order:
- Ask for the outcome of the national security quick scan. It was carried out before your contract went to market; if it was not carried out, that is an answer in itself.
- Ask which of the four applications your contract carries, access-to-site, physical storage, digital storage or cloud service. This is the question most often answerable, even by someone who does not have the TBB category to hand.
- Ask when the NBIV investigation will be requested, and by whom by name. Not whether, but when and by whom. That moves the conversation from a question to a schedule.
- Put your own start date next to it. If that falls before the clearance, it is not your risk but a problem in the contract's planning, and that is where it belongs on the table.
And if this runs through a main contractor rather than directly, the only thing that changes is who you put these four to. The main contractor submits the intended use of a subcontractor to the client and the NBIV for approval in advance (requirement 1.5.1), and a subcontractor may not start work until a clearance has been issued for them too. So your start date hangs on that request, and on an approval that does not come automatically.
And then it starts
Once the TBB category and the application are settled, it gets concrete. The security plan is drawn up by the security officer, approved by your highest governing body and endorsed by the NBIV (requirement 1.1.8). The NBIV may ask you to carry out a self-inspection first, using the self-inspection list, to gauge how far you already comply (requirement 1.1.10). And before you may start work, the ABRO clearance has to be in place.
Nor does it stand still after that. Where the threat picture changes or a security incident occurs, the security level can be adjusted during the term, possibly at the NBIV's direction. An implementation that assumes a fixed level for the whole contract assumes something the document itself does not promise.
Where I think this goes wrong at most companies
This is my assessment, not a figure. The mistake I expect is not that people do too little, but that they do the wrong thing first, because sitting still feels like falling behind, and because an adviser selling a phased programme naturally wants to start at phase 1.
The honest order is less satisfying. Ask first, then delimit, then sort out people, and only then build. Reverse it and you deliver a security plan for a level that turns out not to apply, in an architecture that is not permitted.
Frequently asked questions
Can we not just start on the security plan?
You can do the delimitation and the role appointments now, and that genuinely saves time. The content of the plan depends on the TBB category and on which chapters the NBIV declares applicable, and that difference is not a nuance: between TBB 4 and TBB 2 the requirements on physical security, personnel and cyber all three change.
Who carries out the national security quick scan?
The contracting government body, using an instrument from the national counterterrorism coordinator. As a supplier you do not perform it. What you can do is ask what came out of it, because that determines whether ABRO applies to your contract at all.
May we run the contract in the cloud?
Only at TBB 4, that is Departmental CONFIDENTIAL. From State Secret CONFIDENTIAL upward public cloud solutions cannot be used. Private cloud does not fall under that chapter and is assessed as regular IT under the Cyber chapter.
Does the NBIV assess our product?
No. The investigation focuses on the security of your operations as far as the special contract is concerned, and the document states in so many words that the requirements and the investigation do not address the quality or security of the product or service you deliver.
How long does such a programme take?
I do not know, and anyone claiming to know is not basing it on a public source. What I can say is where the lead time sits, and it is not in the writing: in the NBIV's appointment of the security officer, and in the security screening of your people. Those are the two you can set in motion earliest.
We are ISO 27001 certified. Can we lean on that?
Partly. According to the ministry, existing certificates or security declarations can help establish more quickly whether you meet the ABRO requirements, and at TBB 4 there is some overlap with ISO 27002 and the Dutch government baseline. But the ABRO requirements are worded more specifically, and ABRO is integral: governance, personnel and physical security as well. See also our NIS2, ISO 27001 and IEC 62443 service.
Further reading
- ABRO 2026, the requirements document itself (PDF, 91 pages, Dutch)
- Dutch government: security requirements for government contracts (ABRO)
- Ministry of the Interior: Q&As on ABRO
- Netherlands Enterprise Agency: ABRO for entrepreneurs
- CyberBusters: ABDO or ABRO, which one applies to your contract
- CyberBusters: ABRO 2026 & ABDO guidance



